Privacy Policy

• Your progress is saved in your browser. It is not sent to a GamerDex server.
• Cloud sync is optional and off until you turn it on. When it is on, your data goes to your own GitHub or Google Drive account and nowhere else.
• We cannot read your data, because it is not on any server that we run.
• We do not show ads, sell data or share data with anyone.
• We count visits with privacy friendly page statistics from Cloudflare. Our own code sets no cookies.

GamerDex is run by an independent developer. The trackers are fan made and are not affiliated with, or endorsed by, any game publisher. In this policy, "we" means GamerDex. You can reach us as described in the Contact section.

Every tracker saves what you enter, such as levels, goals, notes and settings, in your browser's local storage on your device. This is how the trackers work without an account. The data does not leave your browser unless you export a backup file yourself or turn on cloud sync. Local storage also holds your preferences, such as language and theme.

If you clear your browser data, this information is deleted. Export a backup file from time to time to keep a copy.

Some trackers can keep your progress in your own cloud account so that your devices stay in step. Today this is available in the Whiteout Survival Tracker with GitHub or Google Drive. You choose the provider, and you can disconnect at any time.

What is stored and where

Two small files are saved in your account. The data file holds your progress, in the same format as the backup file that you can export. The meta file holds the names of your devices and the time of the last sync. They are saved in a folder named Gamerdex, inside a subfolder for the tracker. With GitHub this is a private repository named gamerdex-data that you create. With Google Drive it is a visible folder named Gamerdex in your Drive. The files do not contain your sign in details.

How the sync works

Your browser talks to your cloud provider directly. Changes from several devices are merged in your browser. GamerDex does not receive a copy of your data.

Signing in

To sign in we use a small sign in service at auth.gamerdex.app. Your browser sends it the one time code that the provider gives you, or a refresh token to renew your access. The service exchanges it with the provider, using app credentials that only the service holds, and returns your tokens to your browser. The service stores nothing. It does not log your tokens or your data, and its logs record only technical error codes. Your tokens are kept in your browser's local storage on that device and are never uploaded.

Google Drive

• We ask for one permission only, the Drive file scope (https://www.googleapis.com/auth/drive.file). It lets GamerDex create and open only the files and folders that it created itself. It cannot see, list or change any other file in your Drive.
• We do not ask for your email address, your name or your profile.
• We use the access only to save and load your tracker data for you. We do not use it for anything else.
• We do not read your Google data and we do not transfer it to anyone.

GamerDex's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

GitHub

Gamerdex Sync is a GitHub App. You install it on one repository that you choose. It can read and write the contents of that repository and read its basic metadata. It cannot reach your other repositories or your account settings. The tracker syncs only to a private repository and does not use a public one.

Other providers

We may add other providers later, such as Microsoft OneDrive or Dropbox. They are not available today. If we add one, it will use the narrowest access that the provider offers, the rules in this policy will apply to it, and we will update this page before it is released.

Our websites use Cloudflare Web Analytics to count visits and to see how fast pages load. It reports aggregated statistics, such as which pages are viewed, where visitors come from, and the browser and device type. Cloudflare states that it does not track individual visitors across websites. We do not use these statistics for advertising, and we do not link them to your tracker data. See Cloudflare's privacy policy for details.

GamerDex does not set cookies. We use your browser's local storage, as described above, to save your progress, your preferences and, if you turn on sync, your sign in tokens. The trackers need this to work. The companies that deliver our websites may use technical cookies for security.

Our websites are delivered through Cloudflare. The sign in service runs on Vercel. Like any web host, they process technical request data, such as IP addresses, to deliver pages and to keep the service secure.

Your cloud provider handles your synced data under its own privacy policy. See the privacy policies of Google, GitHub, Vercel and Cloudflare.

• Stop syncing. In the tracker, open Settings, then Cloud sync, then Disconnect. This removes your tokens from that browser. Your data stays where it is.
• Delete the cloud copy. Delete the Gamerdex folder in your Google Drive, or the Gamerdex folder in your gamerdex-data repository on GitHub.
• Remove our access. For Google, open your Google Account permissions page and remove Gamerdex. For GitHub, open Settings, then Applications, and uninstall or revoke Gamerdex Sync.
• Delete the local copy. Clear the site data in your browser, or reset the data in the tracker settings. Export a backup first if you want to keep it.

Because we hold no copy of your data, there is nothing for us to delete on request.

Your cloud files are protected by your provider's security and by your own account. Sign in tokens are kept in your browser on your device, so anyone who can use your browser profile can use them. If you use a shared computer, disconnect sync when you are done. Our websites use HTTPS.

GamerDex is not directed at children under 13. We do not knowingly collect personal information from anyone.

We may update this policy. The date at the top shows the latest change. If we add a cloud provider or change how we handle data, we will update this page before the change takes effect.

If you have a question about this policy, open an issue on GitHub or message us on Discord.