Cookie Policy

What we use

• Strictly necessary:a session cookie when you sign in, and Stripe’s cookies during checkout. No consent required; the app can’t work without them.
• Local storage (not cookies):your snapshots, onboarding progress, and preferences live in your browser’s local storage — they never travel to us unless you enable sync.
• First-party analytics cookies: three cookies set by Unfollo itself, never by a third party. unfollo_vid holds a random visitor identifier, unfollo_sid holds a random session identifier that expires after 30 minutes of inactivity, and unfollo_analytics_ok holds the literal value 1 when you have opted in. None contains an email, a social username, or anything derived from your archive or your IP address.
  They exist so a completed checkout can be attributed to the visit that produced it, which a browser-storage-only identifier cannot do.

Analytics: first-party, and not anonymous

Earlier versions of this page said our analytics were “anonymous, cookieless”. Both halves of that are now wrong and this page has been corrected: analytics do set the three cookies above, and because a signed-in visit is linked to your account they are first-party pseudonymous, not anonymous.

In the EEA, the UK and Switzerland nothing is collected until you opt in. Elsewhere these disclosed first-party analytics run with a one-tap opt-out in You → Privacy Center; opting out deletes the cookies, the identifiers and the records keyed to them. Global Privacy Control and Do Not Track switch analytics off everywhere, regardless of the setting. Full detail is in the Privacy Policy.

What we don’t use

No advertising cookies, no cross-site tracking pixels, no fingerprinting, and no third-party analytics collector — not Google Analytics, Plausible, PostHog, Mixpanel or Amplitude. Nothing on this site loads a script from another company; the Content-Security-Policy forbids it.