Skip to content
Restro

Security and data

Your restaurant’s data stays yours, and stays separate

What we do to protect your account, your staff and your guests — and how to reach us if you find something we missed.

The audit log in the dashboard

How your data is protected

Every restaurant in its own lane

Every table that holds restaurant data is protected by row-level security in the database, so a request on behalf of one restaurant cannot read another’s, even if application code were wrong.

  • Row-level security on tenant data
  • Payment gateway credentials encrypted at rest
  • Theme scripts run in a cross-origin sandbox
Diagram of tenant isolation

Who can do what

Roles are built from individual permissions, so a cashier can open the till without seeing last month’s revenue. Every sensitive action is written to an audit log with who, what and when.

  • Roles from individual permissions
  • Audit log of sensitive actions
  • Sign-in sessions you can review and revoke
Roles and permissions screen

Your data, on request

Anyone with an account can download a copy of their personal data, manage marketing consent, and erase their account from their profile. Erasure removes the identity while keeping the records tax law requires.

  • Self-service data export
  • Consent you can change
  • Account erasure
Privacy controls in the profile

In practice

  • Encryption in transit

    Every page and API call over HTTPS.

  • Two-factor sign-in

    Time-based codes for owner and staff accounts.

  • Tenant isolation

    Row-level security on every restaurant table.

  • Audit log

    Who did what, and when.

  • Data export

    A copy of your personal data as a file.

  • Erasure

    Remove your identity from the platform.

Responsible disclosure and questions

Put the whole thing on one system

Start on the free plan and see it with your own menu — the offline till included. Nothing to cancel if it is not for you.

  • No card needed
  • Arabic and English, built in
  • Sells offline on every plan