Security
A plain account of how DineTide protects your data. We describe what the system does; we do not claim certifications we do not hold.
Your data stays yours
Every restaurant apart
Each organization's data is separated in the database and in every request. Staff of one restaurant can never read another's.
People see only their part
Roles decide what each person can see and do, per outlet. A waiter does not see the books; a cook does not see the payroll.
DineTide staff need your approval
Our own staff cannot look into your data unless you approve a request, for a set time, read-only, with a notice shown to your team and every look recorded in your audit trail.
Signing in and keeping a record
Passwords and second factor
Passwords are stored only as strong one-way hashes. An authenticator app can be required, and is required for DineTide staff.
A record that cannot be edited
Payments, refunds, discounts, approvals and settings changes are written to an audit trail that nobody, including us, can change afterwards.
Approvals for risky actions
Large refunds, write-offs and similar steps can need a second person, with a fresh sign-in.
Running it safely
Backups you can restore
Backups are checked, and restoring them is rehearsed, not assumed.
Limits and watching
Sign-in and public forms are rate limited; unusual activity raises alerts.
Checked before every release
Releases pass automated tests for access control, injection and secrets, and a scan of the software we depend on.
Read our privacy policy and compliance statement, or ask us a question.
