Player data requests

Now and then a player will ask what the agent knows about them, or ask you to delete it. This page is how to handle that. Because the agent runs in your community, these requests come to your team first, and we help you fulfill them.

What a player can ask for

A player interacting with the agent may ask to:

• See the questions tied to their Discord identifier.
• Delete those records.

The agent stores very little per player: their questions, and an identifier so it can behave sensibly toward them. See what we collect.

How to fulfill a request

When a player asks, gather their Discord user ID (or enough to identify them) and send the request to us on Slack or at support@atcampfire.xyz. Tell us whether it’s an access or a deletion request. We action it against your community’s data and confirm back to you, so you can close the loop with the player.

Deletion is permanent. Once a player’s records are removed, they’re gone from your analytics too. That’s expected, and it’s the right outcome for a deletion request.

Deletion and your analytics

Removing one player’s questions has a negligible effect on your aggregate views, since analytics are about topics and counts, not individuals. You won’t see a player vanish from a chart, because they were never a line on it.

Your obligations

You know your players and your jurisdiction better than we do. You decide when a request is valid and communicate with the player; we’re the processor that carries out the deletion or export on your community’s data. The division of responsibility is set out in the data processing addendum. If you need a copy, ask us.