Privacy Policy
Wobl · Party Games Offline — last updated 19 November 2026
Wobl doesn’t know who you are. There are no accounts, no advertising and no tracking across other apps or websites. Since November 2026 the app sends anonymous usage statistics — which screens are opened and for how long, what is tapped, which games are played and how rounds end, and which options are chosen in settings — so we can see what works. From version 1.0.6 it also records how the app’s own screens look while it is used, and sends a technical report when the app crashes. None of this includes anything you type, your IP address or your location. The only thing you write that ever reaches us is feedback you choose to send — and it arrives without your name, your device or anything else that says who wrote it.
The rest of this page explains exactly what the app keeps, what it sends and to whom — including the three random identifiers that do leave the phone — because “we collect nothing” is easy to write and worth being specific about. It covers the app on iPhone and iPad (App Store) and on Android (Google Play).
What stays on your phone
Everything the app remembers is stored locally on the device:
- your settings — language, theme, number of players, chosen decks, round length, which Mafia roles you play with;
- a note of which games have already had their one free round with an extra deck;
- the shuffle bags that keep a card from repeating before the deck has gone round;
- a note of whether the one-time unlock has been purchased, so the app works offline;
- a random identifier the app creates the first time you open the purchase screen or restore a purchase, for example
wbl-3f2ab19c…. It is not derived from anything about you or your phone, and its only job is to tell the purchase service that this install is the one that bought the unlock; - a random installation ID that the app’s update software creates the first time the app runs. It goes with each check for content updates, described below;
- a random statistics ID that the app’s statistics software creates the first time the app runs, statistics that have not been sent yet, and the app version seen last time, so that an update can be told apart from a new install. The statistics ID is not derived from anything about you or your phone, and it is not either of the identifiers above.
Anything you type into a game — such as the word for Who Am I — is never sent anywhere. It is saved on the phone only so that an interrupted round can carry on, and it is cleared when the party ends, or after twelve hours without a move. Feedback is different: while you write it, the draft is saved on the phone so it is not lost if the app closes, and a message sent without a connection waits on the phone until it can go out.
Deleting the app deletes all of the above from the phone. A backup of the phone can keep a copy. On iPhone and iPad, app data is part of iCloud and computer backups, as for any app. On Android, the app keeps the data it stores out of Android backup and device-to-device transfer, so a reinstall or a new phone starts with fresh settings. The iPhone and iPad copy is kept by Apple, not by us. The purchase itself is held by the store, not by any backup: on a new phone, Restore purchases brings it back from your Apple Account or Google account.
What leaves your phone
The games themselves are fully offline: you can play the entire app in airplane mode. Three technical connections exist. None carries your name, your contact details or anything you type; each carries one random identifier, described below. A fourth happens only when you send feedback. All four travel encrypted, over HTTPS.
1. Purchases (Apple or Google, and RevenueCat)
The one-time unlock is sold by the store you installed the app from: by Apple through the App Store on iPhone and iPad, and by Google through Google Play on Android, using Google Play Billing. The store handles the payment; we never see your name, email, Apple Account, Google account or card details.
A promo code typed into the app goes straight to the store: the app opens the App Store’s or Google Play’s own redemption page with the code, and the store redeems it like a purchase. The app sends the code nowhere else.
Each store’s purchase is separate. An unlock bought on iPhone does not unlock the app on Android, or the other way round: the app has no accounts that could link the two. Restore purchases asks your own store account — your Apple Account on iPhone and iPad, your Google account on Android.
We use RevenueCat to check whether this device owns the unlock. RevenueCat is contacted only once you open the purchase screen or restore a purchase; from then on the app also checks with it when it starts, so an unlock that went through is never lost. RevenueCat receives:
- the random
wbl-…identifier described above, and the random statistics ID, so that a purchase can be counted in the usage statistics (section 3); - the record of the purchase from the store — Apple’s receipt or Google Play’s purchase token, with the product, price and currency — and the fact that the purchase happened;
- standard technical details that come with any internet request — IP address, device model, operating system version, app version, store country. On iPhone and iPad, RevenueCat’s software also sends Apple’s identifier for vendor, a code iOS gives one developer’s apps on a device.
RevenueCat does not receive your name, email address, Apple Account or Google account, and we do not link that identifier to any person. If you never open the purchase screen, nothing is sent to RevenueCat. When a purchase or a refund happens, RevenueCat reports it to our usage statistics under the statistics ID — the product, its price and currency — so we can see how many people who play also buy the unlock.
2. Content updates (Expo)
New decks and fixes are delivered as content updates rather than full app releases. Each time the app starts, it asks Expo’s update service whether a newer version of the app’s content exists. That request carries the technical details any internet request carries — IP address, platform, app and runtime version — and one identifier: the random installation ID described above, which Expo’s update software creates on the phone the first time the app runs and keeps for as long as the app is installed. It is not derived from anything about you or your phone, and it is not the purchase identifier; it lets the update service tell installs apart, so it can deliver updates and count how many installs have each one. If the app crashed the last time it ran, the request can also carry a short technical description of that error. See Expo’s privacy policy.
3. Usage statistics (PostHog)
Since November 2026 the app records how it is used and sends this, in small batches, to PostHog (PostHog Inc.), which stores it in the European Union, in Frankfurt. We use it to see which games are played, which parts of the app are used, where people get stuck and what to improve. It carries:
- which screens are opened, by their name in the app, for example
/game/spy, and how long each one stayed open; - what is tapped, by the button’s name in the app, and where on the screen — never the text on it, which can be something you typed;
- games: when one is started, which game, the number of players set, the deck chosen, which round of the evening it is, whether the words come from a deck or from the players, whether the app guides the host, and whether the app is unlocked or the round is a free round with an extra deck; when a round ends, how long it took and how it ended — for example which side won in Mafia or whether the word was guessed; when a game is finished, when it is left, and when the app is put in the background mid-round;
- choices made in settings, in game setup and in the catalog filters — language, theme, number of players, decks, Mafia roles and who hosts, round length, sound and vibration, and the mood, time or type of game picked in the filters — as the option chosen, never as anything typed;
- when the rules or the purchase screen are opened and from where, and whether a purchase, a restore or a promo code went through, was cancelled or failed — never the code itself;
- that a feedback message was sent — never its text;
- when the app is installed, updated, opened, brought back and put in the background;
- the app version and its language, the region set in the phone’s language and region settings (for example
UA), the operating system and its version, the type and size of the screen, and the time. The region is a setting on the phone, not your location: nothing is worked out from GPS or from your IP address; - the random statistics ID described above, and a session ID that changes each time the app is used.
Screen recordings (from version 1.0.6). To see where people get stuck, the app records its own screens while it is in use — what the app shows and where it is tapped — and sends the recording to PostHog. Anything you type is hidden in the recording before it leaves the phone: the feedback field and the word a friend types in Who Am I are blanked out, and the keyboard is not recorded at all. Nothing outside the app is recorded, and neither are the app’s logs or its network requests. Recordings are kept for 30 days.
Error reports (from version 1.0.6). When the app hits an error or crashes, it sends a technical report so we can fix it: what went wrong and where in the app’s code, the app version, the device model and the operating system version.
It never carries anything you type — no player names, no words, no answers, no feedback. PostHog receives the IP address that comes with any internet request; it is set to discard it without storing it, and no location is worked out from it. The statistics are not linked to a name or an account, not combined with data from other apps or websites, and not used for advertising. They are kept for up to one year.
4. Feedback you send (Cloudflare)
At the end of a game you can write to us. Nothing is sent unless you press Send. The message goes to a small service of ours hosted on Cloudflare, and it carries exactly four things:
- the text you wrote;
- the app version, for example
1.0.3; - the app’s language, for example
de; - a random code made for that one message, so that a message resent after a dropped connection is not stored twice. A new code is made for every message, so two messages cannot be linked to each other or to your phone.
We do not store your IP address, device, country or any identifier. Like any internet request, the message reaches Cloudflare with your IP address; the service uses it for a moment to stop the same address from sending more than a few messages a minute, and then forgets it. The service keeps no logs.
Because the message carries nothing about who wrote it, we cannot reply to it. If you want an answer, write to us through Support instead. Please don’t put your name, contact details or anything else personal into feedback — if you do, it is stored like the rest of the text.
Feedback is kept for 180 days and then deleted automatically. It is read only by us, to fix and improve the app, and it is never shared or sold.
What we never do
- No tracking and no location. The usage statistics in section 3 stay with us; there is no Firebase, no Sentry and no advertising software in the app.
- No advertising and no advertising identifiers: no App Tracking Transparency prompt on iPhone, and no use of the advertising ID on Android, because nothing follows you across other companies’ apps or websites.
- No accounts, no sign-in, no email collection.
- No selling or renting of data, and no sharing of it for advertising. The four services named above handle data only to do their job for the app.
- No microphone, camera, contacts, photos, files or location access, and no tracking of physical activity. The app asks for none of them. On Android, the only permissions it uses are internet and network-state access (for updates, purchases and feedback), vibration (for haptics) and Google Play billing.
Children
Wobl is rated 12+ and is meant for a table of friends. It does not knowingly collect personal information from anyone, of any age. Usage statistics are anonymous, and feedback is the only thing anyone writes that reaches us — it carries nothing that identifies the person who wrote it.
Your data, and removing it
To remove everything the app has stored on your phone, including an unsent feedback message, delete the app from your device. On iPhone and iPad, a backup of the phone keeps its copy until that backup is deleted; on Android, the app’s data is not part of the phone’s backup. To have a feedback message you already sent deleted before the 180 days are up, write to us via Support with a few words of it and roughly when you sent it — since it carries no name, that is how we find it — and we will delete it and confirm. If you would like the purchase record held by RevenueCat removed, write to us via Support and we will ask them to delete it — note that this may prevent restoring the purchase later. Usage statistics stop when the app is deleted; a reinstall starts with a new random statistics ID that cannot be linked to the old one, and what was sent before is deleted automatically after one year. Because the statistics carry no name, we cannot find one person’s records by name; if you want them deleted sooner, write to us via Support.
Changes
If this policy changes, the date at the top changes with it. If a future version of the app ever starts collecting something, that will be said here plainly, before it ships.