Privacy Policy

Effective 2 November 2026 · Applies to the EvmetricsOBD app for iPhone and iPad (and Mac, when released) and to the evmetrics.co.uk website

1. Who we are

EvmetricsOBD and the evmetrics.co.uk website are developed and published by Evmetrics Ltd, a private limited company registered in England and Wales (company number 15685915), registered office 10 Westminster Road, Macclesfield, England, SK10 1BX. Evmetrics Ltd is the data controller for any personal data described in this policy. You can reach us at hello@evmetrics.co.uk.

2. Vehicle diagnostic data

The app communicates with your vehicle through an OBD adapter you own (Bluetooth, Wi-Fi or USB) and reads diagnostic data such as sensor readings, battery telemetry, trouble codes (DTCs), the vehicle identification number (VIN) and the odometer. This data is:

• processed on your device;
• stored only on your device (and in your personal iCloud, if you enable sync — see section 8);
• never transmitted to Evmetrics Ltd unless you choose to send a research log (below).

Research submissions. Where available, the Full Vehicle Scan, PID Scanner and Reverse Engineering tools include an optional "Send to EvmetricsOBD" button. When you tap it, the log from that tool and any note you add are sent to Evmetrics Ltd and stored on Google Cloud in the UK. We use them to add support for your vehicle. A log contains the responses your car's modules gave, the vehicle platform, the app version and the first 10 characters of your VIN (which identify the model and year, not your car). The app removes the full VIN before sending. Because a log records what the modules answered, it can include a module's serial number if a module reports one. It does not contain your location, name or any device identifier, and we do not record your IP address. Nothing is sent unless you tap Send. If you then email us about the submission, we keep that email thread to reply to you. To have a submission deleted, email hello@evmetrics.co.uk with its ID.

The Android app. EvmetricsOBD for Android keeps your readings, fault codes and VIN on the phone, excluded from Android's cloud backup and device transfer. It has no account, no analytics, no advertising, no location logging, no Assistant and no cloud sync, so sections 3 to 8 of this policy don't apply to it. The only data it sends is a research submission you choose to send, as described above; to check that the request comes from a genuine copy of the app, it uses Firebase App Check with Google's Play Integrity service, which involves Google processing information about the app and device. Android asks for the Nearby devices (Bluetooth) permission to find and connect to your adapter; on Android 8 to 11, Android requires the Location permission for Bluetooth scanning, and the app does not read your location.

3. Location

With your permission, the app uses your location while in use to record journeys (route maps, distance) and to keep logging vehicle data while your phone is locked during a drive or charging session. During a Track Day session it also uses precise location to time laps and draw the track map. Location history is stored on your device as part of your journey and track session records. It is not sent to us or to any third party. You can deny or revoke location access at any time in iOS Settings; the app works without it.

4. Online lookups and the update check

VIN lookup (NHTSA), off by default. If you turn on Settings → Privacy → Look up vehicle details online, the app adds make, model, year and trim to your diagnostic reports by sending the VIN to the US National Highway Traffic Safety Administration (NHTSA) vPIC API, a public government service. The request contains only the VIN — no name, email, location or device identifier. NHTSA's handling of requests is governed by its own web policies. With the setting off, nothing is sent and reports simply leave those fields out.

Update check. When it opens, and when you return to it, the app downloads a small settings file from evmetrics.co.uk/obd/app-config.json. It tells the app whether a newer version is available and switches features on or off without an app update. The request is a plain download that carries no account, VIN, vehicle data or device identifier; like any web page, our web host sees the IP address it came from in its standard server logs. If the download fails, the app carries on as normal.

5. The Assistant (on device)

Where it is available in your version of the app, the Assistant lets you ask about your car in plain English. It runs on Apple's on-device Foundation Models, which means the language model itself is part of the operating system on your iPhone, iPad or Mac. Your question and your vehicle data are processed locally and are not sent to Evmetrics Ltd, to Apple, or to anyone else. There is no API key, no account and no per-question cost behind it. It requires Apple Intelligence to be available and enabled on your device; where it is not, the app tells you why and the rest of the app is unaffected. Trouble-code names come from a database bundled with the app, entirely offline.

Earlier versions of EvmetricsOBD offered optional trouble-code research through Google's Gemini API. That has been removed. The app now makes no outbound AI requests of any kind.

6. Siri, Shortcuts and Spotlight (iOS)

On iOS the app offers Siri phrases, Shortcuts actions and Spotlight search results. To make these work, the app hands selected vehicle information to Apple's on-device Spotlight index: vehicle names, registrations and VINs from your Garage, current sensor readings, the fault codes found by your last scan, and — with EvmetricsOBD Pro — recent journeys and workshop checklists. It also indexes the standard SAE trouble-code table bundled with the app.

• This index is maintained by iOS on your device. It is not sent to Evmetrics Ltd, and we have no access to it.
• Nothing is indexed while Demo Mode is on, so sample data never ends up in your search results.
• Deleting a vehicle in the app removes it from the index; deleting the app removes everything it indexed.
• Spoken requests to Siri are handled by Siri itself, under Apple's privacy policy and your Siri settings. The app receives only the resulting request and answers it from data already on your device.

7. Usage analytics, crash reports and performance data (iOS)

The iOS app uses Firebase Analytics (Google LLC) to understand which features are used and where the app fails, so we can improve it. Collection is deliberately coarse and isn't linked to your name, VIN or car: screen views, adapter connect/disconnect outcomes, transport type and the adapter's model name, scan started/completed events with fault counts, warnings and alerts shown, report generation, purchase/restore outcomes, which Siri, Shortcuts and Spotlight features are used, and a once-a-day status (how many vehicles are in your garage and how many were scanned recently, whether you have Pro, and how many and which widgets are installed). When something fails, such as a backup, an import or export, a save to disk or a scan, the app records that it failed and a system error code, never the error text or file names. The app never logs VINs, GPS locations, sensor readings or any content of your vehicle data as analytics. Google works out your approximate country from your IP address, and our reports group by country.

Crash reports and performance data. The iOS app also uses Firebase Crashlytics and Firebase Performance Monitoring (Google LLC) so we can fix crashes and slow screens. A crash report contains the stack trace, the state of the app, and device and OS details. Performance data contains app start times, the timing and address of the app's network requests, CPU and memory use, and device and OS details. Google also receives your IP address, which it uses to group performance data by location. Each carries an identifier for this installation of the app: an installation UUID for crash reports and a Firebase installation ID for performance data. These are not linked to your name, VIN or car, and we do not use them to track you across apps or websites. The app adds no vehicle data to these reports.

• You can turn analytics off at any time with Settings → Privacy → Share anonymous usage data; the choice applies immediately. This switch covers usage analytics only. Crash reports and performance data still go to Google while it is off.
• The Mac build, when released, will ship without Firebase and send none of this.
• Google's processing is governed by the Firebase privacy documentation.

8. iCloud sync (optional)

If you enable iCloud sync, your Garage vehicle records, Workshop checklists, Fleet costs and journeys are stored in your private iCloud container, managed by Apple and protected by your Apple ID. Evmetrics Ltd has no access to it. Apple's handling of iCloud data is described in Apple's privacy policy.

9. Reports and exports you share

You can generate diagnostic reports (HTML) and export journeys, workshop templates, fleet records, GPX tracks or Track Day sessions (PDF, CSV, GPX or .evmtrack) as files. These may contain vehicle data such as the VIN, odometer and location history. They leave your device only when you choose to share them, and only to the destination you pick in the iOS/macOS share sheet.

10. Device permissions

• Bluetooth — to connect to your OBD adapter.
• Local network — to connect to Wi-Fi OBD adapters. If you save a Wi-Fi adapter's password so the app can join its network automatically, it is kept in the device keychain.
• Notifications — to warn you if the battery pack overheats while charging and the app is in the background. Requested the first time you charge; you can turn the alert off in Settings.
• Location (while in use) — journey logging and background data capture, as described in section 3.
• Motion sensors: during a Track Day session the app reads the phone's accelerometer to show G-force. iOS doesn't ask for permission for this. The readings are kept only in the session, on your device.

11. Data retention and deletion

Because your data lives on your device, you are in control of it. You can delete individual reports, journeys and vehicles inside the app, disable iCloud sync, or remove everything by deleting the app. The only server-side copy of your vehicle data is a research log you chose to send (section 2), which we delete when you ask. Usage analytics, crash reports and performance data (section 7) are held by Google in Firebase and in our Google Cloud reporting.

12. The evmetrics.co.uk website

Server logs. Like any web server, ours records the IP address, date and time, page requested and browser type (user agent) of each request. We use these logs only to run and secure the site, on the basis of legitimate interests, and keep them for a limited period.

Google Analytics, only with your consent. We use Google Analytics 4 (provided by Google Ireland Limited and Google LLC) to see which pages are read and how people find the site. It is loaded only after you click Accept in the cookie banner; until then nothing from Google Analytics runs. The legal basis is your consent (UK GDPR and EU GDPR Art. 6(1)(a); UK PECR reg. 6 and the EU ePrivacy Directive Art. 5(3)). It sets two cookies:

• _ga: distinguishes visitors; expires after 2 years;
• _ga_0JXJY90TMZ: keeps the session state; expires after 2 years.

We send Google Consent Mode signals that allow analytics storage only, never advertising storage or personalisation. Your choice is stored in your browser (localStorage), not in a cookie. You can change it at any time with Cookie settings in the page footer; withdrawing consent deletes the Google Analytics cookies. Google may process the data in the United States under the EU-US Data Privacy Framework and its UK Extension.

Fonts and code libraries. Fonts are served from our own server. A few data pages on evmetrics.co.uk (maps and charts) load code libraries from public content delivery networks such as jsDelivr and unpkg, so your browser sends your IP address to those services when you open one of those pages. The EvmetricsOBD pages don't.

13. Your rights

Under the UK GDPR, and the EU GDPR if you are in the European Union, you have rights of access, rectification, erasure, restriction, portability and objection, and you can withdraw consent at any time. Apart from research logs you choose to send (section 2) and the analytics, crash and performance data in section 7, which carry an installation identifier rather than your name, we do not hold personal data about you on our systems, so most requests can be fulfilled directly on your device — but if you have any question or concern, contact us at hello@evmetrics.co.uk and we will help. You also have the right to lodge a complaint with the UK Information Commissioner's Office (ICO) or, in the European Union, with the data protection authority of the country where you live.

14. Children

The app is not directed at children under 13 and we do not knowingly collect personal data from children.

15. Changes to this policy

If the app gains features that change how data is handled (for example online vehicle-record lookups), we will update this policy and the App Store privacy label before those features ship. The effective date at the top reflects the latest revision.