Skip to content
Legal · LordTracker

Privacy Policy

Last updated: November 17, 2026

On this page

Michael Ketzer ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use and protect personal data when you use LordTracker, our Top Lords alliance tracker at toplordstats.com and lordtracker.com (the "Service"). Personal data is any information that relates to an identified or identifiable person.

Trial and subscription records

We record the account ID, normalised email address, game kingdom and alliance identity, workspace ID, and trial start and end times to enforce the once-per-user and once-per-alliance trial. Trial eligibility records survive workspace deletion and are retained to prevent repeat trials, subject to applicable data protection rights. Paddle receives your checkout email and workspace/account reference, and we store Paddle customer, subscription and processed event IDs to reconcile billing.

Account deletion and workspace archiving

You can delete your account in Account settings. First leave workspaces you do not own. If you own a workspace with other members, transfer ownership to one of them. If you own a workspace with an active paid subscription, cancel it and wait until it ends, or transfer ownership. These checks protect workspace members and prevent paid workspaces from losing their billing owner.

Deletion removes your display name and email from the account, deletes your passkeys and authentication challenges, removes your support threads and replies, removes your memberships and invitations you created, clears written rating feedback and disables your referral code. Existing sessions stop granting access. We keep a pseudonymous account reference for retained billing and referral ledgers, one-time rating rewards, contribution provenance and audit events; it cannot be used to sign in. Trial eligibility records retain the original normalised email and game identity to prevent repeated free trials. They are subject to applicable data protection rights.

Sole-owner workspaces without active paid billing are archived when you delete your account. Archiving hides a workspace from the dashboard, stops collection and revokes sync credentials while keeping game data and history. Archiving a workspace directly keeps its memberships. These records remain until you request erasure, subject to legal retention duties and other workspace members’ rights. Contact us to request erasure of archived game data or review of retained personal records.

Changing your email requires a six-digit code sent to the new address. Existing sessions stay signed in. Passkeys are optional; email codes remain available for recovery. We store passkey public keys, never your fingerprint, face image or device’s private key. Short-lived passkey challenges expire after five minutes and can be used once.

1. Controller and contact

The controller responsible for processing personal data in LordTracker (formerly TopLordStats), the Service at toplordstats.com and lordtracker.com, is:

Michael Ketzer
Email: support@lordtracker.com

For any privacy question or to exercise your rights, contact us at support@lordtracker.com.

DataPurposeLegal basis
Account and sign-in: display name, email address, email-change challenges, optional passkey public keys, device names, counters and use dates, one-time sign-in codes (stored only as a keyed hash), sign-in attempt records, session cookieCreate and secure your account, sign you in, prevent abuseArt. 6(1)(b) GDPR (contract); Art. 6(1)(f) GDPR (security)
Workspace data: selected kingdom, managed alliances, settings, plan, members you invite and their rolesProvide your workspace and enforce access rightsArt. 6(1)(b) GDPR (contract)
In-game data about lords and alliances: in-game names and IDs, alliance tags, ranks, power, hero power, kills and their historyShow rosters, rankings, history and the kingdom overviewArt. 6(1)(b) GDPR for your workspace; Art. 6(1)(f) GDPR (managing an alliance; publicly visible game rankings)
Screenshots you upload and in-game screens captured for auto-syncExtract the text and numbers needed for your importArt. 6(1)(b) GDPR (contract)
Kingdom map scans: the position of every headquarters in your kingdom with the Lord’s in-game name, alliance tag and level, and the game’s replies as receivedShow your alliance a map of its kingdomArt. 6(1)(b) GDPR for your workspace; Art. 6(1)(f) GDPR (managing an alliance; the map is visible to every player in the kingdom)
LordTracker Companion, an optional Android app: the phone’s name, app version and connection dates, chosen alliances, the game account’s Lord ID, kingdom and alliance, its own total hero power, own-alliance VS ranking rows (player IDs, names, scores, day and week), complete alliance rosters, game event IDs and start/end times, and app status reportsConnect your phone, sync authorized alliance data and game schedules, prepare Lord links and hero power readings for review, and find app faultsArt. 6(1)(b) GDPR (contract); Art. 6(1)(f) GDPR (finding faults in the app)
Billing data from Paddle: name, email, country, subscription status and transaction references (no full card details)Manage your subscription and entitlements; accountingArt. 6(1)(b) and (c) GDPR (contract; legal obligations)
Support messages and the email address you write fromAnswer your request and keep a record of itArt. 6(1)(b) and (f) GDPR
Technical logs: IP address, browser and device type, requested page, time of accessOperate and secure the website, investigate errorsArt. 6(1)(f) GDPR (secure operation)

In-game names are pseudonyms chosen by players. We only process in-game data needed to provide the Service. We do not use your data for advertising and we do not sell it.

Public kingdom pages also show castle counts we receive from LordScanner (lordscanner.com), a Top Lords map service run by the same operator: for each kingdom LordScanner has scanned, the number of castles, castles per level band, how many alliances hold at least 50 castles, and when the kingdom was last scanned. These are aggregate counts. They contain no player or alliance names, alliance tags, game IDs or map positions.

Kingdom map scans

Workspace owners and managers on a plan with auto-sync can scan their kingdom’s map. Our collection accounts read the kingdom map in the game, which every player in that kingdom can see, and we store each headquarters on it: its position (X and Y), the Lord’s in-game name, alliance tag and headquarters level. A scan covers every Lord in the kingdom, not only your alliance’s members. To check a scan, we also keep the game’s replies as received for a short time. They carry the same details plus game player and alliance IDs, shield timers and each Lord’s home kingdom.

Map positions are private to the workspace that ran the scan. Only its members who can open that alliance see them. We never show them on public pages, in the public API or to other workspaces, and we do not publish a map. Section 8 says how long scans are kept.

From each completed scan we also keep an overview for the map, built from the same details: the headquarters without game IDs, each alliance’s number of headquarters and their levels, the areas where an alliance’s headquarters stand together, how densely each part of the map is settled, and for each such area how many of the kingdom’s top 200 Lords by total hero power in our public rankings have their headquarters there. That last figure is a count; we never mark which headquarters are theirs. The overview is as private as the positions and is deleted together with them.

A Lord removed through Remove your Lord is left out of our public pages and of these map overviews. Apart from the overviews, that list does not change private workspaces, so a stored scan keeps showing the Lord’s headquarters to the workspace that ran it until the scan’s positions are deleted. You can ask us to delete your Lord from stored scans sooner, or object to this processing, as section 9 describes.

LordTracker Companion (Android app)

The Companion is an optional Android app. Nothing in this part applies unless you install it. On your phone it reads what Top Lords receives from the game’s servers. For that it uses Android’s VPN connection. Only the games you switched on in the app go through it; your other apps do not. When LordTracker authorizes an officer account, it sends read requests for VS rankings, your alliance’s roster and game event windows through the existing game connection. Reads run on connection, hourly, when you refresh, and at 01:30 and 01:58 UTC. It sends no game actions and does not sign in again. If you enable the optional background session, it sends keepalive heartbeats to hold the existing game connection for up to 24 hours after you close the game, so these reads can continue. This option is off by default and ends when you switch it off, stop collection or disconnect.

During normal use, the app sends us the game account’s Lord ID, kingdom and alliance, and that Lord’s own total hero power. It sends them only for a Lord in an alliance you chose for the phone when you connected it. The app learns a Lord’s alliance when the game starts. If the Lord leaves that alliance while the game is open, the app holds its hero power back until the game starts again. Hero power is sent only for a Lord that an officer has confirmed as yours. We use the Lord ID to prepare a link request and the hero power to prepare a reading. An officer of your alliance reviews both before they count.

The app can also send your own alliance’s daily VS ranking rows received from the game: player IDs, names, scores, day and week. Only an authorized officer account’s readings are kept, and they save automatically. A reading only raises a score; it never lowers one or brings back one deleted after the Companion saved it. Opponent rows are excluded. Complete, verified alliance rosters can also sync automatically under the alliance’s existing roster safeguards: player IDs, names, kingdoms and in-game ranks. A VS ranking is never treated as a complete roster.

Authorized officer accounts can also sync supported game event IDs and start/end times to the chosen alliance’s calendar, including event availability windows and Race to Ace phases. These times do not establish battle start times or register players. Officer calendar changes and cancellations are preserved. The app sends no event notices, chat or free-form descriptions with these schedules.

Outside these facts and the optional debug capture below, other game content stays on your phone, including sign-in data, chat and mail. The app forwards it unchanged.

On your phone the app keeps a list of the kinds of messages the game sent and the names of their fields, without their contents, and a short note when the app itself stopped with an error. Both leave your phone only if you share them yourself.

About each connected phone we store the name it gave itself (usually its model), which version of the app it runs, when it was connected and last used, the alliances chosen for it, the game account it last read, and diagnostic reports the app sends so we can find faults: that reading started or stopped and why, that a game session of a Lord in an alliance you chose started or ended, that an upload worked or failed, counts of the app’s own events (how often it connected, read, uploaded or met an error), and yes-or-no or small facts about the phone, such as the Android version, the network type, the battery level, whether the VPN permission is granted, whether battery saving or a background limit is on and whether notifications are allowed. These reports contain no game data and nothing about other players. The phone signs in with its own key, of which we store only a hash.

To offer updates, the app asks our server about once an hour whether a newer version exists. This request names the app’s version and, like every request to a website, comes from your phone’s IP address. It names no account. To limit how often new phones can be connected, we keep a keyed hash of the IP address a connection request came from for up to two days; the address itself is not stored.

The app can also read a second game, for a separate service that is not LordTracker. That is off until you switch it on in the app, which then names the service and lists what it sends. What the app reads from that game goes to that service under its own privacy policy and not to us. The counts of the app’s own events described above cover the whole app.

You can disconnect a phone in the app or under Settings in your account at any time; it can then send nothing more. Section 8 says how long we keep this data.

Optional game message capture (Companion 0.2.8 and newer): only after you choose “Capture game messages for 1 hour” and confirm, the app sends decoded requests, responses and push events from the selected game for support debugging in Reactor. This can include game player IDs, names, scores, unknown commands, timestamps and request IDs. Login credentials, chat, mail body and payment content are redacted on the phone and again on the server. Other apps and browsing are excluded. You can stop at any time; capture does not resume after the app process restarts. Pending messages retry from private app storage for up to 24 hours and are discarded on disconnect. Captures are kept for seven days from the session’s expiry, then deleted by daily cleanup (up to a day later). Captures from the second game go to that separate service under its own privacy policy. The legal basis for this optional sharing is your consent, Art. 6(1)(a) GDPR; stopping withdraws consent for further recording. Contact support to erase a submitted capture.

3. AI processing of screenshots

When you import screenshots, or when auto-sync captures in-game screens for your alliance, the images are sent to Google's Gemini API to extract text and numbers. Google acts as our service provider. The images are used only to process your import; we do not use them to train AI models. Extracted data is stored in your workspace, where you can review and correct it.

4. Payments

Payments are processed by Paddle.com, which acts as our reseller and the Merchant of Record for all orders. Paddle collects and processes your payment details as an independent controller under its own privacy notice. We receive only the information needed to manage your subscription, such as your name, email address, country, subscription status and transaction references — never your full card details.

5. Recipients

We share personal data only where necessary:

  • Service providers acting on our instructions: OVH (web hosting), Cloudflare (website traffic protection), Vercel (retained hosting and object storage), Neon (database), Letterpier (sending and receiving email) and Google (Gemini API for screenshot processing).
  • Paddle, as Merchant of Record, for checkout, payments, tax, invoicing and refunds.
  • People you invite to your workspace, who see the alliance data their role allows.
  • Professional advisers, such as tax advisers or lawyers, where needed and bound to confidentiality.
  • Authorities or courts, where we are legally required to disclose data or need to protect our rights.

6. International transfers

Some providers process data outside the European Economic Area, for example in the United States or the United Kingdom. Where this happens, we rely on an adequacy decision of the European Commission (such as the EU–US Data Privacy Framework for certified providers, or the UK adequacy decision) or on the European Commission's Standard Contractual Clauses, together with additional safeguards where required.

7. Cookies and local storage

We use only cookies and local storage that are strictly necessary to provide the Service: a session cookie that keeps you signed in, security tokens that protect sign-in, and local storage for preferences such as your theme. We do not use advertising or third-party tracking cookies, so no consent banner is needed. You can block cookies in your browser, but you will not be able to sign in.

8. How long we keep data

  • Account data and passkeys: until you delete your account or revoke a passkey, with the pseudonymous and trial records described above retained for their stated purposes.
  • Sign-in codes: expire after ten minutes and can be used once; attempt records are kept only as long as needed to enforce sign-in limits.
  • Workspace and alliance data: while your workspace exists, including when archived. A subscription ending does not erase your game history. Contact us to request erasure.
  • Kingdom map scans: the game’s replies as received are deleted 3 days after a scan finishes. Each alliance keeps the positions of its two newest completed scans; older completed scans lose them once they are 3 days old, together with the map overview built from them. A scan that failed or was canceled loses its positions and replies after 24 hours. What stays of a scan is when it ran, its status and which map areas it covered. The deletion runs once a day, so it can take up to a day longer. Removing an alliance from your workspace deletes all of its scans at once.
  • LordTracker Companion: a phone stays connected until you disconnect it, or until it has not been used for 90 days. 30 days after that we delete the phone’s record with everything that belongs to it. Status reports and the receipts of what a phone sent are deleted after 30 days, and a connection request one day after it expired. The deletion runs once a day, so it can take up to a day longer. Deleting your account deletes your phones at once. Lord links, hero power readings, VS scores, imports and roster readings are alliance data and are kept like the rest of it.
  • Screenshots and captures: kept only as long as needed to process and review the import, then deleted. The extracted data and a fingerprint of each image, used to detect duplicates, stay with your workspace.
  • Billing records: as long as required by tax and commercial law (up to ten years).
  • Support messages: as long as needed to resolve your request and for a reasonable period afterwards.
  • Security and administration audit events: pseudonymous account and workspace references, action and time, retained to investigate security, ownership and billing changes. They contain no email addresses, codes or authenticator responses. You can request review or erasure subject to legal duties.
  • Technical logs: typically up to 90 days.

9. Your rights

Under the General Data Protection Regulation (GDPR) you have the right to:

  • access the personal data we hold about you (Art. 15);
  • rectification of inaccurate or incomplete data (Art. 16);
  • erasure of your data, subject to legal retention duties (Art. 17);
  • restriction of processing in certain circumstances (Art. 18);
  • data portability — receiving your data in a structured, machine-readable format (Art. 20);
  • object to processing based on our legitimate interests (Art. 21);
  • withdraw consent at any time where processing is based on consent, without affecting earlier processing;
  • lodge a complaint with a data protection supervisory authority, in particular in the country where you live or work.

To exercise your rights, email support@lordtracker.com. We respond within one month; where requests are complex or numerous, this may be extended by up to two further months, and we will tell you why.

10. Security

We protect personal data with appropriate technical and organisational measures, including encryption in transit (HTTPS), hashed sign-in codes, role-based access controls and the principle of least privilege. No method of transmission or storage is completely secure, but we work to protect your data and will notify you and the authorities of a personal data breach where the law requires.

11. Children

The Service is not intended for children under 13 (or 16 where local law requires). We do not knowingly collect their personal data. If you believe a child has given us personal data, please contact us and we will delete it.

12. Changes to this policy

We may update this Privacy Policy. The date at the top shows the latest version; for significant changes we will inform you by email or in the Service. Please also see our Terms of Service and Refund Policy.

13. Contact

Questions about privacy at LordTracker? Email support@lordtracker.com. Top Lords is a game by GAME SPARK PTE. LTD.; its own privacy practices are governed by the publisher's policies, not this one.