Privacy policy

Last updated: [DATE]. Booknatin is operated by [YOUR FULL NAME OR BUSINESS NAME], [CITY], Philippines. Contact: [YOUR EMAIL].

What Booknatin does

Booknatin lets shops take bookings online. When a customer books, Booknatin adds the booking to the shop owner's own Google Calendar and to a Google Sheet in the shop owner's own Google Drive.

Information from shop owners

• When a shop owner signs in with Google, we receive their name, email address and Google account ID.
• We store the shop's settings: shop name, link name, services, prices, staff names and working hours, opening hours, contact details and links shown on the booking page (phone, Facebook, Messenger, Google Maps), the shop's photos (logo, cover, service, staff and gallery photos), and plan, trial and payment dates.
• We store an encrypted connection key from Google so bookings can be saved while the owner is offline.
• If the owner adds team members (managers or barbers), we store each team member's email address, name, role and last sign-in time. Team members sign in with Google using only their name and email; Booknatin never asks for access to their Calendar, Drive or Gmail.
• We store the number of bookings each shop receives, without any customer details.

Information from customers who book

Customers enter their name, mobile number, and optionally their email and a note. If the shop accepts QR payments, customers may also upload a screenshot of their payment. Booknatin sends these straight to the shop owner's Google Calendar and Google Sheet to create the booking. Payment screenshots are saved to a folder in the shop owner's Google Drive. Booknatin does not store customer details or payment screenshots in its own database. Customers get a private link to cancel or reschedule; that link contains only booking reference numbers, not personal details. The shop owner controls this information in their Google account.

If a customer ticks "Remember my details on this phone", their name, mobile number and email are saved in their own phone's browser so the form fills in next time. This is never sent to Booknatin's database, and "Not you?" on the form removes it.

Shops can turn on reminder emails. The evening before an appointment, Booknatin reads that day's bookings from the shop's own Google Sheet and sends the reminder from the shop's Gmail. Booknatin only remembers the date it last sent reminders, not who received them.

How we use Google user data

• Google Calendar (calendar.events): to check when the shop is busy so customers only see free times, to add new bookings and blocked times (breaks, days off) as events, and to move or remove an event when a booking changes. When checking busy times we read only event start and end times, not titles or details.
• Google Drive (drive.file): to create one bookings spreadsheet and add each booking to it, and to save customers' payment screenshots in a "Booknatin payment proofs" folder. Booknatin can only access files it created. It cannot see any other files in the owner's Drive.
• Gmail (gmail.send, optional): to send booking confirmations, reminders, cancellations and changes from the shop owner's own Gmail to the customer, and booking alerts and a morning summary to the owner. Booknatin can only send email; it cannot read the owner's inbox.
• We do not use Google user data for advertising, we do not sell it, and we do not let people read it except as needed for security or to comply with the law.
• Booknatin's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Removing access and deleting data

• Shop owners can remove Booknatin's access at any time in their Google Account under Security → Your connections to third-party apps. Their bookings stay in their Google account.
• To delete a shop and its settings from Booknatin, email [YOUR EMAIL]. We delete it within 30 days.

Where data is processed

Booknatin runs on Cloudflare. Bookings are stored by Google in the shop owner's account.

Changes

If we change this policy, we will update the date at the top of this page.