Racing Legends

Draft — not legal advice; have a licensed attorney review before relying on it.

Privacy Policy

Last updated November 17, 2026 · version 2026-11-17-draft

This policy explains what personal data Racing Legends collects, why, who processes it for us and what you can ask us to do with it. It describes what the service actually does today, during the beta.

Who is responsible

[Operator legal name and mailing address, to be completed] operates Racing Legends and is responsible for your data. Contact: privacy@racinglegends.app.

What we collect

  • Account details: your racer name, your password (stored only as a salted scrypt hash, never in plain text) and, if you link one, your Discord account (its ID and username). We do not ask for an email address.
  • Invitations and consent: invitation requests (the racer name you want, your Discord username, old handle if any, your reason for joining and your IP address); for each access code, when it was claimed and from which IP address; and a record of your terms acceptance (terms version, time, code and IP address).
  • Original-account claims: if you ask to reclaim an account from the original game, the evidence you provide, an optional contact detail and a hash of the password you choose.
  • Game client device identifiers: when you log in with the game client it sends a machine identifier, your network adapter (MAC) address and your computer name. We store the latest values on your account to detect fraud and ban evasion. They are never used to log you in.
  • Gameplay data: cars, parts, money and points, an append-only ledger of economy transactions, badges, teams, buddy lists, leaderboard standings, activation-code redemptions and race results (elapsed time, reaction time, wins, payouts, an anti-cheat verification value and whether the run was flagged).
  • Content you create: avatar images (stored in our database), profile remarks, in-game mail, team details and support tickets (topic, an optional email address, the name of a player you report and your notes).
  • Technical data: IP addresses stored with each login session, access-code claim, terms acceptance, invitation request and activation-code attempt. IP addresses are also used in memory for rate limiting and appear in server logs, including the race server's connection logs. Server logs can include your racer name. Passwords, session keys and codes are redacted from logs.
  • Sign-in log: each sign-in attempt (game client, game code, Discord, website, Telegram or staff panel) records the time, how you signed in, whether it worked and why not, your racer ID and the name typed, your IP address, the user agent, the game client version and program name, a one-way hash of the game client's device identifiers and, when a banned account is refused, the ban it matched. We use it to investigate account takeovers and ban evasion.
  • API access monitor: for security and abuse prevention our API counts requests per IP address per hour (signed-in requests, anonymous requests, whether they look like the game client or our website, requests over the limits and the busiest minute). For requests made without signing in it also keeps the routes or game actions called, the user agents, which edge they came through and one sample of the request headers (the header names, user agent, accept, referer, origin and host values and the forwarding addresses; never passwords, session keys, cookies or tokens). It does not store your racer ID. Addresses with suspicious patterns are flagged for staff, who can block an address or range; a block records the address or range, the reason, who set it, when and when it ends or was lifted. Every block and lift is written to our moderation log.
  • Moderators see only the first two parts of an IP address in these logs; admins see the full address.

Chat and automated moderation (Ichiban)

  • Lobby and race chat is not saved to our database, except for the recent lines attached to a /report (see below) and lines that lead to a moderation action. The race server keeps the most recent lines of each room in memory so moderation has context.
  • Every chat line is checked by an automated filter on our own servers. A line that matches the filter or mentions Ichiban is sent to Google's Gemini API together with the author's racer name and role and up to 8 recent lines from the same room (which include other players' racer names). The line is also sent to Google's embedding API to look up the relevant rules.
  • A /report line in game chat is not shown in the room and is not sent to Ichiban or to Google. It files a report in our moderation log and a Player report ticket on our support desk, stored in our database. They hold your racer name, the racer name you reported, your reason, the room name and up to 10 recent lines from that room's chat (which include other players' racer names). Staff review them.
  • Ichiban can warn, mute, kick or ban automatically when it is confident; less certain cases go to a human review queue. Lines that lead to a moderation action are stored with that action (who, what, why and the message).
  • Race results flagged as implausible are counted: several flagged results within 24 hours can lead to an automatic mute or ban.
  • If you think an automated decision is wrong, contact us and a staff member will review it.

How we use your data

  • To create and run your account, the game, races, teams and leaderboards.
  • To keep the game fair and safe: anti-cheat checks, moderation, rate limiting, fraud and ban-evasion detection.
  • To review invitation requests and original-account claims.
  • To keep a record of your consent to these terms.
  • We do not sell your personal data, show advertising or use analytics or tracking tools.
  • [Legal bases for processing under GDPR / UK GDPR, if applicable: to be completed by counsel.]

Email

We do not currently send automated email: there is no email verification, no password-reset email and no login-link (magic link) email. If our team invites you, the invitation with your access code is sent by a person on Discord in reply to your request.

Who processes data for us

  • Vercel: hosts this website.
  • Railway: runs our API, game servers and database (including avatars).
  • Cloudflare: DNS, the content delivery network for car artwork and the web bridge to the game server.
  • Google: the Gemini API for chat moderation and some anti-cheat and content tools; Google Fonts, which our pages load from Google's servers, so Google receives your IP address when you visit.
  • Our staff and moderators can see account, gameplay, support and moderation data as needed for their role.
  • We may disclose data if required by law or to protect players and the service.
  • These providers may process data in the United States and other countries.

How long we keep data

  • Login sessions expire after 30 days without use and are then deleted.
  • Sign-in log entries are deleted after 180 days. API access monitor counts are deleted after 90 days. Address flags, IP blocks and moderation log entries have no automatic deletion yet.
  • Other data is kept while your account exists and the service runs. We do not yet have automatic deletion schedules for race results, logs or moderation records. [Retention periods to be set with counsel.]
  • During the beta, data may be reset.

Your choices and rights

  • You can ask us to access, correct or delete your account data, or to explain how it is used, by emailing privacy@racinglegends.app. There is no self-service tool yet; staff handle requests by hand and may need to confirm the account is yours.
  • We may keep some records after deletion where needed for security, fraud prevention or legal reasons, such as ban records and the economy ledger.
  • Depending on where you live (for example the EEA, the UK or some US states) you may have further rights, including to object, to restrict processing and to complain to a data protection authority.

Children

Racing Legends is not directed to children. Accounts are for people aged 13 and over; we ask you to confirm your age at sign-up but do not verify it. If you believe a child has given us personal data, contact us and we will delete the account.

Security

We hash passwords with scrypt, redact secrets from logs, serve the website over HTTPS and limit request rates. No system is perfectly secure; tell us right away if you suspect your account has been compromised.

Changes

We will post changes on this page with a new version and date.