- Legal documents
- Cookies
Documents
Cookies and local storage
This is what Quiet Social writes to your device. No advertising trackers, no tracking from one site to another, and audience measurement without any identifying cookie, described below.
Contents
What is written to your device
Here is the list, public site and application alike, apart from the audience measurement described below. The last three rows concern only the application, not the public site:
| Name | Type | Role | Duration | Attributes |
|---|---|---|---|---|
| quiet-theme | Local storage | Remembers whether you chose the light or dark theme on the public site. Written only if you use the toggle. | Until you erase it yourself | — |
| quiet-social-session | Cookie | Links your pages together and keeps you signed in. Set from the first page: it carries the protection of the site's forms, including the contact form. | 120 minutes of inactivity | HttpOnly, Secure, SameSite=Lax |
| XSRF-TOKEN | Cookie | Protects your forms against cross-site request forgery. Set from the first page. | 120 minutes | Secure, SameSite=Lax |
| remember_web_… | Cookie | Recognises you after the session has ended. Written only if you tick "Remember me" when signing in. | 400 days, or until you sign out | HttpOnly, Secure, SameSite=Lax |
| theme | Local storage | Remembers the theme of the application interface, which is separate from the one on the public site. | Until you erase it yourself | — |
| _x_isOpen, _x_isOpenDesktop, _x_collapsedGroups | Local storage | Remember whether the application sidebar is open and which groups you have collapsed. | Until you erase it yourself | — |
All of those in this table are set by this site itself. The last column gives each cookie's attributes: "HttpOnly" prevents any script from reading it; "XSRF-TOKEN" is not, on purpose, because the page has to read it back to send it with your forms. "Secure" lets it travel only over an encrypted connection. "SameSite=Lax" keeps it from being sent with a request coming from another site.
Display preferences are not cookies: they stay in your browser and are never sent to the server.
Quiet Guard receives the application's error reports from our server, and Spirion SAS (service-smtp.fr) delivers its emails from that same server: neither writes anything to your device or loads any script on this site.
Audience measurement
The public pages of the site are measured from our server with Quiet Metrics, a service we publish ourselves. No script is loaded in your browser. Measurement writes at most two cookies: qm_visit, on the measured public pages, and qm_ignore, only if you ask for it.
| Name | Type | Role | Duration | Attributes |
|---|---|---|---|---|
| qm_visit | Cookie | Signals that a visit is under way, so you are not counted twice if you change networks. Its value is "1" for everyone. | 10 sliding minutes | Secure, SameSite=Lax |
| qm_ignore | Cookie | Keeps your refusal to be measured. Set only if you open a public page of the site with ?qm_ignore=1; ?qm_ignore=0 removes it. While it is there, qm_visit is no longer set. | 5 years | Secure, SameSite=Lax |
Neither contains an identifier. To stop being measured in this browser: refuse audience measurement. To change your mind: accept measurement again. The processing is described in the privacy policy.
Third-party services
Apart from payment (see below), two pages, and only two, load a third-party resource: the contact form and account creation. They load Turnstile, the anti-bot check service of Cloudflare, Inc. (101 Townsend St., San Francisco, United States).
Cloudflare then receives your IP address, the fingerprint of your encrypted connection and your user agent, in order to tell a person from a program. This happens on those two pages, and nowhere else on the site. Cloudflare's widget may also write to your browser storage for its own operation; we do not read what it writes there.
We use it because a decoy field is not enough to stop bots. Turnstile works with no advertising tracking cookie and no puzzle to solve; Cloudflare remains a third party established outside the Union, whose role is described in the privacy policy.
Paying for a subscription will happen on a Stripe page, outside this site: Stripe sets its own cookies there, under its own responsibility. On this site, a single page, the payment confirmation page (3-D Secure), behind sign-in, loads a third-party resource: js.stripe.com. It opens only when the bank requires that confirmation; Stripe then sets on this site two fraud-prevention cookies, __stripe_mid (one year) and __stripe_sid (30 minutes), necessary for the security of the payment you asked for. As long as payment is not open, no payment is offered.
Why there is no banner
No banner is shown to you because none of these items requires one.
We consider the session cookies strictly necessary: they carry sign-in and form protection, which exempts them from consent under article 82 of the French Data Protection Act (loi Informatique et Libertés). The "Remember me" cookie is set only if you ask for it. Display preferences are set on your initiative or by the interface you use. The anti-bot check, confined to those two pages, is strictly necessary to prevent automated submissions and account creations; it serves neither audience measurement nor advertising.
We consider that audience measurement meets the exemption conditions set by the CNIL (deliberation no. 2020-091 of 17 September 2020): purpose limited to the traffic of this site alone, aggregate statistics, no transmission to a third party, a ten-minute cookie, data kept twenty-five months at most, and a way to object, described above. The qm_ignore cookie records a refusal: the CNIL guidelines exempt trackers that keep a person's choice. Its 5-year duration is the one Quiet Metrics sets, so that a refusal once expressed need not be repeated.
Social networks
No share button, no pixel, no iframe and no social network script is embedded in this site. Reading these pages exposes you to no tracker from Meta, LinkedIn, Pinterest or Bluesky.
Publishing is different: the content you send then goes to the network you chose, and what happens there is governed by its own terms and its own cookies, on its own site. We have no control over that.
Erasing or refusing
Your browser lets you erase this site's cookies and local storage at any time, and block them in advance.
The consequences are predictable: erasing the theme preference returns you to your system theme; blocking the session cookie stops you staying signed in, and therefore using the service.