Child Safety Standards
Published standards for Happy — com.mgcstudios.makemehappy — required by Google Play's Child Safety Standards policy.
Last updated: 2026-06-29. This page is the canonical, stable reference for Happy's child-safety standards. It is not a PDF, is not editable inside the app, and is hosted at a permanent, publicly reachable URL.
1. Published standards against CSAE
Happy is a decentralized, visual social network built on the Nostr protocol. Any depiction, promotion, or normalization of child sexual abuse or exploitation (CSAE) is prohibited across every surface where user-generated content can be uploaded, viewed, distributed, or stored.
The standards below apply to images, video, captions, usernames, profile metadata, and any linked material. They cover the five areas required by Google Play's policy:
- Prohibition of CSAM. Content that is, depicts, or alludes to child sexual abuse material is not permitted. Violating content is removed and the uploader's account is suspended.
- Reporting child-safety concerns inside Happy. Users can flag child-safety concerns from the in-app report flow on any post, profile, or comment. Reports of this class are routed to a human reviewer. The in-app reporting flow is the primary channel.
- Compliance with child-safety laws. Happy complies with applicable child-safety statutes in each jurisdiction where it operates, including the obligation to forward reports of suspected child sexual abuse material to the relevant national authority (for example, NCMEC's CyberTipline in the United States, and the equivalent national body in each operating country).
- Designated point of contact. A standing contact is available to discuss Happy's CSAE prevention practices and policy compliance with regulators, hotlines, and app-store reviewers:
- Anti-grooming and minor-protection design. Happy's direct-message and comment surfaces are designed so that contact features cannot be repurposed to target minors. Any pattern that matches known grooming indicators (rapid-follow of a newly-registered account, private-message solicitation of image material, etc.) is escalated to manual review.
2. Detection and response workflow
- Detection. User in-app reports, reports to child-safety@mgcstudios.app, and any trust-and-safety partner escalations.
- Triage. A trained moderator reviews each report. Reports of suspected CSAM are escalated immediately and prioritized ahead of other safety categories.
- Action. Confirmed CSAE content is removed, the uploader is suspended, and where required by applicable law the matter is reported to the relevant national authority.
- Preservation. The minimum account and content metadata needed to support a law-enforcement request is preserved per the relevant jurisdiction's retention rules, then deleted thereafter.
3. Reporting child-safety concerns
4. Disclosure and updates
This page is the public reference of Happy's child-safety standards. Material changes (a new enforcement mechanism, a new reporting channel, a change in retention rules) are recorded at the top of the page with a dated note. Historic revisions are not removed.