> ## Documentation Index > Fetch the complete documentation index at: https://docs.reactor.inc/llms.txt > Use this file to discover all available pages before exploring further. # Content Moderation > How Reactor moderates the content you submit, and what happens when a session is flagged Reactor takes the safety of its platform seriously, which means we moderate certain requests. The content you submit to a model is screened against our content policy, and a session that violates it is terminated. *** ## What gets evaluated Moderation evaluates every element of your request. Both the text you prompt with and any reference images you upload are screened, so a request may be flagged for either a text or an image violation. *** ## What we moderate We moderate content that is sexual, violent, hateful, or otherwise unlawful. This is a high-level summary, not an exhaustive list. For the full policy on what is and is not permitted, see our [Acceptable Use Policy](https://www.reactor.inc/legal/acceptable-use). *** ## What happens when content is flagged When submitted content violates the policy the session is terminated. A terminated session behaves like any other ended session: the connection closes, the GPU is released, and your SDK observes the session leaving the `ready` state. See the [connection lifecycle](/concepts/sessions#connection-lifecycle) for how to handle a session ending in your application. *** ## Billing Moderation does not change how you are billed. You pay [per session-second](/resources/billing#when-billing-starts-and-stops) from the moment a session reaches `ready` until it is terminated, so a session ended by moderation simply stops the meter at termination. The moderation check itself carries no separate charge. *** ## Next steps The connection lifecycle, including how a session ends. How sessions are metered and how to minimize cost.