Draft — pending approval
Child safety standards
These proposed standards apply to Cursor Style Chat (style.cursor.chat) and its web chat at cursor.style. They are pending owner approval. They do not introduce an age gate or age-based behavior.
[OWNER: Approve these standards, identify the legal operator and set the effective date.]
Prohibited conduct
Child sexual abuse and exploitation (CSAE) are prohibited. This includes child sexual abuse material (CSAM), grooming, sexual solicitation of a minor, sextortion, trafficking, and promoting, facilitating or linking to that conduct. The prohibition covers messages, profiles, groups and uploads, including content generated or manipulated with AI. Do not request, create, upload or distribute this material.
Reporting and blocking
On the web, use Report on a message or profile/user and Block on a user. The server has report and block handling; reports can be reviewed in moderation tools. For the v2 app, use the message/user menu's Report and Block actions. [VERIFY: Check exact labels, coverage and accessibility in the final app; these actions are planned for v2 and are not proven for every shipped version.]
You can also report a concern to [email protected]. Include the account/message identifiers, location in the service and a brief description. Do not download or forward suspected CSAM or attach it to an email. For immediate danger, contact local emergency services.
Moderation and enforcement
The code includes text/image moderation integrations, user reports, staff review tools, message removal and account bans. Automated moderation can miss content or make mistakes. [VERIFY: Confirm deployed moderation coverage, staffing, escalation, appeal process and response times; the code does not prove continuous review or detection of every CSAM item.]
Proposed enforcement includes removing prohibited content and restricting or banning responsible accounts, with escalation of urgent child-safety concerns to the designated lead. [OWNER: Approve enforcement responsibilities and the urgent response procedure.]
Handling suspected CSAM and reporting to authorities
Proposed procedure: authorized staff assess reports promptly; remove or disable access to confirmed CSAM; preserve only necessary evidence securely when lawful; restrict access to authorized personnel; and report confirmed cases to NCMEC or the relevant regional authority as applicable. Staff should avoid unnecessary copying or redistribution of suspected material.
[VERIFY: Confirm applicable legal reporting/preservation duties, the NCMEC or regional reporting channel, secure evidence handling and deletion periods. No implemented NCMEC reporting workflow was verified in this codebase; this is an approval-dependent procedure.]
[OWNER: Assign trained responders, approve the CSAM escalation/reporting workflow and record how reports to NCMEC or the relevant authority will be made.]
Named child-safety contact
[OWNER: Name the child-safety lead, their role and monitored child-safety email; confirm authority to act and receive Google Play notifications.]
Until a dedicated contact is approved, the existing general support address is [email protected]; it is not yet verified as a staffed child-safety channel. [VERIFY: Confirm monitoring, coverage and the Play Console child-safety contact declaration.]
These sections address the subjects in Google Play's Child Safety Standards guidance. Publishing a draft does not certify compliance. See the privacy policy and account deletion information.
