Your numbers belong to you alone.
A restaurant's financials are a trade secret. That is exactly how we treat them.
In short
Your data is encrypted in several layers. Nobody on the team has a screen in the app where they could see your numbers. Technically there is one access route for operations and system recovery, and it belongs exclusively to Václav Horníček, founder of master.restaurant. The key to your texts is kept outside the database, and every time the service tool reads your data, it is written to an audit log you can see in your account.
How it works, in plain words
Think of your numbers as the contents of a safe.
The road to the safe
When you enter a sale or an expense in the dashboard, it travels to us through a secure tunnel, the same technology your bank uses. Nobody along the way can see inside.
Where the safe stands
Your data sits in a data centre in Ireland, inside the EU and under European rules. The disks are encrypted, so even a stolen disk shows nothing but scrambled characters.
Every restaurant has its own deposit box
The database lets each account reach its own data and nothing else. No other account can get into your box, not even by mistake. The database itself enforces this rule, and automated tests check it.
Texts get a second lock
Notes and names you write yourself, such as dishes, ingredients or calendar events, are also encrypted with a separate key that is not kept in the database. Anyone who got into the box still could not read them.
Who is looking?
Nobody on the team has a screen in the app that shows your numbers. There is one technical access route for operations and repairs, and it belongs exclusively to Václav Horníček, founder of master.restaurant.
A visitors’ book you keep yourself
Every time the service tool reads your data, it is recorded in a log you can see in your account under Data access. An empty list means nobody has accessed your data through the service tool. The database refuses to edit or delete these records.
Your numbers are your trade secret. We build it so you don't have to take our word for it.
The path your numbers take
The layers, technically
Encryption in transit (TLS)
All traffic between your browser and the application, and between the application and the database, runs over HTTPS with TLS 1.2 or newer. Anyone listening in along the way sees only ciphertext.
Encrypted disks (AES-256)
The database runs on the Supabase platform, with its disks encrypted using AES-256. The backups the platform makes are encrypted the same way.
Separated accounts (row level security)
Every table holding your records carries a row level security rule in the database: each account reads and writes only its own rows. The database enforces the rule itself, not just the application, and automated tests cover it.
Text encryption in the application (AES-256-GCM)
Notes on revenue, expense and recurring entries, your own subcategory names, calendar event titles and, in plate costing, dish names, ingredients, preparation steps, allergens and the chef's notes are encrypted in the application with AES-256-GCM. Each account has its own data key, wrapped by a master key that is not kept in the database. Amounts, dates and main categories such as Payroll or Rent are not encrypted, because the database calculates your totals and food cost from them; they are protected by encryption in transit, encrypted disks and account separation.
No screen with your numbers
The master.restaurant admin has no screen and no interface that shows a member's records: revenue, expenses, notes, plate costing, inventory, calendar or break-even. We removed the former tool for signing in as a user. The admin sees only operational totals: user counts, subscription status, invoices, feedback and messages.
One technical access route, and a log you can read
Technical access for operations and system recovery belongs exclusively to Václav Horníček, founder of master.restaurant. Reading a member's data through the service tool requires a stated reason and is written to the audit log (who, when, which account and why), which you see under Data access; the database refuses to edit or delete those records. To be straight with you: the database can also be managed directly in the hosting provider's console, where encrypted texts appear only as ciphertext, and that kind of direct access is not written to your log.
Data in the EU
The database, sign-in and file storage run with Supabase in a data centre in Ireland, in the EU. The application runs on a server in the Czech Republic, and that is the only place your texts are decrypted, in memory, when you open your dashboard.
GDPR and full erasure
You have the right to access, correct, erase and port your data, and to object to its processing. Deleting your account deletes all your records, keys and access log entries. Send requests to privacy@master.restaurant.
Frequently asked questions
Who can see my numbers?
You, and anyone you give your login to. The master.restaurant team has no screen in the app that shows your data.
Is there any technical access to my data?
Yes, one, and it belongs exclusively to Václav Horníček, founder of master.restaurant. Reading through the service tool requires a reason and is written to the log you see under Data access. Directly in the database console your texts are only ciphertext, but that kind of access does not appear in your log. Automated calculations of totals, such as monthly figures for reminder emails, are not logged either.
What happens if the database leaks?
Your texts, meaning notes and names, would be ciphertext without the key, which is not kept in the database. Amounts and dates would be readable, which is why encrypted disks and account separation protect them. We would rather tell you that plainly.
Where is my data physically stored?
The database is in a data centre in Ireland, in the EU. The application runs on a server in the Czech Republic.
Can I delete everything?
Yes. Deleting your account removes all your records, keys and access log entries.
Do you share data with third parties?
We do not sell or share your data. These processors help us run the service, each in its own role only: Supabase (database, sign-in and file storage; Ireland, EU), Stripe (payments; receives your billing details, not your records), Resend (email delivery; some reminder emails contain summary figures such as your food cost percentage) and the hosting provider in the Czech Republic that runs the application.
Ready to try it?
Instant access