Reporting & Enforcement Policy
This policy explains current report categories, priority handling, moderation states, and the enforcement actions available in the pre-launch product.
Pre-launch legal notice
This policy reflects the current pleasedtobe product and safety design. pleasedtobe is still in pre-launch development. The final legal operator identity, legal contact information, jurisdictional provisions, and provider-specific disclosures must be reviewed and finalized by qualified counsel before public launch.
1. What can be reported
Current reporting tools support reports concerning posts, users, and profile music. Additional targets, including individual direct messages, are not yet supported by a dedicated reporting interface in the pre-launch product.
2. Report categories
- UNDERAGE CONTENT OR USER
- NON-CONSENSUAL CONTENT
- STOLEN OR LEAKED CONTENT
- HARASSMENT OR THREATS
- IMPERSONATION
- SPAM OR SCAM
- ILLEGAL CONTENT
- WRONG CONTENT LABEL
- OTHER
3. Priority and triage
The current system marks reports concerning underage content or users, non-consensual content, or illegal content as CRITICAL priority. Stolen or leaked content is marked HIGH priority. Other categories are STANDARD priority unless later changed by moderation tooling.
HIGH or CRITICAL priority changes triage and initially places the report in an escalated state. It does not automatically hide content, restrict the reported user, add a strike, or establish that a violation occurred.
4. Review states
- OPEN: submitted and awaiting review.
- ESCALATED: submitted with elevated priority.
- IN REVIEW: actively being reviewed by moderation.
- RESOLVED: review completed with a resolved outcome.
- DISMISSED: review closed without the report being upheld.
5. Possible moderation actions
Depending on the available evidence and severity, moderators may remove posts or profile music, add account strikes, restrict an account, restore a previously restricted account, update report status, or take other supported administrative action.
Moderation history may be retained to help evaluate repeated violations, safety risk, and later reports.
6. What reporters should provide
- Choose the most accurate category available.
- Describe the issue clearly and include relevant context in the report description.
- Do not file knowingly false reports, coordinated abusive reports, or reports intended primarily to harass another user.
- Do not use the reporting system as a substitute for emergency services when someone faces immediate physical danger.
7. No automatic finding from a report
A report is an allegation or safety signal, not proof. pleasedtobe may consider the reported content, account history, contextual information, technical records, and other relevant evidence before acting.
8. Appeals and reconsideration
The current pre-launch product does not provide a dedicated automated appeals workflow. Moderation decisions may be revisited administratively, but a formal appeal process, response times, and contact channel must be finalized before public launch.
9. Emergency and legal matters
If you believe someone is in immediate danger, contact appropriate emergency services or local authorities. pleasedtobe's in-product reporting system is not an emergency-response service.
Processes for lawful government requests, preservation requests, copyright notices, and formal legal notices must be finalized with counsel before public launch.