Privacy Policy

The short version

No ads, and nothing is sold. We count visits with our own software on our own server, without cookies and without following anyone between sites. Accounts are optional. Everything public works without one. If you choose to log in with Discord, we store the minimal identity Discord provides (ID, username, display name, avatar) and, only if you choose to link it, your public Embark ID. The bot cannot read your messages, and the only thing stored about a Discord server is the channel config you set.

Linking with the browser extension uses your Embark login session: clicking Verify & link gives us specific permission to use your Embark session token and browser session, one time, to read your username from Embark's API. We read it once, keep only your Embark ID and account number, and discard the session immediately. The in-game code method uses no Embark session at all.

One thing to know before you link: if you link an Embark ID, your Discord user ID can be shared as proof that the account is yours, but only with partners we approve by hand (a tournament organizer, a community bot). It is never published openly. Details are in Linking your Embark ID below; unlinking removes it immediately.

What the bot stores

One small database, holding only what the features need:

· the server (guild) ID and the channel IDs you set with /config
· the date of the last daily forecast post, so it is not posted twice
· a list of already-announced bans (leaderboard name and detection time), so the same one is not posted twice

That is the entire list. No Discord user IDs, usernames, avatars, member lists or message content are stored.

What the bot cannot see

The bot has no Message Content intent, so what people write in your channels is never delivered to it. It does receive message metadata (ids and timestamps), used only to tell whether its own feed post is still the newest message in a channel you configured; none of that is stored. Beyond that it only receives the slash commands people explicitly run on it. The player name you type into /stats is used to build the reply and is not written to any database. If you run /stats with no name, your Discord user ID is used at that moment to check whether you linked an Embark ID on the website. The check is not logged or stored by the bot. Operational logs record errors and counts for debugging, not a record of who ran which command.

Deleting your data

Remove the bot from your server and its stored configuration is deleted automatically. /config disable switches a feature off without removing the bot.

The website

Browsing the site requires no account and sets no cookies until you log in. Small preferences (your light/dark theme choice, and whether to show "Login" or "Account" in the top bar) are kept in your browser's local storage and never leave your device.

We do measure traffic, with our own installation of Umami running on our own hardware. For each visit it records the page you opened, the site that linked you here, and the details your browser announces to every site it visits: browser, operating system, device type, rough screen size and language. It also works out an approximate location - country, region and city - from your IP address.

It sets no cookies and stores nothing on your device, and your IP address itself is never kept: it is used once, hashed together with your browser details, only to group the pages of one visit into a single session. Nothing follows you to other websites, nothing names you, and the numbers go to nobody but us. There are no ad networks, embedded third-party trackers or fingerprinting.

As with any website, the hosting and proxy layer keeps standard request logs (IP address, timestamp, requested path, user agent) for a short period, purely to keep the service up and to stop abuse. These logs are not used to profile visitors and are not shared or sold.

Optional accounts: log in with Discord

Signing in uses Discord's standard OAuth flow with the smallest scope Discord offers (identify). We receive and store your Discord user ID, username, display name and avatar, plus first- and last-login times. We do not receive your email address, your servers, your friends or your messages. The scope doesn't include them.

Logging in sets one login cookie so you stay signed in (it expires after about 30 days), plus one short-lived cookie that exists only for the minutes of the sign-in handshake itself. Both are functional cookies for your session only. Neither is used to track you, and no third party can read them.

You can log out at any time. To delete your account entirely, email [email protected] from a way we can verify and we will remove it.

Linking your Embark ID

Linking is optional. If you link, we permanently store your Embark ID (name#tag), the handle already shown on the public leaderboard, and Embark's internal account number for your account. That number is kept as a record only. It is never shown on the site and is never available through the public API. We never store your Embark password or email.

Account numbers collected before 16 August 2026 were deleted at the time. They were restored on 22 September 2026, and collection resumed the same day.

To confirm you really own the account, linking uses the finalstracker.net browser extension, and this method uses your Embark login session. Clicking Verify & link is what grants the permission: by using this linking method you give finalstracker.net specific permission to use your Embark session token and browser session, one time, to read your username from Embark's API. Nothing is read until you click, and choosing not to link means we never touch it at all.

What that permission covers, and nothing more: the extension reads your Embark (id.embark.games) session and sends it to us once, over an encrypted connection. We use it to read your Embark profile a single time, directly from Embark, keep your Embark ID and Embark's internal account number from that read, and discard your session immediately. The rest of what that profile returns, including your email and date of birth, is read past and never kept. The session is held in memory for that one request; we do not store it, log it, or use it for anything else, and the extension itself keeps nothing. We never use it to make any change to your Embark account. The extension only reads id.embark.games cookies, only sends them to finalstracker.net, and only when you click.

If you would rather not install anything, the alternative is the in-game name challenge: we show you a one-time code, you add it to your Steam name (or PSN / Xbox gamertag) and load into the game, and we read it back off the public leaderboard we already collect. That route involves no Embark session and no extension at all, and we store nothing beyond the same Embark ID. No account number is collected on that route. It only works for accounts in the tracked top 10,000, since that is all Embark publishes. The code is discarded once the link is made, or after 24 hours if you never finish.

What a link is used for: your leaderboard entry shows a claimed checkmark (visible to everyone), and the Discord bot can pull up your own card when you run /stats with no name. Profile cosmetics use the same link: your name colors and which of your tournament badges displays beside your name.

Your Discord user ID may be shared as proof that you own the account, but only with approved partners. Our API can report which Discord account owns a verified Embark ID, so that a tournament organizer or a community bot can confirm a claim without taking the claimant's word for it. That is the point of verifying: it lets you prove an account is yours somewhere we have no involvement.

It is not public. That lookup sits behind an access key we issue by hand, to named parties who tell us who they are and what they need it for, and it can be revoked at any time. The open, key-free part of the API says only whether an account has been verified, which is the same thing the checkmark on the leaderboard already shows. It never says by whom. We do this so that a Discord user ID cannot simply be harvested next to an in-game name by anyone who asks.

What is shared with an approved partner is the numeric Discord user ID and the Embark ID it is linked to, and nothing else: not your Discord username, display name, avatar or email. If you would rather your Discord and Embark accounts were never connected for anyone, do not link one, or unlink: everything on the site works without an account.

Unlinking is self-service on your account page, deletes the stored Embark link immediately, and removes it from those lookups with it. The internal account number recorded when you linked is kept.

Re-verifying. If you rename your Embark account, the link can end up pointing at a name that no longer exists. Re-verifying repeats one of the checks above and moves the link to your current Embark ID. It stores nothing new: the same Embark ID, updated, and the same account number.

The public API

We publish a free public API serving the same leaderboard data the website shows: standings, rank score history, seasons, cutoffs, renames, tournaments and badges. It needs no account and no key, so anyone can read it.

The open part carries only data that is already public on this site. Nothing about a visitor appears in it, and nothing about you appears in it unless you have linked an Embark ID, in which case it says that the account is verified but not who verified it.

The ownership lookup is the one restricted part. It returns the Discord user ID behind a verified Embark claim, it requires an access key we issue individually, and we keep a record of which key was issued to whom so that access can be withdrawn. See the section above.

Calls to the API are subject to the same short-lived request logs as the website (IP, timestamp, path), kept to keep the service up and stop abuse, and not used to profile anyone.

Player data on the leaderboard

The tracker mirrors public information that Embark Studios publishes on its ranked leaderboard: in-game name and tag, rank, rank score, league, and any platform handles shown publicly there, plus the history we build from repeated snapshots. No private information, email addresses, real names or player IP addresses are collected, because we never have them.

If you are a player and want your entry hidden from this site, email us and we will remove it. Note that we cannot remove you from Embark's official leaderboard, only from here.

Third parties

Only two are involved: Discord, which delivers the bot's messages and provides the optional sign-in, and applies its own privacy policy to both, and Embark's public leaderboard, which is the source of the data (and, for the optional Embark link, confirms the account you own, see above). We do not sell anything, and we do not hand your data to advertisers, data brokers or analytics companies - the visitor statistics described above run on our own server, which is exactly why they add no third party to this list.

Our API is not a third party, but it is worth being plain about: the open part makes the public data on this site readable by anyone, and we have no control over who reads it or what they build with it. The restricted ownership lookup is different: it goes only to parties we approve individually, and we can withdraw it.

Children

The service is not directed at children under 13, and Discord's own terms require users to be at least 13 (or older where local law says so).

Changes and contact

If this policy changes, the date above is updated. Questions, data or removal requests: [email protected].

See also the Terms of Service.