This page summarises the technical and organisational measures ("TOMs") required by Art. 32 GDPR, and referenced as Annex II of our Data Processing Agreement.
All traffic to and from Startling menu is encrypted with TLS. HTTP requests are redirected to HTTPS, and we use HTTP Strict Transport Security to tell browsers to remember that.
Startling menu is a multi-tenant platform: every venue's menus, orders, and staff accounts are isolated from every other venue's at the database query level, not just in the application UI. This isolation is enforced centrally, so it applies automatically to every new feature rather than depending on each developer remembering to filter by venue.
Staff access is role-based and scoped to a specific venue: an account can be an Owner, Manager, Waiter, or Kitchen user, each with different permissions, and access to one venue's dashboard does not grant access to another's. Passwords must be at least 12 characters with a mix of character types, and accounts lock out temporarily after repeated failed sign-in attempts.
We set standard security headers (including a Content Security Policy, anti-clickjacking protection, and strict referrer policy) on every response, and we don't load any third-party scripts, fonts, or trackers on any page that collects personal data — see our Sub-processors page for the short, complete list of what we do use.
TLS private keys and origin certificates are never committed to source control.
We run an automated process that anonymises or deletes personal data once the retention periods described in our Privacy Policy have elapsed, rather than keeping it indefinitely by default.
Venues can request an export of their own data, or its erasure, at any time — see our data request form.
If we become aware of a security incident affecting personal data, we will notify affected venues without undue delay, so they can meet their own 72-hour notification obligation to their supervisory authority.
Security and reliability work is ongoing — this page describes today's measures, not a finished state, and we'll update it as our infrastructure matures.
Other documents