OpenWorld Privacy Policy
App: OpenWorld · Developer: OdobGames
com.odobgames.openworld
Last updated: 17 July 2026
OpenWorld (“we”, “us”, “the app”) is developed by OdobGames. This policy explains what we collect, why, who receives it, how long we keep it, and what you can do about it. It describes the app as it actually works — including the things we don’t do, which matter just as much.
OpenWorld is an 18+ app that pairs you with strangers for chat. Please read section 7 (“What we do not do”) before you decide what to share here.
OpenWorld is not for children, and we do not knowingly collect data from anyone under 18. If we learn that a user is under 18 we delete the account. Our Child Safety Standards explain how we handle child sexual abuse and exploitation, how to report it, and who to contact.
1. What we collect
Account information
- Your email address, and either a password or your Google account identifier if you use Sign in with Google. Sign-in is handled by Firebase Authentication (Google); we do not store your password ourselves.
- Your date of birth, which you enter at registration. It is stored privately and cannot be edited afterwards. Your birth year only (not the full date) is shown on your public profile so a chat partner can see your approximate age.
Profile information (public to other signed-in users)
- Display name, unique @username, profile photo, banner image, bio, gender, country, and interests.
- Your country is the one you pick from a list when you register. We do not detect it, and the app has no location permission.
Content you create
Posts, reels (short videos), stories, comments, stickers you send, and the messages you send in random chat, direct messages and group chats.
Your device identifier
We store your device’s Android ID on your account. We use it for one purpose: enforcing bans at the device level, so that someone banned for serious abuse cannot simply create a new account on the same phone. It is not used for advertising or tracking across other apps.
Notification tokens
A Firebase Cloud Messaging token per device, so we can send you notifications about messages, friend requests and activity on your content.
Matchmaking and chat records
While you look for a random chat, we record that your account is waiting. Once paired, we record the chat session and its messages so both people can see the conversation, until it expires (section 5).
Reports and moderation records
If you report someone, or someone reports you, we keep a record of that report. If a moderator opens a case about serious or illegal conduct, that case includes a snapshot of the account details and the evidence involved. See section 5 for how long these are kept.
Purchase status
If you buy OpenWorld+, we record your entitlement status (whether your account is premium). Payment is processed by Google Play — we never receive or store your card or payment details.
So that a single purchase cannot be redeemed twice, we also keep a small purchase record: a one-way hash of the Google Play purchase token, the order ID, and the identifier of the account that redeemed it. This record is anti-fraud and replay protection, so it is kept permanently and, unlike the rest of your data, is not erased when you delete your account (see section 5).
Advertising
The free version of the app shows ads from Google AdMob. The AdMob SDK may access your device’s advertising identifier to serve and measure ads. Where required (for example in the EEA and the UK), the app shows you Google’s consent form before ads are personalised, and your choice there controls it. OpenWorld+ removes ads.
2. The registration selfie — analysed on your phone, never uploaded
When you create an account, the app opens the front camera and captures a frame to check that a single, clear, front-facing face is present, and to estimate whether that face looks like an adult’s.
That image is analysed entirely on your device and is never uploaded. It is not sent to us, not sent to Cloudinary, not stored on any server, and never seen by any person. The check runs locally using Google ML Kit face detection and an age-estimation model bundled inside the app. The captured frame is written to the app’s private storage on your phone for the moment it takes to analyse it, and is removed when you clear the app’s storage or uninstall the app.
We therefore do not collect biometric data and do not build a face template, faceprint or any other identifier from it. This is a “does a real adult face appear to be present” check — it is not identity verification, not certified age verification, and it can be wrong in both directions.
This is separate from your profile photo, which you choose yourself and which is uploaded and shown publicly (section 3).
3. What is uploaded, and where it is stored
Your account data, profile, content and messages are stored in Google Firebase (Firebase Authentication, Cloud Firestore and Realtime Database). The photos and videos you upload — profile photo, banner, post images, reel videos, story media, chat images and stickers — are stored with Cloudinary, our media host.
Both Google and Cloudinary operate global infrastructure, so your data may be processed on servers in the United States and in other countries where they operate. If you use OpenWorld from outside those countries, your data is transferred there.
4. Who your data is shared with
| Who | What they receive, and why |
|---|---|
| Firebase (Google) | Your account, profile, content, messages, notification tokens and device identifier. Firebase provides our sign-in, database, realtime presence, notification delivery and anti-abuse (App Check) infrastructure. See Google’s Privacy Policy. |
| Cloudinary | The photos and videos you upload. See Cloudinary’s Privacy Policy. |
| Google AdMob | Ad requests from your device, which may include your advertising identifier and coarse device information, to show and measure ads in the free version. See how Google uses data from apps that use its services. |
| Cloudflare | We run a small service on Cloudflare Workers for three jobs. First, notifications: when an action of yours triggers a notification to someone else, that service receives the recipient’s account identifier and the notification title and text (which can include a display name and a short preview of a message or comment), so it can send the push. Second, purchase checks: if you buy OpenWorld+, the same service receives your Firebase sign-in token, the Google Play purchase token and the product identifier, so it can confirm your purchase with Google and unlock your premium status. Third, for administrators only, media removal: when an administrator deletes illegal media, the service receives the links to the media to delete so it can erase those files. See Cloudflare’s Privacy Policy. |
| ccMixter | Background music for stories and posts is browsed and streamed directly from ccMixter, a third-party music community. When you open the music picker or play a track, your device contacts ccMixter directly, so they receive your IP address and what you searched for. We do not send them your account details. See ccMixter’s privacy information. |
| Google Play (Billing) | If you buy OpenWorld+, the purchase is processed by Google Play under Google’s own terms. We receive confirmation of the purchase and a purchase token — never your payment details. |
| Other users | Your public profile, posts, reels, stories and comments are visible to other signed-in users by design. See section 6 on what is visible in random chat. |
| Authorities | Where the law requires it, or where we believe it necessary to report serious or illegal conduct — in particular sexual content involving minors. |
We do not sell your personal information.
We do not use any analytics or tracking SDK. The app contains no Google Analytics, no Firebase Analytics, no Crashlytics and no third-party behavioural tracking. We do not build advertising profiles about you. Apart from AdMob’s own ad serving, nothing in the app follows what you do.
5. How long we keep things
Content in OpenWorld is short-lived by design. Whether or not you delete your account, content expires on a timer:
| What | Stops being visible after |
|---|---|
| Posts and reels (photos and videos) | 7 days |
| Stories | 24 hours |
| Direct and group messages, and stickers sent in chat | 24 hours |
| Photos sent in any chat (random chat or DM) | 10 minutes |
| Random chat conversations | When either person leaves, or within 24 hours |
Expiry is not instant deletion — be aware of the lag. The app hides expired content immediately, but the job that actually erases it from our infrastructure runs once a day. Expired content can therefore remain on our servers for up to about 24 hours after it disappears from the app. Uploaded media is cleaned from Cloudinary on its own daily schedule, counted from when it was uploaded: chat images within about an hour, stories and stickers within about 48 hours, and post, reel and comment media within about 8 days. Until a file is collected, it is unreachable from inside the app, but a direct link to it would still load.
Your account, profile and friendships are kept for as long as your account exists.
Reports and moderation cases
Reports and moderation cases are kept after the reported account is deleted, and are not on any automatic expiry timer — we retain them until they are removed manually. We keep them as safety and legal evidence, so that a record of harassment, abuse or illegal content cannot be erased by the reported person simply deleting their account. They are stored separately from your profile and are not publicly visible.
Purchase records
The purchase record described in section 1 — a hashed purchase token, the order ID and the redeeming account’s identifier — is kept permanently and is not deleted when your account is. It exists so that one purchase cannot be redeemed twice, which only works if the record outlives the account. It contains no payment details.
6. Random chat is not anonymous
Do not use random chat expecting to stay unidentified. Whether your identity is visible depends partly on the other person’s subscription, not only yours:
- A partner using the free version sees a masked nickname and a blurred profile photo.
- A partner with OpenWorld+ sees your real display name, your @username, your gender and your age.
- If you have OpenWorld+, your display name and photo are revealed to everyone — that reveal is part of what OpenWorld+ is.
7. What we do not do
Messages are not end-to-end encrypted. Connections to our infrastructure use HTTPS/TLS, but your messages are stored in a form we can read. Do not treat OpenWorld chats as private or secure.
Our administrators can read chat content. Accounts marked as administrators can open a moderation panel that lists active random chats and can read the messages in them, and can end a chat or send a moderation notice into it. This exists so we can act on abuse. It means a conversation in OpenWorld is never private from us.
Images are screened on your device, but the check is not perfect. Before any image is uploaded — a post, a comment, a story, a photo or sticker sent in chat, your profile photo, avatar or banner — it is screened by a nudity classifier running on your phone, and the upload is blocked if the image is classified as sexual. This check fails closed: if it cannot run, the upload is refused rather than let through. A face and age check also runs on your registration selfie and on the media you share. Videos are screened by sampling a few frames and running the same check over those — a best-effort spot-check, not a full scan of every frame.
All of this runs entirely on your device — no image or video is sent to any outside moderation service. No automated check catches everything, so it is not a guarantee: human review and user reports remain the backstop, so please still report anything you see (section 9). Separately, an on-device banned-word filter runs on text, and an on-device block stops free accounts sharing contact details in random chat. Because these checks run on your device, a modified copy of the app can attempt to bypass them.
We do not collect precise location. The app requests no location permission at all.
8. Permissions the app asks for
- Camera — for the registration selfie check, and for taking photos and videos to share. Only what you capture and choose to send is uploaded.
- Microphone — for audio when you record a video or reel.
- Notifications — to alert you to messages and activity. You can decline or turn it off in Android settings at any time.
Photos you pick from your gallery are selected through the Android photo picker, which gives the app only the item you chose — not your whole photo library.
9. Your choices and rights
- Edit your profile at any time from Profile → Edit profile.
- Block anyone, from any post, reel, story, profile or chat. Blocking also stops them being matched with you in random chat again.
- Report anyone, from any of the same surfaces.
- Turn off notifications in Android settings.
- Control ad personalisation through the consent form the app shows where required, and through your Android advertising settings.
- Delete your account — see section 10.
- If you are in the EEA, the UK, California, Brazil or another region with data protection rights — such as access, correction, portability, objection, or restriction of processing — contact us at the address in section 12 and we will action your request.
10. Deleting your account
From inside the app:
- Open OpenWorld and sign in.
- Tap the Profile tab.
- Tap Edit profile.
- Scroll to the bottom and tap Delete my account.
- Confirm with Delete permanently.
Without the app (if you uninstalled it or cannot sign in), see our account deletion page, at https://openworld-app-56794.web.app/eliminar-cuenta.html, which explains how to request deletion by email and lists in detail what is erased.
You are signed out as soon as you confirm, and your account is queued for permanent deletion. It cannot be undone. Deletion is carried out by an automated job that runs once a day, and in normal operation completes within about 24 hours. Because that job can fail or be delayed, we commit to completing deletion within 30 days of your request. Uploaded media is removed from Cloudinary on the schedule in section 5 — media attached to your content can take up to about 8 days to be collected.
As explained in section 5, reports and moderation cases involving your account are retained after deletion.
11. Children
OpenWorld is not directed at children and you must be 18 or older to use it. We do not knowingly collect data from anyone under 18. The date of birth you give at registration and the on-device face check in section 2 are our only age controls, and neither is a reliable proof of age. If you believe someone under 18 is using OpenWorld, please report them in the app or contact us below and we will remove the account.
12. Contact
Questions about this policy, or a request about your data:
13odob27@gmail.com
13. Security
Connections between the app and our infrastructure use HTTPS/TLS, access to data is restricted by server-side security rules, and the app uses Google Play Integrity (Firebase App Check) to make it harder for modified clients to reach our data. No method of transmission or storage is completely secure, and as stated in section 7, your messages are not end-to-end encrypted.
14. Changes
We may update this policy. If we make a material change, we will update the “Last updated” date above and, where appropriate, tell you in the app.