Skip to content
motorwatch.
Back to Motorwatch

The details, made clear

Your privacy. Clearly explained.

What information Motorwatch needs, why it matters, and the choices that stay with you.

Draft for reviewUpdated 30 October 2026 · Not yet effective
A preview of the planned service. Accounts, vehicle monitoring and Stripe payments are not connected here. These drafts do not replace the policies on the current Motorwatch website.
Details to confirm before launch
  • Add Motorwatch’s legal operator name and postal address; retain privacy@motorwatch.co.uk as the privacy contact.
  • Verify extension data collection and analytics controls for the versions actually distributed in each browser store.
  • Confirm processing bases, provider contracts, production hosting/email suppliers, data locations and international-transfer safeguards.
  • Set and publish retention periods, backup deletion schedules and the process for handling rights requests. Review the finished notice before launch.

01

A purpose for each detail

Accounts, saved vehicles, alerts and payments each need different information.

02

Separate choices

Optional product news and analytics are separate from the service you ask for.

03

A clear point of contact

Ask about your information, request a change or raise a concern.

01

Who we are & what this covers

Motorwatch helps people understand vehicle asking prices. This draft covers the website, the browser extension and the planned account, watchlist, email and membership services.

Motorwatch would be responsible for deciding how personal information is used to operate these services. The legal name of the operator and its postal contact address must be added here before this notice takes effect. The privacy contact is privacy@motorwatch.co.uk.

In this website preview: account, watchlist and feedback forms keep entries in the page’s temporary memory; they are not submitted to Motorwatch or saved as an account. The market report email signup is live: it sends your email address and chosen report to Resend so we can email you a confirmation link. Google Analytics and PostHog are live too, but only if you allow analytics. Hosting for this preview is provided separately by Vercel, which may process technical request information to deliver and protect the site. Use example details when trying the other forms.

The cookie controls separately remember your essential/analytics choice, notice version and timestamps in this browser’s local storage. The choice is honoured for 180 days and is not sent to a server. Read the storage details.

02

The information involved

The planned services need different information depending on what you choose to use:

  • Your account: name, email address, sign-in information and security events, such as verification and password-recovery requests. Supabase Auth is the selected sign-in provider.
  • Your watchlist: listing links, vehicle identifiers and details, recorded asking prices, your alert rules and notification preferences.
  • Your membership: plan, billing contact details, subscription status, transaction references and invoices. Payment details would be entered through Stripe. Motorwatch’s planned integration would use payment references and limited card details, rather than storing full card numbers or security codes.
  • Your messages: support enquiries, optional uninstall reasons, comments and an email address if you choose to provide one. Uninstall feedback does not need an email address.
  • Technical and usage information: requests, device and browser information, online identifiers, usage events and error information used for security or measurement, depending on the service and your choices.

An email address is needed for an account and email alerts. Optional feedback and product-news choices are separate. You can still browse public reports and use the free extension without signing up for a paid membership.

03

The extension & vehicle data

The extension reads vehicle information on supported listing pages and communicates with Motorwatch to retrieve or contribute asking-price observations. This is how a price history can build up as listings are observed. A vehicle record may include a listing identifier or URL, specification, asking price and observation time.

The extension also has device storage for features such as saved notes and preferences. The extension source reviewed for this redesign includes Google Analytics event reporting, an installation-level identifier, session information and page-view fields. These are not safely described as “no personal data” or assumed to be anonymous.

Release verification needed: the exact fields, page coverage, analytics controls and retention must be checked against each released browser version. This website preview does not change the installed extension or its tracking settings.

Weekly market reports are intended to describe groups of vehicle listings, without publishing account emails or private watchlists. Asking prices are not confirmed sale prices. See how to read the data.

04

Why we use it

The proposed legal bases below must be checked against the final service and documented before launch:

Providing the service — contract. Creating and managing an account, maintaining the watchlist you request, sending its service alerts and administering a paid membership.

Optional communications and measurement — consent. Product news, optional report subscriptions and the proposed website analytics setup. Choosing these is separate from creating an account.

Keeping the service reliable — legitimate interests. Preventing abuse, investigating errors, answering support requests and understanding voluntary feedback, with safeguards and a balance against your rights.

Required records — legal obligation. Keeping records needed for tax, accounting and other applicable legal duties.

Vehicle alerts are based on the vehicles and rules you select. The planned service does not make decisions about your eligibility for credit, insurance or employment.

05

Service providers & sharing

The selected providers for the new service are:

  • Supabase: account authentication and the planned account/watchlist database. Supabase privacy information.
  • Stripe: checkout, recurring payments, invoices and billing management. Stripe may also process information for its own payment-security and legal purposes. Stripe privacy policy.
  • Google Analytics: website measurement, only when you allow analytics: pages viewed, where visits come from, and actions such as install clicks, report searches and report signups. Google signals and ad personalisation are off, and events never include your email address. Google’s analytics data information.
  • PostHog: website measurement and comparing versions of a page, on its EU cloud, only when you allow analytics: the same pages and actions as Google Analytics, with an online identifier. Session recording is off, and events never include your email address. PostHog privacy policy.
  • Resend: sends market report emails (which may include one clearly labelled sponsor message; sponsors never receive your details) and stores the email address and the reports you follow (make, model, model year and how often), plus whether you’ve unsubscribed. Resend privacy policy.
  • Hosting: Vercel serves the website. Its data handling for production is still to be confirmed.

Access should be limited to what each provider needs for its role. Information may also need to be disclosed to professional advisers or authorities where there is a valid legal reason. External listing sites, browser stores and community platforms have their own privacy notices.

06

Storage, retention & security

The proposed approach is to retain account and watchlist information while it is needed to provide your service, and then delete or anonymise it when that purpose ends, subject to records that must be kept. Stopping a subscription and deleting an account are separate actions.

Billing records may need to remain for legal and accounting purposes. Support and feedback records should be kept only while needed to handle the matter and a proportionate follow-up period. A minimal record of an unsubscribe request may be needed to respect your choice.

The final notice must specify the retention periods or precise criteria for account data, observations, analytics, logs, backups, support and billing. Backup deletion may follow a different schedule from removal from the active service; that schedule must be explained.

Supplier locations, chosen database region and any transfers outside the UK are not yet finalised. Before launch, Motorwatch must identify relevant destinations, the applicable transfer safeguards and how you can obtain information about them. Selecting a UK database region alone would not establish that every provider processes everything in the UK.

07

Emails & your choices

The planned account lets you manage vehicle alerts, digests and optional report or product-news emails separately. Marketing choices are optional and would include an unsubscribe route in each message.

Changing marketing preferences would not stop messages needed to operate your account, such as a requested reset, security notice or important billing information. Uninstalling the browser extension would not automatically cancel a website membership or unsubscribe an email address.

Google Analytics and PostHog stay off until you choose to allow analytics, and you can turn them off again from “Cookie settings”. The cookie policy explains the controls.

08

Your rights & contacting us

Depending on the circumstances, you can request access, correction, deletion, restriction or a portable copy of your personal information. Where processing relies on consent, you can withdraw it without affecting earlier lawful use.

Your right to object: you can object to processing based on legitimate interests and to the use of your information for direct marketing. Contact privacy@motorwatch.co.uk.

We may need to confirm your identity to protect the information involved. Some records may need to be retained where a legal duty or other valid exception applies.

You can raise a concern with Motorwatch and can also complain to the UK Information Commissioner’s Office through the ICO’s complaints service.

09

Changes to this notice

The effective notice will carry its own version and date. Material changes to the way information is used should be explained before they take effect where required. New uses requiring consent would need a new choice, rather than being authorised simply by editing this page.

This draft was updated on 13 October 2026. Its structure was checked against ICO privacy-notice guidance; it still needs the operational details and a legal review before use as a live notice.