1. Who is responsible
DriveStable Ltd is the controller for personal information used by the DriveStable service. DriveStable Ltd is registered in England and Wales under company number 17410560. Its registered office is 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ.
For privacy questions or to exercise a data-protection right, email hello@drivestable.co.uk.
2. What this policy covers
This policy covers the DriveStable Google Play open beta, its signed-in Personal and private Squads services, beta support and the public DriveStable website. It does not cover an independent service or app that you choose to open from DriveStable.
The beta does not include public Squad discovery, Marketplace, payments, live vehicle-tax lookup, public profiles or advertising.
3. Information used in the beta
Account and authentication
When you sign in, DriveStable receives the account identifier and profile details needed to recognise your account, such as your email address, display name and verified-email state. Authentication is provided by Auth0, a service of Okta. DriveStable does not place authentication tokens in vehicle records or feedback drafts.
Personal vehicle records on your device
Vehicle profiles, registration and VIN details, mileage, maintenance, fuel or charging, expenses, journeys, reminders, photos and document references are primarily stored in the app's local database on your Android device. Selected app data may be included in Android backup when backup is enabled; Android and your Google account control that backup service.
Private Squads and safety controls
Signed-in private Squads use account identifiers, membership and role state, invitation state, build and dyno entries, meet activity, achievements, private Cruise records, reports, blocks and removal actions. These records are used to provide the private group and its safety controls. A member may deliberately publish a private build update and optionally attach a dyno-sheet image as member-only evidence. Selected evidence is stored in DriveStable's beta object storage and is available only through the authenticated private-Squad service; it is user-supplied and is not independently verified by DriveStable. The optional Squad Live feature shares fresh location only with current members of the selected private Squad, for up to one hour at a time. Ghost mode stops sharing and removes stored location fields. Private Cruises are included; public Squad discovery remains excluded.
Official MOT history
When you request an official MOT lookup, the vehicle registration is normalised and sent through DriveStable's authenticated API to the DVSA MOT service. DriveStable returns the available official MOT history to you. The beta does not perform automatic or background registration lookups, and live vehicle-tax lookup is not included.
Transferred Vehicle Passports
A buyer can choose to claim a transferred Vehicle Passport using a one-time code supplied by the seller. The code is checked by DriveStable's authenticated service and the verified sign-in email must match the transfer invitation. A successful claim provides access to the transferred vehicle identity and bounded history attached to that Passport. Dealer administration and Marketplace transactions are not part of the Personal beta.
Private Squad activity alerts
If enabled in notification settings, the Android app periodically checks the signed-in account for new private Meets, live Cruises, Squad invite requests and shared build updates. A private notification may show the Squad name and, for a single build update, the member display name, a shortened vehicle label and build details. Its public lock-screen version remains generic. Locations and invitation codes are not placed in notifications or saved notification state. These checks may be delayed and are not an emergency service.
Premium preview
The beta may show proposed Premium features and prices. Purchases, subscriptions and payment collection are not active, so DriveStable does not receive payment-card or billing information through the beta.
Diagnostics and support
Privacy-minimised crash and app-not-responding diagnostics may be sent to Sentry. They can include the app release, environment, basic Android or device information and network metadata needed to deliver the report. DriveStable configures these reports to exclude vehicle records, registrations, VINs, documents, routes, notes, screenshots and authentication tokens.
If you choose Send beta feedback, DriveStable prepares a draft containing the app version and basic device details. You choose the sharing app and recipient, can edit the draft, and control any additional text. Saved vehicle records are not attached automatically.
Website beta interest
If you register interest on the beta information page, DriveStable receives your name, email address, selected experience, optional note and limited campaign-attribution details. These details are used to record your interest and allow the beta team to respond or provide relevant beta updates.
Website campaign measurement
On the public DriveStable website, you can choose whether to allow Google Ads measurement. The tag library is present site-wide, but advertising storage, analytics storage, advertising user data and personalisation are denied by default. In that restricted state, Google may receive the consent state and a cookieless page-measurement ping. Measurement cookies and Fleet lead-conversion commands remain off unless you allow optional Google advertising. If you allow it, Google's tag may store or read measurement cookies and receive limited browser, device, page and campaign-attribution information. A successfully delivered Fleet enquiry may then be recorded once as a conversion using a non-personal submission reference. DriveStable does not send the form's name, email, company or message to Google. You can reopen Privacy choices in the website footer.
4. Why information is used
| Purpose | Information | Lawful basis |
|---|---|---|
| Provide sign-in and requested private features | Account, membership and feature records | Performance of the service agreement with you |
| Protect users and enforce private-Squad controls | Roles, blocks, reports, removals, optional live location and security records | Legitimate interests in safety, security and preventing abuse |
| Find and fix beta stability problems | Minimised diagnostics and feedback you choose to send | Legitimate interests in operating a reliable and secure service |
| Record and respond to website beta interest | Name, email address, selected experience, optional note and campaign attribution | Consent and legitimate interests in managing beta access |
| Handle rights requests and legal obligations | Contact, verification and request records | Legal obligation and legitimate interests in demonstrating compliance |
| Measure the effectiveness of DriveStable campaigns | Consent choice, limited website usage and campaign attribution and selected experience; no contact, vehicle, fleet, note or message contents | Consent |
DriveStable does not use open-beta information for advertising, automated decisions with legal or similarly significant effects, or the sale of personal information.
5. Service providers and transfers
DriveStable uses providers only where needed to operate the service: Auth0/Okta for authentication; Cloudflare and Neon for the protected Platform API, database connection and private-Squad evidence storage; DVSA for official, user-requested MOT history; HERE Technologies for map content in the private Cruise and Squad Live experience; Sentry for minimised stability reporting; and Android/Google for device backup and on-device ML Kit processing when the relevant feature is used. Resend delivers website beta interest and Fleet enquiry emails to DriveStable. Google also hosts the tag library and provides optional Ads campaign measurement across the website. Its tag receives denied consent by default and may send a cookieless page-measurement ping; measurement cookies and Fleet lead-conversion events remain off unless the visitor allows them. A feedback app you select receives only the draft and content you choose to share.
Some providers may process information outside the United Kingdom. Where a restricted international transfer occurs, DriveStable requires an applicable adequacy basis or recognised contractual safeguards. You can ask for more information using the privacy contact above.
DriveStable may also disclose information where required by law, or where necessary to establish, exercise or defend legal claims.
6. Retention and deletion
Local app records remain on your device until you delete them, clear the app's storage or uninstall the app. Android backups follow the backup controls and retention applied to your Google account and device.
Account and private-Squad information is kept while your account is active and then deleted or anonymised when it is no longer needed to provide the service. Diagnostics, support messages and beta-interest, enquiry and rights-request records are kept only for the period needed to respond, investigate the issue, protect the service or demonstrate that a request was handled. A limited record may be retained where required for security, fraud prevention, a legal obligation or legal claims.
The DriveStable website keeps your measurement choice in the browser until you change it or clear the site's local storage. Google applies its own retention controls to campaign-measurement data; DriveStable keeps only the campaign reporting needed to assess its campaigns and improve its marketing.
Read the account deletion processfor the practical steps and what happens after a request.
7. Your rights
Depending on the circumstances, you may have rights to access, correct, erase, restrict or receive a copy of your personal information, and to withdraw consent where processing relies on consent.
Your right to object: You may object to processing based on DriveStable's legitimate interests. Explain what you object to by emailing the privacy contact, and DriveStable will assess the request against any compelling lawful grounds.
DriveStable may need enough information to verify that a rights request relates to you, but will not ask for more than is necessary. You also have the right to complain to the UK Information Commissioner's Office at ico.org.uk.
8. Security and changes
DriveStable uses access controls, short-lived authentication, encrypted transport, environment separation, data minimisation and role-based private-Squad controls. No system can be guaranteed completely secure, so suspected privacy or security problems should be reported promptly to the privacy contact.
This policy will be reviewed as the beta changes. If DriveStable introduces a new purpose or material data use, the policy and relevant in-app notice will be updated before that processing begins.