DEEPWORKS
Privacy
PRIVACY POLICY

DEEPWORKS is a browser game. It collects a small amount of anonymous gameplay data to balance the game and to run the leaderboard. It does not sell your data, does not run ads, and does not track you across other websites.

Last updated 2 September 2026

The short version

  • No email address, no password, no real name. You can claim a callsign for the leaderboard if you want one; it is optional and it is the only thing you ever type in.
  • No advertising, no ad networks, no cross-site or third-party tracking.
  • Your personal information is never sold or shared for money or for anything else.
  • What is collected is gameplay telemetry tied to a random identifier, plus the country your request came from.
  • You can turn collection off entirely, on this page, at any time.

What is collected

When you play, the game sends gameplay events to our own server at /api/e. Every field is listed here.

DataWhat it is and why
Random player idA random UUID generated in your browser and kept in your browser's local storage as dw_pid. It is not derived from anything about you or your device — it is just a random number. It exists so a player's second run can be told apart from two different players' first runs.
Run id and run numberA fresh random id per run, and a count of how many runs you have started. Used to group the events of one run together.
Gameplay eventsRun started, wave reached, death, run completed, boss attempted, boss killed, which weapon, ability or upgrade you picked, a Legendary found, weapon mastery reached, and at the end of a run a per-weapon summary (shots, hits, damage, headshots, kills) and the run's credit economy (earned, spent, unspent). Upcoming releases add holdout completions and attachment pickups, fits and sales. The exact event names are run_start, wave, death, run_complete, boss_attempt, boss_kill, weapon_select, ability_select, upgrade_select, legendary, weapon_stats, run_end, mastery, holdout, attach, part_found and part_sold; anything else is discarded by the server.
Run detailsIn-game numbers attached to those events: wave number, kills, credits, combo, weapons and rarities, ability and tier, upgrades taken, and time taken to kill the final boss.
Game versionThe build you played, so a balance change can be separated from the runs before it.
Callsign and recovery code (optional)If you choose to claim a callsign it is stored against your random player id and shown on the leaderboard for your runs. The one-time recovery code that lets you restore that callsign on another device is stored only as a SHA-256 hash; we cannot read it back and cannot recover it for you if it is lost. Claiming is never required and declining costs nothing.
CountryA two-letter country code, determined by Cloudflare from the network your request arrived on. Country level only — not a city, not a region, not a precise location.
TimestampWhen the event happened, set by our server rather than trusting your device's clock.

What is not collected

  • No email address, phone number, password, or payment details. A callsign, if you claim one, is a name you choose for the leaderboard, not your real name, and we ask you not to use one.
  • Your IP address is not stored. Cloudflare, which serves this site, necessarily processes it to deliver the request — as any web host does — and we derive only a country code from it. The address itself is never written to our database.
  • No cookies are set. The random player id lives in local storage, not a cookie, and is never sent to another site.
  • No mouse tracking, no keystroke logging, no screen recording, no fingerprinting.

What is published

The leaderboard is public. For each of the 25 fastest Overseer kills it shows the country, the game version, the weapons and ability used, and the time taken.

Your random player id and run id are never published and never leave the database — the leaderboard query does not read those columns. Nothing on the leaderboard names a person unless you have claimed a callsign, in which case your rows show it instead of staying anonymous.

One honest caveat: a country code plus an exact time is not a name, but if very few people from a given country have finished the game, someone who already knows you played could reasonably guess which row is yours. If you would rather not appear at all, opt out below and your runs will not be recorded.

Do Not Sell or Share My Personal Information

We do not sell your personal information. We do not share it for cross-context behavioural advertising. We never have, and there is no version of this site that does.

There is no advertising business here, no data broker, no analytics vendor, and no third party receiving gameplay data. There is therefore nothing to opt out of in the "sale" sense — but you can still switch off collection completely:

Checking…

Third parties

  • Cloudflare hosts this site and stores the gameplay data described above, on our behalf, as our infrastructure provider. It processes your IP address to serve the request.
  • Google Fonts supplies the two typefaces these pages use. Your browser requests them from fonts.googleapis.com and fonts.gstatic.com, which means Google receives your IP address and user agent as part of that request. No gameplay data is sent to Google, and no font request carries your player id.

That is the complete list. There are no other embeds, pixels, tags, or SDKs on this site.

How long it is kept

Gameplay events are kept while they are useful for balancing the game and for the leaderboard. Because the data holds no real name, email, or address, it is not personally identifying on its own. A claimed callsign stays for as long as you keep it; write to us if you want it removed.

Your choices and rights

  • Turn it off. Use the control above. Nothing is sent while it is off.
  • Break the link. Clearing this site's local storage in your browser discards the random player id. A new one is generated the next time you play, and previously recorded runs can no longer be associated with you — that id was the only thing connecting them.
  • Ask about your data. Depending on where you live you may have rights to access, correct, delete, or port personal information, and not to be discriminated against for exercising them. Because we hold no identifier that can be matched to a person, we usually cannot locate "your" rows on request — but you can reach us at developer@playdeepworks.com and we will help however we can.

Contact

Questions about this policy, a request about your data, or anything else about the game: developer@playdeepworks.com. We read everything and answer within a few days.

Children

This game is not directed at children under 13, and we do not knowingly collect personal information from them. Since no email address or personal details are ever requested, and a callsign is a made-up name rather than a real one, there is nothing here for a child to hand over.

Changes

If this policy changes, the date at the top changes with it and the change is noted in Updates.

© 2026 DEEPWORKS. All rights reserved.
The DEEPWORKS name, game, artwork, and source are the property of their author. No part of this site or game may be reproduced, redistributed, or used to train machine-learning models without permission.