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

• Passwordless login by email or phone (one-time codes). No stored passwords to leak.
• 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.

Sub-processors

The full list of sub-processors—payments, database, hosting, email, SMS—is maintained on the Privacy page. Changes get 30 days' notice before they go live.