Multi-tenant isolation
Each shop’s bookings, customers, and branding stay scoped to that shop. Marketplace listing is opt-in.
Security at Booknexo
Booknexo stores appointment and customer data for many businesses on one platform. Security design starts with tenant isolation, least-privilege access, and encrypted transport.
Authentication & roles
Owners, managers, staff, and customers get different dashboard portals. Private routes are noindexed and login-gated.
Encrypted in transit
Public sites and APIs are served over HTTPS. Secrets such as provider API keys are stored server-side.
Infrastructure
Application data is hosted on modern cloud infrastructure (Supabase/Postgres backend) with service-role access limited to trusted server paths.
Payments
When online payments are enabled, card data is handled by Stripe. Booknexo does not store raw card numbers. Connect onboarding keeps payouts under the shop’s Stripe account.
Your responsibilities
- Keep staff accounts accurate and remove leavers promptly
- Collect marketing/SMS consent required in your jurisdiction
- Use strong passwords and protect dashboard access
- Review connected email/SMS provider credentials regularly
Security FAQ
Is Booknexo secure for customer booking data?
Booknexo isolates each shop’s data in a multi-tenant architecture, serves traffic over HTTPS, and restricts dashboard access by authenticated role. Shop owners remain responsible for how they handle client consent in their industry.
Who can see another shop’s customers?
Shops are isolated. Staff and owners only access their own shop context. Platform admins have separate elevated roles for support operations.
How do I report a security issue?
Email hello@booknexo.com with details. Do not publicly disclose exploit details before we can respond.