Privacy Policy
Last updated: 2026-08-31 · Version: 1.1
We use strictly necessary storage for the service and, where required by law, we request consent for analytics/measurement and advertising personalization. In the EEA/UK we apply Google Consent Mode v2 signals and minimize reliance on third‑party cookies by using server‑to‑server (S2S) measurement where possible.
Categories
- Strictly necessary — authentication/session, security, user settings.
- Measurement/analytics — advertising attribution (e.g., RedTrack, Google Ads) and aggregated performance.
- Personalization/advertising — personalized ads where consent is granted (EEA/UK).
What we store
| Name | Provider | Purpose | Type | Expiry |
|---|
| session_id / auth token |
First‑party (our site / Supabase) |
Authenticate user and keep you signed in |
HTTP cookie / local storage |
Session / up to 12h |
| gclid / wbraid / gbraid |
First‑party URL parameter (Google Ads) |
Attribution of ad clicks; passed server‑side for measurement |
URL parameter / first‑party storage (if needed) |
Short‑lived (attribution window) |
| rt_click_id (if used) |
First‑party (RedTrack script) |
Cookieless/S2S attribution where applicable |
Local storage / session storage |
Up to 12 months (config‑dependent) |
Exact names/expiries may vary based on deployment. We aim to use cookieless/S2S modes wherever feasible.
Consent Mode (EEA/UK)
Before consent, we set Consent Mode signals to denied for ad_user_data and ad_personalization. After consent, we update signals to reflect your choice. You can change your choice anytime via the button below.
Manage cookies / Change consent
How to control cookies
- Use the "Manage cookies" button above (opens our consent manager where available).
- Configure your browser to block or delete cookies (this may affect functionality).
Who receives your data
We share personal data only with service providers acting on our behalf. We do not sell personal data. The categories of recipients are:
- Hosting and infrastructure — servers that run the site and the game.
- Database and authentication — storing your account and your game history.
- AI model providers — the text you write to the Guide during a game is sent to AI providers so the Guide can reply. It is not used for advertising and is not sold.
- Payment providers — card and payment details are collected and processed by the payment provider, not stored by us.
- Analytics and advertising — measurement and attribution, as described above.
- Error monitoring and email delivery — technical error reports and transactional email.
Leela Online plugin for ChatGPT
We publish a Leela Online plugin that runs inside ChatGPT. It is separate from any account on this site.
- What it processes — the messages you write while shaping your question, and the result of your single die roll.
- Session identifier — we generate a random technical identifier so that the turns of one game belong together. It is not linked to any account and contains no personal information.
- Retention — the session exists in server memory only and is discarded within 2 hours. Plugin games are not written to our database and no account is created for you.
- No AI provider in the plugin — the plugin's replies come from a fixed script on our server; it does not send your messages to any AI model provider.
- Abuse protection — your IP address is processed briefly to rate-limit requests and in standard web-server logs.
- Recipients — the conversation happens inside ChatGPT, so OpenAI, as the operator of ChatGPT, processes it under its own privacy policy.
- If you follow the link to continue on this site, the rest of this policy applies from that point.
Questions about this policy or about your data: contact us.