Privacy Policy

1. Who we are and what this covers

Omega Software Solutions (“we”, “us”) is a small independent game developer in the United States. This policy covers:

• this website, omegagamesonline.com, including the playable builds we host at /play/;
• our games — Wreck Run, Merge Bastion, Daybreak Factory and Necrowave — in every form we ship them: playable in a browser on this site, embedded on a game portal, and as Android applications (com.omega.wreckrun, com.omega.mergebastion, com.omega.daybreakfactory, com.omega.necrowave);
• the Android build of Necrowave, which is not released. It is not on Google Play or any other store, and nothing on this site installs it. Necrowave’s browser version is live here and playable today. What this policy says about advertising is written to cover the Android build too, so that nothing here has to be rewritten on the day it ships.

Our games are ad-supported, and section 4 describes advertising for the whole catalogue rather than game by game. Where a specific build differs today — the copies hosted on this site, for instance — that difference is stated as a current fact about that build, not as a promise about the game.

It does not cover a third party’s own site or store. When one of our games is played inside a portal such as CrazyGames or Poki, or installed from Google Play, that platform is an independent controller of whatever it collects, under its own privacy policy. The same is true of the advertising networks described in section 4.

Contact for anything in this policy: omegasolutionsbusiness@gmail.com. We have not appointed a data protection officer and are not required to.

2. What we collect

From this website

Nothing that identifies you. The site is static HTML, one stylesheet and one small JavaScript file, all served from our own server. There are no forms, no accounts, no comment system, no newsletter, no cookies, no analytics service, no advertising tags, no social media widgets and no fonts or scripts loaded from another company’s domain.

Like every web server, ours writes ordinary access logs: the requesting IP address, the date and time, the file requested, the HTTP status, the referring page and the browser’s user-agent string. We use these only to keep the server running and to investigate abuse or errors. We do not combine them with anything else, do not build profiles from them, do not sell or share them, and rotate them off the server in the normal course of operating it.

From our games

We receive nothing from our games. They have no telemetry of ours, no crash reporting, no event tracking and no identifier that reaches us. They save your progress to your own device and never send it to us, because there is nowhere to send it: we operate no game server and no player database.

We never ask you for: your name, email address, phone number, postal address, date of birth, precise location, contacts, photos, microphone or camera input. No game of ours contains a form, a login or a text field that asks for information about you.

That is a statement about us. The advertising software inside a build reads identifiers and technical facts in order to request an ad, and section 4 sets out what those are and who receives them. We are not one of the recipients.

3. Progress stored on your device

Each game keeps a small amount of gameplay state so you can pick up where you left off. It is written to your own device and is readable only by the game that wrote it:

• In a browser (this site or a portal embed): to the browser’s own storage for the page’s origin, where the game mounts its save area in IndexedDB. It is not a cookie, is never sent with an HTTP request and is not visible to us or to any other website.
• On Android: to the application’s private storage directory, which Android isolates from other apps and removes when the app is uninstalled.

What is actually stored is gameplay values only:

Wreck Run	best score, best flip count, coins, number of runs, the skin you have selected and unlocked, mute setting, the last day seen, your per-level records and stars, today’s daily-track score with the seven-day strip and streak behind it, a flag saying the control card has been read, and the debris layout your previous wrecks left on the track
Merge Bastion	best wave, best threat level, best wave at each threat level, which of the towers you have discovered, which codex bounties you have claimed, runs played, the daily siege record and streak, tutorial and hint flags, mute setting, and a local table of your own best runs: wave, hybrids, kills and threat, with no names, stored on your device only and never uploaded
Daybreak Factory	a single saved factory state: cash, machine levels, the live order and crate state, the permanent perks you have earned, your badges and lifetime counters (taps, crates, orders, earnings), mute setting, and the timestamp of the current 24‑hour day
Necrowave	banked gold, the rank of each permanent upgrade bought from Old Moss, which characters, weapons and arenas you have unlocked and which arenas you have cleared, endless mode and your best endless time, curse level, mastery and the lore you have read; a lifetime tally of what you have killed and built; a snapshot of a run in progress, so a field you walk away from resumes where you left it; and your settings — the separate volumes, haptics and their strength, screen shake, damage numbers, reduced flashing, the extra safe-area inset and language

None of it identifies a person, and you can delete all of it at any time. See Your choices and controls. Identifiers used for advertising are separate from this save file: they are stored by the advertising software itself, in the builds that carry one, and are described in section 4.

4. Advertising, and the third-party software involved

Our games are ad-supported. Advertising is part of how every Omega game is funded, in every form we ship it.

On Android, advertising is served through AppLovin MAX, a mediation SDK that is part of the application. On a game portal such as CrazyGames or Poki, advertising is served by that portal’s own SDK, which the build we submit there carries. Whichever SDK is in play, the ad is requested from and delivered by that company’s servers, not by us; we run no ad server and no game server. Our games have no age gate, so the advertising in them is configured to be non-personalised for every player rather than only for children: no behavioural or interest-based targeting, and no advertising profile built from play. The Children’s Privacy Policy sets that commitment out in full.

Advertising software of this kind reads the device or browser identifiers it needs to request and measure an ad. On Android that includes Google’s advertising ID, which is why an Android build carrying that software declares the advertising-ID permission (com.google.android.gms.permission.AD_ID) along with internet and network-state access — the ad SDK’s own manifest is what adds them. Which of our builds does that today, and which does not yet, is set out under Google Play Data safety alignment below. On the web the portal’s SDK stores its own identifiers in the browser alongside its own cookies. The advertising SDK also receives ordinary technical facts about the request — device or browser type, operating system, language, coarse country, and the ad slot being filled.

We do not receive any of it. The ad networks, and the portals that host our games, are independent controllers for what they collect, under their own privacy policies. We hold no player record, no profile and no advertising identifier of our own, and none of the game’s saved progress reaches us or reaches an advertiser.

Where a game offers you an ad in exchange for a bonus, declining it costs you only that bonus — nothing else in any game depends on it. We do not describe the shape an advertisement takes on screen here, because that is a product decision that can change in an update; what does not change is the description above of what advertising software reads and who receives it.

The copies hosted on this site

The web builds we submit to a game portal carry that portal’s SDK script. The copies of Wreck Run, Merge Bastion and Daybreak Factory we host at /play/ are the same export with that script tag removed, by the sync step that publishes them. Necrowave’s browser build was never a portal export and carries no portal SDK at all; its advertising code selects an ad provider only when it is running on Android with the AppLovin plugin present, and in a browser neither is true, so it falls through to a provider that requests nothing. While you play any of the four on omegagamesonline.com, every file the page loads comes from our own server: no request goes to a portal, no ad is requested, no portal storage is used, and your save is written to this browser’s own storage for this origin.

That is a description of how these copies are built and published, not a commitment about what this site will always host. If a build served here ever requests an ad, this page and the Cookie Policy will say so before it goes live, and the date at the top of the page is the record.

Necrowave

Necrowave is playable in a browser on this site, and that build requests no ad, for the reason given just above. The Android build of Necrowave is not released. It is not on Google Play or on any other store, and nothing on this site installs it. We set out its advertising position ahead of publication rather than after the fact, and the description above applies to it in full.

Necrowave is built for Android with the AppLovin MAX mediation software compiled into it. Because that software is present, its application manifest declares Google’s advertising-ID permission (com.google.android.gms.permission.AD_ID), internet access and network state, and with them the further permissions the ad software and the game engine bring along: the Android ad-services permissions (ACCESS_ADSERVICES_TOPICS, ACCESS_ADSERVICES_ATTRIBUTION), Wi‑Fi state, wake lock, foreground service, boot-completed and vibrate. AppLovin and the ad networks it mediates are independent controllers for whatever they collect, under their own privacy policies; it does not come to us.

Necrowave’s Android build is also being built with optional paid unlocks sold through Google Play, and one of the things a paid unlock is intended to grant is the removal of advertising. Nothing in Necrowave can be bought today, in a browser or anywhere else, because it is listed nowhere; the Refund Policy describes the route once it is.

What does not change for Necrowave, on either platform: we run no game server and no player database, we ask for no account, and the game’s own progress is written to the device you are playing on and stays there — the browser’s own storage here, the app’s private directory on a phone. Before the Android build is published, this page will carry its complete permission list and a Google Play Data safety declaration that matches the build being submitted.

Google Play Data safety alignment

None of our games is on Google Play yet, so no Data safety form has been submitted for any of them. We are writing the declaration here first, so that it can be checked against the build it belongs to.

For any Android build of ours that carries advertising software, the Google Play Data safety declaration says: Device or other IDs — collected, shared with third parties, used for advertising, and the store listing is marked Contains ads. It is not optional and not user-controllable within the game, because it is how an ad is requested at all. We collect no other category: no personal information, no location, no messages, no photos, no files, no contacts, and no app activity sent to us.

The declaration is always written against the artifact actually submitted, and today the catalogue is not in one state. The Android build of Necrowave has the AppLovin MAX software compiled into it and its manifest declares the advertising-ID permission; the browser build of the same game, which is what this site hosts, loads no ad SDK and requests no ad. That build carries the game’s own advertising code, because it is one codebase, but that code selects the AppLovin provider only when it is running on Android with the AppLovin plugin present; in a browser neither is true, so it falls through to a provider that requests nothing and contacts no ad network. The current Android builds of Wreck Run, Merge Bastion and Daybreak Factory do not yet have an ad SDK linked into them, and declare no Android permissions at all — not the advertising ID, not internet access. Those three are ad-supported games and their Play releases will carry the ad software, the permissions and the declaration above; this page and the date on it are updated before such a build is submitted, not after. If a build ever ships without advertising software in it, its declaration and its manifest say that instead.

Hosting

This site runs on a virtual server we rent from DigitalOcean, which processes traffic to the site as our hosting provider. There is no content delivery network, no tag manager and no A/B testing service in front of it.

5. What we never do

• We do not sell personal information for money, and we have not done so in the preceding twelve months.
• We do not build a profile of you, score you, or make automated decisions about you, and we hold no advertising profile.
• We do not send marketing email, because we have no email addresses.

Each of these describes what we do. Advertising in our games is served by third-party software, and what an ad network does with the identifiers it reads is governed by its own policy, not by this list. We ask for advertising to be non-personalised, but identifiers still leave the device for the ad network, so where a law such as the California CPRA treats advertising of this kind as a “share” of personal information we take the conservative position: assume that serving ads in our games is such a share, made by the advertising SDK rather than by us.

6. Children

Our games are suitable for a general audience and are age‑neutral. We collect no personal data ourselves from anyone, of any age, and the advertising in our games is configured to be non-personalised for every player, so there is no behavioural or interest-based advertising to children. That second commitment applies to every game we publish, including Necrowave, and the children’s policy says how. Full detail, including our COPPA and Google Play Families position, is in the separate Children’s Privacy Policy.

7. Legal bases (UK/EU)

Where the UK GDPR or EU GDPR applies, the only personal data we process is the IP address and request metadata in our server access logs. Our legal basis is legitimate interests (Article 6(1)(f)): keeping the website available, secure and free of abuse. On-device game progress is not transmitted to us and so is not processed by us; storing it on your device is strictly necessary to provide the game you asked to play. Personal data processed by the advertising software in a build, or by the portal hosting it, is processed by those companies on their own legal bases and under their own policies, including any consent they are required to collect from you.

8. Your rights

UK GDPR and EU GDPR

You have the right to access, correct, erase, restrict or object to the processing of your personal data, and the right to data portability and to complain to your supervisory authority (in the UK, the Information Commissioner’s Office).

We want to be straightforward about what those rights amount to here: we hold no account, no profile and no player record for you, so in almost every case there is nothing to export, correct or delete. If you believe a specific server log entry relates to you, write to us with enough detail to find it (the approximate date, time and IP address) and we will search for it and delete it where we can. We cannot invent a record we never kept, and we will tell you plainly when that is the answer rather than pretend otherwise. A request about data held by an advertising network or a portal has to be made to that company; we can pass on what we can, but we cannot reach their records.

California (CCPA/CPRA)

California residents have the right to know what personal information is collected, used, disclosed or sold; the right to delete it; the right to correct it; the right to opt out of sale or sharing; and the right not to be discriminated against for exercising those rights. We collect no personal information beyond server access logs and we sell no personal information for money. Because the advertising in our games is served by third-party SDKs, and the CPRA treats targeted advertising as a “share”, the effective controls are the platform ones: on Android, Settings → Privacy → Ads → Delete advertising ID (or opt out of ad personalisation); in a browser, your browser’s cookie and site-data controls together with the ad choices offered by the portal you are playing on. You may also write to omegasolutionsbusiness@gmail.com, and we will pass on what we can, though we hold no record of our own to delete. We verify a request only to the extent we can, which given the absence of accounts is usually not at all.

Other United States privacy laws

Residents of Virginia, Colorado, Connecticut, Utah, Texas and other states with comprehensive privacy laws have comparable rights of access, deletion, correction and opt-out, including opt-out of targeted advertising. The same answer applies: we hold no targeted advertising profile of our own, run no sale of personal data and perform no profiling; the controls that actually govern advertising are the platform ones listed above, and we respond to requests at the address above.

9. Your choices and controls

• Delete browser game data: clear site data for omegagamesonline.com (or for the portal you played on) in your browser’s settings, or use a private window. This erases your saved progress permanently; there is no backup, so it cannot be restored.
• Delete Android game data: Settings → Apps → the game → Storage → Clear data, or uninstall the app.
• Advertising controls: on Android, Settings → Privacy → Ads lets you reset or delete your advertising ID and turn off ad personalisation. In a browser, clearing site data for the portal you are playing on clears the identifiers its advertising has stored.

10. Retention

Server access logs are kept only while they are useful for security and troubleshooting and are then rotated and discarded. Game progress on your device is kept until you clear it or uninstall the game. We cannot delete it for you, because we cannot reach it. We hold no other records about players. Data held by an advertising network or a portal is retained under that company’s own policy, not ours.

11. Security

The site is served over HTTPS with a valid certificate and is entirely static: there is no database, no login, no user upload and no server-side code that could be made to leak player data, because there is no player data on the server to leak. The server is kept patched and administrative access is restricted to key-based authentication. No system is perfectly secure, but the surface here is deliberately as small as we could make it.

12. International transfers

Our server is located in the United States. If you visit the site from elsewhere, your request necessarily reaches a server in the United States. Because we collect no personal data from you beyond access logs, there is no ongoing transfer of personal data to manage on our side. Advertising networks and portals operate internationally and make their own transfers under their own policies.

13. Changes to this policy

If we change what our software does, we will update this page and the date at the top before the change ships, and update our Google Play Data safety declaration to match. Our games are ad-supported by design, so a change in which networks serve them, or in what a build requests, is a change to this page rather than a surprise. We do not have your email address, so we cannot notify you individually; the date at the top of this page is the record.

14. Contact

Email omegasolutionsbusiness@gmail.com with any privacy question, request or complaint. Write “Privacy” in the subject line and we will answer as quickly as a small team can, and within any period the law that applies to you requires.

All policies