Security and privacy

Your guests' details, kept the way you would keep them.

The short version: the data lives in Canada, only your staff can see it, we never see a card number, and you can take all of it with you whenever you like.

Where the data lives

Bookings, guest records and messages are stored in a Postgres database run by Supabase in its Canadian region, in Montreal (ca-central-1). The app itself runs on Cloudflare's network, close to whoever is using it.

Two things leave Canada by design. Emails to your guests go out through Resend and texts through Twilio, both in the United States, because that is how a message reaches a phone or an inbox. They carry only what the message needs: a first name, the time, a link.

Who can see it

• Your staff, by role. Owners, managers and hosts each see what their job needs. Staff sign in with a one-time code sent to their email or phone, so there are no shared passwords at the door.
• Nobody at another restaurant. Every restaurant's data is walled off in the database itself, not just in the app. Each request is checked against the restaurant it belongs to, and we test that wall on every change we make.
• Maitrebook, only to help you. When you ask for help, Dominic can open your account for 30 minutes at a time. He has to give a reason, a red banner shows the whole time, and every change he makes is written to an audit log.

Cards

Card holds and deposits run through your own Stripe account. Guests type their card into Stripe's own form, so the number goes straight to Stripe and never touches Maitrebook's servers or yours. A held card is never charged on its own: a charge takes two separate decisions by your staff.

Consent and Canadian law

• CASL. When a guest agrees to texts, we record when, how and on which page. Every text carries STOP, and STOP is honoured at once.
• PIPEDA. You decide what is collected about your guests and why; we hold it for you and use it for nothing else. We do not sell it, share it with other restaurants, or market to your guests.
• Accessibility. We build the booking widget and this site to WCAG 2.1 AA, the standard Ontario's AODA points to, and fix anything that falls short as soon as it is reported.

Export and deletion

Export your bookings and guests to a spreadsheet from Settings at any time, on any plan, even after you cancel. If a guest asks to be forgotten, tell us and we erase their record and their messages. If you cancel, we keep your data for at least 90 days in case you come back; ask, and we delete it sooner.

Keeping it running

Errors are reported to us the moment they happen, tagged with the restaurant, and we are alerted on a run of failed texts, failed emails or server errors. Forms open to the public carry Cloudflare Turnstile to keep bots out.

Live status is at maitrebook.instatus.com.

Found a problem?

If you think you have found a security problem, email [email protected] with "security" in the subject. Dominic reads it the same day. Our privacy policy has the full detail.