FatesForge Tracker is a desktop app that records your own matches in Might & Magic: The Card Game, and fatesforge.app is its website. This page explains what information it collects, where that information goes, and what you can turn off.
The short version: the tracker reads your game’s own network traffic to record your matches on your own computer. Some of it is sent to our server — mostly anonymised match statistics, and your match history only if you use cloud backup. We do not sell anything to advertisers, and there are no cookies, no analytics and no third-party trackers on this site.
Who is responsible
FatesForge operates FatesForge Tracker and fatesforge.app, and is responsible for the information described here.
For any privacy question or request, including deleting your data: [email protected]
What stays only on your computer
Most of what the tracker records never leaves your machine. Your match database, your card statistics, your decks and your settings are stored locally in your Windows user profile. If you never turn on cloud backup, that data stays there.
The tracker works by reading the game’s own encrypted network traffic on your computer to see what happens in your matches. It does not modify the game, and it never sees your game account password.
What the desktop app sends us
1. Anonymised match statistics — on by default, and you can turn it off
After each match the tracker sends the match’s identifier, your hero and faction, your opponent’s hero and faction, your deck’s name and card list, the result and the game mode. This is what powers the community statistics — win rates and popular decks. It is tagged with your player identifier so the same match is not counted twice.
You can turn this off in the tracker’s settings, under community statistics. Turning it off stops future submissions.
2. Diagnostic and error logs
So that crashes and tracking failures can be found and fixed, the tracker sends error and warning logs roughly every five minutes while it is running. These contain your player identifier, the app version, your operating system and processor type, and the log entries themselves — error messages, which part of the app they came from, and technical details such as a match identifier, a hero name or a software error trace.
There is currently no setting to turn this off. We would rather say that plainly than bury it. These logs exist to fix faults; they are never used to build a profile of you and are not shared with anyone. A session with no errors uploads nothing at all. If you want your diagnostic logs removed, email us and we will delete them.
3. Cloud backup — only if you enable it
If you have a PRO subscription and use cloud backup, your match history, match action records, decks and deck version history, and a short list of your tracker settings are uploaded to our storage so you can restore them on another computer. This is stored under your player identifier.
What the website collects
- Signing in. You sign in with your game account. The website stores a sign-in token and your preferences in your browser’s own local storage so you stay signed in. The site does not use cookies, and there are no analytics or third-party tracking scripts of any kind.
- Published decks. If you choose to publish a deck, the deck, the name you give it and your chosen public handle become visible to everyone. Likes, view counts and reports on published decks are recorded.
- Messages and reports. If you contact support or report a deck, we keep the message and your player identifier so we can reply.
- Hosting. The site and server run on Cloudflare, which processes technical request information such as IP addresses in order to deliver and protect the site.
Payments
Card payments are handled by Stripe. We never see or store your card details — only a payment reference and whether your subscription is active and until when.
If you pay with cryptocurrency, we store the transaction reference, the wallet address you paid from, and which network you used, so that the payment can be verified and cannot be submitted twice. Transactions on a public blockchain are public by their nature: that is a property of the blockchain, not a choice we make.
Who can see your data
No other player can read your cloud backup, your match history or your private settings. The backup system identifies you from your verified sign-in rather than from anything you could type, specifically so that one account cannot request another’s data.
Being honest about the limit of that: as the operator we hold the credentials to the storage, so we are technically able to read what is in it. Our commitment is that we only do so when it is necessary to operate or fix the service — investigating a failed backup, or a reported deck — and never to look up a particular player’s decks or match history out of curiosity or competitive interest.
How long it is kept
- Anonymised match statistics are kept indefinitely, because the community statistics are built from them.
- Diagnostic logs are kept until they are no longer useful for debugging. We would rather say that than publish a number we are not yet enforcing automatically.
- Cloud backups are kept while your account exists, so they are there when you reinstall.
- Published decks stay published until you unpublish or delete them.
Your rights
You can ask us to show you what we hold about you, correct it, delete it, or send it to you in a portable form. You can also object to the anonymised match statistics — the settings toggle does this directly, and you can ask us to remove past submissions.
There is no self-service “delete everything” button today. Email [email protected] and we will do it by hand, within 30 days and usually much sooner.
If you are in the EU or UK and you believe we have handled your data badly, you can complain to your national data protection authority.
Children
The tracker is not intended for children under 16, and we do not knowingly collect their data.
Changes
If this policy changes in a way that matters, we will update the date at the top and say so in the tracker’s release notes.