Your privacy.
Stewards Room keeps incident evidence together so people can review it fairly. This notice explains what happens to your information, including when another driver submits a case involving you.
Updated 11 October 2026
Waiting list
If you join the waiting list, we store your email address, the date you joined and your request for an availability email. We use this only to contact you about a space becoming available. Joining creates no account and grants no app access. The site owner can see this list. We keep your entry until the waiting list closes or you ask us to remove it; email stewardsroompro@gmail.com to withdraw your request.
Who is responsible
Stewards Room is operated by Jan Hui, an individual based in the United Kingdom. Contact stewardsroompro@gmail.com for privacy questions, requests or complaints.
Jan Hui is responsible for information used to operate the website, accounts, support and security. Your league also decides why incidents are reported, which participants and stewards take part, and how sporting decisions are used. Ask your organiser for its privacy notice. Where Stewards Room processes league records on the league’s instructions, the league remains responsible for those instructions; we help it handle requests.
Information we use
- Account identifiers, racing/display names, verified email addresses and linked Discord identifiers. Discord sign-in can also provide server membership information needed to check league access.
- Incident descriptions, driver accounts, racing names, video and image uploads, links, timestamps, annotations, rules, assessments, decisions and appeals. Footage may show other drivers’ usernames or incidental personal information.
- Private support messages, notification preferences, delivery status and records needed to answer requests or complaints.
- Technical and security information, including session cookies, access checks, request information and records of changes to a case.
We do not need your full date of birth, home address, identity documents, school, medical history or private conversations to review a racing incident. Do not upload them. Please crop or mute unrelated personal information before uploading, while keeping the racing evidence accurate. Contact us if sensitive information was included accidentally.
Why we use it
We use information to provide accounts and the service you request, assemble and review incidents, check access, support appeals, deliver requested service messages, answer questions and protect the service. We use contract where processing is necessary to provide a service under an applicable agreement, and legitimate interests for fair incident administration, support, security and handling disputes. We assess necessity and the effect on participants, with particular care for children. Legal obligations may require us to keep or disclose particular records.
Optional email and Discord alerts follow your notification preferences. We do not sell participant information or use case evidence for advertising. An uploader’s confirmation is not consent on behalf of every person shown in a clip. You may object to processing based on legitimate interests; we will consider your circumstances and explain our response.
When someone else submits information about you
Information may come from another participant, a league organiser, an authorised steward or a connected Discord workflow. A racing incident may be reviewed even if you did not submit it. The organiser or reporting participant should give you this notice when contacting you about the case. Contact us with the case reference or enough information to locate it if you have not been told what is held about you. You can provide your own account, correct factual information and challenge a decision through the case’s review and appeal process.
Who can see a case
Access depends on your role in the case. In a personal case, the owner can see material needed for their own review. Once drivers share an incident through invitations, each driver, including the owner, sees only their own private statements; authorised, uninvolved stewards can review all accounts. Participating drivers can see permitted evidence and published decisions; other drivers’ private accounts and draft steward discussions are restricted. Authorised site administration may need access for support, security or a rights request. An ordinary case URL does not grant access. A driver invitation is a separate, expiring link that one signed-in account can accept to join that incident. Send it only to the intended driver: possession of the invitation does not verify their racing identity.
The public example is a separate, curated historical excerpt. Submitting a case does not publish it on the public website or grant permission to use it in marketing. Exported reports and information already sent to a recipient may also be held by that recipient.
AI review and verdicts
Outside approved leagues, AI is limited to one incident per account per UTC day. We keep a short-lived account and incident reference to enforce that limit, including after an incident is deleted. The next successful cleanup after midnight UTC removes the previous day’s allowance records. These records contain no evidence or driver statements.
If an involved driver or authorised reviewer requests AI review, the service sends case accounts, rule text, evidence descriptions, selected uploaded images and sampled video frames to OpenAI. Structured account identity fields use labels, but free text and images can still identify people. Full continuous video, audio and saved external links are not analysed by this feature.
AI can be wrong, miss context and misread replay or network effects. It extracts supported facts from the supplied imagery; the selected rule tree determines the verdict and configured penalty. Driver accounts are treated as claims. Incomplete evidence can prompt a request, and unsupported paths require exception review. You can appeal with new evidence or a material omission and request human review through your league or our feedback route. Do not send unnecessary sensitive information.
OpenAI states that API content is not used to train its models by default unless the customer opts in. We request responses without application-state storage. This does not guarantee zero retention: provider abuse-monitoring records may normally be retained for up to 30 days, subject to legal and safety exceptions. OpenAI’s API data controls explain its arrangements.
Service providers and international processing
Sites hosting and its Cloudflare infrastructure store and deliver website records and evidence. Supabase provides authentication; Discord provides linked sign-in and configured league integrations. OpenAI receives the selected material only for requested AI preparation. Resend handles email delivery when enabled. Our public contact mailbox is hosted by Google.
Some provider processing, support and storage takes place outside the UK, including in the US. Choosing a European project or sending region does not mean all processing remains in Europe. In particular, Resend’s Ireland sending region does not move its stored message and log data out of the US. Applicable provider contracts and transfer safeguards govern these transfers. Contact us for details or a copy of the relevant safeguards, with confidential commercial information removed where appropriate.
League administration and service usage
League owners supply a league name, racing title, activity status, approximate active-driver count and races per year for registration review. Owners can view their own league’s operational stats. Stewards Room administration can review registrations and service-wide usage. These counts are not a public driver roster.
AI usage receipts record the model, time, incident and league reference where applicable, provider status, token counts and an estimated service cost. They contain no evidence or driver statements and are removed after 14 days by scheduled cleanup. An interrupted call can leave its cost unknown. League registration details remain while needed to operate the league; registration audit entries are kept for 14 days.
Season sporting register
A league can explicitly adopt a season register for new reviews. Membership in a season is based on the first publication date, not an inferred race date. This retains your verified account link, case reference, decision revision, policy version, fixed-code findings, mapped sanction recommendations, connection finding and challenge status. It does not retain clips, statements or evidential explanations. Season records expire on the league’s stated deletion date, at most 30 days after a season of up to 366 days. Ordinary 14-day case deletion does not delete this minimal register. Existing cases are not silently moved onto longer retention.
Only confirmed individual connection faults count towards connection suitability alerts. An unattributed artifact, shared-server problem or racing incident is not a driving penalty. Explicit league repeat rules count published recommendations, not proof a sanction was served. Appeals, superseded decisions and challenged records are excluded. Threshold actions remain recommendations; the site does not enforce them in a simulator.
See My sporting records to inspect or challenge your linked records, even after the original case expires. A challenge suspends repeat counting and an uninvolved league steward can void a mistaken record. Contact us for correction, access, restriction or deletion, including records whose original evidence has expired. A successful privacy erasure covers the season record too.
Our 14-day case retention rule
Draft and personal cases are deleted after 14 days without a saved change. League cases are deleted 14 days after the final decision and appeal window have closed. Resolved feedback is deleted after 14 days. An open review, appeal, complaint or documented preservation hold can suspend deletion while it is needed; we review holds rather than keeping them indefinitely.
Deletion removes original uploads, derived frames, accounts and case history through scheduled cleanup. A discarded personal case loses access immediately. Existing saved records receive a fresh 14-day transition period before the new rule can delete them. The cleanup process can take longer during an outage, which we investigate. Account and league membership records remain while needed to provide your account; ask us to close it when you leave.
The 14-day rule covers records under our application’s control. Service providers may retain security logs and backups for separate periods, and recipients may keep downloaded reports or messages. We cannot recall copies already downloaded by someone else. Minimal security, legal or billing records may remain where needed for a documented purpose.
Your rights and complaints
Depending on the circumstances, you can ask for access, correction, deletion, restriction or portability of your information, or object to its use. These rights are not absolute: another person’s privacy, an open dispute or a legal requirement can affect what we can do. We will explain any restriction. We normally respond to rights requests within one calendar month; if a permitted extension or clarification is needed, we will explain it.
Email stewardsroompro@gmail.com with “Privacy request” or “Privacy complaint”. Include a case reference if you have one, but do not send identity documents unless we ask for proportionate verification. You may also use the private contact form when signed in. We acknowledge privacy complaints within 30 days, investigate and communicate the outcome without undue delay. You can complain to the Information Commissioner’s Office.
Young drivers and changes
The service is for ages 13 and over, including drivers aged 13–17. We use private defaults for everyone and do not use targeted advertising, public driver profiles or engagement rewards. Read Young drivers for a shorter explanation and how a trusted adult can help. If information about an under-13 has been uploaded, contact us so we can assess and restrict or remove it where appropriate.
Material changes to how we use existing information will be explained through the service or appropriate direct communication. The date above identifies this notice version.
Questions? stewardsroompro@gmail.com. You do not need an account to contact us.