CHILD SAFETY STANDARDS / CSAE — POPA (EN)
1) Purpose & Scope
This document describes Popa’s externally published standards and safety practices to prevent and respond to CSAE/CSAM on our platform. It applies to all user activity on Popa, including content shared via:
- Video posts and media content
- Comments, replies, and other user interactions
- Profiles, usernames, bios, and user-generated text
- Any other features that enable user-generated content or communication
2) Definitions (High-level)
For the purposes of these standards:
- CSAE refers to content or behavior that sexually exploits or endangers a child, including grooming, coercion, or sexualization of minors.
- CSAM refers to any visual or textual material that depicts or promotes sexual abuse or exploitation of children, including attempts to share or distribute such material.
Note: Exact legal definitions can vary by jurisdiction. We follow the strictest reasonable interpretation in enforcing safety standards.
3) Prohibited Content & Behavior
Popa prohibits (non-exhaustive list):
- Any CSAM, or any attempt to create, share, store, distribute, or link to CSAM
- Any sexual content involving minors, or content that sexualizes minors (real, fictional, or AI-generated)
- Grooming: attempts to befriend, manipulate, or coerce minors for sexual purposes
- Sexual extortion (sextortion), coercion, threats, or blackmail involving minors
- Solicitation or facilitation of sexual contact with minors
- Sharing personal information of minors with exploitative intent
- Any content that encourages, normalizes, or assists child exploitation
4) Safety by Design (Prevention Measures)
We use a combination of policy enforcement, product controls, and operational processes to reduce risk:
- Community rules & enforcement: We remove violating content and take action against accounts involved in CSAE/CSAM.
- User reporting tools: In-app reporting is available to report content and users.
- Review workflow: Reports are triaged and reviewed; high-risk child safety reports are prioritized.
- Account actions: We may warn, restrict, suspend, or permanently ban accounts based on severity and evidence.
- Cooperation with lawful requests: We may preserve information and cooperate with competent authorities when required.
5) How to Report Safety Concerns (In-App & External)
5.1 In-app reporting
If you encounter suspicious content or behavior involving a minor, please report it using Popa’s in-app reporting tools. Typical report entry points include:
- Video / Post: open the content menu (often
•••) → Report - Comment: long-press or open comment options → Report
When reporting, choose the most relevant reason (e.g., Child Safety, Sexual content involving minors, or similar), and add details if you can (what happened, where it happened, and why you believe it involves a minor).
5.2 Email reporting (alternative)
If you cannot access in-app reporting, contact our Child Safety Point of Contact:
venft.contact@gmail.com.
Please include subject line [POPA CSAE] and provide:
- Username(s) or profile link(s) involved
- Content link(s) / screenshot(s) if available
- Date/time and description of the issue
6) How Popa Responds to CSAE/CSAM Reports
We handle CSAE/CSAM reports with urgency and care. Depending on the case, we may:
- Triage and prioritize child safety reports for fast review
- Remove or restrict content that violates these standards
- Take account action (restriction, suspension, permanent ban)
- Preserve relevant data as appropriate for investigations or legal compliance
- Escalate to relevant authorities/child protection organizations when required by law or when there is a credible risk of harm
7) Child Safety Point of Contact
Google Play and authorized entities may contact our designated point of contact regarding potential CSAE content found on our platform:
- Email: venft.contact@gmail.com
- Website: popa.venft.vn
This representative is responsible for responding to child safety escalations, coordinating enforcement actions, and supporting investigation requests as required by law.
8) Transparency & Updates
We may update these standards to reflect policy changes, new safety practices, or legal requirements. The “Last updated” date at the top of this page will be revised accordingly.
This document is provided for compliance and transparency purposes and does not replace legal advice.