LMNRD, based in the Netherlands, is the controller of the personal data described here.
Contact us about anything on this page at [email protected]. We answer within a few days, and within one month for any formal data request.
| Data | Why | Lawful basis | Kept |
|---|---|---|---|
| Email address | To create and secure your account, and to send password resets | Performance of a contract | Until you delete your account |
| Password | Sign-in. Stored only as a salted hash by our authentication provider; we never see it | Performance of a contract | Until you delete your account |
| If you sign in with Google: your name, email address and profile picture link, as Google shares them | To create your account and sign you in. We never see your Google password | Performance of a contract | Until you delete your account |
| Passkeys, if you add one: the public half of the key and the date you added it | To sign you in without a password. The private half never leaves your device | Performance of a contract | Until you remove the passkey or delete your account |
| Username | So other players can find and invite you | Performance of a contract | Until you delete your account |
| Your saved games: characters, story text, maps and chat | To store and restore your campaigns across devices | Performance of a contract | Until you delete the save or your account |
| Your homebrew: spells, monsters, items, species, classes and subclasses you make | To keep them and use them in your games | Performance of a contract | Until you delete them or your account |
| Your own AI API key, if you supply one | To send your turns to Google on your behalf | Consent | Until you remove it |
| Purchase and credit records | To deliver what you paid for, and for tax records | Legal obligation | 7 years (Dutch tax law) |
| Play statistics: when you play and for how long, which AI you play on, the kind of play (solo, multiplayer, tutorial), your device type, how many turns you take, and which features you use, such as opening the map or the shop. Never anything you write. | To see how the game is doing and what to improve | Legitimate interest | 2 years, or until you delete your account |
| Visit statistics: pages viewed, country, browser and device type, counted by Cloudflare Web Analytics without cookies | To know how many people visit the site | Legitimate interest | Only as totals; we never see who you are |
| Error diagnostics | To find and fix crashes | Legitimate interest | Kept in your browser unless you send them to us |
We do not use tracking cookies or advertising identifiers, and we never sell or share statistics about you. Visits are counted by Cloudflare Web Analytics, which sets no cookies and does not identify you. Our own play statistics are used only by us, to see how the game is doing; you can object to them by emailing us. The site stores a sign-in token and your display preferences in your browser; these are necessary for the service to work and are not used to profile you.
You can also play without an account. Your quests and your API key then stay in your browser tab and are deleted when you close it; nothing about them reaches our database, and we collect no play statistics. The AI still receives your turns as described below.
This is the part most worth understanding, so we will be plain about it.
Your prompts go from your browser directly to Google. They do not pass through our servers. Google processes them under your own agreement with Google.
Your prompts pass through our servers so we can meter usage, and are then sent to Mistral AI in the European Union using our API key. After the Dungeon Master replies, a second, smaller Mistral model reads the reply to keep your character sheet, inventory and battle board in step with the story. Mistral does not use our requests to train its models, and keeps them for up to 30 days to detect abuse, then deletes them.
The background work that costs you no credits (the running summary of your quest and the story plan) also goes to Mistral, as long as turns you paid for cover it. Otherwise it goes to Google's Gemini instead, on a free tier key, and so does your turn itself if Mistral is unavailable at that moment. On its free tier Google may use what it receives to improve its products, and people at Google may review it. This is one more reason to keep real personal information out of your story. We do not store the content of your prompts on the server beyond the moment of the request; what is stored is your save file, which lives in your account because that is what a save file is.
Nothing leaves your machine. We never see it.
In every case: do not put real personal information about yourself or anyone else into your story. It is a fantasy game; treat it as public writing.
We do not sell your data, and we do not share it with anyone not listed above.
In a multiplayer game, other players in your lobby can see your username, your character, and everything you write in that game. Do not put anything in a shared game that you would not want those people to have.
Under the GDPR you may ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or object to our use of it. Email [email protected] and we will respond within one month.
You can delete individual saves in the app at any time. To delete your whole account and everything in it, go to Account and choose Delete account. It happens straight away, and a running Premium subscription is cancelled with it. Any credits left over are lost. We keep only the purchase records that Dutch tax law requires, with your name taken off them. If you cannot sign in, email us and we will do it within 30 days.
If you think we have handled your data badly you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.
This service is not intended for children under 16. We do not knowingly collect data from them. If you believe a child has given us data, contact us and we will remove it.
Data is encrypted in transit. Passwords are hashed. Your API key is stored in a table only your own account can read. No system is perfectly secure, and we will tell affected users without undue delay if a breach puts their data at risk.
If we change this policy in a way that matters, we will tell you in the app before it takes effect. The date at the top always reflects the current version.