Last Updated: November 26, 2025
Summary: RaceMetrics RC is committed to protecting your privacy. We collect minimal data necessary to provide our RC racing analytics service, use Supabase for secure authentication, and never sell your personal information.
Welcome to RaceMetrics RC ("we," "our," or "us"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our RC racing analytics platform at app.racemetricsrc.com.
By using RaceMetrics RC, you agree to the collection and use of information in accordance with this policy.
When you create an account, we collect:
| Data Type | Purpose | Storage Location |
|---|---|---|
| First Name | Personalize your account, identify you in the system | PostgreSQL Database |
| Last Name | Personalize your account, identify you in the system | PostgreSQL Database |
| Email Address | Account authentication, sign-in notifications, account recovery | Supabase (EU/US) & PostgreSQL |
| User ID | Unique account identification | Supabase & PostgreSQL |
| Authentication Tokens | Secure session management | Browser (localStorage) & Supabase |
You may optionally provide:
| Data Type | Purpose | Storage Location |
|---|---|---|
| Primary Transponder ID | Link your race results to your profile | PostgreSQL Database |
| RC Car Information | Track your vehicles (manufacturer, model, custom name) | PostgreSQL Database |
| Club Memberships | Associate with racing clubs and venues | PostgreSQL Database |
| Simulator Preferences | Personalize your interface and analytics | PostgreSQL Database & Browser (localStorage) |
| Your Postcode (UK) | Calculate distances to race venues on the home page and power the "Nearby venues" filter. You enter this yourself in Account → Preferences → Location (optional). You can also use your device's location services to auto-detect it; that detection happens entirely in your browser — only the postcode text is stored. | PostgreSQL Database |
| Cached Location Coordinates | Latitude / longitude derived from your postcode via postcodes.io (see §3.2). Stored so we don't re-lookup your postcode on every page load. Cleared when you clear your postcode. | PostgreSQL Database |
| Distance Unit Preference | Miles or kilometres, used when rendering distances on the home page | PostgreSQL Database |
About your postcode: We store the postcode text and its approximate latitude/longitude on our servers. We do not share it with third parties. It is only used to compute distances between you and race venues. You can remove it at any time via Account → Preferences → Location → Clear — this also deletes the cached coordinates.
We collect and display publicly available race results:
Note: This data is sourced from public race timing systems and is already publicly available. We aggregate and analyze this data to provide insights.
When you use our service, we automatically collect:
We use Supabase (supabase.com) as our third-party authentication service provider. Supabase handles all user authentication, password-less login (magic links and OTP codes), and session management on our behalf.
Why We Use Supabase:
What Data Supabase Processes:
| Data Category | Details | Purpose |
|---|---|---|
| Email Addresses | Your email address | Send magic links and OTP codes for authentication |
| Authentication Tokens | Session tokens, refresh tokens, access tokens | Maintain secure logged-in sessions |
| User IDs | Unique identifier for your account | Link authentication to your RaceMetrics RC profile |
| User Metadata | First name, last name, email confirmed status | Profile information and account verification |
| Sign-in Activity | Timestamps, IP addresses, device information | Security monitoring, fraud detection, audit logs |
| Email Delivery | Email sent status, delivery confirmations | Ensure authentication emails are delivered |
Supabase Security & Compliance:
Data Sharing with Supabase:
When you create an account or sign in, we share your email address with Supabase for authentication purposes. Supabase processes this data on our behalf as a data processor under a Data Processing Agreement (DPA) that ensures your data is protected according to applicable privacy laws.
Your Rights with Supabase:
While Supabase processes your authentication data, you maintain all your privacy rights. You can request access, correction, or deletion of your authentication data by contacting us. We will coordinate with Supabase to fulfill your request.
Learn More:
We use postcodes.io (postcodes.io), a free UK postcode lookup API, in two situations:
In both cases the postcode text is sent to postcodes.io to retrieve approximate latitude/longitude coordinates plus a human-readable locality label (e.g. "Kidsgrove, Stoke-on-Trent"). These values are cached on our servers so we never re-send your postcode on subsequent page loads.
Postcodes.io is operated by Ideal Postcodes and is built on Ordnance Survey Open Postcode data. See their about page and privacy policy.
The Find Tracks page and the in-page venue map use OpenStreetMap (openstreetmap.org) to render the map background.
When you view a map, your browser fetches map tile images directly from OpenStreetMap's public tile servers. This means OpenStreetMap receives:
We do not pass any account information, name, email, or venue context to OpenStreetMap. OSM tile requests happen entirely client-side; our servers are not in the loop.
OpenStreetMap is operated by the OpenStreetMap Foundation. See their privacy policy and tile usage policy.
RaceMetrics RC ingests publicly-published race results and venue metadata from three upstream sources. These scrapes happen on our servers — your browser does not communicate with these sites when using RaceMetrics RC, and we do not pass any of your personal information to them:
All three sources publish their data publicly. We are an aggregator and analytics layer — race results, driver names, and club metadata originate with those sources, not with us. If you appear in our data and want a correction, it usually needs to happen upstream first; contact us via /bug-report and we'll help.
Any registered user can suggest improvements to a venue's public record via the kebab menu → Submit Venue Info on a venue page. This form accepts:
Submissions are stored under your account email and reviewed manually by an administrator before any of the suggested values are applied to the public venue record. If an admin approves an address-only submission and the address contains a UK postcode, that postcode is also looked up via postcodes.io (§3.2) so the venue gets distance + locality data. Rejected submissions are retained in our database for audit purposes but are not applied to the venue.
We use the collected information for:
You have the right to:
We currently do not send marketing emails. Authentication emails (magic links, OTP codes) are essential for the service and cannot be opted out of while maintaining an account.
RaceMetrics RC is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe we have collected information from a child under 13, please contact us immediately.
Your data may be transferred to and processed in countries outside your country of residence, including the United States and European Union, where our service providers (Supabase) operate. We ensure appropriate safeguards are in place for such transfers.
We may update this Privacy Policy from time to time. We will notify you of any changes by:
Your continued use of RaceMetrics RC after changes constitutes acceptance of the updated policy.
If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us:
For users in the European Economic Area (EEA), we process your personal data based on:
Your Privacy Matters: We are committed to transparency and protecting your data. If you have concerns or questions, please don't hesitate to reach out.