Glowbee — Child Safety Standards

Last updated: September 2, 2026

Zero-tolerance policy: Glowbee strictly prohibits any content or behavior involving child sexual abuse and exploitation (CSAE). This includes grooming, sextortion, child trafficking, and any sexualization of minors or child sexual abuse material (CSAM). We act immediately on violations and report to the relevant authorities and law enforcement.

Safety by design

• A parent-owned closed circle: child accounts exist only when created by a parent; friendships activate only after explicit in-app parent approval. A stranger cannot message a child — this is enforced on the server itself, not only in the UI.
• No strangers: no public search, no friend suggestions, no public feed — adding requires a private code, under the parent's oversight (the parent sees, removes, and blocks any of the child's friends).
• On-device safety scanning: children's outgoing media is scanned on the device itself before sending; suspicious content is blocked.
• Disappearing, restricted content: media is viewed then disappears; children cannot save it.

Prevention, detection & removal

We prevent, detect, and remove abuse material via: on-device scanning before sending, the parent-approved circle model, parental controls, and human review of reports. On discovery of any child sexual abuse material (CSAM) we remove it immediately and preserve the necessary evidence.

Text-filter languages: written-profanity screening uses lists we write and maintain ourselves: an Arabic list (Modern Standard and mainly Gulf dialect) and a Latin-script list built around English. The remaining interface languages — Turkish and Japanese among them — have no dedicated list, and are only covered where they overlap with the Latin one. Even within Arabic, dialects differ greatly — a word that is ordinary in one country can be an insult in another and the reverse — so coverage is inherently uneven across dialects. The screening is automated, probabilistic and not free from error, and is not a substitute for parental supervision.

Limits of that scanning, stated plainly: automated scanning covers photos and video on the sender's own device before sending. Audio clips (the in-app audio library and friend-to-friend sharing) are not scanned automatically at all — we have no model for audio. Their protection rests on two things: the other party is a parent-approved friend, and a child's audio sharing works only with their parent's explicit permission, which the parent can withdraw at any time. Reporting and blocking are available on any clip.

In-app reporting

• A "Report abuse 🚩" action is on every friend, content item, and chat — reports reach our review queue immediately.
• A "Block permanently ⛔" action cuts all contact and prevents re-adding.
• Parents can block or remove any of their child's friends from the dashboard.

How we handle reports

• We review abuse reports and act within a reasonable time (we commit to a 24-hour target): removing content, restricting or terminating accounts.
• On suspicion of child sexual abuse material (CSAM), we report to law enforcement and the National Center for Missing & Exploited Children (NCMEC) in accordance with applicable law.
• We preserve reported content as evidence for a set period (90 days for ordinary reports, up to 365 days for suspected CSAM), accessible only to our safety team, then delete it.

Child-safety point of contact

Child-safety officer: Yousef Alhelfy. For reports, child-safety inquiries, or to discuss our CSAM-prevention practices: glowbeeco@gmail.com.