Privacy

What we collect, and why

Last updated 29 August 2026

RaceDash.live is in early access and run by a small team in the United Kingdom. This page describes what the service actually does with your data. It is deliberately specific rather than generic — if something here doesn't match what you see, that's a bug worth telling us about.

Who is responsible

RaceDash.live is the data controller for the information described here. Contact us at privacy@racedash.live about anything on this page.

What we collect

Three things, and nothing else.

Your Google account details

When you sign in with Google we receive your name, email address, profile picture URL, and the account identifier Google issues for you. We never receive or store your password, and we never gain access to any other part of your Google account.

What you create in the app

Organisations, dashboards, their configuration, the members you invite, and any share links you generate. This is stored because it is the service.

Ordinary technical logs

Our hosting provider records standard request information, including IP addresses, for security and reliability. We do not use analytics, advertising, tracking pixels, or fingerprinting, and we do not build profiles of visitors.

Why we're allowed to hold it

Account and content data is processed to perform the contract between us — you asked us to run the service and we cannot do so without it. Technical logs are processed on the basis of our legitimate interest in keeping the service secure and working.

Timing data is not personal data

Lap times, positions, pit stops, and gaps come from timing feeds that are already public at the circuit or on a livestream. We treat that as public information about a race, not as information about you.

You can generate an unlisted link to a dashboard so that people without an account can view it. Anyone who has that link can open it. It is unlisted rather than secured — much like an unlisted video — so treat it as public the moment you send it, and assume it may be forwarded.

You can revoke a link at any time, which stops it working immediately. Share links only ever expose the race view; they can never reach your organisation's private content, and that boundary is enforced by the service rather than by a setting you could get wrong.

Who else touches it

Google Cloud Platform and Firebase host the service and process data on our instructions, in their capacity as our processor. That covers authentication, the database, and hosting.

Our pages load web fonts from Google Fonts, which means Google receives the IP address of visitors in order to serve those files. No other third party receives your data. We do not sell it, and we do not share it for advertising.

Where it is stored

On Google Cloud infrastructure. Some processing may take place outside the United Kingdom, under the safeguards Google provides for international transfers.

How long we keep it

Account and content data is kept while your account is open. If you ask us to delete your account, we remove your personal data and the content you own, other than anything we are legally required to retain. Technical logs are kept for a short period and then discarded.

What you can ask for

Under UK data protection law you can ask us for a copy of your data, ask us to correct it, ask us to delete it, ask us to restrict or stop certain processing, or ask for it in a portable form. Email privacy@racedash.live and we will respond within one month.

If you are unhappy with how we have handled your data you can complain to the Information Commissioner's Office at ico.org.uk.

Cookies and browser storage

This marketing site sets nothing at all. The app stores your sign-in session in your browser, which is strictly necessary to keep you signed in, and it is not used for tracking. There are no advertising or analytics cookies, which is why you are not being asked to dismiss a banner.

Children

The service is not intended for children under 13, and we do not knowingly collect their data.

Changes

If we change this page materially we will update the date at the top and, where the change affects you, tell account holders directly.