Last reviewed: 2026-08-20
Cookie policy
Valyzer sets three first-party cookies and none from a third party. Two are necessary for sign-in to work and cannot be turned off without losing the ability to sign in; the third stores your analytics decision and only exists once you have seen the cookie notice.
Necessary versus analytics
Necessary cookies keep your account sign-in working: without them you cannot sign in or complete the Google or email-link flow. The analytics cookie is opt-in: it starts off, and only turns on if you press "Accept" on the notice.
What we measure, and what we do not
If you accept, we measure visits, registration entry, reading dossiers and observatories, opening sources and sharing attempts. Reading events carry a public topic, channel, allowed campaign, timestamp, random event ID and a sessionStorage ID that expires after 30 minutes. We do not send selected text, arbitrary URLs or the sign-in cookie. We do not store your plain IP in these events, use no cross-day identifier to measure return visits, and load no third-party SDK. Declining analytics does not prevent reading or sharing.
How to change your decision
Use the controls on this page to accept or reject analytics at any time. The change applies immediately in this browser. You can also clear the `valyzer_consent` cookie in your browser settings; in that case, the notice will appear again on your next visit.
| Cookie | Purpose | Category | Duration | Attributes |
|---|---|---|---|---|
__Host-valyzer_session | Keep you signed in | Necessary | 1 hour, or until you sign out | HttpOnly, Secure, SameSite=Lax |
__Host-valyzer_oauth | Complete Google sign-in or the email-link flow | Necessary | At most 10 minutes | HttpOnly, Secure, SameSite=Lax |
valyzer_consent | Remember your decision on this same policy | Preference | ≈180 days, or until you withdraw it | Secure, SameSite=Lax, readable by the browser |