Privacy Policy — Ride Ready: Garage
Last updated: 10 May 2026
Who we are
Ride Ready: Garage is operated by Christopher Bird, trading as BirdTech, a sole trader registered in the United Kingdom.
Contact: privacy@ride-ready.uk
ICO registration number: ZC121698
We are the Data Controller for all personal data processed through this app.
What data we collect and why
We collect only what is necessary to provide the service.
| Data | Why we collect it | Legal basis |
|---|---|---|
| Email address and password | To create and secure your account | Contract |
| Vehicle registration numbers | To track your vehicles and retrieve official data | Contract |
| Vehicle details (make, colour, fuel type, year, engine size) | Retrieved from the DVLA to populate your vehicle records | Contract |
| MOT expiry date, road tax expiry date, tax/SORN status | Core service — tracking document expiry | Contract |
| Insurance policy details (provider, policy number, cover level, start date, renewal date, premium cost, payment type, direct debit amounts) | Entered by you when you choose to enable insurance tracking for a vehicle. You can create a shared policy and link it to one or more vehicles, or track insurance details directly on each vehicle. Tracking is off by default and entirely optional. | Consent |
| MOT test history and defects | Retrieved from the DVSA to show your vehicle’s test history | Contract |
| Service history records (date, odometer reading, service type, who performed the work, provider name and location, items completed, cost, notes, next service date and mileage) | Entered by you to track your vehicle’s maintenance history | Contract |
| Fluid logs (date, odometer reading, fuel type, quantity, cost, station notes) | Entered by you to track fuel and oil usage for a vehicle | Contract |
| Vehicle tasks (title, description, priority, due date, status) | Created by you to track to-do items for your vehicles, or auto-generated by the app as expiry reminders for MOT, road tax, and insurance | Contract |
| Garage items (name, notes) | Created by you to track non-vehicle items such as bicycles, tools, or other equipment | Contract |
| Notes | Free-text notes you choose to add to a vehicle | Contract |
| Ride logs (date, title, free-text location, conditions, notes, duration, distance, speed, elevation, power output) | Entered by you, extracted from an imported GPX file, or computed from a live GPS recording session | Contract |
| GPS route coordinates | Extracted from an imported GPX file or captured during a live recording session; up to 500 sampled coordinate pairs are stored to display your route on a map | Contract |
| Ride start and end timestamps | Extracted from an imported GPX file or set automatically when a live recording starts and stops; used to identify which of your vehicle settings were active during a ride | Contract |
| Continuous GPS location stream (live recording only) | Accessed in real-time while you actively record a ride using the Record feature. Your device’s GPS stream is processed locally to calculate distance, speed, and elevation gain; only the computed metrics and a sampled route (up to 500 coordinate pairs) are stored. The raw GPS stream is not transmitted to or stored on our servers. Location is accessed only while the recording screen is active and you have tapped Start Recording — it is not accessed in the background. | Contract |
| Performance settings (category names, setting names, units) | Created by you to define the trackable setup parameters for a vehicle or item (for example, tyre pressures, suspension, or gearing) | Contract |
| Performance setting values and logs (recorded value, optional notes, and timestamp for each entry) | Entered by you to track how your setup changes over time | Contract |
| Events (title, description, free-text location, date, time, event type, status) | Created by you to plan and track upcoming events such as track days, shows, or tours | Contract |
| Event participants (which of your vehicles or items will attend, their role, readiness status, and optional notes) | Created by you when planning which assets to bring to an event | Contract |
| Distance unit preference (miles, km, or hours) | Stored per vehicle or item so the app displays values in your preferred unit | Contract |
| Session token | Keeps you signed in between app sessions | Legitimate interests |
| DVLA API response snapshot | Stored to detect changes in official vehicle data between lookups | Legitimate interests |
Contract (UK GDPR Article 6(1)(b)): We cannot provide vehicle document tracking without processing vehicle and account data. Processing is necessary to perform the service you signed up for.
Consent (UK GDPR Article 6(1)(a)): Insurance policy details are collected only when you explicitly enable insurance tracking for a vehicle. You can withdraw consent at any time by disabling tracking for that vehicle, which removes the vehicle’s link to any insurance policy. If the policy is a shared policy linked to other vehicles, the policy record itself is retained until all vehicles are unlinked from it or your account is deleted. All insurance data is permanently deleted when you delete your account.
Legitimate interests (UK GDPR Article 6(1)(f)): Session tokens and DVLA snapshots are technically necessary for the app to function reliably. Neither is shared with third parties. Both are deleted when your account is deleted.
CSV import and export
You can bulk-import service records by uploading a CSV file. The contents of that file are processed to create records in your account and the file itself is not stored. You can also export your service records to a CSV file at any time — this download goes directly to your device and is not retained by us. CSV export is one way to exercise your right to data portability (see Your rights below).
GPX file import
You can import a GPX file to automatically populate a ride log with metrics (distance, speed, elevation, and power output) and a sampled GPS route. The GPX file is parsed on your device and is not uploaded to our servers. The extracted data — including up to 500 GPS coordinate pairs representing your route — is stored in your account. The raw file is not retained.
Live ride recording (early beta)
When you use the Record feature, the app requests access to your device’s GPS location via your device’s location services. You must explicitly grant this permission when prompted; if you deny it, the feature is unavailable. Location is accessed only while the recording screen is active and you have tapped Start Recording — it is not accessed in the background or at any other time.
Your GPS stream is processed entirely on your device to calculate distance, speed, and elevation gain in real time. The raw stream is never transmitted to or stored on our servers. When you stop and save a recording, up to 500 sampled GPS coordinate pairs and your computed ride metrics are stored in your account.
After saving, the ride’s start coordinates are sent to Nominatim (for reverse geocoding to a place name) and Open-Meteo (for historical weather conditions), in the same way as coordinates from a GPX import. See the “Who we share data with” section for details of those services.
This feature is currently in early beta. GPS accuracy depends on your device hardware and signal conditions. Recorded metrics should not be relied upon for safety-critical or legally consequential purposes.
What we do not do
- We do not sell your personal data to any third party.
- We do not share your data with advertisers.
- We do not use analytics SDKs or tracking software.
- We do not collect advertising identifiers.
- DVLA and DVSA API keys are stored on our servers only — they are never sent to your device.
Who we share data with
We share data only where necessary to operate the service.
Supabase Inc. acts as our Data Processor. They host our database and authentication service on servers located in the EU (Paris, France). Supabase processes data only on our instructions and under a Data Processing Agreement. The EU has a UK adequacy decision, so no additional transfer mechanism is required.
We send vehicle registration numbers to the DVLA Vehicle Enquiry Service and the DVSA MOT History API (both UK Government services) to retrieve official vehicle data. No other personal data is sent to these services.
Nominatim (OpenStreetMap Foundation) is used to convert the GPS start coordinates of a ride (whether imported from a GPX file or recorded live) into a human-readable place name (for example, “Silverstone, Northamptonshire”). We send only the coordinates of your ride start point. No account-identifying information is transmitted. Nominatim is operated by the OpenStreetMap Foundation, with servers in the EU.
Open-Meteo is used to retrieve historical weather conditions at the time and location of a ride (whether imported from a GPX file or recorded live). We send the GPS start coordinates and the date of the ride. No account-identifying information is transmitted. Open-Meteo is operated by Zippyfrog AG, Switzerland. Switzerland has an adequacy decision under UK GDPR, so no additional transfer mechanism is required.
We do not share your data with any other third party.
How long we keep your data
All account data — including vehicle records, MOT history, service records, insurance policies, tasks, garage items, ride logs (including any GPS routes captured via live recording or GPX import), performance settings, events, and your authentication credentials — is kept for as long as your account is active.
When you delete your account, all of your data is permanently and immediately deleted from our systems. Session tokens on your device are cleared when you sign out.
We do not retain your data after account deletion.
Your rights
Under UK GDPR you have the following rights. To exercise any of them, contact us at privacy@ride-ready.uk. We will respond within one calendar month.
| Right | What it means |
|---|---|
| Access | Request a copy of all personal data we hold about you |
| Erasure | Delete your account and all associated data (also available in-app via My Account) |
| Rectification | Correct inaccurate data |
| Portability | Receive your data in a machine-readable format |
| Object | Object to processing based on legitimate interests |
| Restrict | Ask us to pause processing while a complaint is resolved |
You also have the right to lodge a complaint with the UK supervisory authority, the Information Commissioner’s Office (ICO): ico.org.uk/make-a-complaint
Minimum age
This service is intended for users aged 16 and over. We do not knowingly collect data from anyone under 16. If you believe a person under 16 has created an account, please contact us and we will delete it.
Changes to this policy
If we make material changes to this policy we will update the date at the top of this document. Continued use of the app after changes constitutes acceptance of the updated policy.
Contact
Christopher Bird, trading as BirdTech