Your customers' details deserve better than a spreadsheet
Here is what we do to protect your business data and your customers, described plainly, including the things we have not done yet.
Your data stays yours, separately
Every record belongs to one business, and the database itself enforces that boundary (row-level security), so a bug in the app can’t quietly show one business another’s customers.
Double-booking protection in the database
Overlapping holds on the same resource are rejected by a database rule, independent of the application, so busy moments can’t corrupt your schedule.
Hardened sign-in
Passwords are stored as salted hashes. Sessions use HTTP-only cookies, can be revoked, and reset links and invitations are single-use and expire. Sign-in and public endpoints are rate limited.
Least privilege roles
Owners, managers and staff see and change only what their role allows. Removing a team member ends their access immediately.
Payments never touch our servers
Card details are entered into Stripe’s payment form. We only store payment identifiers and status, and verify Stripe’s webhook signatures.
An audit trail
Booking creation and status changes record who did what and when, so disputes have answers.
Collect less. Delete on request.
No tracking
- No cookies for the customers who book
- No analytics scripts, ad pixels or fingerprinting
- The only third-party script is Stripe, and only on the deposit payment form
Rights built into the product
- Customers can download or erase their own data from their booking link
- Owners can export or erase any customer and export the whole business
- Owners can permanently delete the account, taking its data with it
What we haven't done (yet)
Found a vulnerability?
Please email privacy@example.com with details. We will acknowledge your report, keep you updated, and fix confirmed issues promptly. Please give us reasonable time before disclosing publicly.
Built carefully, so you can focus on your customers
Try it free during early access.