What we collect

The agent collects only what it needs to answer questions and show you analytics. This page is the plain-language version of that. For the formal terms, your agreement and our data processing addendum govern.

What the agent reads

In a channel on the allowlist, the agent reads messages so it can answer the ones that are questions about your game. It does not read anything in channels you haven’t added. A private staff channel the agent was never given stays entirely outside its view.

What it stores

To power the dashboard, the agent keeps:

• The questions asked and the answers it gave.
• A message and channel reference, so a flagged answer can be traced back.
• A player identifier from Discord, used to avoid answering one person the same thing repeatedly and to enforce rate limits.
• Topic and confidence it worked out for each question, which drive your analytics.

What it ignores

• Non-allowlisted channels. Never read, never stored.
• Direct messages. The agent works in your server, not in players’ DMs.
• Content unrelated to your game in an allowlisted channel is not what the agent is there for, and it isn’t surfaced in analytics.
• Sensitive personal data. The agent isn’t a place for it, and it doesn’t seek it out.

Your connected sources

If you connect source code or design docs, the agent reads them to ground its answers, the same way it draws on the published game. A few commitments:

• Read-only, and scoped to what you pick. You choose which repositories and workspaces to share, and the agent only reads them.
• Used only for your game. Your code and docs ground answers for your community. They are not shared with other studios and not used to train a shared or global model.
• Yours to revoke. Disconnect a source any time in the dashboard, and the agent stops reading it. See how the agent is trained.

Player identity in your views

Your analytics are about questions and topics, not about who asked. The dashboard’s aggregate views, exports, and the weekly digest never carry a player’s Discord identity. The identifier exists so the agent can behave sensibly per player and so a specific report can be traced, not so your team can profile people.

Where this is set down

The specifics of retention, processing location, and your obligations live in your agreement and data processing addendum. See processing and retention for the working summary, and player data requests for handling an individual player.