Processing & retention

This is the working summary of how long the agent keeps data and where questions are processed. The binding details are in your agreement and data processing addendum; if anything here and there differ, those govern.

How long data is kept

By default, the agent keeps the questions and analytics that power your dashboard for a rolling window, and older records age out on a schedule we agree with you. The window is long enough to see trends across patches and seasons, and short enough that nothing sits around without a reason.

If your studio needs a shorter or longer retention window to match your own policy, we can set that for your community. Ask on Slack or at support@atcampfire.xyz.

Processing

When a player asks a question, the message is processed to work out the answer, and the question and answer are stored for your analytics. Processing happens on our infrastructure and our model providers under contract. The details of who processes what, and where, are set out in the data processing addendum.

Any source code and design docs you connect are read to ground answers, not to train a shared model, and they stay under your control: disconnect a source and the agent stops reading it. See your connected sources.

Clearing data yourself

You don’t have to offboard to clear stored data.

• Clear a channel’s history. Removing a channel from the allowlist stops new collection there; ask us to purge its past records if you want them gone too.
• Clear a date range. If you want a stretch of stored questions deleted, tell us the range.
• A single player. Handled on player data requests.
• A connected source. Disconnect a repository or workspace in the dashboard, and the agent stops reading it. See how the agent is trained.

Deletion on offboarding

When you offboard, your community’s stored questions and analytics are deleted on the schedule in your agreement. If you want an export first, pull it from exports or ask us to prepare a full one.

Security

Data in transit and at rest is protected with standard encryption, and access on our side is limited to the people who run the service. For a security review, a copy of our current documentation, or a DPA, contact us and we’ll get it to the right person on our team.