The short version. A driver page here is off until its driver turns it on. Claim your page, choose to share it, and it fills in from your iRacing results. Until you do both, nothing about you is published on Racezon — not your stats, not your name, not your rivalries. Where you appear in someone else's race result you appear as an unnamed row. Names, when shown at all, are abbreviated — "Ayrton S.", never the full name. If you want even the unnamed row gone, you don't need an account and you don't need to explain yourself: use the Remove this page button on the page itself, or email support@racezon.gg.
Who is responsible for your data
Marcelo Eduardo de Andrade Junior Consultoria em Tecnologia da Informação LTDA (CNPJ 39.835.654/0001-70), Santos/SP, Brasil, is the controller of the personal data described here. You can reach us at support@racezon.gg for any question or request about your data.
Where the data on driver pages comes from
Racezon is an independent project. It is not affiliated with, endorsed by, or operated by iRacing.com Motorsport Simulations, LLC.
A switched-on driver page is built from competition data that iRacing publishes about its members: licence class, iRating, Safety Rating, and the results of races you took part in (finishing position, incidents, laps, the other drivers on the grid). iRacing's own privacy policy, in the version effective 1 September 2025, answers the question of whether that information is private with a flat no: it states that a member's name, avatar and personal stats page, along with racing statistics including licence level, skill level and safety rating, are available to the public.
Nothing is published unless the driver switches it on
That iRacing treats those fields as public is not the reason we show them. We show them because the driver asked us to. A page displays data only when the driver has claimed it and turned on public sharing. Without both, the request is refused on our servers before it ever reaches iRacing: there is no partial page, no preview, no share card and no cached copy to find. The same gate applies everywhere else the driver could surface — drivers who have not switched their page on are left out of rivals lists and name search entirely, and appear in race grids and incident cases only as an unnamed row.
We do not publish full names. Everywhere a driver's name appears — profile pages, race grids, head-to-head pages, community pages, share images — it is shortened to a first name and an initial ("Ayrton S."). That is done on our servers, so the full name is not in the page, not in the data behind it, and not visible to anyone inspecting the site. Searching for drivers by name requires a free account. That search runs against iRacing's own driver lookup, so it can find a driver who never came here — but following the result lands on a page with nothing on it, because the gate above still applies. Without an account you can only look a page up by iRacing Customer ID, a number you have to be inside iRacing to know.
We do not have access to and never collect your iRacing password, payment details, email address, home address, telemetry, voice chat, or private messages.
Why we may hold it (legal basis)
For a driver who switched their page on, the basis is that driver's consent, which they can withdraw at any time by switching it back off.
That leaves one narrower case. To show a race, we have to fetch the race, and a race result names everyone who was on the grid — including drivers who never came here. For holding that result, and for publishing it with those drivers unnamed, we rely on legitimate interest (GDPR Art. 6(1)(f)) and the equivalent basis under Brazil's LGPD (Art. 7, IX): a classification is a public record of a shared public activity, and removing the rows would misstate the result for the drivers who did consent. We balance that against your interests by removing the identity — no name, no customer ID, no link — by never publishing contact details or identity documents, and by honouring removal requests, which reach the cached copy too. See Your rights.
For data you give us by creating an account, the basis is performance of a contract (providing the service you asked for) and, for analytics cookies, your consent.
What we collect
If you never switched a page on
Nothing about you is published. What we hold is one thing: the race results we fetched to show a race, which name every driver on that grid — including you. Your customer ID and name sit in that cached result; the published version of it has your row with no name, no ID and no link. We do not ask iRacing for your career, we do not compute your rating, rivalries or trust score, and there is no page of you to find.
If you create an account
- Your email address, username, and password (stored and verified by AWS Cognito — we never see it).
- The iRacing customer ID you claim.
- Whether you turned public sharing on. Off is the default, and turning it back off stops publication everywhere — page, grids, rivals, search, share cards.
- An avatar, if you choose one or upload one.
- Content you create: clips, incident cases, votes on them, and commends.
Automatically
- Standard server logs from our hosting provider (IP address, browser, pages requested), kept for a short period for security and debugging.
- Analytics — currently none. We do not run Google Analytics or any other analytics product at the moment, and no analytics cookie is set. If we turn it on, it will be behind the consent banner described under Cookies.
The RZ Trust Score is calculated automatically
A switched-on page can show an RZ Trust Score out of 100. We compute it, automatically, from two kinds of input: your iRacing hygiene (incidents per race, races started, licence class) and your record here (commends from other drivers, and how the community read incidents you were part of). iRacing describes its own iRating and Safety Rating as profiling; ours is the same kind of thing, and we would rather say so than let you discover it.
It is a reputation signal inside this community, not a decision about you: it grants and refuses nothing, here or anywhere else. Even so, under LGPD Art. 20 you can ask us to explain how yours was reached and to have it looked at by a person — email support@racezon.gg. Switching your page off removes it from view entirely.
Content other people write about you
Racezon lets drivers who shared a race raise an incident for review, and lets others read it and say how they see it. These are opinions and testimony from other players. They are not findings of fact, they carry no weight with iRacing, and they have no effect on your iRacing account, iRating, Safety Rating or licence — iRacing is the only body that rules on iRacing incidents, and its own protest form is the only formal route. If you have not switched your page on, you are shown in a case as "Private driver", with no name and no link. If something written about you is abusive, false, or identifies you beyond your racing, email support@racezon.gg and we will review and remove it.
Who we share it with
We do not sell your data. We share it only with the providers that run the service:
- Amazon Web Services — hosting, database and authentication (United States).
- SendGrid — for sending email if you opt into our digest. The digest is not being sent yet; when it starts, it is opt-in and every message carries an unsubscribe link.
- Google Analytics — not in use today. Listed here because we may enable it, and only ever after you accept cookies.
Our servers are in the United States, so if you are in the EU/UK or Brazil your data is transferred internationally. Public driver pages are, by design, visible worldwide.
Your rights
Under the LGPD and the GDPR you can ask us to: confirm what we hold about you, get a copy of it, correct it, delete it, restrict or object to how we use it, and withdraw consent you previously gave. Specifically, on Racezon you can:
- Have your page removed and de-listed — even if you never signed up, and without giving a reason. We take the page down, replace the cached copies, tell search engines not to index it, and then erase your name from our records: it is overwritten wherever another driver's clip, commend or incident review referred to you, and the derived data we had cached about you is deleted outright.
One honest exception: the free-text description another driver wrote when raising an incident is evidence in that case, so we do not machine-edit it. It goes to a human for review within the same 15 days, who removes or closes it by hand. - Delete your account, which also releases your claim on your page.
- Correct anything wrong that came from us rather than from iRacing.
- Opt out of email at any time, from any email we send.
Email support@racezon.gg. We aim to answer within 15 days, which is the LGPD deadline and inside the GDPR's one month. If we cannot identify you as the driver in question we may ask for something that reasonably shows the account is yours — we will never ask for your iRacing password.
You also have the right to complain to a supervisory authority: the ANPD in Brazil, or your national data protection authority in the EU/UK.
Children and young drivers
iRacing admits members from the age of 13, so some driver pages may describe minors. We do not knowingly create accounts for anyone under 13, and we treat removal requests concerning a minor as a priority — from the driver or from a parent or guardian. If you are a parent or guardian and want a page about your child removed, email support@racezon.gg and we will act on it without requiring you to create an account.
How long we keep it
- Driver pages: refreshed while the page is switched on; deleted on request.
- Cached race results: the raw result of a race, which names its whole grid, is kept while the race page exists. Publication of it is already anonymous for anyone who did not switch a page on; deletion of the cached copy is on request.
- Account data: until you delete your account.
- Server logs: 60 days, then deleted automatically.
- Removal requests: we keep the request itself — your customer ID, the reason you gave, the email you contacted us from, whether it concerned a minor, and the date. We keep it so the page is not rebuilt later by an automated job, and so we can show we acted. That record is not published anywhere.
Cookies
We use one cookie to keep you signed in. It is strictly necessary and has no alternative. We set no analytics or advertising cookies at all today. The consent banner is built and will appear only if we ever enable analytics; until then there is nothing to consent to, so you are not asked. If that changes, declining will be a single click, with no penalty and no repeated nagging.
Security
Passwords are handled by AWS Cognito and never reach our servers. Traffic is encrypted in transit. We keep the amount of personal data we hold deliberately small — the best protection for data about you is our not having it.
Changes
If we change this policy in a way that materially affects you, we will update the date at the top of this page and, where it matters, tell account holders by email.