Privacy

We are a hobbyist sim racing community, not a business with a data department. We collect the least we can get away with, we do not sell any of it, and there is no advertising anywhere on this site. This page explains the details anyway, because you are entitled to them and because writing it down keeps us honest.

Last updated 9 September 2026. The data controller is Sausage Dodgers Racing. For anything on this page, email sausagedodgeradmin@gmail.com.

You can use most of the site without telling us anything

Championships, standings, the schedule, rules, protests, liveries and the team pages are all readable without signing in. We do not know who you are and we are not trying to find out.

What we collect when you sign in

Signing in happens through Discord. We ask Discord for two permissions and no more: identify, which tells us who you are, and guilds.join, which lets us add you to the SDR server. We never see your email address, your password, your DMs, or anything you do in other servers.

From that, we store:

• Your Discord user ID, username and avatar image link.
• The racing disciplines you pick, so we can give you the right roles.
• Flags read from your roles in our Discord server: whether you are staff, a race steward, a full team member, and which Patreon tier you are on. That last one comes from your Discord role, not from Patreon. We have no connection to your Patreon account or your payment details.

Applications

Applying to join happens in a private ticket channel on Discord, not on this website. Whatever you put in that channel, including your name, age, location and occupation, lives in Discord and is covered by Discord's own privacy policy as well as this one. Management can read it. It is not published anywhere and it never touches this site's database.

What gets published

Championship standings and entry lists show driver names as they appear on SimGrid. If you race with us, expect your racing name and your results to be visible on the site. Personal details attached to SimGrid accounts, such as email addresses and linked platform IDs, are stripped out before anything reaches these pages.

Protests and licence points

If you file a protest through the site, we keep what you wrote, the race and driver it concerns, any evidence link you gave, and the conversation that follows. Stewards can see it. The driver you are protesting is not told unless a steward decides to bring them into the discussion.

Where a protest was raised or adopted from a Discord ticket, messages are mirrored between the two so the conversation reads the same in either place. When a protest is closed, a transcript may be posted to a private staff channel on our Discord.

If stewards rule that you committed an infringement, we record the licence points, the reason, who decided it and when. That record is how penalties are applied consistently and how repeat incidents are recognised, so it is kept as a disciplinary history rather than deleted when a protest is closed.

We will send you a Discord message when there is an update on a protest you are part of. That is a notification, not a newsletter, and it only ever relates to a protest you are already involved in.

Coaching and feedback

If you book an hour at the Academy, we keep who is coaching, who is being coached, when, and the note you left about what you wanted to work on. Your coach is sent that note, along with your Patreon tier if you have one, so they know who they are meeting and what to prepare. Nobody else sees it.

Our feedback form is closed at the moment while we rework it. What follows describes answers already sent through it.

We keep your answer, the multiple choice picks alongside it, and which round of asking it belongs to. It also goes to a private staff channel on our Discord, which the form said before you sent it. It is not posted publicly.

An answer sent normally is kept against your profile, with your name on it, so we can come back to you about what you said. If you ticked the box asking us not to keep your name, we stored no author against it at all, and the staff channel shows it as anonymous. Being straight about the limit of that: the answer still carries the time it arrived, and our server keeps an ordinary request log, so it is not the same as untraceable. It means we are not holding a record of who wrote it.

Records we keep behind the scenes

• When staff do something privileged, such as posting an announcement or deleting a member's data, we log who did it, what they did, when, whether it worked, and the IP address the request came from. This exists so that staff actions can be audited, and it is visible only to admins.
• We record when you sign in, as a list of times rather than only the most recent one. It is how we can tell whether the community is getting more or less active, and it means a sign-in nobody recognises can be spotted. Visible only to admins, and it goes when your profile does.
• Our host, Cloudflare, keeps standard server logs including IP addresses for around 24 hours. That is ordinary web infrastructure and applies to any site you visit.

Cookies

No advertising cookies, no tracking pixels, no third-party analytics. Every cookie we set is doing a job:

• Session cookies keep you signed in. Without them you would be signed out on every click.
• A "you have signed in here before" marker, which holds the value 1 and nothing else. It decides whether the button in the header says Join or Sign in.
• A short-lived cookie that remembers which disciplines you picked before signing in, so your choices survive the trip to Discord and back. It expires after ten minutes and it is cryptographically signed so it cannot be tampered with.
• A "where you were heading" cookie, set only when a page asks you to sign in first, so you land where you meant to rather than on the paddock. It expires after fifteen minutes.
• Two markers on your own device that remember when you last opened your paddock and where you were standing in each championship at the time. They are what lets the page say what changed while you were away. They never leave your browser, they are never read by anyone else, and the worst an edited value can do is show you the wrong figure about your own racing.

All of them are strictly necessary for the site to work, which is why you are not being nagged by a consent banner.

Why we are allowed to do this

Our lawful basis is legitimate interests: running a members' community, giving members the right roles and access, keeping the racing fair, and keeping the site secure. You can object to any of it at any time, and the practical consequence is that we delete your profile and you carry on using the site signed out.

Who else touches your data

We use a small number of services to run the site. Each one only gets what it needs to do its job:

• Discord for sign-in, roles, and community content.
• Supabase for the database and sign-in sessions.
• Cloudflare for hosting and protection against attacks.
• SimGrid for championship, entry and results data.
• YouTube for embedded broadcasts. We use the no-cookie embed, so YouTube does not set tracking cookies unless you press play.
• Bunny Fonts for typefaces, chosen specifically because it does not log visitors or set cookies.

None of them are given your data to use for their own purposes, and nobody buys anything from us, because we do not sell it.

Where your data lives

Our database is hosted in Ireland. Cloudflare serves the site from data centres around the world, and Discord is a US company, so some of what we hold about you is processed outside the UK. Both operate under the safeguards required for international transfers.

How long we keep it

Your profile stays for as long as you have an account with us. Ask us to delete it and we anonymise the record: username, avatar, Discord ID and discipline picks are cleared. Staff action logs are kept for accountability. Cloudflare's server logs age out on their own after about a day.

Protests and licence points are kept after that, because they are a record of decisions affecting other people as well as you: a ruling that awarded points to one driver is also the reason another driver's protest was upheld. Where we can, we detach them from your profile so the decision survives without pointing back at your account. If you want a protest record dealt with differently, ask us and we will look at it case by case.

Coaching bookings and feedback answers stay attached to your profile record, which after an anonymisation no longer carries your username, avatar or Discord ID, so what is left is the answer rather than the person. Feedback is kept while a round of asking is open and for as long afterwards as it is useful to compare against the next one, which in practice means a season or two. If you would rather something you sent was removed outright, ask us and we will do it.

Deleting your site profile does not remove you from our Discord server or delete anything you posted there. That is Discord's, and you control it from your side.

Your rights

UK data protection law gives you the following. Email sausagedodgeradmin@gmail.com to use any of them. They are free, and we will come back to you within a month.

Children

This site is not aimed at under-13s, which is also Discord's minimum age. If you believe a child has given us data, tell us and we will remove it.

Changes

If we change what we collect or why, we will update this page and move the date at the top. Anything significant gets announced in Discord rather than quietly slipped in.