Your data is yours
Export it whenever you want, in a format any spreadsheet opens.
You check it yourself: export and open the file. It does not depend on us doing it for you.
A base you can work on with confidence
Your data is yours, and the system says what it does not know instead of making it up.
How each one is checked
The home page tells you what we promise. Here is how you can verify it yourself, without taking our word.
We say what we do not know
An undeclared allergen shows as unknown, never as "does not contain".
The catalogue tells «not declared» apart from «does not contain», and that difference is checked dish by dish before publishing.
Isolation between restaurants
The database refuses to read another restaurant’s data, and that is checked on every release.
It is not a rule of the program: the database itself refuses the read, and that is verified on every deploy.
Off the network, the limit is stated
Writing an order and leaving it queued keeps working with no connection, and the screen does not call it sent until it actually leaves. What needs the server is bounded, and it is this:
- Taking payment
- Confirming a booking
- Closing the bill
- Authorising a discount
None of them can be composed without a connection, and the system says so with the reason in front of you instead of letting you press and wait.
The list of what needs the server is closed and lives in one place: the same one the system uses to refuse is the one you see above.