Security and data

• Per-restaurant data isolation

  Every database query runs with a specific restaurant’s rights; PostgreSQL row-level security policies prevent seeing anyone else’s data even with a direct query. This is checked by automated tests.

• A restricted app role

  The server connects to the database with a role that has no superuser rights and cannot bypass policies; permissions are granted table by table.

• Roles and zones

  Owner, manager, staff. Staff see only their own stock zones (bar, kitchen, floor) — also a database rule.

• Login and passwords

  Login is via Supabase Auth: Provido does not store passwords. The session lives in a protected cookie (httpOnly, SameSite=strict).

• Activity log

  Orders, price changes, stock corrections and payments are recorded with author and time.

• Code does the money

  Amounts, quantities and dates follow tested rules. A language model does not write prices or quantities in e-mails to suppliers.

Personal data is processed under the privacy policy. To export or delete your data, write to us. Privacy