Privacy policy
1. Controller
SimRacingKanal, owner: Thomas Ilemann
Robinson-Crusoe-Str. 80
37627 Deensen
E-mail: simracingkanal@gmail.com
Each league on this site is run by its own organisers. For questions about a specific league, please contact its admins on Discord.
2. What we store and why
- Discord login: Discord ID, display name, avatar, the servers you share with the bot and your roles there. Needed to log you in and to know which leagues you may see and manage (Art. 6(1)(b) GDPR). The website silently re-reads servers and roles every 12 hours; for admins and race control the bot additionally checks the roles with Discord every 15 minutes so that removed rights end right away. If you leave a Discord server, Discord tells the bot; your membership in that community is then removed immediately. When the bot joins a new server or a community is approved, it asks Discord for each existing account individually whether it is a member there (with roles and admin right), so that admins can create leagues right away (the bot neither loads nor stores member lists).
- Code of conduct: when you confirm it, we store the confirmed version and the time – as proof, for as long as your account exists (Art. 6(1)(b) GDPR).
- Racing identity: RaceRoom user ID or – for Le Mans Ultimate, Automobilista 2, Assetto Corsa Competizione and Assetto Corsa – your Steam ID (confirmed via Steam login; we only receive the ID, never a password), your real name and the names you used in result files. Needed to match race results to you.
- League participation: registrations (class, car, livery, number; in leagues with splits also the split and your self-assessment if you have no rating yet), attendance, results, incidents, penalties, strikes, tickets and protests including chat messages, driver rating. Leagues can use the driver rating (Elo, safety) as a minimum requirement for registration and to sort drivers into splits of similar strength.
- Confirmations: time of confirming that you are at least 14, 16 or 18 (depending on the league) – for drivers aged 14 or 15 also the time of confirming their parents' consent – that your name and results are published, and of accepting the league rules.
- Driver rating across SimLigaManager (only if you switch it on, from 16): whether you show yourself across SimLigaManager. Then all logged-in users – also from other communities – see your driver name, country, Elo, safety rating and the number of your rated races per simulation; never your races, leagues or communities (consent, Art. 6(1)(a) GDPR, can be switched off at any time).
- eSports teams (only if you accept an invitation): a team is its own entry with name and logo on a Discord server with our bot – either a dedicated team server (approved by the operator) or a team of a league community, created by its admins. The team admins – the community admins (Discord admins) of the server the team is on, plus admins and team chiefs on the roster – invite members of the server with one role to one or several simulations (one invitation, one acceptance for all simulations listed; a community admin can add themselves as team chief when creating the team, with the same consent); anyone already on the roster can be added to further simulations by the team admins without a new invitation – everything below then applies to that simulation too, and you can leave at any time; we store the invitation (who invited whom, when, role, optional message) and – as your consent – the time you accept, decline or leave. An unanswered invitation expires after 30 days; it stays stored with the status “expired” and the time (visible in your data export) and is deleted together with your account. From accepting, the team members – accepted roster members and the community admins of the team's server (even without a roster place), not all members of the server – see your SimLigaManager races and results in this simulation from all communities, including private ones (team calendar, results feed, Discord posts in the team's server). The team profile also shows which community manages the team (for communities that keep to themselves, outsiders only see “a community”); only team members see the names of the community admins. Your name, role, Elo and safety rating appear on the team profile, which all logged-in users see; under 16, users outside the team only see your initials (and no rating). Visitors without login only see the team's name and logo. For races outside the SimLigaManager the team enters its own dates and may upload a results file: we only read it in memory and do not keep it; we store only the rows of the team's own drivers (overall and class position, class, laps, best lap, status) and the field size – never the names of other drivers. These results only count for the team, never for the driver rating, achievements, Wall of Champions, records or the news ticker. Discord posts on the team server show the team drivers' names in full, also under 16 (as with league posts). If the team chief switches them on, our bot posts in channels of the team's Discord server (results of official SimLigaManager races of team drivers – for private communities without league or community name –, a reminder 24 hours before a race), creates Discord events there for the team's dates and the SimLigaManager races of its drivers (for private communities only “Race of …” with track and time) and sends drivers assigned to a date a Discord message 7 days and 24 hours before (can be switched off under My account → Race reminder). The legal basis is your consent (Art. 6(1)(a) GDPR); you withdraw it at any time by leaving the team (My account → My teams) – the team then sees no new races or results. Memberships and your result rows are deleted together with your account. If a team has no drivers on its roster for 7 days, it is deleted together with its calendar, gallery and chat (its admins get a message one day before).
- eSports teams – line-ups, planning, gallery, team chat: team admins (community admins of the server, admins and team chiefs) can put roster members into line-ups (name, order; shown on the team profile like the roster) and assign team chiefs to line-ups. Team admins and managers can ask about your availability for a date (we store your answer yes/no/maybe and when you were asked and answered; asked by Discord message with buttons) and plan stints for long races (driver, start, duration/laps, note; you get a Discord message 30 minutes before your stint, can be switched off under Race reminder). Dates, stints and availability are deleted one year after the date; dates with a result stay as team history, without stints and availability. Team admins can register a season team in a league for the team; you are invited to it with the league's normal team invitation. Team gallery: pictures uploaded by admins, team chiefs and managers (optionally linked to a driver, line-up and car) are only visible to the team members (roster and community admins of the server) and are kept until the team deletes them; we store them without metadata on our server and only deliver them after checking the membership. Team chat (switched on for new teams, team admins can switch it off): messages, pictures, GIFs and reactions in the team channel are read and written only by roster members with an accepted invitation and the community admins (Discord admins) of the server the team is on; in a line-up's channel by its members plus admins, team chiefs, managers and the community admins of the server; team admins can delete messages. Messages are deleted automatically after 30 days, including pictures and reactions.
- Driver market (only if you use it): teams publish search requests (simulation, class, role, minimum Elo/safety, languages, times, text), leagues with open registration and free places appear automatically (never leagues of communities that keep to themselves); all logged-in users see both. If you switch on “Looking for a team / league” (from 16), we store your details (simulations, class, role, times, languages, text); only people who run a team or a league – team chiefs and admins of a team, the community admins of Discord servers with a team and league admins (not managers) – then see them together with your name, Elo, safety rating and number of races. Contact only runs via SimLigaManager: applications and requests with a chat (messages and time), status, and when each side released the contact – your Discord name is only shown once both sides have released it. The other side only gets a Discord message as a notice, without content. You can decline or block requests. We delete requests including the chat 180 days after the last message and expired or closed search requests after 90 days; switching off “Looking for …” deletes your details immediately. Legal basis: your consent (Art. 6(1)(a) GDPR).
- Prediction game (only if you predict): per race and class your picks for pole and podium with the time. Nobody but you sees your picks; the league leaderboard shows your name (driver name, otherwise Discord name) and your points to the members of the community and the registered drivers of the league. We calculate the points from the result, they are not stored. Your picks are deleted one year after the end of the season (for special events one year after the event) and together with your account.
- Year in review: we store nothing extra for it – it is calculated from your results and your driver rating and only visible to you (My account). You download the image to share yourself; what you do with it is up to you. We only remember that you have seen the notice about it.
- Lights Out (reaction test, only if you play): every reaction time or jump start with its time, and whether you show yourself across SimLigaManager. The leaderboard of your communities shows your name and best time to the members of that community; across SimLigaManager only if you switch that on yourself (consent, Art. 6(1)(a) GDPR, can be switched off at any time; only from 16, under 16 never across SimLigaManager). Attempts older than 12 months are deleted – except your best time; everything is deleted together with your account.
- SimRacingKanal on Instagram and Facebook: for SimRacingKanal's leagues and special events, public posts with a graphic are created automatically on Instagram and Facebook (preview, “live now”, result) – likewise for races of other communities that SimRacingKanal commentates, as long as that community's admins don't switch it off in their settings (on by default, also for communities that otherwise keep to themselves; only races from the moment it is switched on are posted). Drivers of such communities are only named after they have seen the notice about it in the SimLigaManager; until then only their initials are shown. Like the commentator in the stream, they name drivers, for example the championship leader or the podium. The legal basis is our legitimate interest in reporting on the leagues' races (Art. 6(1)(f) GDPR). You can object at any time: untick the box under My account → Instagram & Facebook – future posts then only show the initials of your first and last name (e.g. “C. B.”). For drivers under 18 or of unknown age, only the initials are ever shown. The same applies to commentators – if they object or are under 18, the post names no commentator. We store the posts (text, graphic) and, if applicable, when you objected; we delete the graphic on our side after 30 days and the entry with the text after one year. If you delete your account, we remove your name from the stored texts and delete the related graphics immediately. The posts go to Meta Platforms (Instagram, Facebook) and are public there; Meta's privacy policy also applies, including a transfer to the USA. SimRacingKanal can delete Facebook posts; Instagram posts only by hand – contact us via the contact form.
We do not collect an e-mail address at login (only the contact form asks for one without login, see below). There is no tracking and there are no ad networks (own ads see “Advertising”). Cookies are only used for the login session and your settings (language, order of the sidebar) – for the operator also a marker so that the operator's own visits to the showcase and demo are not counted, and one for his confirmed device (second factor); light/dark mode and some views are remembered locally by your browser and are not sent to us. The look chosen under My account (Discord look or “Rennstrecke”), whether the custom mouse pointer is on and which community you pinned to the top of the start page are stored with your account so that they apply on every device; this is included in the data export and deleted with your account. If you, as an admin, voluntarily turn on the second factor under My account (off by default), we store the secret for the authenticator app encrypted and your recovery codes only as a check value; a cookie remembers your confirmed device for 30 days. Turning it off deletes both; the data export only shows since when it has been set up. The fonts of the “Rennstrecke” look are delivered by our own server; there, only your browser remembers when you last opened the news (for “new since your last visit”), this is not sent to us.
Server logs: to defend against attacks and abuse, our server logs every request with time, requested address (without parameters), result and duration. The IP address is only stored encrypted; only the operator can decrypt it, with a key that is not stored on the server – and only if an attack or abuse has to be investigated. Browser identifier and referrer are not logged. Logs are deleted automatically after 7 days (Art. 6(1)(f) GDPR – legitimate interest in secure operation). Older logs up to 5 Oct 2026 contained the IP address unencrypted; they are deleted automatically by 12 Oct 2026. Against too many pairing and sign-in attempts we also briefly count attempts per internet address – only as a non-reversible check value (hash), deleted after 24 hours at the latest.
Images from other services: profile pictures, server icons and emojis from Discord, car and track images (e.g. RaceRoom, Le Mans Ultimate, The SimGrid) and GIFs (Giphy, Tenor) are fetched and served by our server. Your browser does not load them from these services; they receive no data about you. For the GIF search in the chat our server only sends the search term and the language to GIPHY.
Voice room: in the chat's voice room, audio goes encrypted directly from browser to browser (WebRTC) or, if that is not possible, via our own relay server; it is not recorded. Our server brokers the connection and stores for a few minutes who is in the room. With a direct connection, participants can see each other's IP addresses. Only our own server (STUN/TURN) is used to set up the connection; no third-party server is contacted.
Visitor counter (“online” and “visits” on the website): without cookies and without storing IP addresses. From the IP address and the browser identifier – if you are logged in, from your account ID, so that phone and PC count only once – we compute a one-way code that changes every day (at midnight German time); it is kept only for the current day and afterwards reduced to the number of visits per day. It is not possible to recognise you with it or to follow you across days (Art. 6(1)(f) GDPR, legitimate interest in anonymous reach statistics). For the showcase and demo pages the operator also counts how many different people opened them: for guests with the same daily code, for logged-in users with the account ID, only so that nobody is counted twice. These figures are only visible to the operator and are deleted together with your account. If you request access to the demo on the demo page, we store with your account when you asked, whether and when the operator granted or declined it and until when access is valid – so that only approved accounts can open the demo (Art. 6(1)(b) GDPR). This is included in the data export and deleted together with your account.
Livery designers: if you create a designer profile, your name, description, services, links, portfolio images and ratings are visible to all logged-in users after approval. Requests, applications and chat messages are only visible to you and the respective client (league admins or the requesting driver). Profile and images are deleted together with your account.
Commentators: if you create a commentator profile, your name, description, services, links and ratings are visible to all logged-in users after approval. Applications and chat messages are only visible to you and the admins of the league concerned; agreed fees are only used for average prices shown to league admins.
Contact form: name, topic, message and – without login – your e-mail address (when logged in also your Discord account) go only to the operator to answer your request (Art. 6(1)(b) or (f) GDPR). Against spam we do not store your IP address in plain text, only as an irreversible check value, together with the message. Handled messages are deleted after 180 days at the latest, immediately on request, and together with your account.
Bug reports (beta phase, admins, race control, commentators, livery designers, photographers and sponsors only): title, description, affected page, browser identifier and an optional screenshot go to the operator and are only used to fix bugs. Screenshots are not public. If your account is deleted, the report is kept without your name. Handled reports are deleted 180 days after they were closed, including the screenshot.
SLM Duell (racing game, only if you play): for every finished race – also against the computer – we store the track, total time, best lap, whether you won and the time; this produces the leaderboards per track (your name and time for the members of your community; across SimLigaManager only if you switch it on yourself – consent, from 16, can be switched off at any time), the badge for the winner of the track of the week, the message “leads the track of the week” in your community's news bar and your unlocked liveries (stored together with your chosen one). We delete races after one year – except your best time per track – and everything with your account. If you challenge someone from your community, we store who challenged whom on which track, the answer, times, whether you are currently on the duel page, your race times and the winner; your opponent gets a direct message in SimLigaManager (the rules for direct messages apply). The race itself runs directly between your two browsers or via our own server; the browsers exchange your car's position and speed and the network addresses needed for the connection (the other browser may see your IP address). We delete this connection data after 2 minutes, duels after one year and with your account. Track layouts of real circuits: © OpenStreetMap contributors (ODbL).
League chats: messages in the driver chat are seen by the league's drivers, in the race control chat only by race control and the admins. They are deleted automatically – in the driver chat after 7 days, in the race control chat after 30 days (including images and reactions). If you report a message (“Report driver”), we store who reported which message and when: the message is then hidden for you and the person is blocked for you in direct messages. The league admins receive a Discord message from our bot with the name and text of the reported message (without your name); the operator receives the message, the five messages before it and your name in order to look into abuse (Art. 6(1)(f) GDPR) – this is handled like a contact message and deleted after it has been dealt with. The record of who reported which message is deleted with the message or with your account; if you delete your account, we also remove your name and Discord ID from stored reports (as reporter, reported person or author of a quoted message).
Practice leaderboard (RaceRoom, only if the community runs our practice program on its RaceRoom server): the program sends the live data of the practice servers (RaceRoom name and ID, car, lap times). For drivers registered in the league we keep the personal best time per track for the season; it only appears on the league's practice page and does not count for championship, rating or track records. For troubleshooting we additionally log for 14 days who was on the server (RaceRoom name and ID), with car, best lap, number of valid laps and why a time did (not) count, as well as whether the server delivered data – visible only to the league's admins and the operator, deleted automatically after 14 days.
Activity rating: when you are logged in, we only store per day that you visited the site (date only, no time, no pages) – the only exception: which race analyses you opened (once per race and driver, with the time; as a steward also whose analysis you checked), because that earns a point. From this and data stored anyway (races driven, attendance answers, driver chat messages, photos, thumbs, reviews) we calculate the activity rating of the last 30 days, visible to logged-in members. The days and opened race analyses are deleted after 90 days and removed together with your account (Art. 6(1)(f) GDPR – legitimate interest in an active community).
Commentator reviews: if you drove in a commentated race, you can rate the commentator with stars and an optional comment. Stars and comment are visible without your name to the commentator, the operator and logged-in users who may see the league (comments and league); the star average is visible to all logged-in users. We store who rated so that everyone can rate only once.
Advertising: we only show our own ads (image and link, labelled as advertising), no ad networks, no cookies. We count how often an ad was shown and clicked – only as numbers per day, without any data about visitors. So that the same visitor counts as at most one click per ad and day (and advertising enquiries are limited), the server keeps the one-way daily code described under the visitor counter in memory until the end of the day; it is never stored. A click on an ad takes you via our site to the sponsor; from there the sponsor's privacy policy applies. Advertising enquiries (company, contact person, contact details, message) are stored only to handle the enquiry (Art. 6(1)(b) GDPR) and deleted 180 days after the decision – accepted enquiries only once the ad has ended.
Minors: leagues can allow drivers from the age of 14. Drivers aged 14 or 15 may only register with the consent of their parents or legal guardians (Art. 8 GDPR); they confirm this with a checkbox when signing up, and we store the time. We cannot verify the consent ourselves – if we learn that it is missing, we remove the registration and, on request, the account. Parents or guardians can contact the operator at any time (see 1.) to request access to or erasure of their child's data. For their protection, drivers under 16 cannot use direct messages, requests to photographers, commentator/livery designer/photographer profiles, the display of their own stream and other drivers' streams (league race broadcasts stay visible); their name is not shown in polls.
Birthday (optional, My account): used only to check your age for leagues with a minimum age and – only if you allow it (default off) – to congratulate you on your birthday in the news ticker – visible only to logged-in members of your communities, showing your name but never your age (Art. 6(1)(a) GDPR, consent). If a newly entered birthday does not match your “14 or 15” statement from the last 12 months, that statement continues to apply until it has been checked: the operator receives a Discord message from our bot with your name and either accepts or deletes the birthday; we store the time until then (Art. 6(1)(c) and (f) GDPR, protection of minors). You can change or delete it at any time under My account; it is deleted together with your account.
Your own streams (optional, My account): if you enter your YouTube or Twitch channel, our server regularly checks whether you are live – for YouTube via the public channel page, for Twitch via the official Twitch API (only your channel name is sent). While you are live, logged-in users see your name, the title of your stream, the number of viewers and the link under “LIVE” – members of your communities always, users of other communities only if at least one of your communities allows sharing (a setting of the community admins; private communities never share); members of your communities and drivers of your leagues also see your stream links permanently on your driver profile, marked LIVE while you are streaming. In the “Rennstrecke” look your running stream can also be embedded there as a preview (only after the viewer clicks, see “Streams”); for this our server remembers the YouTube video currently running. Remove the links under My account to stop both. This is not available under 16. If you entered two channels, LIVE only shows the one you choose for it (YouTube or Twitch); only that one is checked then. From version 1.0 you only appear under LIVE with Pro.
Messages from the bot: our Discord bot sends you direct messages about your leagues – for example race reminders, the server password, moving up as a reserve driver, a split change, bans from strikes and the decision on your Pro beta tester request. You can switch off race reminders and split messages under My account; messages about your starting place always reach you.
Help chat “Ask Mr. Pitwall” (only for league admins and race control, only if you use it): We send your question and the previous questions and answers in the open chat window, together with the text of our guides, to the AI “Claude” of Anthropic, PBC (USA), which writes the answer. We do not transmit your name, your account, your league or any other SimLigaManager data – please do not put personal data into your question yourself. Anthropic processes the data as a processor only to create the answer and, according to Anthropic, does not use it for training; the transfer to the USA is based on appropriate safeguards (EU standard contractual clauses). We store neither questions nor answers; the history only exists while the page is open. Per question we only store the time, the number of tokens and the cost (not linked to you) and, for the limit of 30 questions a day, a non-reversible checksum of your account with the time, which is deleted after one day. The legal basis is our legitimate interest in helping admins and race control use the site (Art. 6(1)(f) GDPR).
Weekly series: reporting a driver with video (only in leagues run as a weekly series without race control): drivers registered for the league can report another driver – with a short description, optionally the race and a video as evidence (MP4, MOV or WebM, at most 15 MB). We store the report (who reports whom, text, race, time) and the video. Only the admins of this league see report and video; the reported driver is not notified. Each driver can have at most 3 open reports at a time. We delete the video as soon as the admins have decided (ban or reject), but at the latest after 30 days: if the admins have not decided by then, the report is closed automatically and the video deleted (after 7 days the admins receive a Discord message from our bot with the number of open reports, without names); the report itself stays stored with the decision until the league is deleted or one of the two drivers deletes their account. If the admins ban a driver, we store the ban (driver, RaceRoom ID, reason, who banned, time) and add the RaceRoom ID to the ban list of the community's RaceRoom servers (via their server software). The ban applies until an admin lifts it; then we remove the ID from the ban list. The legal basis is our legitimate interest and that of the league in fair racing (Art. 6(1)(f) GDPR). Your reports and bans against you are included in your data export under My account.
Suggested reason for race control decisions (only for race control and league admins, only when they click “Suggest text”): To write the reason of a decision, we send the following to the AI “Claude” of Anthropic, PBC (USA): the names of the drivers of this race involved (offender, other drivers, drivers accused in the report, reporting driver) as shown on the result page (unregistered drivers only with initials in leagues that use initials), the text of the driver’s report in the ticket, the race, track, lap and corner, the decision entered by race control (type, seconds, strikes, points deduction), the rulebook of the league created in the SimLigaManager and up to three earlier reasons of the same league as a style guide. Messages in the ticket chat and data of other leagues are not transmitted. If you delete your account, your name in the stored reasons is replaced automatically. Anthropic processes the data as a processor only to create the text and, according to Anthropic, does not use it for training; the transfer to the USA is based on appropriate safeguards (EU standard contractual clauses). The suggestion is only inserted into the form; only what race control saves is stored, as with any decision. Per suggestion we only store the time, the number of tokens and the cost (not linked to anyone) and, for the limit of 60 suggestions a day, a non-reversible checksum of the account with the time, which is deleted after one day. The legal basis is our legitimate interest and that of the league in consistent, clearly worded decisions (Art. 6(1)(f) GDPR).
SLM News (previews, race reports, season previews and season reviews): For races of a league that uses SLM News, SimLigaManager has reports written by the AI “Claude” of Anthropic, PBC (USA). For this we transmit a fact package about the race: league, season, track, date, result with driver names as shown on the result page (unregistered drivers are left out or shown with initials), car numbers, cars, laps, times and gaps, race progress from the result file (positions, pit stops, retirements, contacts), race control decisions with their reasons and the championship standings; for a preview also attendance and season record; for the season preview, once 80% of the places are taken (at the latest shortly before the first race), the calendar, the cars, the entry list (name, number, class, car, team) and last season’s final standings; for the season review, when the season is ended, the final standings, the winners and podiums of every race and the championship lead over the season. No Discord IDs, email addresses, Elo or safety values. Anthropic processes the data as a processor only to create the text and, according to Anthropic, does not use it for training; the transfer to the USA is based on appropriate safeguards (EU standard contractual clauses). The report is published automatically for the members of the community (for special events all signed-in users, unless the community keeps to itself), guests never see it; the league's admins and race control can edit or withdraw it at any time. If the league has chosen a Discord channel for SLM News, our bot posts the report's title and intro there once (they may contain driver names), with a link; the report itself can still only be read by logged-in users. The legal basis is our legitimate interest in reporting on the league's races (Art. 6(1)(f) GDPR). The report and the fact package are stored until the race is deleted; if you do not want to be named in a report, contact the league or us – we will remove the name; if you delete your account, your name in the reports is replaced automatically. So that the “New in SLM News” box disappears after reading, we store on your account when you last opened a report; it is deleted with your account. If you react to a report with an emoji, we store the report, the emoji, your account and the time – other readers only see how many people reacted with which emoji, never who. Reactions are deleted automatically after 30 days and together with your account.
SimLigaManager Pitwall (voluntary, aged 18 or over; part of Pro – until version 1.0 for Pro beta testers, afterwards with Pro): If you pair the Windows program with your account, it reads along in Le Mans Ultimate, RaceRoom and Assetto Corsa Competizione (it only interferes with the game when your team sets your pit stop in the team lobby – see below) and analyses every session on your PC. It only sends races of a league you are entered in to our server, as a summary per lap: lap time, times per track section, speed trace, braking points, shares of throttle, brake and coasting, longitudinal and lateral acceleration (samples), fuel use, tyre temperature (inside, middle, outside), tyre pressure and wear, your position, gap and car number of the cars directly ahead of and behind you, pit times (also those of other cars, without names), overtakes, detected off-track moments and slides, and one lap of your positions on track (for the track map). The program does not transmit other drivers' names. These races appear in your race analysis. Pitwall does not transmit practice, qualifying and races on other servers – they only stay as a recording on your PC (see below); the only exception is the reference lap. Only you see these values, not race control and not the operator. Technical check values: After every session Pitwall also sends anonymously – without reference to your account or device, without track and lap times – the simulation, program version, number of laps and whether ride height, suspension travel, dampers, tyre temperature, tyre pressure, yaw rate, raw pedal values, wheel speeds and steering force were read plausibly, plus their averages, the highest steering force value and the steering wheel angles (set and car). This lets us spot errors when reading a game. We only store daily totals per simulation and delete them after 60 days. Team lobby (ACC): If you are in the roster of an eSports team, you can create a lobby for your team in Pitwall (optionally with a password) or join one. Lobby members see your name and whether you are online. While you drive, Pitwall sends your live values (speed, gear, rpm, pedals, steering, fuel, tyre temperature and pressure, brake temperature, driver aids, lap times, delta, position, pit) to us several times per second; the lobby members see them in their Pitwall and overlay, your team's roster also on the team's “Live analysis” page. Only the latest state is kept, plus per lap the lap time, validity, fuel used, tyres, pressure and position as the lobby's lap history (used for the fuel calculator, tyre trend, stints and driver comparison) – visible only to the team's roster, not to the operator or anyone else, deleted 30 days after the lobby ends (it ends when nobody has been online for 10 minutes), with “Delete all Pitwall data” and with your account. The legal basis is your consent by joining; you can leave the lobby at any time. Set pit stop (Pro): Roster members with Pro can set fuel, tyres, tyre pressure and repair for the driver at the wheel; the driver's Pitwall then sets the pit menu in the game (LMU via the local interface on your PC, ACC by key presses) and reports whether it worked. Only the latest request is kept (values, who made it, for whom, result) until the lobby ends. By joining the lobby you allow this. Send log: If you click “Send log” in Pitwall, the program sends the latest entries of its log (technical messages such as connection, detected games, updates – no driving data) to us so we can find an error. Only the operator sees it; we keep the last 5 per PC for at most 14 days. The operator can ask for the log with a notice that appears as a Windows notification – it is only sent when you click. On every connection Pitwall also reports its program version including the build stamp. Reference lap: From every session you drive yourself, Pitwall sends your fastest valid lap: simulation, type of session, track and track length, car and class, lap time, times per track section, speed trace, braking points and the conditions (fuel at the start of the lap, air and track temperature, wetness, tyre temperatures of the lap – as far as the game provides them). With your account we store your best time per day, track and car (time and date only) – this gives your progress per track and the anonymous ranking "faster than … % of drivers", which others only see as a percentage without names; we delete it after 365 days. If the lap is the fastest of all SimLigaManager drivers on this track in this car (overall or in a race), we store the whole lap with its conditions and keep it until someone is faster. Other Pitwall users see it in their analysis and as a live comparison in the overlay – anonymously, without name, car number or account; only the lap time, the car, the conditions and the values of the lap are shown. If you set a record or yours is beaten, our bot sends you a Discord message (without the other driver's name; at most one per track and car per day). Everything is deleted with "Delete all Pitwall data" and with your account. If you request access, we store the time of your request until the operator has decided. When a PC is connected to your account, you receive a Discord message from our bot with the name of the PC. For each paired PC we also store its name, the program version, the time of your consent and of the last connection, and a key (only as a check value). The legal basis is your consent (Art. 6(1)(a) GDPR); you can withdraw it at any time by unpairing the PC and choosing "Delete all Pitwall data" under My account. Otherwise the data is deleted together with the result files 90 days after the end of the season (at the latest one year after the last race) and with your account. The program downloads new versions from our server itself and only installs them with a valid signature (only the PC's key is sent). With every connection the program receives a licence signed by us (account number, type of access, expiry date, check value of the key), which lets it run for up to 7 days without internet. On your PC the program stores its settings (the key encrypted by Windows), this licence, the arrangement of your overlays, a log without driving data and your recordings: every session you drive yourself (practice, qualifying, races, also on other servers; never as a spectator) with the same per-lap values as above, plus per lap suspension (travel, ride height), handling (steering effort and oversteer per track position), hard braking, pedal values at rest, steering wheel angle, steering force, wheelspin, rev limiter, brake temperatures, flat spots and impacts; for the 30 fastest laps of each session additionally with the driving line, steering, gear, rpm, tyre temperature and tyre pressure about every 5 metres (for the lap comparison in the program), compressed in the program's folder – without names of other drivers. They do not leave your PC. Pitwall keeps at most the last 50 sessions or 30 days and 50 MB and deletes older ones itself; pinned ones (at most 10) stay until you delete them. You can delete them in the program under Recordings, one by one or all at once. Overlays, the workshop and the OBS link run only on your PC (address 127.0.0.1); their values are not sent to us. If you drive a league or event race you are entered in, Pitwall fetches the car number, Elo and safety grade of the drivers in this race (with splits only your split) for the tower and shows them only in the overlay on your screen, never in the OBS image; they are not stored on the PC. For this the program window uses Microsoft Edge WebView2, which is part of Windows – only for these local pages; the fonts are built into the program (no requests to Google). Whether WebView2 sends diagnostic data to Microsoft depends on your Windows settings.
Pro (optional, “Become Pro” and My account): if you ask to become a Pro beta tester, we store the time of your request until the operator has decided, and the operator receives a Discord message from our bot with your name. You receive a Discord message from the bot about the decision (approved, declined, ended). If you have Pro (as a beta tester or later activated by yourself), we store the time. Logged-in users who may see your driver profile or your chat messages see the Pro badge there. Pro is available from 18; for this we use your birthday or your “at least 18” confirmation when signing up for a league. If Pro ends, we delete the time.
Polls and driver of the day: we store your vote together with your account so that everyone votes only once and can change their vote. In polls, members see who voted for what unless the admins made the poll anonymous; for the driver of the day only the number of votes is shown, never who voted. Your votes are deleted together with your account.
YouTube live streams: for races commentated by SimRacingKanal, SimLigaManager creates a public live stream on the SimRacingKanal YouTube channel 7 days in advance (Google/YouTube, USA). Only information about the race is sent: league, season, track, date, schedule, number of registered drivers, the sign-up link and a thumbnail – no driver names. Likewise, SimLigaManager adds these races to the schedule of the SimRacingKanal Twitch channel 7 days in advance (Twitch Interactive, USA) and sets title, category and tags one hour before the start – also without driver names. We store the access to the channels encrypted.
SimLigaManager survey (30 Oct to 13 Nov 2026): logged-in users who have visited on at least 5 days (counted via the activity days, see activity rating) see a window with 5 voluntary questions once. We store your answers anonymously, that is without your name, your account or the time, only with the day. In addition we store what SimLigaManager already knows: your role (driver, stewards, admin or member), the sims of your registrations, your communities, the chosen look and whether you answer on a phone or a PC. Only the operator evaluates the answers, and only for groups of at least 5 answers. Please do not enter names or personal data in free-text answers. With your account we only note that you took part, so that the window does not come back (legitimate interest, Art. 6(1)(f) GDPR); this note is deleted together with your account. We use the anonymous answers to develop SimLigaManager further. As they are not linked to any account, we cannot hand them out or delete them individually.
Direct messages: members of a community can write to each other within the community (not under 16, not with “do not disturb” or when blocked). Messages (text, GIFs, reactions – images cannot be sent for now) are only visible to the two people involved – not to admins or the operator in the app – and are deleted automatically after 48 hours (in encrypted backups for up to 3 days, in the backup made before installing a new version until the next installation). Drivers under 16 cannot use direct messages. You can block people; if you report a conversation, the last messages of the reported person (at most 20) are sent to the operator to deal with abuse (Art. 6(1)(f) GDPR) and handled like a contact message.
Status: if you set yourself to “away” or “do not disturb”, logged-in members of your communities see this status next to your name (e.g. in “Who is online?” and in the chat).
Gallery and photographers: approved photographers publish race photos in the gallery; photos, the photographer's name, description, website and profile picture and the number of thumbs are visible to logged-in users. We store who gave a thumb so that everyone can vote only once per photo; only the number is shown. Photos can be linked to a race and the drivers on them; they then also appear on the driver profile and the race result (only for users who may see the league), and the driver receives a Discord message. Photos are deleted after 30 days. Requests to photographers and thumbnail requests (purpose, your Discord account) only go to the photographer concerned; when accepted or declined, both receive the other's Discord contact. The pin board can only be read and written by approved photographers and the operator. Profile, photos and pin board posts are deleted together with your account.
Replays: league admins can upload a race's replay file; it contains the names and game IDs of all drivers of the race. It can only be downloaded by the league's race control and admins, the operator and approved photographers who are members of that community and have signed up for the race. Replays are deleted as soon as the race is official and all photographers who signed up are done, at the latest 14 days after upload (Art. 6(1)(f) GDPR).
Stream graphics: for the league's stream overlays you can add a driver photo and your country. Through the league's broadcast interface (only with its key) the league's stream tools receive each registered driver's name, number, team, car, country, photo, RaceRoom or Steam ID and sponsors – for broadcasting that league's races. Wall of Champions: if you finish a completed season in places 1–3, your name, number, car, the results of that season and your driver photo (without a photo your Discord profile picture) appear on a trophy card – in your own account (My achievements) and, as champion, also on the Wall of Champions for logged-in members of the community and drivers registered in the league. Places 1–3: on the race page and in the championship your uploaded driver photo appears on the card when you finish a race or stand in the standings in places 1–3 – visible to everyone allowed to see the league's pages (login only).
Season review: a season's review (name, results, flag, sponsors, driver rating) is, like the starting list and results, only visible to logged-in users who may see the league; you download the image for sharing yourself.
External content: images from other services are delivered by our own server (see “Images from other services”); fonts and scripts of the stream overlays also come from our server. Links to other services (e.g. YouTube, Twitch, Discord, Ko-fi) are only opened when you click them. The only exception is the stream preview in the “Rennstrecke” look (see “Streams”) – it, too, only loads after your click.
RaceRoom profile: if you enter your RaceRoom profile, our server fetches the public profile data (name, ID, country) from RaceRoom.
Streams: races can link to YouTube or Twitch; YouTube or Twitch are only contacted when you click the link. To show the LIVE notice, our server checks the public stream page or, for Twitch, the official Twitch API itself and also remembers the YouTube video currently running (for preview and ReLive) – no visitor data is involved. In the “Rennstrecke” look (My account → Appearance) the live drawer shows a preview of the stream or of the latest race broadcasts (ReLive). The player only loads when you click “Load preview” (two-click solution): YouTube (via youtube-nocookie.com) or Twitch (player.twitch.tv) then receive your IP address and browser details, and Twitch may set cookies; their privacy policies apply. Closing the drawer removes the player again. Running league broadcasts (league, race and broadcast title) are shown in the LIVE menu to visitors without login too – except for communities that keep to themselves: only their members see their broadcasts; drivers' own streams never.
3. Publication
Taking part in a league means that your real name, registration and results are published on this website and in the league's Discord (starting list, results, standings). On the website they are only visible to people logged in with Discord who are members of the same community (Discord server) or registered in the league – visitors without login and members of other communities see no names or results, only a profile of the league (description, dates, registration). Driver rankings, driver profiles, the news ticker and track records also only show your own communities. Only the pit board (leagues without driver names), special events (information and registration), the gallery and the profiles of commentators, livery designers and photographers who offer their services there and, only if you switch it on (from 16), your name and best time in the cross-community Lights Out leaderboard and, only if you switch it on (from 16), your name, country, Elo, safety rating and number of races in the cross-community driver rating and, if you have accepted a team's invitation, your name, role, Elo and safety rating on the team profile for all logged-in users (under 16 only initials), and your races and results in that simulation for the team members (roster and team admins, see “eSports teams”), and – only if you switch on “Looking for a team / league” – your details, name, Elo and safety rating for team chiefs and admins of teams, community admins of servers with a team and league admins (see “Driver market”) and, in public posts of SimRacingKanal on Instagram and Facebook, your name (can be switched off under My account, then initials only; under 18 always initials only) are cross-community – plus, only if you switch it on yourself, your name and stream title in the LIVE display for logged-in users while you are streaming (see “Your own streams”). The driver rating is only visible to logged-in members (across communities only for drivers who switch that on). Ticket contents are only visible to you, the stewards and the league admins (who stand in for the stewards).
Drivers without registration: anyone who appears in a league's result files but has not signed up on SimLigaManager is hidden in results, standings and Discord posts. Instead, a league can choose per season to show such drivers with initials and car number (e.g. “#23 T. I.”), with points in the standings – never with their full name and never in the driver rating; the league's race control sees the name from the result file. For this, an admin of the league confirms that the league informs the drivers and is responsible for this publication; we store who confirmed it and when. Anyone who does not want to appear like this can contact the league or us (contact).
4. Recipients and hosting
The site runs on a server operated by us in the EU. Discord (login, bot messages) and Steam (Steam login) receive the data needed for these functions. Images from other services are loaded by our server itself (see above). Results files come from the game server of the league. For Assetto Corsa our server fetches them itself from the league's server manager (Emperor), whose address the community enters – only qualifying and race files of the league's races, plus the car and track pictures shown in the league; it only reads there. For RaceRoom leagues of SimRacingKanal our server also sets up the race servers via the Gridline Connector on SimRacingKanal's game server: name, password, track, times, cars and, for race 2, the starting order as RaceRoom user IDs of the drivers.
Discord (Discord Inc.) and Steam (Valve Corporation) are based in the USA. Transfers there are based on the European Commission's adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR), which both companies have joined. For the GIF search in the chat our server only sends the search term and the language to GIPHY (USA), no data about you.
5. Retention
Data is kept as long as you have an account or your results belong to a league's standings. Accounts without a driver profile (RaceRoom/Steam ID or entry), community membership or a profile as sponsor, photographer, livery designer or commentator are deleted automatically after 30 days without a visit. The original result files from the game servers (with names and game IDs of all drivers of a race) are kept so that a race can be recalculated and so that every driver can see their own race analysis (lap times, positions, gaps, track limits, contacts – for themselves and, until the result is official, for the league's race control to review incidents; other drivers appear only with the name shown in the result), and are deleted 90 days after the end of the season, at the latest one year after the season's last race; if you delete your account, your name and IDs are made unrecognisable in these files beforehand (Art. 6(1)(f) GDPR). Encrypted backups are kept for 3 days, the backup made before installing a new version until the next installation; server logs for 7 days. Tasks for the Discord bot (e.g. sending the server password to a race's participants, with their Discord ID) are deleted after 14 days, failed ones after 30 days.
6. Your rights
You have the right to access, rectification, erasure, restriction, data portability and objection, and the right to lodge a complaint with a supervisory authority. Under My account you can download all your data and delete your account yourself. When deleted, your results remain in the standings under an anonymous name so that the leagues' tables stay correct. Incident reports and messages you wrote in a ticket chat also remain for the race control – without any link to your account and under the anonymous name, so that decisions and penalties stay traceable.

