Child Safety & CSAE Standards

Ascended Social is intended for people who are at least 18 years old. Age is currently collected as a user representation rather than independently verified. Do not create or use an account if you are under 18. If we learn that an account belongs to a person under 18, we may restrict or remove the account and handle the information in accordance with our Minor-Safety Addendum.

We prohibit child sexual abuse or exploitation material (CSAM/CSEM), sexual or sexualised content involving a minor, grooming, solicitation of a minor, trafficking, and any content or conduct that exploits, endangers, or sexualises a child. This prohibition applies to user-created content, messages, live interactions, exports, and AI-assisted or AI-generated content. Attempts to use prompts or generated content to evade these standards are also prohibited.

We also prohibit threats, coercion, doxxing, or other conduct that places a child at risk. Reports are reviewed under the same restricted moderation workflow as other safety reports, with child-safety reports separately labelled for compliance review.

In the web or mobile app, open the report control for the relevant Flow, Element, Scroll, comment, Whisper, Soul, call, or session and choose Child safety / CSAE. The report is sent to a restricted flagged-content review queue and an audit record is created for the submission and later reviewer action. Reports require a signed in account so the queue can prevent abuse and preserve report accountability.

You can also contact the child-safety point of contact at [email protected]. Please do not email, upload, or attach suspected illegal material. Share only the minimum information needed to locate the account or content, and use the direct reporting channels available in your jurisdiction when appropriate.

• The submission is authenticated, rate-limited, deduplicated, and placed in the child-safety workflow.
• Every child-safety report goes to our staff at the highest priority for human review. Report text is never sent to AI.
• A protected alert is placed in a durable, deduplicated outbox for authorized review channels. Alert notifications contain only safe case metadata and an opaque evidence reference.
• Child-safety report descriptions are not retained in the ordinary application report record. We retain only the category, target identifiers, and limited routing metadata needed for review and accountability.
• An authorised reviewer can record notes and move the report through pending, reviewed, dismissed, or violation states.
• We may restrict content, accounts, or features when our review identifies a violation or an immediate safety risk.
• We aim to review child-safety reports within 24 hours. We do not promise a particular outcome or disclosure of the review result.

This page describes the reporting and review controls we use today. We comply with our legal obligations, including those that apply to reporting child sexual abuse material, and we work with law enforcement where appropriate. We don't use automated CSAM detection or known-image matching, and we don't claim to. A report you submit in the app goes to our staff; it isn't itself a report to the police or any hotline. If a child is in immediate danger, call 911 or your local emergency number first.

These standards work with our Acceptable Use Policy, Minor-Safety Addendum, AI & Generative Content Disclosure, Law Enforcement Guidelines, Privacy Policy, and in-product Community Guidelines.