Children’s Privacy Policy
Last updated: 7 September 2026
The short version
- Our games carry advertising, and it is set to non-personalised. No behavioural or interest-based targeting. No advertising profile built from a child’s play. That holds for every game we publish, and section 6 sets out how.
- We collect no personal information from anyone ourselves, children under 13 included, and we hold no advertising identifier. The advertising software in a build reads the device’s advertising ID so it can request an ad. It never reaches us.
- There is no sign-up, no name entry, no chat, no user-generated content and no way for one player to contact another.
- Game progress is saved on the child’s own device. We run no server that holds player data.
- A parent can wipe everything a game has stored by clearing the site data or the app data, and can reset or delete the device advertising ID in the phone’s own settings. No request to us is needed.
1. Scope
This policy explains how Omega Software Solutions treats children’s data in our games and on this website. It covers every game we publish, including Wreck Run, Merge Bastion, Daybreak Factory and Necrowave, on every platform we ship them to. Section 6 sets out our advertising position for the whole catalogue. It supplements our Privacy Policy, which applies in full to players of every age. It is written against the United States Children’s Online Privacy Protection Act (COPPA) and its Rule, the Google Play Families policy and the Play Families Ads & Monetisation requirements, and the UK Age Appropriate Design Code.
2. We collect no personal information from children
COPPA is concerned with the collection of personal information from children under 13. We collect none of the following, from a player of any age, in any of our games:
- no name, screen name, email address, phone number, postal address or date of birth;
- no photograph, video, voice recording, microphone or camera access;
- no geolocation of any precision;
- no persistent identifier of ours: we set no device ID, no account ID and no cookie to recognise a returning player, and we do no fingerprinting. The advertising software in a build reads the device advertising identifier in order to request and measure an ad — see section 6 — and that identifier is never passed to us;
- no contacts, no social graph, no address book.
Because we collect nothing, there is nothing for us to disclose to a third party, nothing for us to sell, and no verifiable parental consent for us to obtain. Our games never ask a child for information under any circumstances, including in exchange for a reward.
3. Age-neutral design
The games contain no age gate because we collect no data from a player whose handling would depend on age, and an age gate would itself collect a date of birth we do not want. The treatment is identical for every player: no personal data collected by us, no personalised advertising, and no advertising profile built from anyone’s play. That is the highest-privacy setting, and every player is given it without having to ask, which is what an age-appropriate design requires.
Content is cartoon throughout: a comic zombie riding a firework rocket who crashes in a puff of smoke, elemental towers firing at cartoon skeletons on a road, and pixel-art factory machines. There is no realistic violence, no blood, no gambling or simulated gambling, no loot boxes, no alcohol, tobacco or drug references, and no sexual content.
4. No social features and no outbound links in play
There is no chat, no messaging, no friend list, no username, no leaderboard that publishes anything to other people, no user-generated content and no upload of any kind. Merge Bastion’s table of best runs is stored on the device and shown only to the person playing on that device. Nothing in the games links a child out to social media or to an external website.
5. What is stored on the device
Each game writes small gameplay values (a best score, a mute setting, which items have been unlocked, the current factory state) to the browser’s own storage or to the app’s private storage on Android. This is the game’s save file, kept so a child does not lose progress; it is not a profile, is not sent to us, and is not used to recognise a player across sites or apps. The full list is in section 3 of the Privacy Policy. Advertising software stores identifiers of its own, separately from the save file; our Cookie Policy describes that storage.
6. Advertising and monetisation
Our games carry advertising, and we treat it as a children’s-privacy question rather than a commercial one. On Android the ads are served by the AppLovin MAX mediation software that is part of the application; on a game portal such as CrazyGames or Poki they are served by that portal’s own software, which the build we submit there carries.
Our commitment, which applies to every game we publish and is not conditional on a release date: advertising in our games is configured for a child-appropriate, non-personalised experience. No behavioural or interest-based targeting, no remarketing, and no advertising profile built from a child’s play. Where a build is distributed under the Google Play Families programme, it is configured to that programme’s Ads & Monetisation requirements, and any ad network serving it must be one the programme permits. Where a portal hosts our game to a mixed or child audience, the portal is required to serve contextual rather than behaviourally targeted advertising.
Advertising software reads the device advertising identifier in order to request and measure an ad, and an Android build carrying that software declares Google’s advertising-ID permission for that reason. Today that is the Android build of Necrowave; the current Android builds of Wreck Run, Merge Bastion and Daybreak Factory have no ad SDK linked into them yet and declare no permissions at all, and their ad-supported Play releases will declare it in the same way. No browser version of any of the four requests an ad or loads an ad SDK, the Necrowave you can play on this site included — its advertising code reaches a provider only on Android with the AppLovin plugin present, so in a browser it asks for nothing. A browser has no device advertising identifier in any case, so there is none for a child to have read while playing here. Either way we do not receive that identifier, do not store it and do not combine it with anything. We give a portal or an ad network no information about a player, because we hold none. The Privacy Policy keeps the build-by-build position.
A parent can reset or delete the device advertising ID, and turn off ad personalisation, in Android’s Settings → Privacy → Ads. In a browser, clearing site data for the portal the child is playing on clears the identifiers its advertising has stored.
Purchases. There is nothing to buy in Wreck Run, Merge Bastion or Daybreak Factory, so a child cannot spend money in them: those builds contain no in-app purchase, no currency pack and no subscription, and every coin, unlock and perk in them is earned by playing. The same is true of Necrowave as you play it in a browser here: there is nothing in it to buy. Its unreleased Android build is different: that build is being made with optional paid unlocks sold through Google Play, one of which is intended to remove advertising. Nothing in Necrowave can be bought today, because it is not listed anywhere, and this page will describe what it sells before that release ships. Where a game of ours offers a purchase through a store, the store’s own parental controls and purchase authentication apply.
7. Information for parents and guardians
Because we hold nothing about your child, there is no record for us to show you or erase. To review or remove what a game has saved, and to control the identifier advertising uses:
- In a browser: clear site data for the site the game was played on, in the browser’s settings. That deletes the save permanently, along with anything advertising on that site has stored.
- On Android: Settings → Apps → the game → Storage → Clear data, or uninstall the app.
- Advertising ID on Android: Settings → Privacy → Ads lets you delete or reset the advertising ID and turn off ad personalisation for every app on the device.
If you believe a child has somehow provided personal information to us, for example by writing to our support address, email omegasolutionsbusiness@gmail.com and we will delete that correspondence promptly. We do not knowingly retain any personal information from a child under 13.
8. Changes
Any material change to how we treat children’s data will be published here, with the date at the top updated, before the change takes effect in a shipped build, and our Google Play Data safety declaration will be updated to match. Where COPPA requires parental notice before a new collection of personal information, we would obtain verifiable parental consent first. The plan is to keep collecting nothing ourselves, and to keep the advertising in our games non-personalised.
9. Contact
Omega Software Solutions, United States. omegasolutionsbusiness@gmail.com. Write “Children’s Privacy” in the subject line so it reaches the right person quickly.