Cookies
Gielinor Alpha uses cookies only where they are needed to keep you signed in. This notice is a product disclosure, not legal advice — have counsel review it before a public EU launch.
What we use today
The site does not set cookies in its own application code. Authentication is provided by Clerk, which sets first-party session cookies on our domain so you can stay signed in across pages. When the Google AdSense verification snippet is enabled in production, Google may also set cookies or similar storage, or use web beacons and IP addresses, on its domains — see Advertising below.
| Cookie (typical) | Provider | Purpose | Category |
|---|---|---|---|
__session, __client, __client_uat | Clerk | Sign-in session and client state | Strictly necessary |
__clerk_db_jwt | Clerk | Development / debugging JWT (local and preview only) | Strictly necessary |
Exact cookie names can vary by Clerk version and environment. They exist so protected routes (account, allocations, admin) and signed-in actions work. API calls to our backend use a Bearer token from Clerk, not a custom app cookie.
What we do not use
- First-party analytics or product-telemetry cookies
- Social media tracking embeds
- First-party
localStorageorsessionStoragefor tracking
Filter and board state lives in the URL, not in cookies. Fonts are self-hosted via Next.js, so the browser does not load Google Fonts cookies on page view.
We do use first-party localStorage for a few UI preferences — they stay on your device and are not sent to us as analytics:
ga.boardPrimer.dismissed.v1— remembers that you dismissed the first-session board primerga-desk-account— which investment desk is selected on Allocations
Advertising
Production may load Google AdSense on public content pages so Google can verify the site for Ad Manager. We do not run Auto ads or display ad units — there are no Google banners on the board. That snippet is served from Google's domains and may set cookies or use similar technologies (including web beacons and IP addresses) governed by Google's advertising policies and How Google uses information from sites that use our services. We do not use AdSense for rewarded "watch an ad for credits" flows. That opt-in path uses Google Ad Manager rewarded ads (GPT), not Offerwall.
| Cookie / storage | Provider | Purpose | Category |
|---|---|---|---|
Names vary (for example IDE, NID) | Google AdSense | Site verification (no display ads on pages) | Advertising (non-essential) |
Names vary (for example IDE, NID) | Google Ad Manager | Opt-in rewarded ad on Account (Watch ad for credits) | Advertising (non-essential) |
Third-party sites during checkout
When you buy credits, we redirect you to Stripe Checkout. Stripe may set cookies on its own domain while you complete payment. Those cookies are governed by Stripe's policies, not by cookies we set on Gielinor Alpha.
Consent
Strictly necessary authentication cookies do not require a consent banner under typical EU ePrivacy guidance. Google AdSense verification and Ad Manager rewarded ads are non-essential. We do not serve personalized display ads. For Ad Manager Watch in the EEA, UK, or Switzerland, we need a certified consent banner first. Until that is live, Account hides Watch for visitors in those regions. Daily claim still works. Verification may still load the AdSense snippet on public content pages while site review is in progress.
More detail
How we handle account, billing, and marketplace data is described in the privacy policy.