← Back to Chucks

Terms & Conditions

Last updated: June 28, 2026

These terms cover the Chucks web app — the version where you sign in and chat with Chucks to build Dungeons & Dragons encounters. By creating an account you agree to them. We've kept them short and plain so you know what you're getting into.

Bring your own key

Chucks is bring-your-own-key. You supply your own API key for a supported provider (OpenAI, Anthropic, or Mistral), and Chucks uses it on your behalf to generate encounters.

  • You pay for your own tokens. Usage is billed to you by your provider, directly — not by us.
  • We never use your key for our own purposes. It is used only to fulfill your requests. See the Privacy Policy for how your key is stored and handled.
  • Your provider's terms also apply. You are responsible for your provider account, its costs, and complying with that provider's terms of service.

Your data

The Privacy Policy is the full account of what we collect and how we use it. In short:

  • Your conversations are stored so your history is there when you come back. You can delete them at any time by deleting your account.
  • Requests to the language model are traced for debugging and product improvement, and those traces are deleted within 14 days.
  • We do not use your conversations to train models, and we never sell your data or use it for marketing.

Acceptable use

Use Chucks for its intended purpose. Don't abuse the service, attempt to disrupt it, or use it to break the law or your provider's terms.

No warranty

Chucks is provided “as is.” It generates content with the help of language models, which can be wrong, unbalanced, or unexpected — always apply your own judgment as the game master. Dungeons & Dragons is a trademark of its respective owner; Chucks is an independent tool and is not affiliated with or endorsed by them.

Changes to these terms

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

Contact

Questions can be raised on the Chucks GitHub issue tracker.