Cookies and local storage
Last updated: 5 October 2026
Everything Quiet Guard writes to your device, in full. No advertising tracker, no cross-site tracking, and audience measurement without any identifier, described below.
01 What this page covers
Article 82 of the French Data Protection Act does not only cover cookies: it covers any reading from or writing to your terminal. Your browser's local storage and session storage are included, so they are listed here alongside the cookies.
02 What we write to your device
- Session cookie: keeps you signed in to the dashboard. Expires after two hours of inactivity.
- XSRF-TOKEN cookie: protects your actions against request forgery. Expires with the session.
- locale cookie, one year: remembers the language of the page you open, so the bare address serves you the same one next time. Written on entering a language tree, not on every page, and it holds nothing but the language code.
- quiet-theme local storage: remembers the light or dark theme you picked on the site. Kept until you clear it.
- theme local storage: the same preference inside the dashboard, written by the interface itself. Kept until you clear it.
- _x_isOpen, _x_isOpenDesktop and _x_collapsedGroups local storage: whether the dashboard sidebar is open and which of its groups you folded away. Written by the interface, kept until you clear it.
- monitor.enc.key session storage: when you unlock in the browser, holds the key derived from your passphrase for the lifetime of the tab. That key is never sent to us and disappears when the tab closes.
03 Audience measurement
The public pages of the site measure their visits from our server, with Quiet Metrics, a service we run ourselves. No script is loaded in your browser. The measurement writes two cookies at most, on the public pages only; the processing is described in the privacy policy, https://quietguard.dev/en/privacy.
- Cookie qm_visit, ten sliding minutes: says that a visit is already under way in this browser, so that a change of network during the visit, from mobile data to wifi for instance, does not count you twice. Its value is 1, the same for everyone: it does not identify you, and it expires on its own as soon as you stop browsing.
- Cookie qm_ignore, five years: set only if you ask for it, by opening a page of the site with ?qm_ignore=1 at the end of its address, for example https://quietguard.dev/en?qm_ignore=1. It keeps your refusal to be measured; ?qm_ignore=0 removes it. Its value is 1, it is never sent to the measurement service, and qm_visit is no longer set for you while it is there.
04 Why there is no consent banner
Everything above is either strictly necessary to the service you asked for, a preference you explicitly chose, or audience measurement that meets the conditions for exemption. All fall under the exemptions of article 82 III, as set out in CNIL deliberation 2020-091 of 17 September 2020. Your consent is not required, so we have no banner to put in your way.
The audience measurement meets the conditions the CNIL sets: a purpose limited to visits to our site alone, no matching with other processing or across sites, no transfer to a third party, aggregated statistics, a ten-minute cookie where the limit is thirteen months, data kept twenty-five months at most, and a simple way to object, described above.
The qm_ignore cookie, for its part, keeps a refusal: the CNIL guidelines expressly exempt trackers that record the choice a person expressed, since making that refusal depend on consent would defeat its purpose.
05 Third-party resources
The public pages of this site load nothing from outside, with two exceptions: the contact form and the registration page load Cloudflare's anti-robot check, which receives your IP address, TLS fingerprint and user agent. Cloudflare states these are used only to tell a browser from a bot, and our integration sets no cookie. No other page contacts a third party.
The dashboard loads nothing from outside either: its typefaces are your system's own. Payment and subscription management take place on Stripe's pages, to which you are redirected and which are governed by Stripe's own policy.
06 Managing these
Your browser can block or clear cookies and local storage. Blocking the strictly necessary ones prevents signing in.
Questions: privacy@quietsystems.dev.