Cookie Policy
Which cookies Modus sets, what each one is for, and how to change your mind. Short, because there are not many.
Last updated: 26 August 2026
1. What cookies are
A cookie is a small file a site stores on your device so it can recognise your browser on the next request. Related technologies — local storage, session storage — do the same job with different plumbing, and this policy covers all of them. The distinction that matters is not the technology but the purpose: some are what make a signed-in site work at all, and some are there to tell us how the product is being used.
2. Cookies we set regardless
These are the ones without which the Service cannot function. They are set when you use the thing they support, they carry no advertising identifier, and they are not shared with anyone for their own purposes. Under UK and EU rules these do not require consent — but they should still be listed, so here they are.
| Name | Set by | Purpose | Lifetime |
|---|---|---|---|
__session | Clerk | Keeps you signed in. Without it every page would ask for your password again. | Session / up to 7 days |
__client_uat | Clerk | Tells the page whether a session exists before it loads, so a signed-in visitor is not shown a sign-in screen first. | Up to 1 year |
modus-cookie-consent | Modus | Remembers the choice you made on the cookie banner. Storing it is the only way not to ask again. | Until you clear it |
modus-eod-session | Modus | Only on a venue's end-of-day form: proves the passcode was entered on this device. Set when you unlock the form, not before. | Up to 12 hours |
modus-dismissed-* | Modus | Remembers which in-app notices you have closed, so a dismissed banner stays dismissed. Local storage, never sent to us. | Until you clear it |
We also use Sentry to record errors. As we have configured it, Sentry stores nothing on your device — no cookie, no local storage, no session recording. It reports what broke, on which page, so we can fix it.
3. Cookies we set only if you agree
PostHog tells us which parts of Modus are used and where people get stuck — which screens are opened, which flows are abandoned. It is how a feature earns its place. It does not run, and sets nothing on your device, unless you choose Accept on the cookie banner. If you choose Reject, PostHog is loaded but permanently switched off: it holds no identifier and sends nothing.
| Name | Set by | Purpose | Lifetime |
|---|---|---|---|
ph_*_posthog | PostHog | A random identifier that links one visit to the next, so 'ten screens opened' can be told apart from 'ten people opened one screen'. | Up to 1 year |
PostHog is served through our own domain (/ingest) rather than theirs. That is to stop ad blockers dropping the events — not to disguise them, which is why this page names the cookie.
4. What we don't do
We set no advertising cookies. We run no third-party tracking pixels, no social widgets, and no cross-site advertising identifiers. We do not sell or share personal data for advertising, and there is nothing on this site that builds a profile of you for anyone else's purposes.
The booking widget a restaurant embeds on its own website is an iframe served from our domain. It sets the same cookies described above and nothing extra, and it cannot read anything belonging to the site hosting it.
5. Changing your mind
Withdrawing is the same one click as agreeing — that is the point of the button below. Choosing Reject afterwards also clears the analytics identifier already stored, rather than merely stopping new events.
Your browser can also block or delete cookies for any site. Blocking the strictly necessary ones will sign you out and keep you out; that is a consequence of how sessions work rather than a choice we have made.
For everything else we do with personal data, see the Privacy Policy.