Cookies

What we store on your device right now

One key, in localStorage, not a cookie: vivari-motion, which remembers whether you asked the site to reduce animation. That is it. No visitor ID, no fingerprint, no cross-site identifier. When we ship a consent banner, a second key will join it — vivari-consent — holding only the choice you make in that banner (accept, reject, or your per-category picks), so we don't ask you the same question on every visit.

Cookies vs. localStorage — same law, different drawer

A cookie and a localStorage entry are both small pieces of information a site asks your browser to hold. Privacy law (the ePrivacy rules that sit alongside GDPR) treats the act of writing to either one the same way: it requires consent, unless what's being stored is strictly necessary for something you explicitly asked the site to do. Remembering your own motion preference qualifies as strictly necessary — it exists because you set it, and it does nothing without your action. That's the whole reason this page can honestly say "no consent needed" for that one key, while still meaning it when we say a tracking cookie would need your yes first.

Vercel Web Analytics — measured, not tracked

We use Vercel Web Analytics to see which pages get read and which buttons get pressed (events like a banked early-access signup, a Stranger Test completion, or a hero button click). It sets no cookie, reads nothing already on your device, and identifies visits with an anonymized hash that rotates every day — not a persistent ID that follows you between visits. Because it never touches your device's storage, the cookie-consent rule doesn't apply to it; it only requires disclosure, which is what this page and our security page are for.

Not active yet: analytics that would ask first

We're evaluating two additional tools for later. Neither is running today, and neither will run for anyone until a consent banner asks — with a reject button exactly as easy to press as accept.

"Not active" means what it says: the scripts are not loaded, the cookies are not set, and nothing is measured under these names. If that ever changes, a consent banner will ask first — and not before.

What consent will look like when it matters

The day GA4 or Clarity go live, a banner appears with "Accept" and "Reject" as equal, real buttons — never a bright accept next to a grey link. Nothing analytics-adjacent loads before you choose, EU visitors see Google's Consent Mode default to denied until you grant it, and a "Cookie settings" link in the footer lets you change your mind at any time, for any visit, going forward.

What we do not use cookies for

No advertising or retargeting pixels, no cross-site tracking, no cookie-based fingerprinting. The early-access form you can fill out on this site is stored server-side against the email you give us — that's covered in our privacy policy, not here, because it isn't a cookie.