OpenWorld Child Safety Standards
Our standards against child sexual abuse and exploitation (CSAE)
App: OpenWorld · Developer: OdobGames
com.odobgames.openworld
Last updated: 16 July 2026
OpenWorld, developed by OdobGames, is an adults-only social app. This page sets out our standards against child sexual abuse and exploitation (CSAE), how to report it to us, what we do when we receive a report, and who to contact. It applies to every part of the app: the feed, stories, reels, direct messages, group chats and random chat.
These standards form part of our Terms of Service. Our Privacy Policy explains what we keep and for how long.
1. Zero tolerance — the one rule with no exceptions
Child sexual abuse and exploitation is absolutely prohibited on OpenWorld. There is no exception, no context, no "it was a joke", and no second chance. This is the most serious rule we have.
Accounts involved in CSAE are permanently banned, the evidence is preserved, and confirmed child sexual abuse material (CSAM) is reported to the National Center for Missing & Exploited Children (NCMEC) and to the relevant authorities.
Specifically, you may not use OpenWorld to:
- Create, upload, send, request, share or link to child sexual abuse material (CSAM) — any sexual depiction of a person under 18, real, edited, drawn or AI-generated.
- Sexualise a minor in any way, including in text, in a nickname, in a profile, in a caption or in a chat message.
- Groom, solicit, or attempt to make sexual contact with a minor, or try to move such a conversation to another platform.
- Sextort anyone, or threaten to publish intimate images of anyone.
- Traffic, advertise or facilitate the sexual exploitation of a child, including offering, requesting or directing others to such material.
- Post an account, link, hashtag or handle whose purpose is to distribute CSAE material, on OpenWorld or anywhere else.
- Impersonate a minor, or present yourself as a minor for sexual purposes.
This applies to content about a minor regardless of who posted it, and regardless of whether the person depicted consented. A minor cannot consent.
2. OpenWorld is an 18+ app — children may not use it
OpenWorld is built for adults and is not directed to children. You must be 18 or older to create an account. We do not knowingly allow anyone under 18 to register or to remain registered.
At registration you must give a date of birth — which is fixed and cannot be changed afterwards — and the app runs a face check on your phone on a live selfie. That image is never uploaded and never seen by anyone (see the Privacy Policy, section 2).
We are honest about the limits of this. A self-declared date of birth and an on-device face check are not identity verification and not certified age verification. Both can be wrong, and a determined person can defeat both. They raise the barrier; they do not make it impossible for a minor to get in. That is exactly why the reporting channel in section 3 matters, and why we act on reports rather than assuming the gate held.
If we learn that a user is under 18, we delete the account — whether we find out from a report, from moderation, or from the user themselves. You do not need evidence to tell us; a suspicion is enough to report.
3. How to report CSAE to us
Please report it. Reports are the main way we find this content — see section 7 for a frank account of why.
Inside the app
Every account on OpenWorld can be reported from the app, without leaving it. Open the profile, post, reel, story or chat, use Report, and pick a reason from the list.
The report dialog gives you a fixed list of reasons to choose from, and one of them is "Child safety / possible minor". Choose that reason for anything involving a child — it sends the report straight to the top of our moderation queue, ahead of every other kind of report. You can add detail in the text box below if you want to, but it is optional; choosing the child safety reason is enough for us to prioritise it.
Block is next to Report. Blocking hides that person from you and stops them ever being matched with you in random chat again. Blocking is not reporting — blocking protects you, but only a report reaches us. If it involves a child, do both.
By email — and always, for anything urgent
Report CSAE directly to 13odob27@gmail.com. This reaches our child safety point of contact (section 8) and is the fastest route to a human. Use it if the app's report button does not cover what you need to say, if you cannot access the account, or if a child is in immediate danger.
Include the @username of the account, roughly when it happened, and where in the app (random chat, DM, feed, reel, story, group). Content on OpenWorld expires quickly by design — chat messages after 24 hours, photos sent in chat after 10 minutes — so report it as soon as you can. The account and our moderation records outlive the content, so a report is still worth making after the content is gone.
Please do not download, save, screenshot or forward suspected CSAM to prove it to us. In most countries possessing or transmitting it is a crime, even when you mean to help, and doing so can put you at legal risk. Tell us where it is — the account, the time, the place in the app. That is enough for us to act.
If a child is in immediate danger, contact your local police first. We are a small developer and we are not an emergency service. You can also report directly to NCMEC at report.cybertip.org — you do not need our permission, and you should not wait for us.
4. What we do when we receive a report
- We review it ourselves. A human at OdobGames reads every CSAE report. Reports mentioning a child are prioritised over all other moderation work.
- We preserve the evidence record before we remove anything. A permanent moderation case is recorded first, with the account details, timestamps, the reported text and its surrounding context, and the material's identifiers. See section 5 — this order matters and it is not optional.
- We remove the content and permanently ban the account. Bans for CSAE are permanent and are not appealable in the ordinary way.
- We block the device used, so the same phone cannot immediately register a new account.
- We report confirmed CSAM to NCMEC, and to law enforcement where the law requires it or where a child appears to be at risk (section 5).
- We keep the record. Moderation records for serious abuse are retained after the account is deleted, as safety and legal evidence. They are not on an automatic expiry timer — see the Privacy Policy, section 5. Deleting your account does not erase them, and does not end a report already made.
5. Reporting confirmed CSAM to NCMEC
We have a process in place to report confirmed CSAM to the National Center for Missing & Exploited Children (NCMEC), and to the relevant authority in our region. When we confirm CSAM on OpenWorld:
- a complete evidence record is preserved permanently, before anything is removed — the account's identity and identifiers, timestamps, the reported text and surrounding context, and the material's file identifiers and references. We do not simply delete and move on: the record is what a prosecution needs, and it survives account deletion;
- the material itself is then removed from our media hosting immediately, so it is never stored or redistributed from our systems. It remains traceable by NCMEC and law enforcement through the preserved identifiers and the hosting provider's own records;
- a report is filed with NCMEC's CyberTipline at report.cybertip.org, including the account identifiers, timestamps and material references we hold;
- we cooperate with law enforcement and with NCMEC on any follow-up, including lawful requests for the preserved records;
- we report to local authorities in our own jurisdiction where the law requires it, in addition to NCMEC, and we follow the child-protection reporting law that applies to us.
Why NCMEC, and why preserve the record. NCMEC operates the global clearing house that routes these reports to the right police force in the right country, which a single small developer cannot do alone. And a report is only useful if the evidence record still exists when the investigator arrives — so the record comes first, removal second. This is the sequence we follow, in that order: record, report, remove.
6. What we actually do to prevent CSAE
We would rather describe this accurately than impressively. Everything in this section is a measure that exists.
- Adults only. An 18+ age requirement, a date of birth fixed at registration, and an on-device face check on a live selfie (section 2).
- Age-restricted distribution. OpenWorld is distributed on Google Play as an adults-only app, targeted only at the 18+ audience, with Google Play's Restrict Declared Minors control enabled — so users Google knows to be minors cannot download or purchase it.
- Report and Block everywhere. Any account can be reported and blocked from the feed, reels, stories, profiles, direct messages, group chats and random chat, without leaving the app (section 3).
- Human review of every child-safety report, prioritised over all other moderation, with a permanent ban and a device block as the outcome (section 4).
- Evidence preservation and NCMEC reporting as a defined process, not an intention (section 5).
- A banned-word filter runs on text as it is sent.
- Free accounts cannot share contact details in random chat, which blocks the most common way a conversation gets moved off-platform to somewhere nobody is watching.
- Random chat is not private from us. Our administrators can read random chat messages through a moderation panel, and can end a chat or send a moderation notice into it. This is how we act on a random-chat report after the messages would otherwise have expired.
- Sexual content and nudity are prohibited outright for every user, adult or not (Terms of Service, section 3). A blanket ban on sexual imagery is itself a child-safety measure: it means we do not have to distinguish permitted adult nudity from a minor's, because none of it is allowed.
A nudity filter is not a CSAM detector. We want to be precise about this rather than let it sound better than it is. Where we use automated screening of images, it is a classifier that recognises sexual imagery — a different tool from the hash-matching systems that identify known child sexual abuse material. Such a filter removes sexual content; it cannot tell you that the person in an image is a child, and we never treat it as if it could.
We do not operate automated CSAM detection, and we do not claim to. Nothing on OpenWorld scans your content against a CSAM hash database. Our detection of CSAE is reactive: it depends on people reporting it, and on us reviewing those reports and acting. That is why section 3 asks you to report, and why we mean it.
7. Our limits, stated plainly
OpenWorld is built by a small independent developer, not a large trust-and-safety organisation. Nobody reviews chats in real time, and no one is watching every post as it appears. The banned-word filter and the contact-details block run on your device, and a modified copy of the app can bypass them.
This means a report may take time to be actioned, and it means the safety of this app genuinely depends on its users telling us what they see. We would rather say that than let anyone believe an automated system is catching everything, because believing that is what stops people reporting.
What we do guarantee is the part that is in our control: every child-safety report is read by a human, it is prioritised above all other moderation, the account is permanently banned, the evidence is preserved, and confirmed CSAM goes to NCMEC.
8. Child safety point of contact
Our designated point of contact for child safety matters, empowered to speak to our CSAM prevention practices and to our compliance with Google Play's Child Safety Standards policy, and to act on enforcement:
OdobGames — Child Safety Point of Contact
13odob27@gmail.com
This address is monitored, and is the correct channel for users, NCMEC, Google, law enforcement and child-protection organisations. Law enforcement should identify themselves and the legal basis of the request; we respond to lawful requests for preserved records.
9. Compliance with child safety laws
We comply with the child safety laws applicable to OdobGames and to OpenWorld, and with Google Play's Child Safety Standards policy. We keep these standards published and accessible to anyone, review them as our app and the law change, and act on the obligations described here rather than treating them as a formality.
10. Changes to these standards
We may update this page. If we change it materially we will update the "Last updated" date above. If a measure described here stops being true, our commitment is to change this page to match reality — not to leave a claim standing that we no longer keep.
11. Contact
Child safety reports, questions about these standards, or contact from an authority:
13odob27@gmail.com