Security basics
What Booked does under the hood to keep your data safe.
Booked is built on a small set of well-run services and a strict set of rules about how data moves between them.
The short version
- Sign-in with email and a password, Google, an email code, a text-message code, or a passkey. Choose a password you do not use anywhere else, and add a passkey or phone sign-in so you have another way in.
- Row-level security on every table in the database: a staff member from one shop cannot query another shop's rows, even if they compromise a client.
- Card details never touch Booked. All card entry happens inside Stripe's iframes; Booked stores only a Stripe reference and non-sensitive display fields (brand, last four, expiry).
- PII is compartmentalized. Customer contact details live in the shop-scoped tables, not in shared marketing indexes.
- IP addresses are anonymized at write for analytics use.
- HTTPS everywhere. HSTS enabled, TLS 1.2+ only, modern cipher suites.
A unique password, and a second way in
A reused password is the usual way a small-business account is taken. Choose a password you do not use on any other site. A passkey, an email code, or a linked phone number is a way back in if the password is lost.
Whoever controls the shop's email or linked phone can still reset access. Securing that mailbox is the single highest-value thing an owner can do.
What a customer never has
A booking does not require an account. It is reached through a link plus the contact details on the booking. A customer can optionally save bookings and sign in with a passkey on My bookings.
What we cannot protect you from
A device left unlocked, a staff member who should have been removed and was not, or a phone number ported away by someone impersonating you at your carrier. Remove staff the day they leave, and treat carrier account security as part of your own.
Sub-processors
The full list (payments, database, hosting, email, SMS) is on the Privacy page. Changes get 30 days' notice before they go live.