Security & Trust
Your restaurant’s data stays your restaurant’s data.
DineStack is designed around tenant isolation, role-based access, device identity, secure sessions and durable synchronization, so one restaurant’s operation stays separate from another — and the shift keeps going when something fails.
How DineStack protects your operation
- Tenant isolation. Every request is scoped to the restaurant of the person or device making it. One restaurant cannot read or change another restaurant’s orders, staff, menu, devices or settings — a guessed identifier from somewhere else is simply not found.
- Role-based access. Owners, managers, staff and drivers each get the actions their role needs and nothing more. A cashier rings up orders; changing roles, pay rates, tax or devices stays with the people responsible for them.
- Device identity. A register joins your restaurant with a one-time setup code that expires in fifteen minutes and works for one device. Each device has its own credential, stored in the tablet’s secure hardware, and can be switched off from the owner console.
- Secure sign-in. Passwords are stored only as salted hashes, sign-in attempts are rate-limited, and owners verify their email address before a register can be enrolled. Two-factor sign-in with an authenticator app, with one-time recovery codes, is available to every console user — and sensitive actions ask for it again.
- Encrypted connections. Every connection to DineStack is HTTPS, and browsers are told to keep it that way. The owner console cannot be embedded in another site, and session cookies are HttpOnly and expire on their own.
- Audit history. Orders, payments and time punches are recorded as a history that is added to, never rewritten: a correction is a new entry that names who made it and why. Sign-ins and changes to sign-in methods are recorded too.
- Offline data protection. When the connection drops, the register keeps the shift moving and keeps what happened on the device. When it returns, everything is sent once — not twice, and not lost.
- Card data stays out. Card numbers never touch DineStack’s servers. When card payments are switched on, the card reader talks to the payment processor directly and DineStack receives only the result.
What we do not claim
DineStack is early. It has not been through an independent penetration test or a compliance audit, and this page does not imply that it has. If your restaurant needs something specific — a security questionnaire, how data is retained, where it is hosted — email info@dinestack.app and a person who works on the product will answer it plainly.