Last updated: 2026-08-16
1. Who we are
This privacy notice applies to the LMU Broadcast Control desktop application, the licence portal at portal.broadcastcontrol.uk, and the commentator web app.
The data controller is Paul Glover (trading as Broadcast Control). If you have any questions about this notice or your personal data, email privacy@broadcastcontrol.uk.
2. What we collect and why
| Data | Why | Legal basis (UK GDPR) |
|---|---|---|
| Email address | Delivering your licence key, sign-in magic links, and service-related notices. | Performance of contract; legitimate interest for account security. |
| Payment details (via Stripe) | Processing your subscription. We never see or store your card number — Stripe handles this. | Performance of contract. |
| Stripe customer / subscription identifiers | Linking your licence to your subscription so we can issue renewals and let you manage billing. | Performance of contract. |
| Device identifier and name | Enforcing the per-licence device limit you agreed to when subscribing. | Performance of contract; legitimate interest in preventing licence sharing. |
| IP address of sign-in attempts | Rate-limiting sign-in attempts and detecting abuse. | Legitimate interest in service security. |
| Administrative action log | Audit trail of support actions taken on your account. | Legitimate interest in accountability; legal obligation where applicable. |
We do not use analytics, advertising trackers, or marketing cookies. The portal sets a single strictly-necessary session cookie (lmu_portal) once you sign in; no consent banner is required for that.
3. Google account data (Google Sheets Race Control)
Google Sheets Race Control is an optional feature of the desktop application. It stays inactive until you choose to connect a Google account and a spreadsheet — if you never connect one, nothing in this section applies to you.
What we access, and why
| Google data | Why |
|---|---|
Your Google account email addressuserinfo.email |
Displayed in the app so you can see which Google account is currently connected. It is used for nothing else. |
Access to the individual spreadsheets you choosedrive.file |
Creating the Race Control spreadsheet, and writing event details, entry lists and race incidents into the spreadsheet you select. This is per-file access: the app can only ever see spreadsheets it created for you, plus any you hand-pick in Google's own file picker. It cannot list, open or read anything else in your Google Drive. |
Where it goes
Event, entry and incident rows are sent from your own computer directly to your own spreadsheet using Google's API. They do not pass through our servers and are not stored in our database. We never receive a copy of your spreadsheet or anything in it.
How the authorisation is stored
The authorisation that lets the app write to your spreadsheet is held only on your own computer, encrypted with Windows Data Protection (DPAPI) so that only your Windows user account can decrypt it. It is never transmitted to us, and it is never written to the application log.
Limited Use
Broadcast Control's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, we do not transfer it to anyone except where required by law, no human at Broadcast Control reads it, and it is never used to develop, improve or train generalised artificial intelligence or machine-learning models.
Disconnecting
You can disconnect at any time from the Google Sheets window in the app. Doing so revokes the authorisation with Google and deletes the stored credentials from your computer. You can also revoke access yourself at myaccount.google.com/permissions. Revoking does not delete the spreadsheet — it belongs to you and stays in your Google Drive.
4. Who we share it with (sub-processors)
We use the following processors to run the service. Each is contractually bound to process personal data only on our instructions.
- Cloudflare, Inc. — hosts the licence worker, portal, and database (privacy policy).
- Stripe Payments Europe, Ltd. — payment processing and billing portal (privacy policy).
- Resend (Plus Five Five, Inc.) — transactional email delivery (privacy policy).
5. International transfers
Stripe and Resend are based in the United States. Where personal data is transferred outside the UK, we rely on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, published by each processor in their data-processing terms.
6. How long we keep it
- Licence keys, device records, and owner email — kept while the licence is active, and for up to 24 months after cancellation so that renewals and support requests continue to work.
- Sign-in attempt log (email + IP) — retained for up to 30 days for abuse detection, then deleted.
- Webhook event log — retained for up to 90 days for idempotency and reconciliation.
- Administrative audit log — retained for the life of the account plus 24 months.
- Race Control rooms (Stewards Room events) — a room stays available while it is open, and is closed automatically 30 days after it is created if it is not closed sooner. Its record — the incident list, rulings and steward roster — stays readable and exportable for 90 days after it closes, then the room and its entire record are deleted automatically. The licence owner, or an administrator, can close or delete a room sooner at any time.
- Stripe billing records — retained by Stripe according to their own retention policies; we keep customer identifiers only for as long as the linked licence exists.
- Google Sheets authorisation — held only on your own computer until you disconnect or revoke it, at which point it is deleted. We hold no copy, so there is nothing for us to retain.
7. Your rights
Under UK GDPR you can ask us to:
- provide a copy of the personal data we hold about you,
- correct data that is inaccurate,
- delete your data (subject to any overriding legal obligations — for example, tax records),
- restrict or object to how we process it, and
- receive it in a portable format.
To exercise any of these rights, email privacy@broadcastcontrol.uk. We will respond within one month.
If you're unhappy with how we handle your data you can complain to the Information Commissioner's Office (ico.org.uk).
8. Security
All traffic uses HTTPS with HSTS. Sign-in links are single-use, expire after 15 minutes, and are stored only as a SHA-256 hash. The session cookie is HttpOnly, Secure, and SameSite. Administrative actions are logged. We never send or store your payment card number.
9. Changes to this notice
If we make material changes we will update the "Last updated" date and, where appropriate, notify affected users by email.