Privacy, in plain words
This service puts a microphone on your table. Everything below is what that actually means — written to be read, not to be agreed to.
What is recorded, and when
Two different things happen, and only one of them involves listening to the room.
Questions. When somebody says the familiar's name, the words after it are sent to us, answered, and both the question and the answer are kept in that table's session log.
Table talk. Separately, there is a record table talk switch. While it is on, everything the device hears is transcribed and sent to us in chunks, whether or not anyone was talking to the familiar. This is how the timeline, the cast list, the places and the in-game calendar get written.
That switch is off by default, lives on the device rather than on the account, and has to be turned on again for each session. There is no always-on mode and no way for us to turn it on remotely.
Where the audio goes
We never receive audio. Speech is turned into text by the browser, and only text is sent to our servers. We have no recordings of anybody's voice and no way to obtain one.
That is not the same as saying the audio stays in the room. The familiar uses the browser's own speech recognition, and on most browsers that is a cloud service run by the browser's maker — Chrome sends audio to Google, Safari and every browser on an iPhone or iPad send it to Apple. Their handling of it is governed by their privacy policies, not ours. We cannot change this and we are not going to pretend otherwise; if it matters to your table, it is a reason to leave table-talk recording off.
Where the text goes
Transcribed text is sent to a large language model to be answered and summarised. Today that means Anthropic (Claude), with Google (Gemini) as a fallback when the first is unavailable. Both are used through their paid APIs, under terms that do not permit training on the content we send.
The speech that goes to them is whatever your table said while recording was on. We do not filter it, because we cannot — the point of the feature is that nobody has to decide in advance what mattered.
Voices are generated on our own machines rather than a third party's. The voices offered are a library we ship; we do not take voice samples from customers.
What is stored
Per table:
- A running memory — a few hundred words of consolidated notes, rewritten as the session goes.
- A timeline of events, one line each, with any dice rolls, rests and weather noted.
- Corrections anyone made, with the name they joined under and the time.
- A cast list and a list of places, each with a description.
- Session logs — every question asked of the familiar and every answer given.
- The campaign notes and the familiar's persona, as written by whoever wrote them.
- A search index over all of the above.
Per person:
- Account holders: an email address and a hashed password. Nothing else.
- Players who joined by invitation: the name they typed. No email, no password, no account.
We also count tokens and characters used per table per month, to know what it costs to run. That is numbers, not text.
We do not use analytics, advertising trackers, or third-party scripts of any kind. The only cookie is the one that keeps you signed in.
Who can see it
Everyone at your table can read and correct the record — that is deliberate, and it is why there is no hidden profile of anybody. Two things are narrower: the campaign notes are visible only to the DM, and the usage and billing figures only to the table's owner.
Nobody outside your table sees any of it. We do not sell it, share it, or use it to train anything.
Getting it back, and getting rid of it
A table's owner or DM can download everything that table has recorded, as a single archive, and can delete the table outright. Deleting removes the files, the database rows and the search index; it is immediate and it is not reversible.
Deleting your account deletes the tables you own, along with everything in them. If you are only a player at somebody else's table, leaving it removes your membership; the record of what happened at the table stays, because it belongs to the table rather than to you.
Telling your table
Consent is not something a DM can give on behalf of five other people. The invitation page says what recording means before anyone accepts, and the recording switch is visible on every device while it is on.
If somebody at your table does not want to be recorded, leave the switch off. Everything else — asking the familiar things, its voice, the campaign notes — works exactly the same without it.
If something is wrong
This is a small service run by one person. If you want your data out, or out of existence, or you think something here is inaccurate, say so and it will be dealt with by a human — which at this scale is faster than any form would be.