Cookie policy
Last updated: 11 May 2026
Short version: we use the minimum cookies needed to keep you signed in and process payments. No analytics trackers, no advertising pixels, no third-party scripts that follow you around the web.
What is a cookie?
A cookie is a small text file a website stores on your device. Cookies let sites remember you between visits (so you don't sign in again every page), and let them deliver features like payment forms safely.
Cookies we use
| Cookie | Set by | Purpose | Duration |
|---|---|---|---|
__session |
Clerk (auth) | Keeps you signed in while using Shield. | Session |
__client_uat |
Clerk (auth) | Helps Clerk detect when your session has changed. | Persistent (1 year) |
__stripe_mid / __stripe_sid |
Stripe | Fraud detection when you pay or update your card. | 1 year / 30 mins |
What we don't use
- No Google Analytics, Mixpanel, Amplitude or other analytics SDKs on the marketing site or the app.
- No advertising pixels (Meta Pixel, LinkedIn Insight Tag, TikTok Pixel, etc.).
- No fingerprinting scripts.
- No session replay tools.
This is a deliberate choice. We don't need behavioural surveillance to run the product, and our users handle commercially-sensitive correspondence — the less third-party JavaScript executing in their browser session, the better.
How to control cookies
All modern browsers let you control cookies. You can typically block all cookies, block third-party cookies, or clear existing cookies. Note that blocking the strictly-necessary cookies above will stop you signing in or paying — the service won't work without them.
If you're a Shield user and want to use a separate cookie-isolated browser profile for your account, that works perfectly. The product is designed to be paranoid-user-friendly.
Changes to this policy
If we ever add a new cookie (for example if we start running performance analytics on the marketing site), we'll update this page and post a notice to the dashboard.
Contact
Questions? Email privacy@shieldindex.app.