The short version
- We show statistics built from iRacing race results. We don't sell data, show ads or use tracking or advertising cookies.
- To sign up we need your email address and your iRacing customer ID. Google or a passkey handles sign-in, so we never hold a password.
- You choose who may see your name and iRacing ID, who can find you in driver search, and whether you appear in AI rosters.
- You can ask for a copy of your data, or for your account to be deleted, at any time: email privacy@myracing.info.
Who we are
myRacing (myracing.info) is the controller of the personal data described here. It is run independently and is not affiliated with or endorsed by iRacing.com Motorsport Simulations.
For anything about your data, including the requests under Your rights, email privacy@myracing.info. We don't have a dedicated data protection officer; that address reaches the people who run the service.
What we collect
When you create an account and use the site we hold:
| Data | Where it comes from |
|---|---|
| Account: email address, account name, the date you joined | You, or your Google account if you sign in with Google |
| Driver link: your iRacing customer ID and the name on it | You, checked against the iRacing results we hold |
| Sign-in: your Google account ID, passkey public keys, an authenticator app secret and recovery codes if you set them up | You and your device. A passkey's private key never leaves your device. |
| Sessions: when each session started and was last used, and your browser's user-agent string, so you can recognise and sign out your devices | Your browser |
| Activity: when you last signed in and were last seen, the achievements you've been notified about, and which pages you opened each month (see page usage) | Your use of the site |
| Preferences: who may see your name and iRacing ID (with when you chose and the wording you agreed to), search visibility, AI profile settings and, if you add it, your date of birth | You, on My profile |
| Subscription: your plan, when it ends, and what's in your cart | You |
| Messages: your name, email address and message when you write to us through Contact us, and your account and iRacing ID if you were signed in | You |
| Account history: a log of changes to your account (plan changes, suspensions, two-factor resets) made by you or an administrator | Our systems |
Like any website, our servers also see your IP address and browser details on each request. We use these only to deliver pages and keep the service secure, and we don't build profiles from them.
When you vote in a poll, we keep your answers with your account (or, without an account, with a random ID kept in a cookie in your browser) and a scrambled code made from your IP address. The code is different for every poll and can't be turned back into the address; it only lets us allow one vote per network in polls that visitors without an account can vote in (official schedule polls).
Paid plans can't be bought yet. When payments open, card details will go straight to a payment provider (we'll never see or store your full card number) and this policy will name that provider first.
Racing results from iRacing
Most of what myRacing shows is built from iRacing race results: drivers' names and customer IDs, clubs, the sessions they entered, cars, tracks, finishing positions, incidents, laps and iRating. These results are already public on iRacing. We collect them, add our own calculations (myRating, corners per incident, classifications, leaderboards, achievements) and show them to signed-in members.
This covers every driver in the results, including drivers who have never signed up to myRacing. If that's you, this section is our notice to you under Article 14 of the GDPR. You have the same rights as a member: you can ask what we hold about you, object to us processing it, or ask us to hide you from search and leaderboards by emailing privacy@myracing.info with your iRacing customer ID. We'll ask you to prove the customer ID is yours before acting on it.
Ratings and classifications are worked out automatically from results. They are sporting statistics only and are never used to make decisions that have legal or similarly significant effects on anyone.
Why we use it (legal bases)
- To provide your account and the features you use (account, driver link, sign-in, sessions, preferences, subscription): necessary for our contract with you (Art. 6(1)(b)).
- To build statistics from public iRacing results, including about drivers without an account: our legitimate interest, and the racing community's, in sporting statistics about public results (Art. 6(1)(f)). We limit this to racing data, offer search hiding, and honour objections.
- To decide what each plan includes and what it costs (page usage): legitimate interest in knowing which features members use (Art. 6(1)(f)). For each month we count which pages were opened on each plan and on how many days. You're counted under a one-way code made from your account, not your name, email or iRacing ID, and we don't record times, what was on the page or which driver you looked at. Only administrators see the totals.
- To find and fix errors (error reports): legitimate interest in a site that works (Art. 6(1)(f)). When a page fails, on our server or in your browser, we record the error message, the page address, the time, your browser name and version and, if you're signed in, your account, so we can fix it and check whether it affected you. Nothing you typed or saw on the page is recorded, and only administrators see the reports.
- To keep the service secure (two-factor, session records, account history, server logs): legitimate interest in preventing abuse and account takeover (Art. 6(1)(f)).
- Showing your name and iRacing ID to other people while name privacy is on: your consent, given under Name and iRacing ID on My profile (Art. 6(1)(a)). You can withdraw it at any time by choosing Nobody; it takes effect straight away. In a league, the league's organisers confirm their drivers agreed to their names showing on its pages.
- AI rosters: your consent, given by switching on the AI profile (Art. 6(1)(a)). You can withdraw it at any time by switching it off.
- Records we must keep by law, such as payment records once payments open: legal obligation (Art. 6(1)(c)).
We don't use your data for advertising, and we don't sell or rent it to anyone.
Who can see you
Your name and iRacing ID. On My profile you choose who may see them: everyone, signed-in members, or nobody, as your full name or first name and initial. When name privacy is switched on for the site, drivers who haven't agreed (including drivers without an account) appear to everyone else as “Private driver”, with no link, and their driver pages and images below can't be opened by others; their ratings and results still count on leaderboards. A new iRacing ID claim only shows the name once its probation ends. League pages show the names of a league's drivers once the league's organisers confirm those drivers agreed. Administrators can still see names to run the service.
myRacing is for signed-in members only. Other members can see your driver overview and forum signature and compare themselves with you in Head to Head, the same way anyone can look up results on iRacing. Your Ratings, Classifications, Corners per Incident, Achievements, Activity, Feed, Year in Review and Driver Card pages are visible to you only (poster links you share are covered below). On My profile you choose who can find you in driver search:
Your results come from iRacing and stay public on iRacing whichever you choose. To be left out of leaderboards as well, email privacy@myracing.info.
Forum signature images (/sig/…) and Year in Review posters and share pages (/recap/…, /year-in-review/…) and Driver Card previews (/card/…) are public, so they can be shown on forums and social media without signing in. Anyone who knows a customer ID can load one, and it shows that driver's name, club and ratings and race stats (for a year, or for their career on a Driver Card). They follow your search visibility: with members only, signed-out viewers (including forums and link previews) get “not available” instead; with nobody, everyone but you does.
Administrators can see member accounts to run the service and help with support, and can view the site as a particular driver to check what they see. Every use of that is logged.
AI rosters
The AI profile on My profile is off unless you switch it on. With it on, your name, your driver skill (your hosted myRating percentile), the traits you set and your age may be included in community AI rosters for iRacing, which are shared publicly with other sim racers.
If you enter a date of birth, we store it so your age stays current, but only the age goes into rosters, never the date. Switch the profile off to stop being added to new rosters; rosters other people have already downloaded are outside our control.
Where your data is stored
Our servers and databases are run by Amazon Web Services in the United States. When we transfer personal data from the EU, EEA or UK there, we rely on the EU–US Data Privacy Framework (and its UK extension), under which Amazon is certified, and on the European Commission's Standard Contractual Clauses in Amazon's data processing terms. Email privacy@myracing.info for a copy of the safeguards.
How long we keep it
- Account data: while your account is open. When you ask us to delete your account we erase it within 30 days, apart from anything the law requires us to keep.
- Sessions: until you sign out or after 30 days, whichever comes first.
- Account history: while your account is open, so problems with it can be looked into.
- Page usage: 13 months, then deleted.
- Error reports: the last 10 occurrences of each error, and only until it's fixed and cleared; daily counts for 30 days.
- Contact messages: kept so we can follow up on earlier conversations. Ask us at any time to delete yours.
- Payment records: for as long as tax law requires once payments open.
- Racing results: as long as myRacing runs, because ratings and leaderboards depend on the full history. Deleting your account doesn't remove your results from the iRacing data, but you can ask to be hidden from search and leaderboards.
Your rights
Under the GDPR you have the right to:
- Access the personal data we hold about you and get a copy.
- Rectification: have wrong data corrected. You can change your email and preferences yourself on My profile. Your name and results come from iRacing, so they're corrected there.
- Erasure: have your account and the data tied to it deleted.
- Restriction: ask us to pause using your data while a complaint is looked into.
- Portability: receive the data you gave us in a machine-readable format (JSON).
- Object to processing based on our legitimate interests, including the statistics we build from your iRacing results.
- Withdraw consent at any time, for example by switching off the AI profile. This doesn't affect what was done before.
To use any of these rights, email privacy@myracing.info from the address on your account (or, if you don't have one, include your iRacing customer ID). It's free, and we'll answer within one month. We may ask you to confirm your identity first.
You can also complain to a data protection authority, for example the one where you live or work: in the EU and EEA see the list of national authorities, and in the UK the Information Commissioner's Office. We'd appreciate the chance to sort it out with you first.
Security
- Every connection uses HTTPS.
- No passwords: sign-in is by Google or passkey, with optional two-factor (authenticator app or passkey). Two-factor is compulsory for administrators.
- Session tokens are stored only as one-way hashes, so a copy of our database can't be used to sign in as you.
- The website reads racing data through a read-only database account, and access to our systems is limited to the people who run the service.
If we ever have a breach that puts your data at risk, we'll tell the relevant authority within 72 hours and tell you without undue delay when the law requires it.
Children
myRacing is for people old enough to hold an iRacing account. We don't knowingly collect data from children under 13. If you're under 16, please don't switch on the AI profile without a parent's or guardian's consent. If you think a child has given us personal data, email privacy@myracing.info and we'll delete it.
Changes to this policy
We'll update this page when what we collect or how we use it changes, and change the date at the top. If a change is significant (a new kind of data, or a new company we share it with) we'll tell members on the site before it takes effect.
18 October 2026: added error reports (the error, page, time, browser and account when a page fails), used to find and fix problems. No new cookies, and no outside service.
18 October 2026: the site no longer has a light theme, so the mr-theme local storage entry is gone; listed the unfinished schedule poll calendar kept in local storage.
14 October 2026: visitors without an account can vote in official schedule polls: added the mr_poll_voter cookie and a per-poll scrambled code of the voter's IP address (one vote per network).
14 October 2026: added the choice of who may see your name and iRacing ID (consent, Art. 6(1)(a)), the “Private driver” display and the league organisers' confirmation.
11 October 2026: added page usage counts per plan (which pages members open each month), used to decide what plans include and cost. No new cookies.
6 October 2026: Ratings, Classifications, Achievements, Activity, Feed, Year in Review and Driver Card pages are now visible to their own driver only.
5 October 2026: added Driver Card preview images (/card/…), public like Year in Review posters.
5 October 2026: forum signature images and Year in Review posters and share pages now follow search visibility.
5 October 2026: added the mr_banner cookie (remembers a closed site announcement).
4 October 2026: first version.