Privacy Policy
Last updated: June 16, 2026
We take the protection of personal data seriously. This Privacy Policy explains which personal data we process in connection with this website, the driver portal and the operation of SimRacing Republic championships.
1. Controller
The controller responsible for processing personal data is:
Maximilian Fritz Dienstleistung und Handel
Geibelstrasse 17b
45472 Muelheim an der Ruhr
Germany
Email: info@simracingrepublic.com
2. Hosting and Technical Delivery
This website is delivered through our hosting provider. When you access the website, technically necessary access data is processed, including your IP address, date and time of access, requested page, browser and device information, and server log data. This processing is necessary to deliver the website, detect errors and protect our systems. The legal basis is Article 6(1)(f) GDPR.
3. Portal, Registration and Discord Login
For registrations, team management and admin functions, we use Discord login. Depending on the OAuth profile provided by Discord, we may process your Discord user ID, Discord handle, display name, avatar URL and email address. The email address is collected where it is required for secure account assignment, authentication or account management through the login provider.
For team and series registrations, we also process team name, team manager name, team manager iRacing ID, team manager Discord handle, requested car number, iRacing team ID, selected vehicle and class, and driver data such as name, iRacing ID, nationality, driver rank, entry assignment and status information.
Additional operational data may be created in the portal, such as attendance declarations, driver nominations, change requests, admin notes, penalty or review data and timestamps. We process this data to organise championships, manage participants, enforce sporting rules and operate the portal securely. The legal bases are Article 6(1)(b) GDPR where processing is necessary for participation and organisation, and Article 6(1)(f) GDPR for our legitimate interests in secure operation, traceability and sporting administration.
4. Supabase as Backend Service Provider
We use Supabase for authentication, database storage and API services. The portal, registration and operational data described above is processed in our Supabase project. Supabase processes data as a technical service provider or processor where this is required for authentication, storage and delivery of the portal.
5. Public Entry and Driver Data
Certain data may be displayed publicly where this is required for championship operation, entry lists, driver lists, standings or sporting transparency. This may include team name, vehicle, class, car number, iRacing team ID, driver name, nationality, iRacing ID, driver rank and penalty points. Unconfirmed entries and internal administrative data are not intentionally displayed publicly.
6. External Links and Embedded Content
Our website contains links to external services such as Discord, Instagram, YouTube, Google Docs, iStewards and partner websites. If you follow these links, you leave our website; the respective provider is responsible for any processing that takes place there.
Some pages may embed YouTube videos through the youtube-nocookie.com domain. Even with this more privacy-friendly embed option, connection data may be transmitted to Google/YouTube when the video is loaded. If no consent solution is placed before such embeds, videos should only be loaded where they are necessary for displaying the page or where appropriate consent has been obtained.
7. Cookies, Local Storage and Sessions
For login and portal functionality, technically necessary session data, tokens or similar information may be stored in your browser, in particular through Supabase Auth. This storage is required so that signed-in users can remain authenticated and use protected portal functions.
Based on the current technical implementation of this website, we do not use Google Analytics. If analytics or marketing cookies are introduced in the future, they will only be used after appropriate information has been provided and, where required, after prior consent.
8. Recipients and Service Providers
Personal data may be transmitted to technical service providers and platforms where this is necessary for operation and organisation. This includes, in particular, hosting providers, Supabase for authentication and database services, Discord for OAuth login and community communication, and external platforms that you actively access through links or embedded content.
9. Retention Periods
We store personal data only for as long as it is required for registration, championship operation, traceability of sporting decisions, portal security or legal obligations. Data relating to entries, drivers, results and penalties may be retained beyond a single event where it is required for historical tables, sporting documentation, appeals or series administration. Internal administrative data that is no longer required will be deleted or restricted.
10. Data Security
We take technical and organisational measures to protect personal data. These include encrypted transmission via HTTPS, role-based access control in the portal and row-level security rules in the database. Access to admin functions is limited to authorised persons.
11. Minors
Our services are not directed specifically at children under the age of 16. If we become aware that data from children has been processed without the required consent, we will review deletion or restriction of that processing.
12. Your Rights
Subject to the requirements of the GDPR, you have the right of access, rectification, erasure, restriction of processing, data portability and objection to certain processing activities. Where processing is based on consent, you may withdraw that consent at any time with effect for the future.
To exercise your rights, you can contact us at info@simracingrepublic.com. You also have the right to lodge a complaint with a competent data protection supervisory authority.
13. Changes
We may update this Privacy Policy if technical, organisational or legal circumstances change. The current version will be published on this page.