Cookie Policy

Our cookie policy and how we use them

Last updated: 24 July 2026

Our approach to cookies

DemoMate is cookieless by default. We set no advertising, profiling, or cross-site tracking cookies, and our viewer analytics use no cookies at all. The only cookies we set are strictly necessary for a feature you have actively used.

Cookies on shared demos

These are set only after a viewer unlocks an email-gated demo. They are scoped to the demo and are strictly necessary to make gating work:

  • dm_gate_{id} — strictly necessary. An HttpOnly, Secure access token proving the gate was passed, so the viewer is not re-prompted on the next step or refresh. Expires after 24 hours.
  • dm_gate_email_{id} — strictly necessary. Stores the email the viewer submitted so the player can attribute their session. It is readable by the demo page (not HttpOnly) because the player needs to read it; it is not used for advertising. Expires after 24 hours.

Cookies in the app

When you sign in to DemoMate as a creator, we use strictly-necessary session cookies to keep you authenticated and to remember preferences such as your selected organisation and theme. These are required for the app to function and are not used for tracking.

What we do not use

No analytics cookies, no advertising or retargeting cookies, no third-party tracking pixels. Viewer measurement is handled with an in-memory session identifier that is never stored — see the Privacy Policy for how that works and how to opt out via GPC or DNT.