← Back to Chucks

Privacy Policy

Last updated: June 28, 2026

Chucks helps you build Dungeons & Dragons encounters. There are two ways to use it, and they collect different amounts of data:

  • As an MCP plugin, with no account. Your AI assistant calls the Chucks tools directly. We never see your conversation — only the parameters of each tool call.
  • As the Chucks web app, with an account. You sign in, bring your own LLM key, and chat with Chucks. Your conversations are stored so you can return to them.

This policy explains both. The web app collects more, so most of this page is about it.

Using Chucks as an MCP plugin (no account)

When your AI assistant calls one of the Chucks tools, the Chucks server receives the parameters of that call — things like party size, character levels, difficulty, habitats, and the monster names or encounter types being requested. Those parameters are written to server-side request logs.

In this mode, Chucks does not receive:

  • Any account, sign-in, or identity — there is none to attach.
  • Your name, email, or other personal identifiers.
  • The content of your AI conversation beyond what is explicitly passed as a tool parameter.

Using the Chucks web app (with an account)

Your account

Sign-in is handled by Auth0. We store the identifier, email address, and display name associated with your account so we can sign you in and address you.

Your provider API key (BYOK)

Chucks is bring-your-own-key: you supply an API key for your chosen provider (OpenAI, Anthropic, or Mistral) and Chucks uses it on your behalf. When you save a key, it is sent to our server once to be encrypted; only the encrypted form is kept, and it is kept in your browser’s local storage — not in our database. To run a request, your browser sends the encrypted key to our server, which decrypts it in memory just long enough to call your provider, then discards it. We never store your key on our servers, and we never use it for our own purposes — you pay your provider directly for the tokens you use.

Your conversations

Your chats with Chucks are stored so your history is there when you come back. You can delete them at any time by deleting your account (Account → Delete account), which permanently removes your stored conversations along with your account.

Diagnostic traces

To debug and improve the product, requests to the language model are traced through LangSmith. These traces are retained for up to 14 days and then deleted automatically.

Logging and retention

Request logs (Grafana Loki) and language-model traces (LangSmith) are both retained for up to 14 days, then deleted automatically. Anything we log about your use of Chucks ages out within that window.

How we use your data

We use your data only to operate and improve Chucks: debugging issues, fixing prompts and tools, and understanding aggregate usage (for example, how often a tool is called). To diagnose a problem, a team member may occasionally read a stored conversation or trace.

We do not:

  • Use your conversations to train or fine-tune models.
  • Sell, rent, or share your data for marketing or advertising.
  • Build advertising or marketing profiles of you.

Third parties we rely on

To run the web app we share the minimum necessary data with these services:

  • Auth0 — authentication and account storage.
  • LangSmith — language-model traces (14-day retention).
  • Grafana Loki — request logs (14-day retention).
  • Your chosen LLM provider (OpenAI, Anthropic, or Mistral) — receives your prompts to generate responses, under your own key and that provider’s terms.

Deleting your data

Deleting your account removes your stored conversations and account immediately. Diagnostic logs and traces are not tied to that action, but they age out on their own within 14 days.

Children's privacy

Chucks is not directed at children under 13 and does not knowingly collect personal information from them.

Changes to this policy

If this policy changes in a material way, the “Last updated” date above will change and the new version will be published on this page.

Contact

Questions about this policy or about Chucks in general can be raised on the Chucks GitHub issue tracker.