In short
- Restaurant websites set no cookies, except a session cookie when the diner signs in to their account. They use the browser's storage only for what the order needs.
- The dashboard uses a single cookie, the session cookie, which is needed to stay signed in.
- We do not use advertising or analytics cookies. Visits may be measured with Cloudflare Web Analytics, which does not use cookies or identify people.
- We serve the fonts ourselves, without requests to third parties.
In the dashboard
| Cookie | What for | How long |
|---|---|---|
| eats_session | Keeping you signed in. It is HttpOnly (the page's scripts cannot read it) and is needed to use the dashboard | 30 days |
The browser's local storage also keeps the dashboard language and whether you want to hear a sound with each new order.
The delivery zone editor loads the map tiles from OpenFreeMap from the staff's browser.
On restaurant websites
Each restaurant's website sets a cookie only if the diner signs in to their account: eats_customer, a session cookie needed to keep them signed in (it lasts 90 days, no third party reads it and it is removed when they sign out). The website also keeps these items in the browser's storage, only on that device:
| What it keeps | What for |
|---|---|
| The cart for each website | So the order is not lost when changing pages |
| The chosen service (delivery or pickup), the location and the address | Keeping the choice while browsing |
| The name, phone and email from the last order | Filling in the next order on that same device |
| An anonymous diner id | So the phones at the same table share the tab |
| The payment method chosen at a table | Remembering it during the visit |
All of this is needed for the order the diner places. It is not sent to third parties or used to track them or show them ads.
Visits may be measured with Cloudflare Web Analytics, without cookies and without identifying anyone.
Kitchen screens and handhelds
Kitchen screens and handhelds keep in the browser's storage:
| What it keeps | What for |
|---|---|
| The device token | Keeping the paired screen or handheld signed in |
| The staff session | Knowing which staff member unlocked the device |
| The language | Showing the device in the chosen language |
| Light or dark theme and compact view | Remembering how you prefer to see the screen |
| A queue of actions | Keeping actions taken offline until they can be sent |
Error reports
The dashboard sends error reports to Sentry, set up not to collect request contents, cookies or user details.
Restaurant websites load no tracking or error scripts. A few lines send errors from our own scripts to our server, without personal data, and the server passes them on to Sentry.
Your control
Clearing the site data in the browser deletes all of these items. On a kitchen screen or handheld, that means pairing the device again.
When you sign out of the dashboard, the session ends and is no longer valid.
None of these items track people or build profiles: they are not marketing or analytics cookies.