İçeriğe geç

Trust

Trust centre

Everything a restaurant group, its IT team or its procurement asks before signing: where the data lives, who processes it, how it is protected and recovered, and what we are not certified for yet.

Operated by BookNDish

Service status

All systems working

Live checks of every component, the last 90 days of uptime and every incident with its updates.

Open the status page

Security

Encryption in transit and at rest, two-factor sign-in, role-based access, an audit log, rate limits on every public endpoint, and how to report a vulnerability.

Data processing agreement

The GDPR Article 28 terms on which we process your guests’ data. The PDF is already signed for us; countersign it and keep it with your records.

Backups and recovery

The database can be restored to any moment within the recovery window. A full copy is also taken every night to a separate storage bucket with separate credentials; seven daily and four weekly copies are kept, and the latest is restored into a scratch database and checked every month.

Point-in-time recovery window
retention period of our database plan
Recovery point objective (most data that could be lost)
available on request
Recovery time objective (longest time to restore service)
available on request

Sub-processors

No change recorded yet

The companies that run part of the platform for us, what each does, where, and how a transfer is covered. A new or replaced one is announced at least 30 days before it starts.

  • Render

    Hosting of the application

    Frankfurt, Germany (European Union) · Standard contractual clauses

  • Neon

    Hosting of the database

    London, United Kingdom · Adequacy decision

  • available on request

    Storage of menu photos, branding images and database backups

    available on request · Standard contractual clauses

  • Stripe

    Card payments, payouts to restaurants and subscription billing

    the United States and the European Union · EU-US Data Privacy Framework and standard contractual clauses

  • Konnect

    Card and wallet payments for restaurants in Tunisia

    Tunisia · Standard contractual clauses

  • available on request

    Delivery of transactional email such as confirmations, receipts and password resets

    available on request · Standard contractual clauses

  • available on request

    Delivery of order and booking updates by text message and WhatsApp

    available on request · Standard contractual clauses

  • Anthropic

    The AI features (reading menus and supplier invoices, the owner’s assistant), only when the restaurant uses them

    the United States · Standard contractual clauses

  • Sentry (Functional Software, Inc.)

    Error tracking, with personal data removed before sending

    available on request · EU-US Data Privacy Framework and standard contractual clauses

Hear about changes

Leave an address and we will email it when the list changes. We send a link to confirm first.

Where your data lives

The platform runs in Frankfurt, Germany (European Union), with the database in London, United Kingdom. Every restaurant is served from that one region today; separate regions for other markets will be listed here before they open.

Payment cards

Card data never touches our servers: guests type it on the payment provider’s own forms and readers, so our scope is the smallest one, the self-assessment questionnaire SAQ A. The payment providers are responsible for their own PCI DSS compliance.

Account security for groups

  • Two-factor sign-in for everyone, and a policy that requires it for owners, managers or everyone with billing access.
  • Single sign-on with your identity provider (OpenID Connect: Okta, Microsoft Entra ID, Google Workspace) for organisations.
  • Our support opens your account only while you allow it, and every session shows in your audit log.
  • A full export of your data, as CSV and JSON, whenever you want it.

Accessibility

We target WCAG 2.2 level AA on the guest pages, the staff screens and this site, check it with an automated scan on every change, and publish what does not conform yet.

Read the accessibility statement

Certifications

We are not certified yet: we do not hold SOC 2 or ISO/IEC 27001 today, and we will not say otherwise. We build to those controls and plan to seek SOC 2 Type II, then ISO/IEC 27001; this page will say when an audit has started and when it is done. Until then we answer security questionnaires through the contact page.