GamingDiver / Privacy

Privacy Policy

Last updated: November 2026

How GamingDiver Uses Accounts

You can browse public ship/reference pages without signing in. Uploading your own export requires an account so GamingDiver can store your uploads and processed stats securely, restore your dashboard across devices, build trends over time, and give you export/delete controls for stored data.

Upload Processing

When you upload your game data export, GamingDiver reads and parses the file in your browser before saving the upload and processed statistics to your signed-in account:

What We Store

When you create an account and upload data, the following data is stored securely in our cloud infrastructure (powered by Supabase):

All stored data is protected by Row Level Security so only you can access your own data through the application.

How We Use Your Data

GamingDiver staff may access stored data for the following limited purposes:

We will never use your data for advertising, profiling, or selling to third parties.

Authentication Providers

You can sign in with Microsoft, Google, Discord, or email/password. When using a social login provider:

Data Sharing

We never sell or share your personal data with third parties. Your game data and personal information are never sold, licensed, or made available to external parties. Aggregate, anonymized statistics (e.g., leaderboards, global ship performance) may be displayed publicly but will never identify you without your explicit consent.

Fleet pages and Discord digests. A fleet's admin can connect a Discord channel to their fleet page. Each week (or each day, if the admin picks daily) GamingDiver posts a fleet summary there: the fleet's battles and wins and losses, its combined recent win rate, its rank and its top rival, using only what the fleet's public page already shows. The summary can also name members in highlights (their best games and any GamingDiver records they set). A member is only named when their name is already public on GamingDiver (leaderboards), they keep Fleet Sharing on in Profile settings, and the game comes from a replay they made public. Turn Fleet Sharing off and you are left out of every digest.

Discord record feed. When you set a new community record on a ship (Record Damage, Record Frags, Record Planes, Record Base XP or Most Career Frags, in Standard battles), GamingDiver can announce it in a channel of the GamingDiver Discord: the ship, the figure and the name its ship page shows next to the record. The feed never names the player whose record was beaten. Only players who appear in Community Records are named, so turning off Show my name in Community Records in Profile settings keeps you out of future posts; posts already made stay in the channel unless a moderator removes them.

Local Caching

Regardless of account status, GamingDiver stores your processed results in your browser's IndexedDB (local storage). This data:

Minimal Analytics

We use basic analytics to understand site usage and improve GamingDiver. This may include Cloudflare Web Analytics, Google Analytics, Ahrefs analytics, and a public Supabase request for aggregate site counters shown on the landing page.

Battle Replays

If you appear in a replay someone else uploaded, this section is about you.

When a player uploads a battle replay, the file contains information about every player in that battle, not only the uploader. For each player that is: in-game name, clan tag, the ship played, and in-battle performance - damage dealt and taken, kills, position over the course of the match, and the date and time of the battle. We did not get this information from you; we got it from a replay file uploaded by another player who was in the same match.

We use it to produce the tactical replay view, damage attribution, and aggregate community statistics. Some of those aggregate statistics, which never name a player, are part of the paid GD Supporter membership. For players other than the uploader we rely on our legitimate interests in providing battle analysis for a game where this same information is shown in-game to every participant of the match.

Who we are. GamingDiver is operated by QWERTY Holdings LLC, 1001 South Main Street, Suite 49, Kalispell, MT 59901, USA. You can reach us about privacy at [email protected] or at that postal address.

Your rights. You can object to us processing your information, ask for a copy of what we hold about you, or ask us to correct or erase it. To object, email [email protected] with your in-game name; we will suppress your name from public replay views and from community statistics. Suppression is applied to your game account, so it keeps working if you later change your in-game name. You can also complain to your data protection supervisory authority.

Who can see a replay. Uploaders choose who can see each replay: only themselves (private), their fleet, one tournament team they play on, or anyone (public). Watching or uploading a replay on GamingDiver requires a free account. A private replay is visible only to its uploader, and to GamingDiver administrators solely for the purpose of site quality, such as fixing a replay that did not process correctly; we do not browse private replays for any other reason.

Tournament matches. When the players on both sides of a replay match the registered rosters of two teams in a GamingDiver tournament, we label the replay as a scrim or an official match and list it on those teams' tournament and fleet pages. This never changes who can see it: the uploader's choice always applies, and a private replay stays private.

Scorecard screenshots. Uploaders can attach the end-of-battle Personal and Team Result screens (free accounts must). We read them automatically to get each player's exact Base XP and kills for that battle. The images themselves are never shown to other users.

Improving accuracy. To check how accurate our replay analysis is, we compare what a replay shows with the exact per-battle figures in stats exports that players have uploaded to their own accounts, and with other uploads of the same battle. The results we keep and publish are aggregate figures with no player names. Players who have objected, or who have opted out of leaderboards, are left out of this work.

How long we keep it. We keep uploaded replay files and the battle data derived from them for as long as the uploader keeps the replay on GamingDiver. While a replay is on GamingDiver we also keep a research copy of it for up to 24 months to improve our replay processing and support our Base XP research, after which we remove player names and keep only anonymised statistics. When an uploader deletes a replay, or deletes their account, we remove the replay, its Debrief and its research copy from GamingDiver within 30 days. From a deleted replay we may keep a de-identified record of the battle's game data. Our backups are kept for up to 6 months and are used only to restore the site after a failure, so a deleted replay can remain in a backup until that backup expires. If you have asked us to suppress your name, we keep a record of that request indefinitely, so that the suppression continues to apply to future replays.

Purchase records are an exception. If you have bought a supporter subscription or a Founding Contributor entitlement, we keep the record of that purchase after you delete your cloud data, because we need it for accounting. It contains the account it belonged to, what was bought, when it started and ended, and the reference IDs our payment provider uses for the customer and the subscription. It does not contain your card details, which only the payment provider ever holds. Everything else described above is still removed. If you want your purchase records erased as well, email [email protected] and we will handle it by hand.

Your Rights (GDPR Compliance)

If you have an account, you have the following rights:

Export Your Data

Download a complete copy of all your stored data (profile, uploads, statistics) as a JSON file.

Delete Your Cloud Data

Remove your stored exports, processed snapshots, upload history, monthly reports, uploaded battle replays and their Debriefs, and profile fields from GamingDiver cloud storage. Records of any supporter or Founding Contributor purchase are kept for accounting, as described under How long we keep it. Tournament pick’em entries you made are also kept, removed from public leaderboards, so organizers can check results and prize eligibility. They keep your picks and the name you played under, and only a one-way scrambled fingerprint of your email and game account, not the address or account itself. This action cannot be undone. Local browser cache may remain until you clear it separately. Full authentication-account deletion requires a privileged backend/admin deletion flow; contact support if you need the login account removed entirely.

Clear Local Data

To remove all cached data from your browser (this does not affect cloud data):

  1. Go to the dashboard and click "Clear Data"
  2. Or clear this site's data in your browser settings

Verify It Yourself

GamingDiver's client-side code is open and inspectable: