> 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/content-rules-and-reporting.md).

# Content rules & reporting

What isn't allowed on DreamDolls and how to report content.

DreamDolls is an adult platform. Adult roleplay between consenting adult characters is allowed. Some things are never allowed, in chats, images, clips, personas or profiles.

## Not allowed

* Anyone under 18, or anyone presented as a minor.
* Non-consensual scenarios.
* Real people.
* Animals in sexual content.
* Graphic violence, self-harm and drugs used to coerce someone.

Prompts and requests are checked automatically before anything is generated. If something breaks these rules you'll see a message saying it was blocked; blocked image requests aren't charged. Chats that break them can be ended.

## Report content

If you see an image, clip or chat message that breaks these rules:

{% stepper %}
{% step %}

### Open its menu

Find **Report** on the image, clip or message (on images and clips it's in the options menu).
{% endstep %}

{% step %}

### Choose a reason

**This depicts a real person**, **This depicts a minor**, **This depicts a non-consensual scenario** or **Other**, and add details if you like.
{% endstep %}

{% step %}

### We review it

Our team reviews reports, typically within 2 business days.
{% endstep %}
{% endstepper %}

To report a character or a profile, [contact support](/help/account/contact-support.md).


---

# 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/content-rules-and-reporting.md?ask=<question>&goal=<user_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.