Privacy Policy
Effective date: 2026-08-16
This policy explains what TrackXP collects, why, who else sees it, how long we keep
it, and what you can ask us to do about it. It is written to be read — if anything here is
unclear, ask us and we will fix the wording.
1. Who we are
TrackXP ("we", "us", "our") is the controller of the personal information described
here — in California terms, the business; in Canadian terms, the organisation
responsible for it. TrackXP is a trading name; if the registered company name changes,
this page will show the new one and the change will be noted under
Changes.
Privacy contact: [email protected].
We have not appointed a data protection officer. We are not required to have one: we are a
small operation, we do not carry out large-scale monitoring, and we do not process special
category data as a core activity.
2. What this covers
This policy covers trackxp.com, forum.trackxp.com, and the TrackXP games — currently
trivia.trackxp.com, quest.trackxp.com, vtt.trackxp.com and karaoke.trackxp.com, plus any
further TrackXP game we launch on a trackxp.com address. It also covers the TrackXP Discord bot
and Discord Activities, and the TrackXP forum, which we run ourselves on our own servers.
It does not cover other companies' services that you reach from ours. When a page loads
something from a third party — YouTube playback in a karaoke room, for example — we say so
below and that company's own policy applies to what it collects.
3. The short version
- We do not sell your personal information, and we do not share it for
cross-context behavioural advertising. We run no ad networks and set no advertising cookies.
- You can play most games without an account. A guest gives us a display
name, not an identity.
- TrackXP is passwordless. We never hold a password for you.
- Karaoke microphone audio never leaves your device. Only the recognised
words and their timing are sent to us, so a performance can be scored.
- Game replays are private by default and in-game chat is never public.
- Required technologies keep TrackXP secure and make sign-in and games work. Optional
cookies are under your control; today the only optional category is analytics.
4. What we collect and why
The table below is the complete picture. "Legal basis" is the ground we rely on under the EU
and UK GDPR; it is explained further in section 6. "Retention" is
summarised here and expanded in section 9.
| Category | Examples | Where it comes from | Why we use it |
Legal basis (EU/UK) | Retention |
| Account identity |
Username, email address, account creation and last sign-in time, account status and
role, a phone number if you add one for text sign-in, and your chosen profile, history
and presence visibility settings. |
You, when you create or edit an account. |
Creating and running your account, signing you in, and applying your visibility
choices. |
Performance of a contract. |
While your account exists. |
| Sign-in and security credentials |
Short-lived sign-in codes (stored hashed, single-use), session records (we store only a
hash of the session token), a hashed browser identifier used to recognise new-device
sign-ins, passkey public keys, an encrypted authenticator secret, and hashed single-use
recovery codes. |
You, and generated by us when you sign in or enrol a second factor. |
Signing you in and keeping other people out of your account. |
Performance of a contract; legitimate interests in account security. |
Codes 10 minutes. Sessions up to 30 days. Recognised devices while your account exists.
Factors until you remove them. |
| Forum identity link |
Your verified TrackXP username and email as provisioned to the TrackXP forum, plus the
internal identifier linking the two records. |
Derived from your TrackXP account. |
Making one TrackXP identity work on the site, the games and the forum. |
Performance of a contract. |
While your account exists. |
| Gameplay data |
Room codes, player and team names, answers, dice rolls, scores, placements, sung-line
results, story events, XP, achievements, collectibles and game history. |
Created as you play. |
Running a game, resuming one that was interrupted, showing your history, and awarding
XP. |
Performance of a contract. |
Kept so you can review past games; see section 9. |
| Guest participation |
A display name and tag, the game you joined, first and last seen times, and — if you
later claim it — the account it was claimed by. |
Created when you join a room without an account. |
Keeping you in the right seat, letting you rejoin after a refresh, and letting you
claim your results if you make an account. |
Performance of a contract; legitimate interests in running a fair room. |
No automatic expiry today; see section 9. |
| Content you submit |
Trivia Arcade questions, images and avatars you upload, in-game chat, campaign and adventure
text, karaoke song charts, sabotage packs, setlists and stage kits — including any
instrumental you upload as a backing track — plus forum posts. |
You. |
Showing your content to the people you meant to show it to, and moderating it. |
Performance of a contract; legitimate interests in moderation and rights protection. |
Until you or we remove it; see section 9. |
| Karaoke speech results |
The recognised words, their timing, and the recogniser's per-word confidence.
Not the microphone audio, which never leaves the device. |
A speech-recognition model running inside the singer's own browser. |
Scoring the performance against the words on screen. |
Performance of a contract. |
With the game's result record. |
| Moderation records |
Reports you or others make, staff moderation decisions, and files moved to quarantine
as evidence. |
You, other players, our automated moderation, and our staff. |
Enforcing our Terms, protecting other people, and keeping a record
of why we acted. |
Legitimate interests in safety and enforcement; legal claims. |
Quarantined files auto-expire after 30 days; decisions are kept as a record. |
| Technical and security data |
IP addresses, request logs, rate-limit counters, security audit entries, and the
two-letter country of your most recent sign-in. |
Automatically, from your device's connection. |
Keeping the service up, rate limiting, detecting and investigating abuse, and
recovering from incidents. |
Legitimate interests in security and abuse prevention. |
See section 9. The sign-in country is moderation-only and is
never shown on your profile. |
| Feedback and diagnostics |
The message you write, your verified username if you have a valid session, and — unless
you opt out — a limited diagnostic snapshot. |
You, when you choose to send feedback. |
Understanding and fixing the problem, and replying to you. |
Consent; legitimate interests in fixing our software. |
Held in our private error-monitoring project. |
| Analytics |
Google Analytics 4 measurement of page and game usage, with IP anonymisation enabled. |
Automatically, when you open a page. |
Understanding aggregate usage and whether a release broke something. |
Consent (Art. 6(1)(a)). |
Up to 24 months (Google's cookies). |
| Linked Discord account |
Your Discord user id, username and avatar, and the server and channel you choose as a
destination for game announcements. |
Discord, if you choose to link it. |
Posting game announcements where you asked, and letting you play in a Discord
Activity. |
Consent (you choose to link); performance of a contract thereafter. |
Until you unlink, or your account is deleted. |
| Linked Fluxer account |
Your Fluxer user id, username and avatar. |
Fluxer, if you choose to link it. |
Connecting your Fluxer identity to your TrackXP account so Fluxer integrations can act
as you. |
Consent (you choose to link); performance of a contract thereafter. |
Until you unlink, or your account is deleted. |
| Linked Twitch account |
Your Twitch user id, login, display name, avatar URL, and granted scopes. |
Twitch, if you choose to link it. |
Posting your lobby links in your channel and, if you enable the bot, reading chat there. |
Consent (you choose to link); performance of a contract thereafter. |
Until you unlink, or your account is deleted. |
| VRChat world registrations |
A world name, an optional VRChat world id, and a feed key. |
You, when you register a world; the feed key is generated by us. |
Showing TrackXP game state on your world's board. The public feed shows only what the
game's big screen shows. |
Performance of a contract. |
Deleting a world disables its feed immediately; the disabled registration remains until
your account is deleted. Rotating the key replaces the old one. |
| Waitlist |
An email address left on the coming-soon page, the IP it came from, whether we have
invited you yet, and the date/version evidence for your Privacy Policy acknowledgement
and waitlist/launch email opt-in. |
You, if you ask to be told when we open. |
Telling you when TrackXP opens, and stopping the form being abused. |
Consent; legitimate interests in abuse prevention. |
Until we launch or you ask us to remove it. |
How the cookie choice works. The first time you open TrackXP we explain the
required cookies and offer equally prominent choices to use required cookies only or allow
optional cookies. In the EEA, the UK and Switzerland optional analytics does not
load until you say yes; elsewhere analytics runs while the banner is up and stops on the
current page the moment you reject. Other active TrackXP tabs normally follow within about
one second, and background tabs re-check when you return to them. Your answer is kept in the txp_consent cookie for 12 months and
applies across trackxp.com and every TrackXP game. If your browser sends Global Privacy
Control we treat that as a rejection and do not ask. You can change your mind at any time on
Your privacy choices, and withdrawing is as easy as consenting.
The full detail is in the Cookie Policy.
We do not ask for, and do not want, special category data — racial or ethnic origin, political
opinions, religious beliefs, trade union membership, genetic or biometric identifiers, health,
sex life or sexual orientation. Please do not put it in a username, a chat message, a
submission, or a feedback report.
5. The parts that need more detail
Microphone audio in Sabotage Karaoke
The microphone is opened only on the device holding the mic, and only while a song is being
scored — never on the phones of the crowd voting on it. A speech-recognition model downloaded
by the game runs inside that browser and turns the singing into words on the device. Microphone
audio is not uploaded to TrackXP or to a browser speech provider. Only the recognised words,
their timing, and the recogniser's per-word confidence are sent to the game server, where they
are matched against the words on screen to score the performance. We do not record or store
audio of a performance. A room can also be scored by crowd vote alone, which uses no microphone
at all.
Game logs, replays, and in-game chat
- Game replays are private by default. A game's replay (questions, rolls,
scores, story events, sung-line results) is visible to the game's host, to signed-in players
who took part in that game, and to TrackXP staff. It becomes publicly viewable only if the
host enables "Share my hosted games" in their profile settings.
- In-game chat is never public. Even on a shared replay, chat messages are
visible only to the host, the signed-in players who were in that game, and TrackXP staff.
- Staff access. TrackXP staff can access complete game logs — including chat
— for content moderation, abuse investigation, and to improve our games and AI features (for
example, tuning the AI Game Master).
- Shared records. A game is something several people did together. A replay,
a scoreboard, or a chat log is not yours alone, which is why deleting your account removes
your identity from those records rather than erasing the other players' game. See
Your rights.
Feedback and diagnostics
If you choose to send feedback, we send your message to the private Sentry project for that
TrackXP app. When you have a valid active TrackXP session, the server attaches your verified
username so we can follow up in-product; signed-out, expired, disabled, and unverifiable
sessions stay anonymous. We never attach your email, account or session id, cookie, IP address,
or a client-supplied username. You can also opt out of the attached diagnostic snapshot. When
included, it is limited to the page path (never its query or fragment), app release and server,
screen/viewport, language and time zone, network status, and coarse non-identifying game
context such as role, phase, round, connection state, and participant count. We do not include
room codes; room, session, or seat identifiers; account or seat tokens; sign-in codes; private
chat; trivia questions or answers; votes; rolls; authored campaign text; raw request bodies; or
a full game-state snapshot. Sentry's browser monitoring SDK is not loaded, so opening a page
does not begin passive browser error or session collection.
AI features
Tabletop RPG includes an AI Game Master and AI-controlled companions. Prompts sent to it —
your in-game actions and the chat you direct at the DM — are processed by Anthropic to generate
the response, and we log them so we can improve the game. Do not type anything into the AI DM
that you would not want kept in a game log.
Cookies and similar technologies
The full list, with names, purposes and lifetimes, is on the Cookie
Policy. In summary: a required txp_session cookie keeps you signed in and is
HttpOnly and scoped to the TrackXP domain in production; local storage in the games lets you
rejoin a room after a refresh; Cloudflare Turnstile protects sign-up and sign-in from bots; and
analytics is the one optional category currently in use, covered by the note in section
4.
6. Legal bases (EU, UK, Switzerland)
If you are in the European Economic Area, the United Kingdom or Switzerland, we must have a
lawful basis for each use of your information. Ours are:
- Performance of a contract (Art. 6(1)(b)) — running your account and the
games you asked to play. Without this we cannot provide the service.
- Legitimate interests (Art. 6(1)(f)) — keeping the service secure,
preventing abuse and cheating, moderating content, protecting other users and rights holders,
fixing faults, and defending legal claims. We have considered your interests in each case and
kept the data to what the purpose needs; you can object at any time (see
Your rights).
- Consent (Art. 6(1)(a)) — analytics where consent is required, sending us
feedback, linking a Discord account, adding a phone number, and joining the waitlist. You can
withdraw consent at any time, which does not affect what happened before you withdrew it.
- Legal obligation (Art. 6(1)(c)) — responding to a valid legal request, and
keeping records where the law requires it.
7. Who else sees your information
We do not sell your personal information and we do not share it for advertising. We do use
service providers who process it on our behalf, under contract and on our instructions:
| Provider | What it does for us | What it can see |
| Vultr | Hosts our servers and databases (United States). | Everything we store, as our infrastructure provider. |
| Cloudflare | Network security, delivery, bot protection (Turnstile), and object storage (R2) for uploads. | Request metadata including IP address; uploaded files. |
| Amazon Web Services (SES) | Sends our email — sign-in codes and account notifications. | Your email address and the message we send you. |
| Google | Google Analytics 4 (optional). | Usage events with IP anonymisation, only when analytics is enabled. |
| Sentry | Error monitoring and the feedback inbox. | Error reports, and feedback you send, as described in section 5. |
| Anthropic | Powers the AI Game Master in Tabletop RPG. | The prompts sent to the AI DM. |
| Backblaze B2 | Off-site backup storage. | Encrypted backup sets. |
| Twilio | Sends sign-in codes by text, if you add a phone number. | Your phone number and the code. Not used unless you add a number. |
| Discord | Game announcements and Discord Activities, if you link your account. | Your linked Discord identity and the announcements we post. |
| Fluxer | Account linking and game announcements, if you link your account. | Your linked Fluxer identity and the announcements we post. |
| Twitch | Account linking, chat announcements and chat play. | Your linked Twitch identity, granted scopes, and the chat messages TrackXPBot processes. |
Some pages also load content directly from other companies, which means your browser contacts
them and they see your IP address: YouTube (the IFrame Player API, when a
karaoke host drives a room from a YouTube backing track, subject to YouTube's terms),
TMDB (movie images in trivia — "This product uses the TMDB API but is not
endorsed or certified by TMDB"), and the Apple iTunes Search API (30-second
music previews).
Advertising. We run no advertising today. If we ever introduce it, we will
update this policy and the Cookie Policy first, and where consent is
required we will add a separate disclosed purpose before any advertising cookie is set. An
existing analytics choice will not be treated as consent to advertising — we will not start
advertising to you on the strength of a choice or policy that predated it.
We may also disclose information when the law requires it, to respond to a valid legal
request, to protect our rights or someone's safety, or in connection with a merger,
acquisition, or sale of assets — in which case we will say so here before your information
becomes subject to a different policy.
8. International transfers
TrackXP is operated from the United States and our servers are in the United States. If you
use TrackXP from the EEA, the United Kingdom, Switzerland, Canada or Australia, your
information is transferred to and stored in the United States, and may be accessed there by us
and by the providers listed above.
For providers acting on our behalf, we rely on the transfer terms in their standard data
processing agreements, which for our EU- and UK-relevant providers incorporate the European
Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum. You
can ask us for details of the safeguards that apply to a particular transfer using the contact
details in section 19.
9. How long we keep things
The periods we can state precisely are below. Where a row says we have not yet set a fixed
period, that is the truth today: we are finalising a full retention schedule and this section
will be replaced with it. Anything we keep, we keep because we still need it for the purpose it
was collected for, or to defend a legal claim.
| What | How long |
| Sign-in codes | 10 minutes, stored hashed, single-use, and deleted the moment they are used. |
| Sessions | Expire 30 days after sign-in; expired records are swept automatically. Signing out deletes the record immediately. |
| Recognised sign-in devices | The server keeps only a hash of the browser identifier while your account exists; the host-only browser cookie expires after 12 months. |
| Game hand-off tokens | 15 minutes. |
| Account record and profile | While your account exists. On deletion, see section 10. |
| Game history, XP and achievements | Kept so you and the people you played with can review past games. On account deletion your identity is removed from them. |
| Detailed game event logs | In Crowd Quest and Tabletop RPG, the turn-by-turn event log is deleted 90 days after a game ends. The result and score stay in your history; the play-by-play does not. |
| AI Game Master logs | 180 days in Tabletop RPG, for the AI DM and the builder copilot. |
| Campaign builder snapshots | Automatic checkpoints are kept 30 days and playtest snapshots 7 days. Versions you name, publish or fork are kept for as long as the campaign exists — that is deliberate, so your version history does not disappear underneath you. |
| Uploaded files | While the upload is in use. A file you delete, or that we block, is moved to a quarantine bucket that automatically expires after 30 days, then is gone. |
| Moderation decisions | Kept as a record of why we acted, so that a repeat problem can be recognised. |
| Guest records | No automatic expiry today. This is one of the gaps the retention schedule will close. |
| Security and audit logs (including IP) | No fixed period set yet. We are setting one. |
| Backups | Complete local backup sets are kept for 14 days, plus off-site copies. Information deleted from the live service persists in backups until those backups age out. |
| Analytics | Google's analytics cookies last up to 24 months. |
10. Your rights, and how to use them
Wherever you live, you can ask us to do the following. We do not charge for it, and we will
not give you a worse service for asking.
- Know and access — what we hold about you, and a copy of it.
- Correct — fix information that is wrong.
- Delete — remove your account and your personal information.
- Portability — receive your data in a machine-readable format.
- Object or restrict — limit processing based on legitimate interests.
- Withdraw consent — at any time, without affecting what happened before.
- Appeal — if we refuse, ask us to think again. Several US states require an
appeal route; we offer it to everyone.
What deletion actually does
A game is a shared record, so deleting your account does not erase the games other people
played with you. When we action a deletion request we remove the personal information on your
account — your email address, phone number, security factors, linked Discord identity, and
profile — and we replace your name on anything that has to remain with a non-identifying marker
such as "Deleted user". Game results, leaderboard placements, forum posts and community
submissions stay, without you attached to them. We tell you what was removed and what remained.
If you want a specific post or submission taken down as well, ask us and we will do that too,
subject to any moderation record we must keep.
Two limits we would rather state than let you discover. Feedback you sent us
is held in our error-monitoring provider's system with the verified username that was attached
at the time, and deleting your account does not reach it — tell us if you want a specific
feedback report removed and we will do it by hand. Backups keep working
copies of the database for a period after deletion, so information removed from the live
service persists in them until they age out, as described in section
9. Neither is used to rebuild an account we have deleted.
How to make a request
Email [email protected] from the address on your
account and tell us what you want. We verify that it is really you before we act — normally by
confirming that you control the account email — and we will not ask for more information than
that verification needs. An authorised agent may act for you with your written permission.
Requests are handled by hand today. Self-service controls for pausing, exporting and deleting
your account are being built into your profile; when they ship, this page will say so.
We respond within one month under the EU and UK GDPR and within
45 days for California requests, and we will tell you if we need an extension
that the law allows.
11. EU, UK and Swiss notice
If you are in the EEA, the UK or Switzerland, the rights in section 10
are your rights under Articles 15 to 22 of the GDPR and the UK GDPR, and we rely on the legal
bases set out in section 6.
You have the right to complain to your data protection authority. In the UK that is the
Information Commissioner's Office; in the EEA it is the authority for the country you live in;
in Switzerland it is the Federal Data Protection and Information Commissioner. We would much
rather you came to us first so we can put it right.
We do not make decisions about you by automated means that produce legal or similarly
significant effects. Automated content moderation flags material for review; a staff member
makes the decision that affects your account.
12. California notice (CCPA/CPRA)
This section is for California residents, and uses the categories of personal information
defined by the California Consumer Privacy Act as amended by the CPRA.
What we collect. In the 12 months before the effective date of this policy we
collected: identifiers (username, email address, phone number if you add one, IP
address, account and guest identifiers, linked Discord identity); internet or network
activity (request logs, pages and games used, analytics events); geolocation only
in the coarse sense of a two-letter country derived from your sign-in connection;
audio-adjacent information in the limited form of speech-recognition text produced on
your own device (never the audio itself); commercial information in the sense of your
play and submission history; and inferences only to the extent that XP and achievement
levels are derived from play. We collected each of these for the business purposes in section
4, from the sources listed there, and we disclose them to the service
providers listed in section 7.
We do not sell or share your personal information. We have not sold personal
information, and we have not shared it for cross-context behavioural advertising, in the 12
months before the effective date of this policy — and we do not do so now. We have no "Do Not
Sell or Share My Personal Information" mechanism to offer because there is nothing to opt out
of; the analytics controls on Your privacy choices are available
to you regardless.
Sensitive personal information. We do not collect or use sensitive personal
information for the purpose of inferring characteristics about you, so the right to limit its
use does not arise.
Your California rights. To know, access, correct, delete, obtain a portable
copy, limit the use of sensitive personal information, opt out of sale or sharing, and not be
retaliated against for exercising any of them. Use the request route in section
10. We will confirm receipt within 10 business days and respond within 45
days, extendable once by a further 45 days if we tell you why.
Minors. We do not knowingly collect personal information from anyone under
13, and we do not sell or share the personal information of consumers under 16 — because we do
not sell or share anyone's.
Notice of financial incentive. We offer none.
13. Other US state notices
If you live in Virginia, Colorado, Connecticut, Utah, Texas or Oregon, your state's privacy
law gives you rights that we already extend to everyone: to confirm whether we process your
personal data and access it, to correct it, to delete it, to obtain a portable copy, and to opt
out of targeted advertising, sale, and profiling with legal or similarly significant effects.
We do not carry out targeted advertising, do not sell personal data, and do not profile you in
a way that produces such effects, so those opt-outs have nothing to act on — but the request
route in section 10 is open to you.
Colorado, Connecticut, Virginia, Texas and Oregon residents may appeal a
refusal by replying to our decision; we will respond in writing within the period your state's
law allows, and if we still refuse we will tell you how to contact your Attorney General.
Oregon residents may also ask for a list of the specific third parties to which we have
disclosed personal data; ask and we will provide it.
Global Privacy Control. We have no sale or targeted advertising for an
opt-out preference signal to switch off. We honour GPC anyway: if your browser sends it, we
treat it as a rejection of analytics and do not show you the consent banner. It applies on
trackxp.com and on every TrackXP game.
14. Canada
If you are in Canada, we handle your personal information in line with the Personal
Information Protection and Electronic Documents Act (PIPEDA) and the provincial laws that
substitute for it. We collect only what we need for the purposes described in this policy, we
tell you what those purposes are before or when we collect it, and we rely on your consent —
express where the information is sensitive or the use is optional, implied where the use is
obvious from what you asked us to do. You may withdraw consent, subject to legal or contractual
limits, by contacting us; withdrawing consent to essential processing means we can no longer
provide the account.
You have the right to access your personal information and to challenge its accuracy, and to
complain to us and then to the Office of the Privacy Commissioner of Canada. Your information is
stored in the United States and is subject to lawful access by US authorities.
15. Australia
If you are in Australia, we handle personal information in line with the Australian Privacy
Principles under the Privacy Act 1988 (Cth). We collect personal information only where it is
reasonably necessary for our functions, and by lawful and fair means — normally directly from
you. We do not use or disclose personal information for direct marketing. We do not adopt or
use a government identifier as our own identifier for you.
We disclose personal information to overseas recipients — principally in the United States, as
described in sections 7 and 8. You may request
access to, or correction of, your personal information using the route in section
10. If you are unhappy with how we have handled your personal information
or your complaint, you may complain to us first and then to the Office of the Australian
Information Commissioner.
16. Security
TrackXP is passwordless, so there is no password of yours for us to lose. Sign-in codes are
stored hashed and expire in 10 minutes. We store only a hash of your session token, never the
token. Authenticator secrets are encrypted with a key held outside the database, and recovery
codes are hashed and single-use. Staff accounts must pass a second factor before staff powers
apply anywhere on the fleet. Traffic is served over HTTPS and fronted by Cloudflare.
No system is perfectly secure. If we become aware of a breach that is likely to result in a
risk to your rights, we will notify you and the relevant regulators as the law requires.
17. SMS account security
Giving us a mobile number is optional. If you add one to your account, we use it only to
text you sign-in codes and notifications about security events on your own account. We send no
marketing, promotional, game, or community messages by text — those reach you by email and
inside the site. The SMS account security page describes the opt-in, the
messages, and how to stop them.
No mobile information will be shared with third parties or affiliates for marketing or
promotional purposes. We do not sell or rent your mobile number, and we disclose it
only to the messaging carriers that have to handle a message in order to deliver it to you.
Message frequency varies and depends on your own sign-in and account activity; we do not text
on a schedule. Message and data rates may apply under your own mobile plan.
Reply STOP to any message to stop, or HELP for help. You can also remove the number at any time
from Profile → Sign-in & security, which stops the messages without a reply.
We keep the number, the consent wording you agreed to, and the time, IP address and browser
you agreed from, for as long as the factor is on your account and for a limited period after
you remove it, so we can show that consent was given. See
How long we keep things.
18. Children
TrackXP accounts are for people aged 13 and over. If you are in the EEA, the
UK or Switzerland, you must be 16 or over to create an account, or have your
parent or guardian's consent — this is the age at which you can consent to online services for
yourself in most of those countries.
We do not ask for a date of birth at sign-up, so we enforce this by rule and by report rather
than by an age check. If you believe a child under the applicable minimum age has created an
account, email [email protected] and we will remove
the account and their personal information.
Games can be joined without an account, using a room code. The host of a room is responsible
for who they invite into it.
19. Changes to this policy
We update this policy when what we do changes. The effective date at the top always tells you
which version you are reading. If a change is material — a new purpose, a new category of
information, a new kind of recipient — we will say so prominently before it takes effect, and
where the law requires your consent we will ask for it rather than assume it. We will never
apply a materially different use to information we already hold without telling you first.
Privacy questions and requests: [email protected].
Anything else: [email protected].
SMS Account Security
TrackXP sends text messages for one purpose: keeping your account secure. If you
add a mobile number to your account, we text you sign-in codes and notifications about
security events on your own account. We send nothing else by text — no marketing, no
promotions, no game or community updates.
What we send
| When | What you get |
| You sign in to TrackXP using your verified phone number | A one-time sign-in code |
| You add or re-verify a phone number in your account settings | A one-time code confirming the number is yours |
| You change something security-sensitive (sign-in methods, email, recovery codes) | A one-time code confirming it is really you |
| A security event completes on your account (sign-in from a new device, sign-in settings changed) | A notification, so you can act if it was not you |
Every message is triggered by something you did, or by an event on your own account, and goes
only to the number you entered and verified yourself.
What we never send by text
No marketing or promotional messages, no product announcements or newsletters, no game,
score, leaderboard, or community notifications, and nothing on behalf of anyone else. Those
reach you by email and inside the site instead. Adding any new category of text message would
require registering a new messaging campaign with the mobile carriers first.
How you opt in
You cannot opt in by texting us. There is no text-to-join keyword and no
advertised call-to-action for our number. The only way to start receiving these messages is to
add your number yourself, from inside your own signed-in TrackXP account — we never add a
number you did not enter, and we never obtain numbers from a purchased list, a data broker, an
affiliate, or any other third party.
- Sign in to your TrackXP account and open Settings → Account → Phone.
- Choose Add phone and type your own mobile number. The field is never pre-filled.
- Tick the consent box. It starts unticked, and the form will not submit without it. This is exactly what you see:
Above: the opt-in control as it appears on your account page.
- We text you a single verification code. Nothing else is sent, and the number is not enabled,
until you enter that code back into the site — a double opt-in confirming both your consent
and that the phone is yours.
Text messages are optional. You can sign in with your email instead, and an
authenticator app (TOTP) or a passkey secures your account just as well. We never make text
messages a condition of creating an account, buying anything, or using any feature.
What the messages look like
TrackXP: 483920 is your sign-in code. It expires in 10 minutes. TrackXP will never ask you for this code. Reply STOP to cancel, HELP for help.
TrackXP: 620174 is your code to verify this phone on your account. It expires in 10 minutes. Msg & data rates may apply. Reply STOP to cancel, HELP for help.
TrackXP: 915583 is your code to confirm a security change on your account. It expires in 10 minutes. Never share this code. Reply STOP to cancel, HELP for help.
TrackXP: your account was signed in on a new device (Chrome on Windows) on 21 Aug. If this was not you, secure your account at https://trackxp.com/profile. Reply STOP to cancel, HELP for help.
TrackXP: the sign-in and security settings on your account were changed on 21 Aug. If you did not do this, go to https://trackxp.com/profile. Reply STOP to cancel, HELP for help.
TrackXP will never ask you to share a code with anyone, including someone claiming to be our
support team. If a message asks you to do that, it is not from us.
Frequency and cost
Message frequency varies and depends entirely on your own sign-in and account activity —
we do not send on a schedule. Message and data rates may apply, according to your
own mobile plan. TrackXP does not charge you for these messages.
Stopping messages, and getting help
- Reply STOP to any message (or STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT) and we stop texting that number. We also switch text sign-in off on your account, so use your email address to sign in after that.
- Reply HELP (or INFO) for contact details, or email [email protected] at any time.
- Reply START to allow messages again. You will also need to re-add and re-verify the number in Settings → Account → Phone.
- You can remove the number at any time from Settings → Account → Phone, without sending a text at all.
What we do with your number
No mobile information will be shared with third parties or affiliates for marketing or
promotional purposes. We do not sell or rent your mobile number. We disclose it only to
the messaging carriers that have to handle the message in order to deliver it to you, and we use
it only for the messages described on this page.
The Privacy Policy covers what we keep and for how long, and how to ask
for your data or its deletion. The Terms of Service cover the rest of your
agreement with us.
Contact
Questions about SMS account security: [email protected].
Privacy questions: [email protected].