Cookie Policy
Last updated: 12 September 2026
The short version
- This website sets no cookies. Not essential ones, not analytics, not advertising. That is why you have never seen a cookie banner here.
- We run no analytics and no advertising tags, and our ordinary pages load nothing from another company’s domain.
- The games save your progress in the browser’s own storage. A save file is not a cookie, and the save itself is never sent to a server.
- Some of that storage does leave it: the player key, the display name, and a small play record — how much and how often that copy of the game has been played, and the language and time zone the device is set to — which a game with an online leaderboard puts on your score when it submits one. That goes to our own leaderboard service and to nobody else.
- Nothing you play here requests an ad. All four games, Necrowave included. That is about advertising, not about the leaderboard, which works here the same as anywhere.
- Our games are ad-supported. On a game portal, or as an Android app, the advertising software in the build stores identifiers of its own on your device. That is separate from your save file, and it is not something this website does. Section 3 explains it.
1. What this policy covers
This policy explains the use of cookies and similar technologies (local
storage, session storage and IndexedDB) on
omegagamesonline.com, including the playable builds we
host at /play/. It also describes, in
section 3, the storage used by the advertising
software in the builds that carry one — our games distributed through
a game portal or through Google Play. It sits alongside our
Privacy Policy.
Where this page says “this website” or “this site”, it means the pages of omegagamesonline.com and the copies of the games we host here. It is not a statement about our games as distributed anywhere else.
2. Cookies this site sets: none
The site is static: hand-written HTML, one stylesheet, one small JavaScript file and self-hosted images and fonts, all served from our own server. Nothing on it writes a cookie, reads a cookie, or needs one. Specifically, there is:
- no analytics or measurement service of any kind: no Google Analytics, no Plausible, no Matomo, no server-side analytics product;
- no advertising or retargeting tag, and no tag manager;
- no social media buttons, embeds or share widgets;
- no A/B testing, heatmap, session replay or consent-management platform;
- no fonts or scripts loaded from a content delivery network; the two fonts are OFL-licensed and served from this domain;
- no login, so no session or authentication cookie.
Because we set no cookies and use no non-essential storage on our ordinary pages, no consent is required and no cookie banner is shown. You can verify all of this in your browser’s developer tools: the Application panel’s cookie list for this domain is empty.
Our web server writes ordinary access logs, which are described in section 2 of the Privacy Policy. Logs are not cookies and do not involve storing anything on your device.
3. Storage used by the games
Your save file
When you play a game at /play/, the game saves your progress
so it is there next time. It uses the browser’s own storage for this
origin, where the game mounts its save area in
IndexedDB. On Android the same save is written to the
app’s private storage.
The important differences from a cookie:
| Sent to a server? | Browser storage is never attached to an HTTP request the way a cookie is, and the save file is not uploaded. The exception is the leaderboard: in a game that has an online board, the game reads a player key and a display name out of this same storage and sends them, with your score, to our leaderboard service. See below. |
|---|---|
| Readable by other sites? | No. It is scoped to this origin. |
| Readable by us? | No. We have no server-side code that could request it and no way to reach it. What we hold is only what a game submitted to the leaderboard. |
| What is in it? | Gameplay values: best score, coins, unlocks, mute setting, factory state. In a game with an online board it also holds the player key, the display name and a small play record — running totals of how much and how often that copy of the game has been played, and the language and time zone the device reported. The full list is in the Privacy Policy. |
| Is it an identifier? | The gameplay values are not, and nothing in the save is used to recognise you across sites. The player key a leaderboard game keeps here is an identifier, but only for your own row on our board. Identifiers used for advertising are stored separately again by the advertising software, and only in the builds that carry one — see below. |
This storage is strictly necessary to provide the game you asked to play: it is the save file. If your browser blocks storage for this site (a private window with strict settings, for example), the game still runs, but your progress will not survive a reload.
What leaves this storage: the player key, the name and the play record
Wreck Run, Merge Bastion and Daybreak Factory have an online leaderboard, and a board needs to know whose score is whose. So alongside the save, those games keep a player key — a random identifier generated on your device the first time a score is submitted — and, where you have set one, a display name. Alongside them sits a small play record: running totals of when that copy of the game was first and last opened, how many days and sessions it has been played, how long, and how many advertisements it has shown, together with the language and time zone the device reported the first time it ran. All of it lives in the same browser storage or app storage as the save.
Unlike the save, these are sent: at the end of a run the game posts them,
with your score, to a leaderboard service we run at
omegagamesonline.com/api/v1. That happens in the copies hosted
here as well as on a portal or on Android — stripping the portal SDK
removes advertising, not the leaderboard. It is a request to our own server, not
to a third party, and it has nothing to do with advertising: no ad network sees
it. Section 4 of the Privacy Policy lists
every field, says how long we keep it, and explains how to have your entry
removed, which is by email rather than by a button.
Clearing site data or app data deletes the player key and the play record along with the save, so the next run starts a new one and the totals start again at zero. It does not delete the row already on the board. Necrowave has no online leaderboard, and nothing it stores is sent anywhere.
Advertising software stores identifiers
Our games are ad-supported. When a game runs on a game portal or as an Android application carrying ad software — the Android build of every game we publish, as our Privacy Policy records build by build — that software writes and reads identifiers of its own: cookies and browser storage on the web, and on Android the device’s advertising ID together with the ad software’s own local storage. It also handles ordinary technical facts about an ad request — device or browser type, operating system, language, coarse country, and the ad slot being filled.
These identifiers are set and read by the advertising software and the portal, are governed by those companies’ own policies, and are not readable by us. They are separate from the save file described above, which stays on your device. Our Privacy Policy names the advertising software involved and says what it reads and what we never see. Android’s Settings → Privacy → Ads lets you delete or reset the advertising ID and turn off ad personalisation.
The Unity Ads software in an Android build reads and stores identifiers of its own in the same way, Google’s advertising ID among them, and reads an advertising‑consent string if one is present on the device. Resetting or deleting the advertising ID, and turning off ad personalisation, in Android’s Settings → Privacy → Ads applies to it exactly as it does to the rest.
None of that happens in the copies hosted here at /play/,
Necrowave among them: no ad is requested, no ad network is contacted, and the
only things stored are the save file and, in the leaderboard games, the player
key and name described above. In Wreck Run, Merge Bastion and Daybreak
Factory there is no advertising software in the hosted copy at all. Necrowave is
one codebase for both platforms, so its browser build does carry the game’s
own advertising code — but that code only reaches an ad provider on
Android with an advertising plugin installed, so in a browser it loads no ad SDK
and asks for nothing.
4. Third-party scripts in the copies hosted here
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
(site/deploy/sync-builds.sh). Necrowave’s browser build
was never a portal export and has no portal SDK to remove; its advertising
code asks for an ad provider only on Android with an advertising plugin
installed, so in a browser it gets one that requests nothing. While you play
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. The one request that does leave the page is a leaderboard submission,
and it goes to our own server, as
described above.
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 Privacy Policy will say so before it goes live, and the date at the top of the page is the record.
If you play one of our games on a portal such as crazygames.com, that portal’s page is not ours and its cookie notice applies to everything on it, including its advertising.
5. How to inspect and clear this
- Inspect: open your browser’s developer tools and look at Application (or Storage) → Cookies and → IndexedDB for omegagamesonline.com.
- Clear: use your browser’s “clear site data” control for this domain, or clear browsing data with “cookies and other site data” selected. This permanently deletes your saved game progress and your player key; there is no backup.
- Remove a leaderboard entry: clearing site data does not reach it. Email omegasolutionsbusiness@gmail.com with “Leaderboard” in the subject line; the Privacy Policy says what to include.
- Clear what advertising has stored: on the web, clear site data for the portal you played on. On Android, Settings → Privacy → Ads deletes or resets the advertising ID, and clearing the app’s data removes what the ad software stored locally.
- Block: blocking storage for this site is fine; the site works normally and games remain playable within the session.
6. Changes
If we change what this website or the copies hosted here store, we will update this page and the date at the top before the change goes live and, where consent is required, ask for it first. Our games are ad-supported by design, so a change in which advertising software a build carries, or in what it stores, is a change to this page rather than a surprise. The date at the top of this page records the current position.