Privacy Notice

Authentic Racing eSeries · last updated 2026-08-24

This notice explains how Authentic Racing eSeries handles your personal data when you race on our Assetto Corsa EVO servers and use our stats and chat. You can reach Authentic Racing eSeries through its Discord.

Who is responsible

Authentic Racing eSeries is the data controller for the data it processes about its own drivers. Authentic Racing eSeries takes part in the SimRacers network, a shared platform of independent racing communities. Each connected community is its own separate controller for its own drivers.

What we collect

Your Steam ID, your driver name or nickname, your Steam avatar, and your nationality if your Steam profile provides it.
Your racing data: race results and the stats derived from them — ELO rating, Safety Rating, lap times, incidents and similar.
Your entries: race and championship sign-ups, and track votes you cast.
Optional social links you add yourself (Twitch, YouTube). If you add one, we check publicly whether that channel is live so the page can show a “live now” badge.
Chat: the messages you send and any image you attach to one. An address is recorded on one kind of message: the “come race with us” server invite carries the IP address and country you sent it from, for moderation. v0.116.0 narrowed that to the invite alone — an ordinary message, a reaction and a private message record no address at all.
Duels: the challenges you send or accept, the laps that settle them, and the one-to-one rating they build up.
While you are on one of our servers: your car, your lap and sector times, and any incident the server reports, together with the other car in it.
Presence: while you have our stats page open, the fact that you are online. This is held in memory only and disappears when you close the page.

What is public

Our statistics pages are public by design, and that is worth stating plainly rather than leaving you to discover it. Without signing in, anyone on the internet can read driver profiles, rankings, lap times and results, the chat history, and who is online right now.

Two things are deliberately kept back:

Steam IDs — in the online list, on the live timing board, and in incident reports — go only to visitors who have proved who they are. Everyone else sees names and avatars, so a roster still reads as a list of people but cannot be harvested as a live account-to-server map. v0.95.0 extended this to the timing board and incident reports, which had been publishing account ids to anyone.
Chat sender IP addresses and countries are visible to community admins only — never to other visitors.

Two further things are readable without signing in, and it is better to name them than to leave them to be found:

The status file each server publishes — its name, address, current track, and the live board: driver names, cars, nationalities, lap and sector times and the last 25 incidents. Account ids are not in it v0.113.0, and a server the operator has hidden from the public pages does not publish one at all v0.117.0.
Images posted in chat, which are served from an unguessable address without a login, and are deleted once no message refers to them.

Writing is not open in the same way as reading: posting in chat, reacting, editing and private messages all require a proved Steam account or an admin session. The local Notifications feed takes nothing typed by anybody — it carries this Manager's own announcements only v0.116.0.

Following other drivers, and where you are

You can follow other drivers. Following is a bookmark: it needs nobody's permission and reveals nothing new, because a driver's profile, records and career are already public on these pages. Your own follow list is visible to you and to nobody else — there is no way for anyone, including us, to ask who follows a given driver.

Whether other people can see which server you are on is off until you turn it on, and it is your choice, not your community's. An operator can switch the whole feature off for their community; they cannot switch an individual on. From your driver profile you choose one of three answers — nobody (the default), people I follow back, or anyone on the network — and separately who may send you a private message. You can block individual drivers, which overrides every one of those settings in both directions.

While that setting is on, what is published is the minimum that answers the question: your SteamID, the name of the server, its join address, and when you joined it. Not your car, not your lap times, not your position. It is held in memory on the hub, expires within about three minutes of your community's last update, and is never written to disk anywhere. Someone who does not follow you cannot see it at all, and a driver who is offline and a driver who has not allowed you look exactly the same — deliberately, so that the setting itself cannot be detected.

Private messages can now reach drivers at other communities. They travel through the hub, which routes them to the communities that have the recipient and keeps no copy: there is no queue and no message store on the hub. Each side's own Manager keeps its half of the conversation. If a message cannot be delivered, the sender is told so rather than left believing it arrived. No page in this Manager shows a conversation to anybody but the two people in it, and the hub never holds a copy. Be aware of where that promise ends: the messages sit in an ordinary file on this community's own server, so whoever administers that machine can read it, and a chat admin can delete a message from a conversation they cannot see. You can delete every conversation you are part of from your driver profile — that removes this community's copy for both sides; a driver at another community keeps whatever their own Manager stored.

Voice chat passes through this Manager only as call setup. There is no recording, no relay server and no stored audio — the sound goes directly between the people talking, which as in any browser voice call means the participants' network addresses are visible to each other. Who is in a voice room is shown to everyone; the SteamID behind a voice participant goes only to visitors who have proved an identity.

Why we use it, and our legal basis

We process this data on the basis of legitimate interest (GDPR Art 6(1)(f)):

To run our servers, stats pages and rankings, and to share racing results and ratings across the SimRacers network so drivers can be compared community-to-community. Competitive results appearing in rankings is something drivers reasonably expect — and you can object at any time (see your rights below).
To keep chat usable and moderated (this is why a sender's IP is briefly recorded).

Who we share it with

Your racing results and ratings are shared to the SimRacers network and are visible to the other connected communities. The network is coordinated by a central hub hosted in Sweden (EU/EEA), and is accessible worldwide. What travels to the hub is your driver identity and your career stats — not your chat messages and not your IP address. The exceptions are the shared network channels and the network admin room, which are visible to the other communities by design, because that is what they are for. We do not sell your data or use it for advertising.

Specifically, the hub receives and publishes:

Your network profile: SteamID, driver name, nationality, and your career totals with a network-normalised ELO and Safety Rating.
Your lap records — since v0.86.0 there is a network-wide fastest-lap board, one per circuit. A row carries your name, nationality, the car, the lap time, the date and the community it was set in. Only laps that already count on this community's own record board are sent: nothing you cut, nothing an admin removed.
Your race sign-ups, for races published to the network calendar — and, if you enter a race at another community, your SteamID, name, nationality and avatar are passed to that community so it can put you on its entry list.
Your network duels: both drivers' SteamID, name, avatar, nationality and community, the laps that settle the duel, and the ladder rating. This one is published openly by the hub, as are the network leaderboard and the fastest-lap board.
Cross-community series results, where this community takes part in one: finishing position, SteamID, name, nationality, time, best lap and laps.
Your follow and block lists and your two visibility settings, which are kept by the hub rather than here, and — only while you have switched it on — the presence record described above.
Whatever you post in a shared network channel: the message, your name, avatar and SteamID, and any image, which is stored on the hub so the other communities can load it. A private message to a driver at another community passes through the hub to be delivered; it is not stored there.

Outside the network

Discord, if this community has connected a channel. Announcements we send can carry driver names: who joined or left a server, race results and the fastest lap (including the previous record holder), championship standings, the grid for a scheduled race, duel results, and — if you added a Twitch or YouTube link — a “live now” post naming you and linking your channel. Every one of these is a switch the operator turns on; announcements travel to Discord, which is a US company.
Twitch and YouTube, but only if you added that link yourself. Once a minute (Twitch) or every five minutes (YouTube) we ask those services publicly whether the channel you named is live. Your SteamID is never part of the question — only the channel name you chose to publish.
Steam, when you sign in: the sign-in itself is Steam's own, and we then read your public Steam profile once to get your display name and avatar.
A link you paste in chat is fetched by this server so the chat can show a preview. The request comes from this machine, not from the browser of whoever reads it, so nobody's address is exposed to the site you linked.

We do not use any analytics or advertising service, and there is no tracking of visitors between pages.

Two things about the network that are not about you: the hub records a daily count of drivers, communities, servers and laps for a growth chart — totals only, no names — and it derives the country a community's servers are in from the address that community's Manager connects from. That is a fact about the community, not about any driver, and the address itself is never published.

Cookies, and what your browser keeps

This site sets no cookies at all, and nothing here tracks you across sites. What it does use is your browser's own storage, on your device, which we never read from the server:

Your sign-in token after you sign in with Steam, so you stay signed in — and, for operators, the admin panel's own token.
Your own display preferences: theme, text size, which chat channel you were last reading, and which kinds of chat notice you have chosen to hide.

Signing out removes the token. Clearing your browser storage signs you out and forgets the preferences; it changes nothing about the data described above.

How long we keep it

Chat IP address and country are automatically removed after 90 days; the message text remains.
Chat history is capped at roughly the most recent 200 messages per channel — older messages fall off on their own.
Presence is not stored at all — not on this Manager and not on the hub. It lives in memory for as long as you are on a server with the setting on, and is forgotten within about three minutes of the last update.
Private messages are removed after 180 days, and each conversation keeps at most the most recent 200 messages. You can delete all of yours at any time from your driver profile.
Your follow list, block list and these two settings are kept on the hub until you change them, or until you erase yourself from the network — which removes them, including your name from every other driver's list.
Images posted in chat are deleted once no message still refers to them — the sweep runs every six hours.
A Steam sign-in lasts 90 days from your last visit; an operator's panel session lasts 30 days. Both are removed when they expire, and signing out removes yours immediately.
Your racing stats are kept until you delete them or delete yourself from the network (see below).
Backups. This Manager takes automatic backups so a failed update cannot destroy a season, and a backup is a copy of everything above as it stood that day. Data you have deleted survives in older backups until they are replaced.

Your rights — and how to use them

Access & portability — “Download my data” gives you a machine-readable JSON copy of what this community holds about you: your profile and network-sharing setting, your stats and rank, your lap records, the chat messages you posted, your private messages, your duels, your race and championship sign-ups and your race-night votes v0.117.0. Your follow and block lists live at the hub rather than here, and are shown to you on your profile.
Erasure — “Delete me from the whole network” removes you here, at the hub and at every connected community — profile, career stats and your lap records on the network board. Communities that happened to be offline at that moment apply it when they reconnect, for up to 90 days afterwards. You can also wipe just your stats on this community.
Object / opt out — opt out of network sharing; your stats then stay only on this community's pages, and you are left off the network's fastest-lap board as well. Opting out does not block a later erasure request — the network handles “delete me” even for drivers it has no record of.
Rectification — edit your display name on your profile.

Erasing your racing data wipes it here rather than hiding it, so that part cannot be undone. An admin can put you back on the network, but your wiped results do not come back with you.

What an erasure does not reach, so that you know rather than assume: messages you posted in chat stay where you posted them, here and on the other communities that received them — ask an admin, or delete them yourself, which you can do at any time. The same is true of results already recorded in a cross-community series, and of backups, which keep a copy until they are replaced. Everything else — your profile, your career stats, your lap records, your duels, your follow and block lists and any presence record — is removed here, at the hub and at every connected community.

You also have the right to lodge a complaint with your local data protection authority.

How we protect it

Everything this community sends to the network hub travels over HTTPS, with the community's key in a request header rather than in a web address; the admin panel only ever displays that key masked.
Files holding credentials on our server are readable only by the account running the Manager.
A chat connection is accepted only against a short-lived, single-use ticket issued over HTTPS first, and writing is rate-limited.
Anything a driver types is escaped before it is shown to anyone else.
Repeated wrong passwords on the admin panel lock that address out for a while, and the lockout counts the real caller rather than a shared proxy address.
Erasure requests reaching the hub are authorised, rate-limited and logged, so no single community can sweep the network.

International transfers

The network hub is hosted in Sweden, within the EU/EEA. Because the network is open to communities worldwide, and because our stats pages are public, your shared racing data may be viewed from outside the EU/EEA. Where this community has connected Discord, or where you have added a Twitch or YouTube link, the announcements and live checks described above involve services based in the United States.

This notice is provided by Authentic Racing eSeries using ACE Manager. It reflects the current setup of this community and may be updated as the software changes.