Cookie Policy
Effective date: 7 July 2026 · Last updated: 7 July 2026
1. The short version
ZapInto uses no analytics and no advertising trackers. Almost everything below is strictly necessary — sign-in, security, and remembering your consent. The single non-essential cookie (zap_ref) exists so affiliates get credited, and in the EEA, UK, and Switzerland it is set only if you say yes in the banner. Declining it never limits the service.
2. Every cookie we use
| Cookie | Provider | Category | Duration | Purpose |
|---|---|---|---|---|
| __session / __client_uat | Clerk (our sign-in provider) | Strictly necessary | Session / 1 year | Keeps you signed in and protects your account against forged requests. |
| __clerk_db_jwt | Clerk | Strictly necessary | Session | Development-instance session handling (not set in production). |
| cookieyes-consent | CookieYes | Strictly necessary | 12 months | Remembers the consent choices you made in the cookie banner. |
| zap_ref | ZapInto (first-party) | Advertisement | 60 days | Remembers which affiliate link brought you here so that affiliate can be credited if you sign up. Set only after you consent in the EEA/UK/Switzerland. |
| __stripe_mid / __stripe_sid | Stripe | Strictly necessary | 1 year / 30 min | Fraud prevention during checkout. Set only on payment pages. |
We also use localStorage on your device for your theme preference (light/dark). It never leaves your browser.
3. Your consent
In the EEA, UK, and Switzerland, non-essential cookies are set only after you accept them in the banner, which offers Accept and Reject with equal prominence. You can change or withdraw your consent at any time via Cookie Settings in the footer — it reopens the same banner. Your consent choice is logged by CookieYes so we can demonstrate it, as the GDPR requires.
4. More detail
How we process personal data — including the affiliate attribution that follows the zap_ref cookie — is covered in the Privacy Policy. Questions? Contact us— pick "Privacy & data requests".