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.
| 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
- Analytics or product-telemetry cookies
- Advertising or retargeting pixels
- 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.
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. We do not show a cookie wall for the current stack. If we later add analytics, advertising SDKs, or other non-essential cookies, we will update this page and obtain consent before those scripts run.
More detail
How we handle account, billing, and marketplace data is described in the privacy policy.