Most of us in the enthusiast scene think about our OBD port as a tool. Plug in a Bluetooth dongle, pull fault codes, clear a warning light, log a power run on the way to the rolling road. Job done. What fewer people are thinking about is what happens to that data when it goes the other way, when the car itself is continuously generating a record of exactly how you drive, how hard you push it, and what modifications have been made. OBD-II data logging has moved well beyond the workshop laptop. In 2026, it is baked into connected systems, manufacturer apps, insurer telematics, and even some lease agreements in ways most drivers never read about in the small print.
What your OBD port is actually recording
The OBD-II standard became mandatory on all petrol cars sold in the UK from 2001 and diesels from 2004. Every car built since then has a port, typically under the dashboard on the driver’s side, broadcasting a constant stream of data: engine RPM, throttle position, boost pressure, coolant temperature, fuel trims, torque requests, and dozens more parameters depending on the ECU. On a standard road car, this exists to help mechanics diagnose faults. Fine. Understood. But the same data stream that tells a technician your injectors are misfiring also tells anyone plugged in exactly how you’ve been driving.
Modern connected cars take this further still. Manufacturers including Volkswagen Group, BMW, and Ford have built over-the-air telemetry into vehicles sold in the UK, meaning aggregated driving data is transmitted back to manufacturer servers without you needing to plug anything in. VW’s Car-Net, BMW’s ConnectedDrive, and Ford’s FordPass all collect this information. How long it is retained, who it is shared with, and under what circumstances it might be handed to insurers or third parties is buried in terms and conditions most buyers scroll straight past at the dealership.
Why this matters specifically if you’ve tuned or modified your car
Here is where OBD-II data logging becomes genuinely relevant to anyone in the modified car world. A standard remap, for instance, changes fuelling tables and boost targets inside the ECU. A mapped car running more boost than factory spec will generate throttle and torque data that looks nothing like a stock vehicle. Insurers using telematics to monitor policyholders, and plenty of UK insurers do, particularly on younger drivers, can potentially identify discrepancies between declared vehicle spec and what the car is actually doing.
I’ve spoken to a few people in the scene who discovered this the hard way. One lad from Sheffield had a black-box policy, got into a minor prang, and found the insurer querying the logged torque figures against the declared engine output at underwriting. He hadn’t disclosed the remap. The claim got complicated fast. The data doesn’t lie, and if you’ve tuned your car without updating your insurance, that OBD stream is effectively a witness statement waiting to be read. If you’re wondering about the full financial picture of running a modified car in the UK, the breakdown at our piece on the real cost of running a fast car in the UK covers the insurance angle in detail.
Third-party dongles and what they do with your data
The OBD Bluetooth dongle market is massive. Products like the OBDLink MX+, Veepeak, and various own-brand units sold on Amazon UK connect your car to your phone and push data through apps such as Torque Pro or OBD Fusion. Cheap, useful, brilliant for monitoring boost and AFR on a mapped car. The question worth asking is where that data goes once it leaves your phone.
Many of the free apps in this space monetise through data. Aggregated driving behaviour, location, speed profiles, all of it potentially sold to data brokers or used to train insurance risk models. The ICO (Information Commissioner’s Office) published guidance on connected vehicle data in 2025, making clear that vehicle data which can be linked to an identifiable individual constitutes personal data under UK GDPR. Manufacturers and app developers are supposed to obtain proper consent and provide clear privacy notices. In practice, enforcement has been patchy. The connected infrastructure question is bigger than just cars, too; the same protocol-level data vulnerability discussion applies across smart devices generally, which is worth a read via further reading: how smart meters are talking to the national grid: the smets2 communication stack, vulnerabilities, and what ofgem isn’t telling you.
Track day data and the grey area
Here’s a question I genuinely find interesting: if you take your car to a track day and thrash it, does any of that get logged in a way that could affect you later? On a car with manufacturer telemetry enabled, the answer is potentially yes. Some manufacturers distinguish between road and track use by GPS geofencing. Others don’t. If your car logs a session at Silverstone with sustained high RPM, high lateral g-forces, and repeated hard braking events, and that data is accessible to your insurer, there’s a legitimate question about whether that data colours any future claim assessment.
My advice, for what it’s worth: disable or opt out of manufacturer connected services if the car allows it. Check your vehicle’s privacy settings the same way you’d check your phone’s. Some manufacturers bury this under infotainment menus. BMW’s ConnectedDrive, for example, has a data sharing opt-out that most owners never find. And if you’re running a third-party dongle, read the app’s privacy policy before you start logging. It takes five minutes and could matter enormously if you’re tuned and pushing the car hard regularly.
What about DVLA and enforcement?
The DVLA itself doesn’t have direct access to OBD data streams at the moment. Enforcement around modified cars still relies primarily on MOT testing, visual inspection, and self-declaration. But the direction of travel is clear. The DVLA has been expanding its data-sharing frameworks with insurers and police forces, and connected vehicle data will inevitably be part of that picture as the legal and regulatory framework catches up with the technology. Police forces are already using social media to find modified car owners, as covered in detail in our piece on how UK police are using TikTok and Instagram to catch modified car drivers. Adding OBD telemetry to that toolkit is not a stretch.
Practical steps for enthusiasts right now
Audit what’s connected to your OBD port and what apps have access. If you use a permanent Bluetooth dongle, think about whether it needs to stay plugged in all the time or just during diagnostics and data logging runs. Review your insurer’s telematics terms if you have a black-box policy, and make sure your declared spec actually matches what the car is doing. If you’ve remapped, that needs to be on your insurance schedule. Full stop.
On the manufacturer side, go into your car’s connected services settings and understand what data sharing you’ve agreed to. Most manufacturers make this harder to find than it should be, but it’s there. Opting out won’t affect core vehicle functionality in most cases. And stay across what the ICO is doing in this space. Their connected vehicle guidance is not perfect, but it’s a start, and it does give you a basis for asking manufacturers directly what data they hold on you and requesting its deletion under UK GDPR Article 17.
The OBD port isn’t the enemy. It’s one of the most useful tools in a car enthusiast’s kit, and OBD-II data logging done on your own terms gives you insight into your build that nothing else can match. The issue is the data that leaves your control without you realising it. Know what’s being recorded, know where it goes, and make deliberate choices. That’s all.
Frequently Asked Questions
Can my insurer access my car's OBD-II data without my knowledge?
If you have a telematics (black-box) policy, your insurer has agreed access to driving data, often via a physical device plugged into the OBD port or a manufacturer data-sharing agreement. Without a telematics policy, they cannot access it directly, but they may request ECU data as part of a claim investigation, particularly if there’s a dispute about vehicle spec or driver behaviour.
Does remapping my car show up in OBD data?
Yes. A remap changes fuelling, boost, and torque parameters inside the ECU, and those values are visible to anyone reading the OBD data stream. A telematics insurer or a manufacturer’s connected services system can log outputs that don’t match factory spec, which can cause problems if you haven’t declared the modification to your insurer.
Are Bluetooth OBD dongles safe to leave plugged in permanently?
From a vehicle security standpoint, a permanently connected Bluetooth OBD dongle is a potential attack vector, someone nearby could attempt to pair and read data. More practically, the apps those dongles feed data into often have data-sharing policies that aren’t immediately obvious. It’s worth unplugging when you don’t need it and reading the privacy policy of any app you use.
Which UK car manufacturers collect and share the most driving data?
Most major manufacturers active in the UK, including Volkswagen Group, BMW, Ford, and Stellantis brands, collect telemetry through their connected services platforms. The extent of data sharing with third parties varies and is detailed in each manufacturer’s privacy policy. The ICO published connected vehicle guidance in 2025 that’s worth reading if you want to understand your rights.