Our stance on your players’ data.
What happens at your table is your players’ story. Here’s exactly what we write up, what we never analyze, and why that line is built into the architecture, not left to a setting.
"The cavern opened up around them, vast and silent. Far below, water moved in the dark, and Vael raised the lantern to the edge of the drop." "Oh, hang on, pizza’s here, let me grab the door."
"Nice. So how’s work been treating you?"
"Ugh, busy. My boss is being a real—"
"Okay, I’m back, sorry about that. Where were we?" "Back in the cavern, a low sound begins to echo from the darkness ahead of you."
What we write up, and what we never analyze.
We record what your table declares and what happens in the fiction. We never profile, score, or analyze the people at the table.
What we never touch
- Who talked the most, or how engaged each player was.
- Sentiment, participation scores, or behavioral profiles of your players.
- Anything that turns the people at your table into metrics.
What we keep
- The fiction: what happened in the story, in the world, to the characters.
- Decisions and canon events the table establishes together.
- Safety-tool invocations your table openly declares: X-cards, lines, and veils.
It’s the architecture, not a setting.
This isn’t a switch you have to trust us to leave off. Player data never enters the memory layer in the first place. Whatever fails the promotion gate never becomes notes or canon. We also retain your session recording as the archive media source.
Made for safety-focused, professional GMs.
Safety-focused
We honor the safety culture your table builds: X-cards, lines, and veils.
Discord-based
Captured natively from your voice channel, no upload step.
Professional
Made for GMs who get paid to run the table, across many campaigns.
Their story to tell, not data to mine.
That’s one of the boundaries we build Dice Party on.
Back to the homepage