Privacy
Updated on November 6, 2026.
Without an account, Grimory keeps your tables and your characters on this device, not on a server. This page says what leaves it, when and why, and, for those who join the Cloud table, a closed beta with an account, what stays on our server. It covers the app (app.grimory.com.br and, in the beta, beta.grimory.com.br) and the site (grimory.com.br).
What stays on your device
There is no account on a server. The email you sign in with, your profile, your familiar, your tables, your characters and their portraits, sessions, rolls, cast and homebrew stay in this browser's storage (localStorage). We do not see them. Only part of them leaves, when you use the AI (see below).
Your preferences (theme, language, text size, animations and shortcuts), what you last opened in the Compendium and your drafts of sheets, level-ups and prep notes stay there too. Who signed in to each tab and the concept you write for the familiar stay only until you close the tab (sessionStorage).
Every key starts with “grimory”. Grimory's code sets no cookies and uses no IndexedDB, and nothing syncs: another browser starts empty. If the browser blocks storage, everything stays only in the tab's memory.
Cloudflare, which serves the app and the site, may set a technical security cookie (such as __cf_bm) to tell people from bots.
To erase it all, clear the site's data in your browser's settings. To keep it first, download a copy in Your account, under Storage: the file stays with you.
When you use the AI
The AI only comes in when you ask: in Help me create, when you ask for a suggestion in I'll build it, and when you ask a rule in the Compendium. Unless you ask, nothing goes to the AI or to Cloudflare's check.
The first time you use the AI in a tab, Cloudflare checks with Turnstile that a person is asking. Your browser loads its check (challenges.cloudflare.com), which receives signals such as your IP address and your kind of browser, and may store in the browser what it needs for that. It almost always passes unseen; sometimes it asks for a click.
Our server confirms the result with Cloudflare, sending your IP address along, and gives the tab a pass with a random session number, which lives only in the tab's memory. The check comes back when the pass expires (it lasts an hour), when you change networks or when the pass spends its share of the day.
Then each request goes to our server, which runs at Cloudflare, and it passes the request to Anthropic, the company behind the Claude models, which writes the answer. Besides Grimory's instructions, it receives only what the task needs:
- Help me create: the concept you wrote, your answers to the familiar's questions, the table's rules, the language and, when there are any, the characters already at the table (name, class and level). When you ask to change the proposal, the request, the proposed sheet and the character's name and story go too.
- A suggestion in I'll build it: the step, the sheet being built, the table's rules, the language and, when there is one, the request you picked among those the familiar offers.
- Ask a rule: your question, the rules edition and the language.
Your email, your profile's name and the portraits do not go. Anthropic gets the request from our server, not from your device, so it does not see your IP address. Even so, do not write personal data in a request: the familiar does not need it.
The server notes each call in codes and numbers: the route, the model, the tokens in and out, the day's totals and, when something fails, the error's code. It does not note your text, the answer or your address. The exception is rare: when Anthropic refuses a request, its error message goes into the log and may quote part of the request, up to 300 characters. These logs stay in Cloudflare's Workers Logs for 3 days, the limit of the free plan Grimory is on, and are then erased.
What Anthropic does with a request, including how long it keeps it, follows its Commercial Terms and its API data policy (links below).
Your IP address and the daily limit
Every AI call costs money. So there is a ceiling for each day, a share of it for each address and another for each pass, so that no one alone spends everyone's day. An address counts as the whole IPv4 address or, on IPv6, its /48 block; a pass, by its session number.
The server does not keep the address. It keeps a code made from it and the date with a secret key (HMAC-SHA256): without the key, the code cannot be turned back into the address, and the same address gets another code each day. It is a pseudonymous code, and only our server has the key. Each day's counter, with these codes and the session numbers, is erased three days after it opens.
The pass carries a code of the same block, made with the same key, so it only works from where it was asked for.
To stop abuse, Cloudflare's rate limiter counts, each minute, the requests of each address (on IPv6, the /64 block) and of each pass, and how many passes each address gets (on IPv6, the /48 block). For that it uses the address itself, not the code.
The art and the site itself
The app and the site are served by Cloudflare. As with any site, opening a page sends Cloudflare your IP address, your kind of browser and the page asked for.
The illustrations (classes, species, schools of magic, monsters, items and the example characters' portraits) come from arte.grimory.com.br, Grimory's storage at Cloudflare (R2). Each image asked for carries your IP address and your kind of browser, and says which art the screen opened and which site the request came from, but not the page.
The fonts and the code come from Grimory itself. We use no analytics, ads, social media pixels or third-party fonts: the pages' security rule (CSP) only lets the browser talk to Grimory, to arte.grimory.com.br and, in the app, to Cloudflare's check.
The site grimory.com.br stores nothing in your browser. Its familiar demo is a script that runs in your browser, with no AI.
In the Cloud table (beta)
The Cloud table is the closed beta you sign in to with an account, at beta.grimory.com.br: only the emails we invite get in, of people aged 18 or older. There, your tables and your characters stay on our server, so the table plays together, each person on their own device. So, in the beta, what the first part says about accounts, cookies and syncing does not hold: there is an account on the server, a session cookie, and the tables are the same on every device you sign in on. Your preferences and drafts stay in the browser, as said there.
To sign in, you write your email and confirm you are 18 or older. Before a code is sent, Cloudflare checks with Turnstile that whoever asks is a person, as with the AI, and our server checks the result, sending your IP address along. If the email is on the beta's list, it gets a 6-digit code, valid for 10 minutes and 5 tries, and on this browser only. If it is not, nothing is sent, but the email is kept just the same for 10 minutes, with a code nobody gets, so the answer never tells who was invited. The server keeps only a fingerprint of each code, made with a secret key (HMAC), never the code.
Cloudflare sends the email (Email Service). On the free plan, it only sends email to addresses confirmed in Grimory's account: once invited, you get a link from it to confirm yours. It notes each email sent (who it went to, the subject and whether it arrived) and keeps those notes for 31 days. The code is not in the subject, and the email's text is not kept: message previews are turned off.
The code is tied to this browser by a cookie, __Host-grimory-code, which lasts the same 10 minutes. Once you sign in, the browser keeps a session cookie, __Host-grimory-session, which lasts 30 days and, when you use the app past half of them, lasts 30 days again. Both are strictly necessary: each is a random number that the page's code cannot read and that goes only to Grimory, over HTTPS. The server keeps only a digest of each (SHA-256), noting neither where from nor which device; the session's, with when it began and when it expires. Sign out of this account ends this device's session at once, and Sign out of every device ends them all. Both ask the browser to clear the portraits it kept, which it keeps for a day at most.
On the server we keep:
- The account: your email, in the clear, because it is what you sign in with; your profile (name, roles and familiar); when it was made and when you said you are 18 or older.
- The beta's invitation: your email, on the list of those who may sign in.
- The tables you sit at, with everything the table keeps: the sessions and the diary, the rolls, the combats, the game master's prep and cast, the homebrew and the characters seated there. Beside them, the directory: who sits at each table, in which role, and its invite code.
- Your characters away from any table and the rolls made away from one.
- The portraits you send, up to 50, kept apart.
- The open sessions, each by its cookie's digest.
- For 10 minutes, the code waiting: your email, the code's fingerprint and the digest of the cookie of the browser that asked for it.
- For a day, the limits' counts: the codes asked for per network (30 an hour), per email and network (5 an hour) and per email (12 a day), the codes to delete the account, the table codes tried, the name changes and the connections opened per account. The email and the network go in as a fingerprint made with a secret key (HMAC), never in the clear. Before them, Cloudflare's limiter counts, each minute, each network's sign-in requests, by the same fingerprint. It also counts, each minute, the calls each account makes to the server, by its identification number, never the email.
Whoever shares a table with you sees your profile's name, which you choose at the welcome and may be a nickname, and what the table shows: the sheets of the characters seated there, with their portraits, the diary and the rolls. The prep and the cast stay with the game master alone; a private roll, with the game master and whoever rolled it. Whoever has a table's code sees, before joining, its name, description, edition, the game master's name and how many people sit there. Nobody at the table sees your email, and a portrait opens only for whoever sent it and for whoever shares a table with them.
While the app is open, it keeps connections (WebSocket) with the server, one of yours and one for each table. They only say which list changed (rolls, combat, diary…), never the content, and nothing you cannot read; the app then reads again what changed. Each connection opens again after an hour, so the server checks the session again.
In Your account, Take to the cloud sends the server, once per account, the copy the app downloads, without the old copies and without the quarantine's text. The file goes whole and may hold the profiles of other people who signed in on this device, with their emails: the server reads the file and keeps only what goes. The tables you run go, with the diary, the prep, the cast, the homebrew, the combats and the newest 200 rolls, and so do your characters; the example table, the profiles and other people's characters stay out. The other members of those tables go as seats, with the name they had on the device or, if you choose, as Player 1, Player 2 and so on. Either way, their diary notes and their rolls at the table go as they are, and what they wrote may name people. Of the file, only a digest (SHA-256) stays, so the same copy never comes in twice, and the copy on the device stays there.
This data stays at Cloudflare, in the United States: the accounts' directory in a D1 database and each table and each person in a Durable Object, both restricted to the United States.
The account's server notes only an error's kind, when something fails, without what you wrote, your email or your address. Those logs stay in Cloudflare's Workers Logs for 3 days.
When you delete your cloud account
In Your account, Delete the account asks for a new code, sent to your email, valid for 10 minutes and 3 tries. Then it signs out every device of yours and deletes at once, on our server: the account, your email, the sessions, the code waiting, the counts of your codes and the beta's invitation (coming back takes a new one); your characters, your rolls and your portraits; the tables you run, for everyone, after giving back to their owners the characters others seated there; and, at the tables you play at, your seat, your characters, your rolls and your diary notes.
At the tables you played at, what stays is the rolls someone else made for your characters, no longer tied to them but with their label, which may name the character. In the combats and the game master's prep, what your characters did there stays (the Initiative, the rolls, the log), tied only to an identification number, without the name. What other people wrote in the diary and in their notes stays with them.
Your email leaves Cloudflare's list of confirmed addresses by hand, within 7 days. Cloudflare's backups keep the earlier state for a while and then go away by themselves: the D1 database's for up to 30 days (7 on the free plan Grimory is on) and each Durable Object's for up to 30 days. The notes of the emails sent stay with Cloudflare for their 31 days.
Why we process this data
We follow Brazil's General Data Protection Law (LGPD, Law 13,709/2018) and process the least we can. Sending your request to the AI is the service you asked for (art. 7, V). Cloudflare's check, the per-address limit and the server's logs serve the legitimate interest of keeping the AI up and its cost under control, without keeping what you wrote (art. 7, IX).
In the Cloud table, keeping your account, your tables and your characters and sending the code to your email is the service you ask for by signing in (art. 7, V). Cloudflare's check, the sign-in and usage limits and the account server's logs serve the legitimate interest of keeping the sign-in safe and the service up (art. 7, IX). The names, notes and rolls of other people that a game master takes along with their table serve the legitimate interest of keeping the table as it was (art. 7, IX).
Anthropic and Cloudflare also process this data outside Brazil, such as in the United States. That transfer follows art. 33 of the LGPD: the request to the AI and the Cloud table's data, as needed for the service you asked for (item IX), and the rest, under the data protection guarantees of their contracts (item II).
Children and teenagers use Grimory with a parent or guardian's guidance (art. 14). The Cloud table, which keeps the email of whoever signs in, is for people aged 18 or older only.
We do not sell data and do not use it for ads.
Your rights
Under the LGPD, you can ask what we hold about you, ask us to correct or erase it and object to what we do on legitimate interest. Without an account, almost everything is on your device, and you are the one in control. What goes to the AI carries neither your profile's name nor your email, and the address's code goes away by itself within three days.
In the Cloud table, you delete the account in Your account. To get a copy of what it keeps or to correct something, write to the contact below. Someone taken along, with no account, as a seat at another person's table may also ask there for their name to go.
You can also complain to Brazil's National Data Protection Authority (ANPD).
The policies of those who receive data
Contact
Grimory is kept by Atto: Ranielli Montagna Desenvolvimento de Software Ltda. (trading as RM Software), CNPJ 67.919.685/0001-45, based in Paraí, RS, Brazil, which answers for this data. For questions and requests about your data, write to:
When this page changes, the date at the top changes with it.