← ALL WRITING
DILIGENCE

KADOE explained: DVLA keeper data, audits and what a buyer checks

Every postal parking charge on private land starts with a £2.50 request to the DVLA. How that access works, who audits it, what gets it suspended and how the 2026 code changes it, with the checks a buyer should run before trusting a parking operator's revenue.

WRITTEN
READINGThirteen minutes
FORDeal teams, operating partners, parking operators, landowners and motorists

KADOE (Keeper at Date of Event) is the DVLA's electronic service that releases the name and address of a vehicle's registered keeper on a given date. Private parking operators use it to send parking charges to drivers they could not ticket on site, paying £2.50 a record, and they can only get access through membership of an accredited trade association: the British Parking Association (BPA) or the International Parking Community (IPC). Parking companies made 16.9 million fee-paying KADOE requests in 2025/26, and the Government Internal Audit Agency rates around 40% of the operators it audits as red. From 2027, access will also depend on certification under the government's private parking code.

A parking operator without KADOE access is a business with a sign and a camera and no way to send a bill. That makes the data access the most important asset in most ANPR operators, and the one least often diligenced properly. This piece sits under our parking technology due diligence guide, which covers the wider sector. Here I go deeper on the access itself: the law, the money, the audits, the triggers for suspension and the evidence a buyer should demand.

A parking operator without KADOE access is a business with a sign and a camera and no way to send a bill.

What is KADOE and what is the legal basis?

The DVLA's power to release keeper data comes from regulation 27 of the Road Vehicles (Registration and Licensing) Regulations 2002. Regulation 27(1)(e) lets the Secretary of State release register particulars "by any person who can show to the satisfaction of the Secretary of State that he has reasonable cause for wanting the particulars to be made available to him", and regulation 27(2) allows a fee. Pursuing an unpaid parking charge on private land is accepted as reasonable cause. KADOE is the bulk electronic channel for those requests.

Three other pieces of law make the system work:

  • Keeper liability. Schedule 4 of the Protection of Freedoms Act 2012 lets a creditor recover an unpaid charge from the keeper when it does not know the driver, if strict notice conditions are met. For a postal notice with no windscreen ticket, paragraph 9 requires delivery within 14 days of the end of the parking. It applies in England and Wales only.
  • The 2019 Act. Section 5 of the Parking (Code of Practice) Act 2019 says the Secretary of State must have regard to a failure to follow the parking code when deciding whether to disclose keeper data under regulation 27, and whether an association should stay accredited.
  • Contract. Each operator signs a KADOE contract with the DVLA. The most recent version published on GOV.UK, the fee-paying contract for parking companies (version 4.0, 2014), sets out reasonable cause, security, retention, audit, suspension and termination. The DVLA may have updated it since; a buyer should ask for the version the target actually signed.

Can parking companies get my details?

Yes, if three things are true: the company is a member in good standing of the BPA or IPC, it holds a KADOE contract with the DVLA, and the request relates to a parking event on private land where it has reasonable cause to pursue a charge. The DVLA releases the keeper's name and address as held on the date of the event, not today's.

What a motorist can do is limited but real. The data can be used only to pursue that parking charge. If an operator requests data with no genuine event, sends a notice outside the Schedule 4 timescales while implying keeper liability, or passes data to a debt collector without the safeguards the contract requires, those are breaches. The association, the DVLA and the ICO are the routes. Under the Sector Single Code, "repeatedly making requests for registered keeper details when there is no reasonable cause" is a Level 2 breach and "misuse of keeper data" Level 3.

Who can access KADOE and what does it cost?

KADOE has two customer types. The DVLA's published KADOE volumes distinguish "KADOE Fee" customers, who show reasonable cause and pay £2.50 per enquiry, from "KADOE Non-Fee" customers who need data to investigate offences or civil parking contraventions: councils, enforcement agents, toll roads and government bodies. Parking companies are fee customers.

The access requirements, from the published contract and the codes:

Requirement Source
Membership of a DVLA-accredited trade association (BPA or IPC), held at all times KADOE contract A6.1
Tell the DVLA immediately if membership or approved operator status is suspended or ended KADOE contract A6.2
A probationary period of 26 weeks with at least 300 valid manual requests before electronic access KADOE contract definitions
Request only where there is reasonable cause, with evidence to show it KADOE contract B and D clauses
Vetting, training and disciplinary policies for every person with access KADOE contract D7
Annual internal compliance check reported to the DVLA within 28 days KADOE contract D8.2
Prior written DVLA agreement to any change of control KADOE contract H3.1
From 2027, a valid certificate of conformity under the government's certification scheme 2026 code, introduction

Many operators connect through a link provider, a software firm that runs the secure connection. The DVLA spreadsheet shows this: some operators appear twice, once directly and once "via" a back-office vendor, because each link is listed separately.

The fee looks trivial and isn't. At £2.50, the 16.9 million parking requests in 2025/26 cost operators about £42 million (my arithmetic). For an operator issuing a postal charge with a 40% discount, the request is about 4% of the £60 most drivers pay, and it is spent whether or not the charge is ever collected.

How many KADOE requests do parking companies make?

The DVLA publishes request volumes by company, month and customer type. Filtering for fee-paying car parking management customers gives this series, which matches the PA and RAC Foundation analysis reported by the RAC in August 2026:

Year Parking keeper requests Change
2018/19 6.8m
2019/20 8.4m +24%
2020/21 4.4m pandemic
2021/22 8.6m
2022/23 11.1m +29%
2023/24 12.8m +16%
2024/25 14.4m +12%
2025/26 16.9m +17%

Two cautions. A request is not a ticket: a windscreen notice paid within days never generates one, and the DVLA notes volumes count enquiries, including repeat enquiries on the same vehicle. And growth is partly structural. The government's impact assessment cites BPA data that ANPR-managed sites rose 80% between 2018 and 2022, and more camera sites mean more postal charges.

The market is concentrated at the top and long at the bottom. By my count of the DVLA's 2025/26 file, grouping multiple links under one company, about 170 parking companies made fee-paying requests. The five largest (ParkingEye, APCOA, Euro Car Parks, Horizon Parking and Smart Parking) made about 52% of requests, and the top ten about 70%. Roughly two-thirds of companies made fewer than 20,000 requests in the year. The impact assessment's figure, from the BPA, is that the five largest made around 55% of requests in 2023. Movements within the top group can be large: APCOA's requests rose from 0.96 million in 2024/25 to 2.26 million in 2025/26. A movement like that is exactly what a buyer should be able to explain from contracts and site lists.

What do the KADOE audits find?

The DVLA uses the Government Internal Audit Agency (GIAA) to audit KADOE customers. RAC analysis of FOI data published on 19 October 2026 describes what the audits test: whether there is a lawful basis for requests, whether data is used only for parking enforcement, retention and disposal, security, alignment with the industry code, sample charges and the evidence behind each request, ANPR controls, staff access, complaint handling, audit trails, and third-party processors such as debt recovery agents.

The results are poor, though the RAC has published two different bases. Its news article says 90 companies were audited in 2024/25, with 36 (40%) rated red, 11 (12%) amber and 43 (48%) green. Its press release of the same date says 57 were audited in 2025/26, with 23 (40%) red, 5 (9%) amber and 29 (51%) green. Both agree on the number that matters: four in ten audited operators had "significant weaknesses or serious compliance concerns". GIAA describes its ratings as a point-in-time assessment.

Repeat failure is the more telling finding. The RAC names three companies rated red four or more times since 2015, and one large operator rated red in each of its three audits. A single red can be a bad year. A pattern of reds is a control environment.

What triggers a KADOE suspension?

There are three routes to losing access, and a buyer needs to understand all of them.

The DVLA directly. Under clause J3 of the published contract, if the DVLA becomes aware of "any Default", it "may suspend the KADOE Service without further notice and with immediate effect" while it investigates. Resumption can require assurances, specified actions, a re-inspection and a reconnection fee. Three or more defaults of any size, a material breach not fixed within 26 weeks, or a failure to co-operate during suspension allow termination. Insolvency events allow immediate suspension. Public examples are rare because the DVLA rarely comments; in 2018 it suspended UK Parking Control's access while it investigated concerns, saying only that it would be inappropriate to comment further.

The trade association. Membership is a condition of access, so an association suspension stops requests. Annex H of the Sector Single Code sets a points system:

Level Starting points Examples
1 2 (range 1 to 3) Wrong grace or consideration periods, non-compliant signs, missed appeal deadlines, using a non-member debt collector
2 5 (range 2 to 8) Repeated Level 1 breaches, repeated requests without reasonable cause, requesting data for periods where requests are not permitted
3 9 (range 6 to 12) Misuse of keeper data, misleading terminology, incentives for issuing more charges, enforcing on a site with no signs
4 Suspension or expulsion Sustained or intentional misuse of DVLA data, predatory tactics, fraud, unlawful clamping

Twelve points in one go, or within a rolling 12 months, means suspension: at least 14 days, or 28 if there was a suspension in the previous year. The associations must tell the DVLA immediately of any suspension, expulsion or sanction points.

Certification, from 2027. Under the Private Parking Certification Scheme, a conformity assessment body can suspend a single site or the whole certificate. Minor non-conformities must be fixed within six weeks and major ones within four, failing which suspension follows. During suspension the operator may not issue charges, or issue them later for events that happened during the suspension. Repeating the same non-conformity more than twice in a three-year cycle leads to termination, with at least six months before reapplying, and the assessment body must notify the association and the DVLA within 24 hours.

How does the 2026 code change KADOE access?

The private parking code of practice 2026, laid before Parliament on 20 October 2026 and due in force in December, does not change regulation 27. It changes who decides whether an operator is fit to use it. The code says an accredited parking association "may only admit organisations with a valid Certificate of Conformity" from a UKAS-accredited body. So the chain becomes: certificate, then association membership, then DVLA access.

Four practical changes follow. Debt recovery agents must be full association members, and those collecting in-house need the scheme's debt recovery module. Third parties that request keeper data on an operator's behalf fall within the module for issuing charges. Certified organisations must notify their assessment body of ownership changes. And sampling becomes systematic: every certified operator is audited each year, with 10 to 30 charges and their evidence tested depending on size.

The timing has a gap. The government expects UKAS to take until around April 2027 to evaluate assessment bodies, and until then the associations keep their existing sanctions, "with the ultimate sanction being the loss of access to DVLA data". An operator buying another in early 2027 will face the old regime for completion and the new one for its first certification, possibly within months.

What are the data-protection duties?

An operator is a data controller for keeper data from the moment it arrives. The published KADOE contract and the codes stack up as follows:

  • Purpose. Data may be used only for the reasonable cause it was released for: pursuing that charge.
  • Disclosure. Only to a processor or debt collector under a written contract imposing the DVLA's security schedule, or with the DVLA's prior written consent (contract D5).
  • Retention. Each item kept only as long as necessary, then securely destroyed; the evidence of compliance kept for two years from the request, including mismatched or incorrect enquiries cross-referenced to the correct one (contract D6).
  • Security and staff. Minimum security requirements, vetting and training for everyone with access, and the DVLA's right to bar individuals (contract D7 and D11).
  • Incidents. Any loss or misuse notified to the DVLA immediately (contract D10), alongside the 72-hour breach reporting duty to the ICO under UK GDPR where it applies.
  • Inspection. The DVLA may inspect at any time, normally on seven days' notice, and check the electronic trail of any request (contract D11).
  • Code records. Charges, appeals and complaints kept for 36 months under the 2026 code, with personal details removed from complaint records once resolved.

The retention rules pull in different directions. The ICO expects reads of compliant vehicles to be deleted quickly, the DVLA expects keeper data kept no longer than needed, and the code wants three years of charge and appeal records. A back office that cannot separate personal data from aggregate records, and delete one while keeping the other, will fail someone's audit.

What should a buyer check in KADOE due diligence?

This is the list I'd run in technical due diligence on any operator whose revenue depends on postal charges. Most of it can be tested in a week if the data exists. If it doesn't, that is the finding.

Check What to request Red flag
Audit history Every GIAA and DVLA audit report since 2018, the action plans and evidence each action was closed Only a summary; a red rating with open actions; repeat reds
Suspensions Written confirmation of any DVLA, association or site suspension, with dates. Cross-check the target's monthly rows in the DVLA's public KADOE spreadsheet for unexplained months at zero Gaps that management cannot explain
Association standing Membership certificate, sanction points history, correspondence with the BPA or IPC Points accumulating towards 12 in a rolling year
DVLA contract The KADOE contract actually signed, the link provider agreement, and the DVLA's position on change of control No plan for DVLA consent before completion
Certification plan Which modules, which assessment body, mock audit results, gap analysis against the 2026 code "Our association says we're fine"
Volume concentration Requests and charges by site, landowner and contravention type, reconciled to the DVLA's published monthly totals A few sites or one landowner driving most requests; volumes rising faster than sites
Error rates Mismatched enquiries, requests with no notice sent, notices outside the 14-day window, first-stage cancellations for "issued incorrectly" No coded data; high cancellations at specific sites
Evidence chain Ten random charges traced live from camera read to payment or closure Any break in the chain below
Access control List of named users with KADOE access, how credentials are issued and revoked, the audit log by user Shared logins, leavers still active, requests from outside the back office
Processors Contracts with debt recovery agents, mail consolidators and back-office vendors Data passed on without the DVLA's required terms

The evidence chain is the heart of it, because it is what GIAA samples and what conformity assessment bodies will sample:

  1. Read. Entry and exit images with accurate, synchronised timestamps and a clear plate, from a camera with a maintenance log.
  2. Match. Sessions, permits and payments from every channel checked, consideration and grace periods applied, keying errors tested against vehicles on site.
  3. Manual check. A named person reviews the images and match before any request, with the record kept.
  4. Request. A KADOE enquiry tied to that one event, with reasonable cause recorded.
  5. Notice. Posted, not just generated, within the 14-day window, with the posting date recorded.
  6. Appeal and payment. Outcome coded against the Appeals Charter and linked back to the event.
  7. Debt recovery. Hand-off to a member agent under a compliant contract, with the data trail intact.
  8. Retention. Keeper data deleted when no longer needed; aggregate records kept for 36 months.

Ask for the request-to-notice ratio by month. If an operator requests far more keeper records than it sends notices, either its matching runs after the request, which means requesting data it had no cause for, or its posting fails. Both are audit findings.

People risk matters too. In smaller operators, one developer or operations manager often holds the DVLA integration, the link provider relationship and the knowledge of how requests are triggered. Our piece on key-person risk in due diligence covers how to test that, and the technology due diligence checklist covers access control and security in general.

For sellers, the same list is the preparation. A clean audit history, coded data and a certificate in hand before a process are worth more than any adjustment argued later; a vendor technical due diligence report is the way to show it.

If you are buying, investing in or running a parking business and want KADOE access tested properly, we do it as part of technical due diligence for parking operators, alongside the wider work in our parking sector guide.

FREE RESOURCE · PDF + XLSX
The state of UK parking technology 2026
DOWNLOAD FREE →

Questions

Can I stop the DVLA giving my details to a private parking company?

Usually not. If an operator in an accredited trade association requests your details for a parking event on private land, the DVLA treats pursuing an unpaid parking charge as reasonable cause and releases them. The DVLA's KADOE contract allows some records to be marked unavailable for electronic release for personal or domestic reasons, but that is exceptional. If you think your data was requested or used wrongly, complain to the operator, its association and the DVLA, and to the ICO if it is not resolved.

How long can a parking company keep DVLA keeper data?

The published DVLA KADOE contract says each item of keeper data may be kept only for as long as necessary for the purpose it was released for, then securely destroyed, while the evidence showing compliance with the contract must be kept for two years from the request. Separately, the 2026 code requires operators to keep records of charges, appeals and complaints for 36 months. Personal details should be stripped from complaint records once a complaint is resolved.

How quickly must a parking company send a notice to the registered keeper?

For a postal notice relying on keeper liability under Schedule 4 of the Protection of Freedoms Act 2012, where no windscreen ticket was issued, the notice must be delivered within 14 days beginning with the day after the parking ended. A posted notice is presumed delivered on the second working day after posting. That is why ANPR operators request keeper data within days of the event: a slow evidence chain loses the right to pursue the keeper, not just the driver.

What is the difference between KADOE fee and KADOE non-fee?

KADOE fee customers are organisations that show reasonable cause and pay £2.50 per enquiry, mainly private parking operators but also finance houses, insurers and solicitors. KADOE non-fee customers get keeper data free for investigating offences or civil parking contraventions: councils, enforcement agents, toll roads and government bodies. In 2025/26 parking companies made about 16.9 million of the 52.4 million KADOE enquiries, by my count of the DVLA's published data.

Does KADOE work for car parks in Scotland?

The DVLA register covers Great Britain, so a Scottish operator can request keeper data in the same way. The difference is what it can do next. Keeper liability under Schedule 4 of the Protection of Freedoms Act 2012 applies only in England and Wales, so in Scotland the operator has to pursue the driver and the keeper is not automatically liable. The 2026 code does apply in Scotland, so the same compliance and certification rules govern access.

Brannan Coady, founder of Anyway Ventures
Brannan Coady
Founder of Anyway Ventures. Exited founder, former CEO of YourParkingSpace, investor and board member; now building AI inside PE-backed and mid-market businesses. More →

Keep reading

ALL WRITING →
DILIGENCE · 10 MIN
Technology due diligence checklist for private equity deals
Every tech DD checklist covers the same ground. The useful ones say which answers should change the price, the structure or the first 100 days.
DILIGENCE · 9 MIN
Key person risk in due diligence: would the product survive the CTO?
How to tell whether a software business survives its CTO or lead engineer leaving, the evidence to ask for, and how to price and mitigate what you find.
EXIT · 10 MIN
Vendor technical due diligence: what to fix before a sale
A sell-side technology review run early gives the seller time to fix the cheap problems and cost the expensive ones. Here is what a VDD report is, who relies on it, and the fix list in the order I'd tackle it.

Talk about this piece.

The first conversation is free and takes under an hour. If there's an engagement worth having you'll leave knowing its shape and its price. If there isn't, I'll say so.

Book 30 minutes brannan@anywayventures.com