Skip to content

Privacy Policy

Digital Motorsports Club (DMC) & Digital Endurance App

Version 1.4 · Last updated: November 8, 2026

This is version 1.4, replaced on November 14, 2026. View Current Version

1. Who we are

The Digital Motorsports Club ("DMC", "we", "us") runs the Digital Endurance App, the Digital Endurance Championship, and the competition websites of other organisers that use our software (together: the "Platform").

This policy explains which personal data we use, why, how long we keep it, and what your rights are under the European General Data Protection Regulation (GDPR).

Controller: Digital Motorsports Club (DMC), Groningen, The Netherlands. Email: [email protected]

2. What data we collect

  • Name and email: your real first and last name, and your email address.

  • Account IDs: your Discord account ID. For iRacing championships: your iRacing customer ID and the name on your iRacing account. For Le Mans Ultimate championships: your Steam account ID and your Steam profile name.

  • Ratings: your iRacing iRating, Safety Rating and licence class. We get these from official iRacing results, from your iRacing account using your customer ID, and from your Garage 61 account.

  • Race data: your laps, lap times, race times, finishing positions and incident counts. These come from the official results file of each session, which the organiser's Staff upload.

  • Garage 61 data: to compete in the Digital Endurance Championship, and in other championships that require it, you must connect your Garage 61 account. We then read your own laps from the two weeks before each round and from the organiser's races: lap times, the conditions and fuel load of each lap, the car and track, and your telemetry, such as throttle, brake and steering. We also read your iRating and Safety Rating, with their history. For the organiser's race broadcasts, its broadcast program also reads your full lap history in Garage 61 when you are on a line-up: the lap time, car, track, conditions and date of each lap, but not the telemetry of those laps. We only read your own data.

  • Driver profile: a profile picture, a biography, the sims you race, and links to your accounts on other services, if you add them.

  • Broadcast details: your nationality (a country you choose) and how to say your name, if you add them.

  • Team details: a team's biography, year founded, founder's name and home base, entered by the team's owner.

  • Commentary requests: short requests a team's managers write before a round, asking the broadcast commentators not to mention something.

  • Messages: messages between you and an organiser's Staff on the Platform, and when they were sent and read.

  • Payment status: whether your entry fee has been paid, and the payment provider's reference for the payment. We never see your card details.

  • Uploads: files you upload, such as team logos or video evidence.

  • Watchlist records: an organiser can keep a list of people and teams it excluded before. A record holds the name and a short factual description of what happened.

  • Crew applications: if you apply to help run a competition, we store your application, the roles you asked for, the outcome and the explanation you received.

  • Security records: if a file you upload contains malware, we delete the file but keep a record of who uploaded it, when, and what was found.

  • Email records: a record of the emails we send you, including your email address, so we can check that they arrived.

  • Session access records: each time you open the name and password of a race session, we record who opened them, for which event, and when.

  • Name check records: when you register, our system checks whether your name looks like a real name. If it does not, it records why, so the organiser's Staff can look at it.

  • Line-up reservations: a Team Manager can reserve a place in their line-up for a driver who has not joined yet, by entering that driver's iRacing customer ID and, if they want, a name. This data about you comes from the Team Manager, not from you.

  • Browser notifications: if you switch on notifications, we store the technical address and keys your browser gives us to send them to your device.

  • Visitor statistics: only if you agree to analytics. We count which pages are visited, which website you came from, your approximate location (country, region and city), and your type of device, browser and operating system. Our analytics provider, Plausible, uses no cookies, does not store your IP address, and cannot follow you from one day to the next. The statistics are not linked to your account.

You must give us your name, email address and account IDs to take part in competitions. Without them, you cannot compete.

Minimum age. You must be at least 16 to create an account. You confirm this when you accept our Terms, and we record the date. If we find that an account belongs to someone under 16, we close it and erase its data as described in Section 5. Parents can contact us at [email protected].

3. Why we use your data

The law only allows us to use your data with a legal basis. We use three:

  • Contract: we need the data to give you the service you signed up for.
  • Legitimate interest: we have a good reason to use the data, and it does not unfairly harm your interests.
  • Consent: you have agreed, and you can change your mind at any time.

We use your data:

  • To run the Platform (Contract): to create your account, manage your team, match your results to you, give you access to race sessions, and give you the right roles on Discord.

  • To set your name on Discord (Contract): in the organiser's Discord server, your nickname is your full name as on your account, and your roles there match your roles on the website. This also applies when your profile is private. Everyone in that server can see it.

  • To keep competitions fair (Contract and Legitimate interest): to check a season's entry requirements, to place you in a Pro/Am category (Gold, Silver or Bronze), to find cheating and sandbagging, and to let the Stewards make their decisions. Your category is shown publicly with your team's entry and results. Where a championship requires Garage 61, we use your Garage 61 laps to check that you prepared for each round, to set your category from your pace, and to check for sandbagging. Your Team Manager sees whether you are ready for a round. Sandbagging checks are seen only by the organiser's Staff.

  • To show your driver profile (Legitimate interest): your name, profile picture, teams, entries, results and anything you add to your profile are shown publicly on the organiser's website. Profiles are public unless you make yours private in your account. Your name always stays in results, standings and steward decisions, because these are records of real races. Your nationality is shown as a flag beside your name, also when your profile is private. A team's biography, year founded, founder and home base are shown publicly with the team.

  • For the organiser's race broadcasts (Legitimate interest): the organiser's own broadcast program, such as SimCaster AI, receives for each round the display names and Discord IDs of the drivers on its line-ups, the Team Managers, and the organiser's Staff and Race Directors. It also receives the drivers' iRacing customer IDs, categories, iRating, nationality and name pronunciation, the team details and the commentary requests. Where a championship requires Garage 61, it also uses the Garage 61 data of the drivers on its line-ups, including their full lap history, so the commentators can talk about them, for example about their pace on a track, the tracks they know, their preparation for the round and their rating history. It uses all of this for the graphics and commentary. Commentary requests only go to the commentary and are never shown publicly. Your telemetry is never shown or read out on the broadcast. The broadcast program never receives email addresses, payment details, session passwords, or anything about exclusions, appeals or messages.

  • To share news on social media (Legitimate interest): content the organiser publishes on its website, such as results, entry lists, line-ups, standings, track records and photos, is posted automatically on the organiser's Instagram account. Names appear exactly as on the public entry list.

  • To show the organiser's files (Legitimate interest): an organiser can connect folders from its own OneDrive. The website reads the files from OneDrive each time a member opens them, and shows them only to the members the organiser chose. We keep no copy. Personal data in those files is the organiser's responsibility.

  • To answer your messages (Contract and Legitimate interest): your messages are seen only by the organiser's Staff and administrators, never by other participants.

  • To confirm payments (Contract): we record whether your entry fee has been paid, so your entry can be confirmed.

  • To contact you (Legitimate interest): we send important messages, such as steward decisions, race-day information and team invitations, by email, through Discord and, if you switch them on, as browser notifications.

  • To protect race sessions (Contract and Legitimate interest): the session name and password are shown from one hour before the event, only to the drivers on a confirmed entry's line-up and its Team Manager. We record who opens them, so we can find out who shared them if they leak.

  • To help teams plan (Legitimate interest): when a Team Manager reserves a place with your customer ID, we connect it to your account. You then get an invitation, which you can accept or decline. You only join the team if you accept.

  • To check that names are real (Legitimate interest): our Terms require real names. The automatic check never blocks anything. It only asks the organiser's Staff to look, and a person decides. The result is never shown publicly.

  • To handle crew applications (Legitimate interest): so the organiser you applied to can decide on your application.

  • To check registrations (Legitimate interest): if an organiser keeps a watchlist, names entered at registration are compared with it. No one is excluded automatically. A person reviews every match and must confirm that it is the same person or team before anything happens. We have a written assessment of this check, which you can ask for. Organisers never share watchlists with each other.

  • To improve the site (Consent): if you agree to analytics in our cookie notice, we count how the site is used. Analytics is off until you switch it on.

4. Who we share your data with

We never sell your data. We only share it with the services we need to run the Platform:

  • Google Cloud stores our databases and files, in data centres in the European Union.
  • Cloudflare protects the Platform against attacks. All traffic passes through its network.
  • Google Workspace sends our emails. An organiser can choose to send its emails through its own account with Resend instead.
  • Stripe handles payments.
  • Discord handles sign-in, and receives role changes, your full name as your nickname in the organiser's server, and the news, results and steward messages a competition posts there.
  • Steam (Valve): for Le Mans Ultimate championships, you link your Steam account on Steam's website. Steam gives us your Steam ID, and we ask Steam for your profile name.
  • Garage 61 (Rocketeer Comm. V., Belgium): you connect your account there. We, and the organiser's broadcast program, read your data from it, and send it nothing except your sign-in. Its data stays in the European Union.
  • Meta (Instagram) receives the posts an organiser publishes on its Instagram account.
  • Microsoft (OneDrive): we read an organiser's files from its own OneDrive, and send it nothing about you.
  • Your browser's notification service (for example Google, Mozilla, Apple or Microsoft) delivers browser notifications. The messages are encrypted, so this service cannot read them.
  • Plausible Analytics (Plausible Insights OÜ, Estonia) counts site visits, only for visitors who agreed to analytics. Its data stays in the European Union.

Organisers. An organiser's Staff can see the data they need to run their competitions. An organiser's administrators can download a copy of the organisation's records. This copy never contains passwords, sign-in details, payment details or other organisations' data. The download link works once and expires after seven days.

Replies to organisers. Some emails are sent on behalf of an organiser. If you reply, your reply goes directly to the organiser's own email address and is not stored on the Platform.

Malware scanning happens inside our own cloud systems. Your files are not sent to any other company for scanning.

Outside the European Union. Discord, Stripe, Cloudflare, Google, Valve, Resend, Meta, Microsoft and the browser notification services may process data in the United States or other countries outside the European Union. This is protected by the EU–US Data Privacy Framework, where the company is certified under it, or by the European Commission's standard contractual clauses. You can ask us for a copy of these safeguards.

5. How long we keep your data

We keep your account data for as long as you have an account. For other data:

  • Messages: deleted two years after the last message in a conversation.
  • Crew applications: deleted twelve months after the decision.
  • Email records: deleted after twelve months.
  • Session access records: deleted after twelve months.
  • Name check records: kept until your account is deleted or the organiser leaves the Platform.
  • Line-up reservations: kept until the Team Manager removes them or the team is deleted.
  • Browser notifications: deleted when you switch notifications off, or when your browser tells us they no longer work.
  • Visitor statistics: the daily code Plausible uses is deleted after 24 hours. The statistics that remain contain no personal data.
  • Watchlist records: no fixed end date. The organiser must review every record at least once a year and either confirm it is still needed or switch it off. Records that are switched off are no longer used.
  • Commentary requests: deleted 7 days after their round.
  • Nationality and name pronunciation: until you change or remove them.
  • Team details: until the team's owner changes them.
  • Garage 61 data: kept until the end of the season and the appeal deadline after it, then deleted. Categories and decisions based on it stay.
  • Garage 61 lap history read for a broadcast: deleted 7 days after the round. It is read again for the next round.

Deleting your account. You can ask us to delete your account. The deletion happens after 30 days. Until then, you cannot take part in competitions, and you can cancel the request. After 30 days, the deletion cannot be undone.

When your account is deleted, we delete or overwrite your name, email address, account IDs, ratings, driver profile, nationality, name pronunciation, your Garage 61 connection and Garage 61 data, messages, security records, email records, line-up reservations, browser notifications and our copies of your payment details. Your name is replaced with "Former Driver". The founder, home base and biography of teams you own are deleted, and where your name was typed as another team's founder, it is replaced. We also remove your name from written texts where we can, without damaging records about other people. If you find your name somewhere it should not be, tell us and we will remove it if possible.

Some records are kept after your account is deleted:

  • Sporting records: race results, penalties and track records stay, without your name, so past competitions stay complete (Legitimate interest).
  • Entries: your entries stay in the sporting record without your name, and may still show the entry fee and whether it was paid. The payment records themselves are kept by the organiser in its own payment account, not by us.
  • Exclusion records: if an organiser excluded you, it may keep your Discord ID and any game account ID we hold, with the date and the reason, so it can recognise a new registration from you. No name is kept. Only that organiser has this record, and it is kept for as long as the exclusion lasts (Legitimate interest). You can ask for it to be corrected or removed if it is wrong.

When an organiser leaves the Platform. An organiser can ask for its organisation to be deleted. This happens after 30 days, and its administrators can cancel it until then. Everyone involved gets an email when the deletion is requested, and again if it is cancelled. Your own account stays, and you can download your data before the deletion date. When the deletion happens, the organiser's website stops and the personal data it held is deleted. Its results, standings and stewarding decisions stay as a sporting record, without any link to a person.

6. Security

All data is encrypted when it is sent (TLS) and when it is stored (AES-256). Only the Staff and Stewards who need access to the admin tools have it. Uploaded files are checked for malware. If a file fails the check, we delete it and tell you, and you can upload a new one.

7. Cookies

We only use cookies that the Platform needs to work. We use no cookies for analytics, advertising or tracking. Because these cookies are needed, the law (Article 5(3) of the ePrivacy Directive) does not require us to ask for your consent.

Our cookies:

  • keep you signed in;
  • protect the sign-in form against attacks;
  • remember where to take you after you sign in;
  • protect the linking of a Steam account, for Le Mans Ultimate championships;
  • remember your time zone, so race times are shown in your local time;
  • remember your light or dark theme, if you choose one;
  • remember your answer to our cookie notice, including whether you agreed to analytics.

Some of these cookies are deleted when you close your browser. Others last between ten minutes and one year. The full list is on our Cookies page at digitalendurance.app/cookies.

Our analytics uses no cookies, but it runs in your browser, so it only starts if you agree to it. You can change your choice at any time on our Cookies page.

You can block cookies in your browser, but then you cannot sign in.

8. Your rights

You have the right to:

  • see your data: get a copy of the data we have about you, including any watchlist or crew application records about you (without the name of the Staff member who wrote them);
  • correct your data: we check name changes before they are applied, because real names are required;
  • delete your data: with the exceptions in Section 5;
  • limit how we use your data: we then stop the automatic name check and other use based on legitimate interest, except where the law allows us to continue, such as contract use, legal duties, registration checks and exclusion records. We tell you exactly what the limit covers before it starts;
  • take your data with you: in a format other computers can read;
  • object: to any use based on legitimate interest;
  • withdraw consent: for analytics, at any time, on our Cookies page.

Your data download. When you ask for a copy of your data, you get a file you can download once within seven days. After that, it is deleted.

To use these rights, go to the Privacy section of your account, or email [email protected]. The Platform handles requests to see, take or delete your data. A person handles all other requests, and we answer within one month.

9. Complaints

If you think we use your data against the law, you can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

10. Changes to this policy

We may update this policy. Each version has a version number. We tell you about important changes through the Platform, Discord or email before they start.