> For the complete documentation index, see [llms.txt](https://dreamdolls.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dreamdolls.gitbook.io/help/account/refunds.md). # Refunds Our refund policy for tokens and bundles, and what to do if a payment went wrong. ## Tokens Token packs are one-time purchases. Tokens are **non-refundable**, including any unused balance, except where a refund is required by law. There's no subscription, so there's nothing to cancel. The full policy is in the [Refund & Cancellation section of our Terms](https://dreamdolls.ai/terms#refund). ## Automatic refunds When something you paid for fails, you get the tokens back automatically: * A failed image in chat or in the Studio. * A failed or timed-out video clip. * A failed persona image. Voice calls only charge for the time you're actually connected, and the first 15 seconds are free. ## Bundles Unlocked a bundle by mistake? [Contact support](/help/account/contact-support.md). Bundle refunds are reviewed by our team. ## Payment problems If you were charged but didn't get your tokens, or you see a charge you don't recognize, [contact support](/help/account/contact-support.md) with the email on your account and the date of the payment. Billing complaints are usually resolved within 7 business days. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://dreamdolls.gitbook.io/help/account/refunds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.