1. Controller
Alexander Jaeger
Wolfenbütteler Str. 17
30519 Hannover, Germany
E-mail: contact@leonidaracing.com
2. Overview
This website processes personal data in these areas: sign-in and account management (Discord sign-in), your public profile, lap-time submissions and their verification (screenshots as private originals, published best times as the result), your garage, Community (crews, events, sign-ups), reports and moderation, our Discord bot and Discord server (roles, event feeds, Looking for Players), and the technical delivery of the site (hosting, server logs).
3. Sign-in with Discord (OAuth)
We use Discord as an external sign-in service (OAuth 2.0). We request the Discord permissions identify, email and guilds.join; Discord shows them to you before you sign in. Discord sends us your Discord user ID, username, avatar and the e-mail address linked to your Discord account. The e-mail address is stored in your account with our sign-in and database provider and is never shown publicly. With guilds.join, you are added to our Discord server once, right after you sign in; you can leave the server at any time. We never see or store your Discord password.
Legal basis: Art. 6(1)(b) GDPR (providing the service you signed up for). Discord is responsible for processing on its own platform. For users in the EEA, Discord identifies Discord Netherlands BV as the controller; for other users, it identifies Discord Inc. See Discord's Privacy Policy at discord.com/privacy.
4. Your profile
Your display name is shown publicly on leaderboards, in crew rosters and in event sign-up lists. You can change it at any time in My Account › Settings. We keep a history of previous display names so moderators can trace abuse (e.g. someone switching names after a violation); only you and the moderators can see it. It is deleted when you delete your account.
Legal basis: Art. 6(1)(b) GDPR; for the name history Art. 6(1)(f) GDPR (our legitimate interest in a fair community free of abuse).
5. Lap submissions, screenshots and verification
When you submit a lap time, we process the time, the vehicle and other submission details; the screenshot you upload as proof (private, never public); the review and verification status and any moderator notes. If you add a video link, it can be shown publicly next to your time on the leaderboard.
Purpose: proving and checking that a lap time is genuine, preventing cheating and abuse. Legal basis: Art. 6(1)(b) GDPR (providing the service) and Art. 6(1)(f) GDPR (our legitimate interest in a fair leaderboard that can't be manipulated).
Corrections. If a moderator asks you to correct a submission, we store the request and show its reason to you in My laps. When you send a correction, we record the correction time and previous car and lap time so moderators can review the changes. This information is used for submission review and abuse prevention under the legal bases above; it is not published on the leaderboard.
Retention: screenshots are reduced in size when uploaded and deleted 60 days after submission. The exception is the screenshot of the current best time of a vehicle on a track: it stays while that time is the best time and is deleted 60 days after it has been beaten. Proof for submissions still under review or that have been reported is kept until the review or report is closed. When you delete your account, all your screenshots are deleted immediately; the lap time itself stays. Only authorised moderators can see the private originals, and only to review them.
Highlight and analysis videos (optional): If you tick “Feature my video in Leonida Racing highlight and analysis videos” when you submit a lap, or turn it on later in My laps, we may use clips from your lap video in our highlight and analysis videos, credited with your name and a link to the original. We never use your voice, face cam, music, radio or other players’ names. These videos appear only on our website and on our own channels on YouTube, Facebook, Instagram (Facebook and Instagram are run by Meta), X and Reddit, including monetized videos – never on anyone else’s channel. Your consent lasts until you turn it off or the lap is deleted; deleting your account turns it off too. To show what was allowed when a video was made, we store whether you agreed and when you turned it on or off, for as long as the lap exists.
Legal basis for using your video and crediting you: Art. 6(1)(a) GDPR (your consent). You can withdraw consent at any time in My laps. Withdrawal stops use in new videos and does not affect processing that was lawful before withdrawal. It does not automatically remove published videos. Your data protection rights, including deletion rights, still apply. Contact us about an existing publication; you can also ask us to remove your name from its description.
We retain the consent record while the lap exists to document permission and handle disputes, relying on Art. 6(1)(f) GDPR (our legitimate interest in keeping evidence of permissions).
6. Your garage
You can keep a list of cars you own in GTA VI and a wishlist of cars you want. These lists are not shown to other users. Car pages show the number of drivers who have marked a car as owned, without listing their names. Marking a car as owned removes it from your wishlist. You can remove entries at any time. Both lists are deleted from the application database when you delete your account. Legal basis: Art. 6(1)(b) GDPR (providing the garage and wishlist features you request).
Car ratings. If you rate a car on the website or through our Discord bot, we store your account’s rating for that car. Each account has one rating per car; a new choice replaces the previous one. We publish the rating count and an average once a car has at least three ratings, without displaying who gave each rating. Ratings are deleted from the live application database when you delete your account. Legal basis: Art. 6(1)(b) GDPR (providing the rating feature you request).
7. Community: crews and events
Crews: When you join an open crew or request an invite, we store your crew membership or request and its status. The crew leader, commissioners of that crew and moderators can manage memberships, requests and invitations. Your display name is shown publicly in the crew roster once you are a member. We also store crew roles, including commissioner, to manage access to crew tools; your role may be shown with your membership. If you apply for a Crew Leader role, moderators see your application, including your message and links. If you request ICON status or crew verification, moderators see your request, the link you provide and your verification code.
Events: If you host an event, we process its details, the host PSN name and Discord link you provide, and the selected host crew. Public events are shown in the community calendar. On the website, crew-only events and their sign-up lists are available to active members of the host crew, the host and moderators. If you sign up, your display name can appear in the event’s sign-up list. Joining or leaving a crew can affect your access and sign-up eligibility for its crew-only events.
When you submit an event, we store its details and review status. Moderators can review the submission and record a decision or request changes. You can see feedback intended for you in My Account. The same process applies to changes that require approval.
If you join a championship, you are signed up for all of its rounds. If the host bans you from it, we keep that so you can’t sign up for the same championship again.
Public events may also appear in Discord servers following the public calendar, a crew or your host profile. Crew-only events are sent only to matching crew event feeds, where visibility depends on the destination server’s channel and event permissions. A Discord post can therefore be visible to people who are not members of the crew on our website (see section 9).
Legal basis for membership, crew-role and event participation features: Art. 6(1)(b) GDPR. Memberships, roles and sign-ups are removed when you leave or are removed from the crew, the relevant role ends, you cancel or are removed from an event, or you delete your account, as applicable. Event details remain until the event or your account is deleted. Records used to enforce crew or event restrictions are handled separately as described in section 8.
8. Reports and moderation
If you report a lap time or other content, we store your report (what you reported, the reason, your explanation) together with your account. Only moderators see who sent a report; the person or crew you reported is not told by us. You see the status and outcome of your own reports. We keep reports as long as we need them to document moderation decisions; reports you sent are deleted when you delete your account.
If you report by e-mail, we process your name, e-mail address and message to handle the report and tell you the outcome.
Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 16 of the EU Digital Services Act where it applies, and Art. 6(1)(f) GDPR (our legitimate interest in a safe, lawful community).
Crew and event restrictions: To enforce crew and event access decisions, we store the affected account, the crew, event or host concerned, and the date of the restriction. Crew bans and event removals also record which account applied the restriction. A crew ban prevents joining, requesting an invite or being invited to that crew. An event removal prevents signing up again for that event; a host ban applies to that host’s events, including future events. These records are not public. Crew ban lists are available to the relevant crew leader, commissioners and moderators. Event removal and host ban lists are available to the relevant host and moderators. We do not send an automatic message when a restriction is applied; an attempted sign-up or crew join may show that access is restricted.
For these restrictions, we rely on Art. 6(1)(f) GDPR. Our legitimate interest is enforcing access decisions and protecting the community from repeated unwanted participation. You may object to this processing using the contact details above. The rights described in section 14 also apply to these records.
Retention: Event removals are deleted automatically seven days after the event has ended. Crew bans and host bans have no fixed expiry; they remain until the crew leader, a commissioner or the host lifts them, or the crew is deleted. Deleting a single event does not remove a host ban. If you delete your account, restrictions applied to your account and host bans you applied are deleted; restrictions you applied as a crew leader or commissioner remain without a link to your account.
We store your hosting level, any restriction on submitting events, and the applicable event limits to manage event publication. These settings are available to you and moderators. Rejected event submissions are scheduled for deletion 30 days after the review decision; expired submissions are scheduled for deletion 30 days after their start time.
9. Leonida Racing on Discord
Our Discord bot answers commands, posts event and vehicle updates and selected video updates, manages community roles on our official server, and runs Looking for Players (LFG) searches. When you use a command, button or role menu, Discord sends us the information needed to respond, including your Discord user ID, server and channel details, relevant permissions and the options or text you submit. We do not keep a separate query history for information commands in our application database. Technical logs may be generated.
Roles. On our official server, we use your Discord user ID and website account and role status to assign or remove Registered Driver and the matching Verified roles. We store role-sync status and processing records with Supabase. Self-selected community roles are handled through the bot’s role menus. Changing a Discord role does not change your website role. These roles do not verify your real-world identity.
Feeds and event sign-ups. Server administrators can subscribe channels to the public calendar, a crew, a host, vehicle announcements, new videos or Gellhorn lap records. We store the server and channel IDs, selected source, filters, creator link where applicable, and references needed to maintain posts and server events. Published event cards can include the host’s name and contact link, description, crew and sign-up count. Those cards do not list the event’s participants. Crew-only events are sent only to matching crew event feeds, where visibility depends on the destination server’s channel and event permissions. Using an event sign-up button records or removes your sign-up through your linked website account; your display name can appear in the event’s sign-up list on the website.
Gellhorn lap records. When a lap with a checked video beats an existing record, the bot posts it in subscribed channels with your leaderboard display name, car, platform, lap time and video link. If you change your display name or delete your account, the bot updates existing posts. If the time is later found invalid, its entry is removed from the bot’s posts.
Video and stream feeds. We retrieve public channel details and published video or stream information from selected YouTube and connected Twitch channels. This includes channel identifiers and names, video or stream identifiers, titles, links and publication or start times; Twitch responses can also include the stream category. We use this information to select posts and avoid duplicates, and share matching links in Discord channels that subscribe to the feed. Source-channel settings remain while the channel is listed; item records are removed by a daily cleanup once they are more than 90 days old. Removing an item record does not remove a post already made on Discord. Discord handles link previews through the linked platform; our website does not embed those videos for this feed. We rely on Art. 6(1)(f) GDPR for this distribution of public creator content. Our legitimate interest is keeping subscribing communities informed about selected videos and streams. Affected creators may contact us to exercise the rights in section 14.
Car ratings. When you rate a car through the bot, we use your Discord user ID to find your linked website account and save the rating there. The bot sends the confirmation only to you and updates the public card’s rating summary. Discord processes the interaction on its platform; the rating is not anonymous to us.
Leaderboard. Leaderboard commands can display public racing results, including display names, crew tags, cars and lap times, in the Discord channel where the command is used. If your Discord account is linked to a website account, the response may also identify your place in the selected leaderboard. The response is public in that channel, not a direct message.
LFG. When you create or join a search, we store the host’s and participants’ Discord IDs, the activity and requested group size, creation and expiry times, and the IDs of the search’s server, card and temporary voice channel. The search card shows the host and participants through Discord mentions and may also show the host’s PSN name. The bot checks whether joined participants are still in the temporary voice channel so it can move them when the search ends. Searches normally expire after three hours and can end earlier when closed or left empty.
Pings. The /ping command checks your role and channel permissions and stores your Discord user ID and most recent ping time to enforce a 15-minute cooldown. The message you submit is posted publicly in the selected channel with the chosen notification role.
Retention and deletion. Feed settings and references remain while needed to operate the feed. Removing a feed deletes its configuration, but channel messages may remain on Discord. The bot checks feeds daily and removes affected settings when Discord reports a deleted channel or that the bot has left the server. A daily cleanup removes processed delivery and role-sync jobs seven days after processing, ping-cooldown records one day after the most recent ping, and role-sync records of Discord accounts that no longer belong to an active website account. Jobs that have not been processed yet stay until they are processed.
When you delete your website account, we remove your stored creator link from feed settings and your ping-cooldown record, and the bot removes the roles it gave you. Personal host feeds are scheduled for removal after a one-day waiting period, normally during the next daily cleanup. The bot attempts to remove event posts that are no longer published. Once an LFG search has ended, the bot removes the temporary voice channel and replaces the card with an ended notice without participant mentions, and only then deletes the search record. Discord API errors or missing permissions can delay or prevent those changes. Contact us if a post containing your details remains visible. Provider logs and backups are separate from deletion of live application records and are described in section 11.
Legal basis. We rely on Art. 6(1)(b) GDPR where necessary to provide account features and event sign-ups you request. We rely on Art. 6(1)(f) GDPR for bot responses, role administration, feeds, public event distribution, LFG coordination and anti-spam checks. Our legitimate interests are providing the requested community functions, making published events available to subscribing servers and operating the bot safely. You can object to processing based on legitimate interests using the contact details above. Discord processes data on its platform under its own responsibility, as explained in section 3.
10. Hosting and technical delivery
The website is hosted on GitHub Pages (provider: GitHub, Inc., 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA). GitHub processes technical request data for hosting, such as server logs with the time of access and the file requested. Cloudflare (see below) also processes the original visitor IP address and may forward it to GitHub. GitHub, Inc. is certified under the EU-U.S. Data Privacy Framework; the transfer to the USA is therefore based on the European Commission's adequacy decision (Art. 45 GDPR).
Our domains are registered with Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA). Requests to leonidaracing.com pass through Cloudflare’s network for secure and reliable delivery of the website hosted on GitHub Pages. Cloudflare also redirects requests from www.leonidaracing.com and gellhornracing.com to the current address. In providing these services, Cloudflare processes technical request data, such as your IP address, access time, requested address, and browser information and referring page where supplied.
We rely on Art. 6(1)(f) GDPR for secure delivery, protection against misuse and these redirects. Cloudflare’s Data Processing Addendum forms part of its Self-Serve agreement and governs processing on our behalf under Art. 28 GDPR. Cloudflare also describes processing for its own network-security purposes in its privacy policy. For relevant transfers to the United States, Cloudflare states that it relies on its EU-U.S. Data Privacy Framework certification. Its privacy policy describes retention according to the purpose of processing and applicable legal requirements; there is no single retention period covering every Cloudflare service.
Optional Cloudflare Web Analytics is separate and is loaded only if you allow visitor statistics (section 12). Public content loaded directly from Supabase is described in section 11.
E-mails to contact@leonidaracing.com are received by Cloudflare Email Routing and forwarded to our mailbox. Cloudflare processes the sender address, the message and the technical delivery data for this purpose. Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in being reachable by e-mail).
Legal basis: Art. 6(1)(f) GDPR (our legitimate interest in delivering the website securely and reliably).
11. Database, sign-in and public content (Supabase)
We use Supabase to store and manage account and profile data, submissions, private proof, community content, reports, and the Discord bot’s operational data. Our project database is hosted in an EU region. Processing for the account and community features follows the purposes and legal bases described in the relevant sections of this policy.
Pages with live public content, such as leaderboards, crews and events, load that content directly from Supabase in your browser. This also happens if you do not have an account. Supabase receives technical request data, including your IP address, the requested resource and the time of access. We rely on Art. 6(1)(f) GDPR for this delivery of current public content. Our legitimate interest is operating an up-to-date community website; this is separate from the optional visitor statistics in section 12.
Supabase’s published Data Processing Addendum identifies Supabase Pte. Ltd., Singapore, as the processor and forms part of its service agreement. It provides the processor safeguards required by Art. 28 GDPR and includes EU Standard Contractual Clauses for transfers where required under Art. 46 GDPR. An EU database location does not exclude processing outside the EEA, including in Singapore and the United States. You can request information about the applicable safeguards using the contact details above.
Supabase also processes technical logs. Its current Free-plan documentation lists one day of API and database log retention; this is not a guarantee that every security log, backup or internal provider copy is erased after one day. Retention of the data we store for website features is described in the relevant sections above. Supabase’s DPA, privacy policy and logging documentation provide further information about provider processing.
12. Browser storage, cookies and visitor statistics
When you sign in, your login session is stored in your browser's local storage so you stay signed in. This is technically necessary for the functions you use and needs no consent under Section 25(2) TDDDG. You can remove it at any time by signing out or clearing your browser data.
Display units. If you have not chosen speed and distance units, your browser reads your device’s time zone to select an initial setting. This happens on your device; the time zone is not sent to us for this purpose. If you change the units, your choice is stored in this browser under “lr-units” until you change it or clear your browser data. It is not saved to your account.
We also store your comparison selection and which site notices you have dismissed in this browser, so those choices are kept when you return. You can change the comparison selection on the site and remove these stored choices by clearing your browser data.
Visitor statistics (only with your consent). If you click “Allow” in the notice at the bottom of the page, we use Cloudflare Web Analytics (Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA) to count visits. A script from Cloudflare then records, per page view, the page address, the referring page, the time, browser and device type, country (derived from the IP address) and loading times. Cloudflare Web Analytics sets no cookies, does not store anything in your browser for this purpose and does not create profiles across websites; the IP address is not used to identify you. We only see aggregated figures. Cloudflare is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR). The no-cookie statement applies to Cloudflare Web Analytics; technical browser storage for sign-in and your privacy choice is described above.
Legal basis: your consent, Art. 6(1)(a) GDPR and Section 25(1) TDDDG. Without consent, the script is not loaded. Your choice is stored in your browser's local storage (technically necessary, Section 25(2) TDDDG). You can change your choice or withdraw consent at any time through “Privacy Settings” in the footer. Withdrawing consent stops further collection for visitor statistics; it does not affect processing that was lawful before withdrawal.
We use no other analytics, advertising or tracking services.
13. Minimum age
Accounts are for people aged 16 and over (see the Terms of Use). If we learn that an account belongs to someone younger, we delete it.
14. Your rights
You have the right to access the data we store about you (Art. 15 GDPR), to have incorrect data corrected (Art. 16 GDPR), to have your data deleted (Art. 17 GDPR), to restrict processing (Art. 18 GDPR), to data portability (Art. 20 GDPR), to object to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR), and to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). Please send requests to the contact e-mail above.
Deleting your account: You can delete your account yourself at any time under My Account › Settings › Delete my account. This deletes your display name, your Discord link and login, your garage, car ratings, crew membership and roles, events you created, event sign-ups, crew and event restrictions applied to your account and host bans you applied, reports you sent, your screenshots and video links; submissions not yet reviewed are deleted too. Reviewed lap times remain on the leaderboard as "Deleted driver", without your display name, Discord ID or sign-in link in the retained driver record. Discord posts, bot records and provider copies are handled as described in sections 9 and 11. Deletion is permanent: signing in with Discord again creates a new, empty account.
If you only remove our website from the authorized apps in your Discord settings, your account with us is not deleted; your data stays as it is until you sign in again and delete your account, or send us a deletion request.
15. Changes to this policy
We update this privacy policy when the way we process data changes. The version published at the time of your visit applies. This version: 10 November 2026.