Author Topic: Parking Eye PCN - parking in England, keeper lives in Scotland - & possible non-compliance with POFA Sch 4  (Read 672 times)

0 Members and 0 Guests are viewing this topic.

b789

  • Hero Member
  • *****
  • Posts: 4868
  • Karma: +208/-5
    • View Profile
    • GullibleTree
You will have to log your complaint using the BPA webform. However, you can upload your complaint as a PDF or just enter it into their webform:

https://portal.britishparking.co.uk/compliance/LogComplaint

Quote
Subject: Formal Complaint Against ParkingEye Ltd – Breach of PPSCoP and Improper Handling of Appeal and Complaint

To: aos@britishparking.co.uk

Date: [Insert date]

Dear BPA Compliance Team,

Re: ParkingEye Ltd – Breach of PPSCoP Sections 8.4.1, 11.3 and Improper Use of Data in Scotland

I write to raise a formal complaint regarding the conduct of ParkingEye Ltd, an Approved Operator Scheme (AOS) member, in connection with a Parking Charge Notice (PCN) issued to me as the registered keeper of a vehicle. I reside in Scotland and have no contractual relationship with ParkingEye.

On 19 February 2025, I submitted an appeal to ParkingEye via their online portal. The appeal raised fundamental concerns, including that:

• I am the keeper of the vehicle and reside in Scotland;
• The Protection of Freedoms Act 2012 (PoFA), Schedule 4, does not apply in Scotland;
• ParkingEye’s Notice to Keeper (NtK) was in breach of PPSCoP section 8.1.1(d), as it contained a PoFA warning despite being issued to a Scottish address;
• I denied any liability and expressly stated there would be no identification of the driver.

Despite the clear and concise nature of the appeal, ParkingEye failed to issue any response within the mandatory 28-day period set out in section 8.4.1 of the Private Parking Single Code of Practice (Version 1.1, February 2025).

On 6 March 2025, I submitted a formal complaint through their web portal to raise this non-compliance. I received no acknowledgment within 14 days, in breach of section 11.3.1, and no substantive response within 28 days.

Instead, after I chased the matter, ParkingEye issued an email refusing to process my complaint unless I explicitly agreed to their Privacy Policy and Complaints Policy. Their justification was that, although I clicked mandatory checkboxes to allow submission, I included a written statement making clear I did not agree to those policies and clicked only to bypass the software restriction.

ParkingEye's refusal to process my complaint on this basis is indefensible. It is a clear attempt to obstruct a formal complaint by conflating acknowledgment with consent, despite their obligations as a data controller under UK GDPR and as a BPA member under the PPSCoP.

Furthermore, their insistence that they will delete my complaint correspondence due to my objection to their policies raises serious data governance concerns and undermines the regulatory complaints process.

Breaches Identified:

• PPSCoP 8.1.1(d) – Issuing an NtK with a PoFA warning to a keeper in Scotland, where PoFA does not apply.
• PPSCoP 8.4.1 – Failure to respond to a keeper appeal within 28 days.
• PPSCoP 11.3 – Failure to acknowledge and respond to a formal complaint within 14 and 28 days respectively.
• Improper conditional processing – Refusing to handle complaints unless individuals agree to policies which they may lawfully contest or object to.

Requested action:

I request that the BPA:

• Investigate this matter as a serious breach of the PPSCoP;
• Require ParkingEye to respond to the original appeal and formal complaint;
• Review the legality and fairness of ParkingEye’s practice of rejecting complaints unless “consent” is provided under duress;
• Remind ParkingEye of their obligations under the PPSCoP and the principles of the UK GDPR.

Please confirm receipt of this complaint and advise me of the steps that will now be taken.

Yours faithfully,

[Your Full Name]
[Your Address]
[Your Email Address]
Keeper of Vehicle Registration: [Insert VRM]
PCN Reference: [Insert PCN number, if available]
Never argue with stupid people. They will drag you down to their level and then beat you with experience” - Mark Twain
Like Like x 1 View List

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
@b789 - Thanks a million for this. I have now submitted this complaint to the BPA and received their acknowledgement.

This is what I sent them through their website (on a pdf).

I will report back here on any developments.

Carrie

Quote
Complaint Against ParkingEye Ltd – Breach of PPSCoP and Improper Handling of Appeal and Complaint

Dear BPA Compliance Team,

Re: ParkingEye Ltd – Breach of PPSCoP Sections 8.4.1, 11.3 and Improper Use of Data in Scotland

I write to raise a formal complaint regarding the conduct of ParkingEye Ltd, an Approved Operator Scheme (AOS) member, in connection with a Parking Charge Notice (PCN) issued to me as the registered keeper of a vehicle. I reside in Scotland and have no contractual relationship with ParkingEye.

On 19 February 2025, I submitted an appeal to ParkingEye via their online portal. The appeal raised fundamental concerns, including that:
• I am the keeper of the vehicle and reside in Scotland;
• The Protection of Freedoms Act 2012 (PoFA), Schedule 4, does not apply in Scotland;
• ParkingEye’s Notice to Keeper (NtK) was in breach of PPSCoP section 8.1.1(d), as it contained a PoFA    warning despite being issued to a Scottish address;
• I denied liability and expressly stated that there would be no identification of the driver.

Despite the clear and concise nature of the appeal, ParkingEye failed to issue a substantive response within the 28-day period mandated in section 8.4.1 of the Private Parking Single Code of Practice (Version 1.1, Feb 2025).

On 6 March 2025, I submitted a formal complaint through their web portal to raise this non-compliance. I received no substantive response within 28 days.

Instead, after I chased the matter, ParkingEye issued an email refusing to process my complaint unless I explicitly agreed to their Privacy Policy and Complaints Policy. Their justification was that, although I clicked mandatory checkboxes to allow submission, I included a written statement making clear I did not agree to those policies and clicked only to bypass the software restriction.

ParkingEye's refusal to process my complaint on this basis is indefensible. It is a clear attempt to obstruct a formal complaint by conflating acknowledgment with consent, despite their obligations as a data controller under UK GDPR and as a BPA member under the PPSCoP.

Furthermore, their insistence that they will delete my complaint correspondence due to my objection to their policies raises serious data governance concerns and undermines the regulatory complaints process.

Breaches Identified:
• PPSCoP 8.1.1(d) – Issuing an NtK with a PoFA warning to a keeper in Scotland, where PoFA does not apply.
• PPSCoP 8.4.1 – Failure to respond to a keeper appeal within 28 days.
• PPSCoP 11.3 – Failure to acknowledge and respond to a formal complaint within 14 and 28 days respectively.
• Improper conditional processing – Refusing to handle complaints unless individuals agree to policies which they may lawfully contest or object to.

Requested action:

I request that the BPA:
• Investigate this matter as a serious breach of the PPSCoP;
• Require ParkingEye to respond to the original appeal and formal complaint;
• Review the legality and fairness of ParkingEye’s practice of rejecting complaints unless “consent” is provided under duress;
• Remind ParkingEye of their obligations under the PPSCoP and the principles of the UK GDPR.

Please confirm receipt of this complaint and advise me of the steps that will now be taken.

Yours faithfully,

***
Address: ***
Keeper of Vehicle Registration ***


Like Like x 1 View List

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
I have now had a reply from a "Data Customer Auditor" at the DVLA, who has clearly mostly cut and pasted an all-purpose text written by a self-regarding finger-wagger. The only place she addresses my actual complaint, which was with reference to keeper registration being outside the English jurisdiction, is when she writes:

"PoFA is based on the laws of the location where the Parking Charge Notice was
issued, which in this case is England, where PoFA applies. Therefore, ParkingEye
can utilise PoFA in this situation.
"

and

"(a)s the registered keeper of the vehicle, you are responsible for the PCN and the PCN remains outstanding."

Any advice on how I can escalate to the DVLA's "Step Two"?

Here is the whole of what they sent me:

Quote
Dear [***]

Thank you for your correspondence of 29th March about the release of information
from the Driver and Vehicle Licensing Agency’s (DVLA) vehicle register. I have been
asked to formally review your case at Step 1 of our complaints procedure.

The DVLA takes the protection and security of its data very seriously and has
procedures in place to ensure data is disclosed only where it is lawful and fair to do
so and where the provisions of the Data Protection Law are met. The Agency must
strike a balance between ensuring the privacy of motorists is respected while
enabling those who may have suffered loss or damage to seek redress.

Drivers choosing to park a vehicle on private land do so subject to the terms and
conditions set out on signage in the car park. The need to contact individuals who
may not have complied with these conditions is, in most circumstances, considered
to be a reasonable cause. Data is provided by the DVLA to enable landowners or
their agents to pursue their legal rights and to address disputes. I hope you can
appreciate that if this were not the case, motorists would be able to park with
disregard for the conditions applying with little prospect of being held accountable.

I have investigated the matter with ParkingEye who made the request to the DVLA
for the registered keeper details for Vehicle Registration Number [***]. I have
had sight of their supporting evidence to show that they had reasonable cause to
make their request. The Parking Charge Notice (PCN) was issued as the signage at
the site states tariffs applies after 2 hours and the vehicle remained in the car park
for 2 hours and 34 minutes. ParkingEye have advised that they received an appeal
stating that you would not identify the driver of the vehicle at the time, and they have
responded to you on 5th March. As the registered keeper of the vehicle, you are
responsible for the PCN and the PCN remains outstanding.

PoFA is based on the laws of the location where the Parking Charge Notice was
issued, which in this case is England, where PoFA applies. Therefore, ParkingEye
can utilise PoFA in this situation.

To help ensure motorists are treated fairly when any private parking charge is
pursued the DVLA discloses vehicle keeper information only to companies that are
members of an appropriate Accredited Trade Association (ATA). The purpose of
requiring a company to be a member of an ATA is to ensure that those who request
DVLA information are legitimate companies that operate within a code of practice
that promotes fair treatment of the motorist and ensures that there is a clear set of
standards for operators.

The company in question, ParkingEye, are a member of the British Parking
Association (BPA) which is an Accredited Trade Association for the parking industry.
The BPA’s code of practice is published on its website at
http://www.britishparking.co.uk under the heading “Approved Operators Scheme”. If
a member of this scheme does not comply with the code of practice, it may be
suspended or expelled, during which time no data will be provided to it by the
DVLA. If you feel that any of the practices used by the company do not comply with
the BPA’s code of practice, you may wish to contact the BPA via email at
https://portal.britishparking.co.uk/compliance/LogComplaint or by post at Chelsea
House, 8-14 The Broadway, Haywards Heath, West Sussex RH16 3AH.

We have fully considered all the information available. If you feel that your complaint
has not been resolved, you can request escalation of your complaint to Step 2 of the
complaints process. Further options about our complaint procedure can be found
online at www.gov.uk/dvla/complaints.

Yours sincerely
[***]
Data Customer Auditor
Data Assurance Team/Information & Assurance Group

b789

  • Hero Member
  • *****
  • Posts: 4868
  • Karma: +208/-5
    • View Profile
    • GullibleTree
When escalating to Step Two. use this link, not the one provided in their letter: https://contact.dvla.gov.uk/head-of-complaints which goes to their "head of complaints".

To escalate your complaint to Step Two of the DVLA's complaints procedure effectively, you should focus on three main points:

1. The DVLA response failed to address your actual complaint – namely, the misuse of personal data following its release, not the lawfulness of the initial request.
2. The DVLA’s interpretation of PoFA applicability is legally flawed — PoFA cannot impose keeper liability on someone domiciled in Scotland, even if the alleged contravention occurred in England.
3. The DVLA has wrongly stated that the keeper is liable, when this is a matter for the courts, not the Agency.

Here is a suggested draft for your Step Two escalation:

Quote
Subject: DVLA Complaint Step Two – ParkingEye Misuse of Keeper Data / Breach of KADOE and PPSCoP

Dear DVLA Complaints Team,

I am writing to escalate my complaint to Step Two of the DVLA's formal complaints procedure, as your Step One response failed to address the core issue raised in my original complaint dated 29 March 2025.

This complaint is not about whether ParkingEye had reasonable cause to access my data at the time of the KADOE request. My complaint clearly states that the breach relates to the subsequent misuse of my personal data, in breach of the Private Parking Single Code of Practice (PPSCoP) and ParkingEye’s KADOE contract.

1. PoFA Does Not Apply to Keepers Domiciled in Scotland

Your Step One response inaccurately claimed:

“PoFA is based on the laws of the location where the Parking Charge Notice was issued, which in this case is England, where PoFA applies. Therefore, ParkingEye can utilise PoFA in this situation.”

This is incorrect. The Protection of Freedoms Act 2012 (PoFA), Schedule 4, only permits keeper liability where the parking event occurred on relevant land in England or Wales, and where the registered keeper is domiciled in England or Wales. It does not confer jurisdiction over Scottish residents, and any attempt to assert keeper liability under PoFA against a Scottish keeper is legally defective.

ParkingEye’s Notice to Keeper and subsequent correspondence contained false and misleading statements asserting PoFA liability against a Scottish resident. This is in breach of Section 8.1.1(d) of the PPSCoP, which prohibits operators from implying PoFA liability where it does not apply. Once ParkingEye became aware from the DVLA data that I reside in Scotland, they had an obligation to cease relying on PoFA.

2. Misuse of Data and Breach of KADOE Contract

The DVLA is the data controller for keeper data released under KADOE. Your own framework confirms that data must be used in accordance with the applicable Code of Practice. Where a KADOE recipient issues documentation in breach of the PPSCoP, and continues to misuse the data contrary to the purpose for which it was released, this becomes unlawful processing under UK GDPR and DPA 2018.

ParkingEye’s breach is not minor or technical. It constitutes:

• A breach of Section 8.1.1(d) of the PPSCoP;
• A breach of their KADOE contract;
Misleading processing of my personal data with no legal basis;
• A potential breach of Consumer Protection from Unfair Trading Regulations (CPUTR) 2008.

The DVLA has a statutory responsibility to investigate and sanction such misuse, including through suspension or termination of KADOE access where warranted.

3. Incorrect Assertion of Liability

Your Step One response stated:

“As the registered keeper of the vehicle, you are responsible for the PCN and the PCN remains outstanding.”

This is an entirely inappropriate and inaccurate assertion. Whether I am legally liable is a matter for the courts. It is not within the remit of the DVLA to declare legal liability for a private contractual claim.

I request a proper investigation into the actual issues raised, namely:

• ParkingEye’s breach of the PPSCoP;
• Their continued use of PoFA language in communications to a Scottish keeper;
• The unlawful use of DVLA data in light of these breaches;
• What enforcement action the DVLA will take against ParkingEye under the KADOE framework.

Please confirm this complaint is now under Step Two of the formal DVLA complaints process and provide a reference.

Yours sincerely,

[Your Name]
[Date]
Never argue with stupid people. They will drag you down to their level and then beat you with experience” - Mark Twain
Like Like x 1 View List

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
Thanks again.
I have now submitted the following using the "Head of Complaints" link you suggested:

Quote
Ref: Complaint [***]
Car reg. no. [***]

Dear DVLA Complaints Team,

DVLA Complaint Step Two -- ParkingEye Misuse of Keeper Data / Breach of KADOE and PPSCoP

I am writing to escalate my complaint to Step Two of the DVLA's formal complaints procedure, as your Step One response issued on 9 April 2025 failed to address the core issue raised in my complaint dated 29 March 2025.

This complaint is not about whether ParkingEye had reasonable cause to access my data at the time of the KADOE request. My complaint clearly states that the breach relates to the subsequent misuse of my personal data, in breach of the Private Parking Single Code of Practice (PPSCoP) and ParkingEye’s KADOE contract.

1. PoFA Does Not Apply to Keepers Domiciled in Scotland

Your Step One response inaccurately claimed:

“PoFA is based on the laws of the location where the Parking Charge Notice was issued, which in this case is England, where PoFA applies. Therefore, ParkingEye can utilise PoFA in this situation.”

This is incorrect. The Protection of Freedoms Act 2012 (PoFA), Schedule 4, only permits keeper liability where the parking event occurred on relevant land in England or Wales and where the registered keeper is also domiciled in England or Wales. It does not confer jurisdiction over keepers residing in Scotland, and any attempt to assert keeper liability under PoFA against a keeper resident in Scotland is legally defective.

ParkingEye’s Notice to Keeper and subsequent correspondence contained false and misleading statements asserting PoFA liability against a Scottish resident. This is in breach of Section 8.1.1(d) of the PPSCoP, which prohibits operators from implying PoFA liability where it does not apply. Once ParkingEye became aware from the DVLA data that I reside in Scotland, they had an obligation to cease relying on PoFA.

2. Misuse of Data and Breach of KADOE Contract

The DVLA is the data controller for keeper data released under KADOE. Your own framework confirms that data must be used in accordance with the applicable Code of Practice. Where a KADOE recipient issues documentation in breach of the PPSCoP, and continues to misuse the data contrary to the purpose for which it was released, this becomes unlawful processing under UK GDPR and DPA 2018.

ParkingEye’s breach is not minor or technical. It constitutes:

* A breach of Section 8.1.1(d) of the PPSCoP;
* A breach of their KADOE contract;
* Misleading processing of my personal data with no legal basis;
* A potential breach of Consumer Protection from Unfair Trading Regulations (CPUTR) 2008.

The DVLA has a statutory responsibility to investigate and sanction such misuse, including through suspension or termination of KADOE access where warranted.

3. Incorrect Assertion of Liability

Your Step One response stated:

“As the registered keeper of the vehicle, you are responsible for the PCN and the PCN remains outstanding.”

This is an entirely inappropriate and inaccurate assertion. Whether I am legally liable is a matter for the courts. It is not within the remit of the DVLA to declare legal liability for a private contractual claim.

I request a proper investigation into the actual issues raised, namely:

* ParkingEye’s breach of the PPSCoP;
* Their continued use of PoFA language in communications to a keeper registered and resident in Scotland;
* The unlawful use of DVLA data in light of these breaches;
* What enforcement action the DVLA will take against ParkingEye under the KADOE framework.

Please confirm this complaint is now under Step Two of the formal DVLA complaints process and provide a reference.

Yours sincerely,

[***]
9 April 2025
Like Like x 1 View List

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
I have been thinking about this bit. The DVLA person stated:

Quote
"ParkingEye have advised that they received an appeal stating that you would not identify the driver of the vehicle at the time"

Might Parking Eye have broken data protection law by telling the DVLA that I said I would not identify the driver?

I realise that since I am arguing for the non-applicability of keeper liability outside of the England and Wales jurisdiction it may be obvious that I'm not identifying the driver, but Parking Eye seem to have told an agency not involved in the dispute that I made such-a-such a statement in my appeal.
« Last Edit: April 10, 2025, 01:13:50 pm by carriep »

b789

  • Hero Member
  • *****
  • Posts: 4868
  • Karma: +208/-5
    • View Profile
    • GullibleTree
Never argue with stupid people. They will drag you down to their level and then beat you with experience” - Mark Twain

b789

  • Hero Member
  • *****
  • Posts: 4868
  • Karma: +208/-5
    • View Profile
    • GullibleTree
There is a credible argument that ParkingEye may have breached data protection principles by disclosing the content of your appeal to the DVLA without a lawful basis.

While the DVLA is the data controller for the keeper data it provides under the KADOE contract, it is not a party to the dispute between you and the private parking operator, nor is it an adjudicator or regulator of dispute content. Disclosing information from your appeal to the DVLA probably constitutes unlawful further processing under UK GDPR, particularly if the content of your message was not necessary or proportionate to the DVLA’s inquiry.

Key issues to consider:

there is a credible argument that ParkingEye may have breached data protection principles by disclosing the content of your appeal to the DVLA without a lawful basis.

While the DVLA is the data controller for the keeper data it provides under the KADOE contract, it is not a party to the dispute between you and the private parking operator, nor is it an adjudicator or regulator of dispute content. Disclosing information from your appeal to the DVLA may constitute unlawful further processing under UK GDPR, particularly if the content of your message was not necessary or proportionate to the DVLA’s inquiry.

Key issues to consider:
1. Purpose Limitation (UK GDPR Article 5(1)(b))

Data collected from you for the purposes of handling a parking appeal must not be repurposed arbitrarily. The DVLA’s investigation is into the lawful use of keeper data, not the substance of any appeal. Disclosing your appeal content risks breaching this principle unless the disclosure was strictly necessary and justified.

2. Data Minimisation (Article 5(1)(c))

Even if ParkingEye considered it appropriate to respond to a DVLA inquiry, they should have disclosed only what was necessary. Quoting or paraphrasing your appeal content goes beyond verifying that an appeal was received.

3. Confidentiality and Fairness

You were not told that appeal content might be shared with third parties outside the appeal process. This kind of disclosure, particularly to a non-judicial body, may also infringe your Article 8 ECHR privacy rights and breach the transparency obligations under Articles 12–14 of the UK GDPR.

4. Lack of Legal Basis

There’s no clear legal basis (Article 6(1)) under the UK GDPR for disclosing your statements to the DVLA unless:

You consented (which you didn’t), or
It was necessary for legal obligations, contracts, or legitimate interests, none of which obviously apply here.

Data collected from you for the purposes of handling a parking appeal must not be repurposed arbitrarily. The DVLA’s investigation is into the lawful use of keeper data, not the substance of any appeal. Disclosing your appeal content risks breaching this principle unless the disclosure was strictly necessary and justified.

2. Data Minimisation (Article 5(1)(c))

Even if ParkingEye considered it appropriate to respond to a DVLA inquiry, they should have disclosed only what was necessary. Quoting or paraphrasing your appeal content goes beyond verifying that an appeal was received.

3. Confidentiality and Fairness

You were not told that appeal content might be shared with third parties outside the appeal process. This kind of disclosure, particularly to a non-judicial body, may also infringe your Article 8 ECHR privacy rights and breach the transparency obligations under Articles 12–14 of the UK GDPR.

4. Lack of Legal Basis

There’s no clear legal basis (Article 6(1)) under the UK GDPR for disclosing your statements to the DVLA unless:

• You consented (which you didn’t), or
• It was necessary for legal obligations, contracts, or legitimate interests, none of which obviously apply here.

If you've not sent the stage two complaint yet, I suggest you add the following paragraph:

Quote
Additionally, I must raise a data protection concern regarding ParkingEye’s response to your internal inquiry. Your Step One reply states that “ParkingEye have advised that they received an appeal stating that you would not identify the driver of the vehicle at the time.” This amounts to ParkingEye disclosing the content of my private appeal to a third party (the DVLA), despite the DVLA not being a party to the dispute. This disclosure was made without my knowledge or consent and was not necessary for the DVLA to determine whether there had been a breach of the KADOE contract. Such a disclosure likely contravenes the principles of data minimisation and purpose limitation under UK GDPR Article 5(1)(b) and (c), and I reserve the right to raise this matter separately with the Information Commissioner’s Office (ICO) if necessary.
Never argue with stupid people. They will drag you down to their level and then beat you with experience” - Mark Twain

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
Did you?

To be absolutely accurate, I said in my appeal "There will be no identification of the driver", so as to be non-committal on whether or not I know the driver's identity.

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
I have already submitted the Stage 2 complaint to the DVLA.

Perhaps I should complain to Parking Eye's data controller (before going to the ICO)?

Also the DVLA should know that they aren't supposed to receive such information. Or at least it should have appeared likely to them that the sender didn't have my permission to send it to them. And in any case they should know that they themselves don't need it, any more than they need to know e.g. my height. So it's not clear what they think they're doing when they quote it to me.


There is a credible argument that ParkingEye may have breached data protection principles by disclosing the content of your appeal to the DVLA without a lawful basis.

While the DVLA is the data controller for the keeper data it provides under the KADOE contract, it is not a party to the dispute between you and the private parking operator, nor is it an adjudicator or regulator of dispute content. Disclosing information from your appeal to the DVLA probably constitutes unlawful further processing under UK GDPR, particularly if the content of your message was not necessary or proportionate to the DVLA’s inquiry.

Key issues to consider:

there is a credible argument that ParkingEye may have breached data protection principles by disclosing the content of your appeal to the DVLA without a lawful basis.

While the DVLA is the data controller for the keeper data it provides under the KADOE contract, it is not a party to the dispute between you and the private parking operator, nor is it an adjudicator or regulator of dispute content. Disclosing information from your appeal to the DVLA may constitute unlawful further processing under UK GDPR, particularly if the content of your message was not necessary or proportionate to the DVLA’s inquiry.

Key issues to consider:
1. Purpose Limitation (UK GDPR Article 5(1)(b))

Data collected from you for the purposes of handling a parking appeal must not be repurposed arbitrarily. The DVLA’s investigation is into the lawful use of keeper data, not the substance of any appeal. Disclosing your appeal content risks breaching this principle unless the disclosure was strictly necessary and justified.

2. Data Minimisation (Article 5(1)(c))

Even if ParkingEye considered it appropriate to respond to a DVLA inquiry, they should have disclosed only what was necessary. Quoting or paraphrasing your appeal content goes beyond verifying that an appeal was received.

3. Confidentiality and Fairness

You were not told that appeal content might be shared with third parties outside the appeal process. This kind of disclosure, particularly to a non-judicial body, may also infringe your Article 8 ECHR privacy rights and breach the transparency obligations under Articles 12–14 of the UK GDPR.

4. Lack of Legal Basis

There’s no clear legal basis (Article 6(1)) under the UK GDPR for disclosing your statements to the DVLA unless:

You consented (which you didn’t), or
It was necessary for legal obligations, contracts, or legitimate interests, none of which obviously apply here.

Data collected from you for the purposes of handling a parking appeal must not be repurposed arbitrarily. The DVLA’s investigation is into the lawful use of keeper data, not the substance of any appeal. Disclosing your appeal content risks breaching this principle unless the disclosure was strictly necessary and justified.

2. Data Minimisation (Article 5(1)(c))

Even if ParkingEye considered it appropriate to respond to a DVLA inquiry, they should have disclosed only what was necessary. Quoting or paraphrasing your appeal content goes beyond verifying that an appeal was received.

3. Confidentiality and Fairness

You were not told that appeal content might be shared with third parties outside the appeal process. This kind of disclosure, particularly to a non-judicial body, may also infringe your Article 8 ECHR privacy rights and breach the transparency obligations under Articles 12–14 of the UK GDPR.

4. Lack of Legal Basis

There’s no clear legal basis (Article 6(1)) under the UK GDPR for disclosing your statements to the DVLA unless:

• You consented (which you didn’t), or
• It was necessary for legal obligations, contracts, or legitimate interests, none of which obviously apply here.

If you've not sent the stage two complaint yet, I suggest you add the following paragraph:

Quote
Additionally, I must raise a data protection concern regarding ParkingEye’s response to your internal inquiry. Your Step One reply states that “ParkingEye have advised that they received an appeal stating that you would not identify the driver of the vehicle at the time.” This amounts to ParkingEye disclosing the content of my private appeal to a third party (the DVLA), despite the DVLA not being a party to the dispute. This disclosure was made without my knowledge or consent and was not necessary for the DVLA to determine whether there had been a breach of the KADOE contract. Such a disclosure likely contravenes the principles of data minimisation and purpose limitation under UK GDPR Article 5(1)(b) and (c), and I reserve the right to raise this matter separately with the Information Commissioner’s Office (ICO) if necessary.

b789

  • Hero Member
  • *****
  • Posts: 4868
  • Karma: +208/-5
    • View Profile
    • GullibleTree
Yes, it's appropriate to raise this as a formal data protection complaint directly to ParkingEye’s Data Protection Officer (DPO) before going to the ICO. This gives them an opportunity to respond and either acknowledge the breach or dig themselves a deeper hole. It also shows the ICO (if you escalate) that you've attempted resolution with the data controller first, in line with best practice under the UK GDPR.

And you're right about the DVLA too — they should neither solicit nor retain personal data beyond what is necessary to determine whether their KADOE rules were breached. If they receive extraneous personal data, especially from a third party, they have an obligation under the storage limitation and data minimisation principles to question, redact, or disregard it — not to quote it back to the data subject.

If you've already submitted the Stage 2 complaint, you can send a follow up to the Stage 2 complaint with the following:

Quote
Subject: Supplementary Information – Step Two Complaint [Insert DVLA Reference Number]

Dear DVLA Complaints Team,

Further to my Step Two complaint submitted on [insert date], reference [insert reference number if known], I am writing to provide supplementary information regarding a potential data protection concern that has arisen from your Step One response.

Your previous correspondence stated:

“ParkingEye have advised that they received an appeal stating that you would not identify the driver of the vehicle at the time.”

This indicates that ParkingEye disclosed the content of my private appeal to the DVLA. The DVLA is not a party to the dispute and has no adjudicative role in the appeal. This disclosure occurred without my knowledge or consent and was not necessary for the DVLA to assess whether ParkingEye had complied with its KADOE obligations.

This action appears to contravene the data minimisation and purpose limitation principles under UK GDPR Article 5(1)(b) and (c). It also raises questions under the transparency and fairness requirements of Articles 12 to 14. I believe this disclosure constitutes a further misuse of my personal data, beyond the original misuse that formed the basis of my Step Two complaint.

Please ensure this concern is added to the ongoing investigation. I reserve the right to escalate this matter separately to the Information Commissioner’s Office (ICO) depending on the outcome.

Yours sincerely,

[Your Name]
[Your address or reference details, if required]
[Date]
Never argue with stupid people. They will drag you down to their level and then beat you with experience” - Mark Twain

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
Thanks again!

I have now made a data protection complaint to Parking Eye as follows, through their website (here), but haven't yet received an acknowledgement.

Will contact the DVLA as per your suggestion later today when I have the time.

Quote
Dear Parking Eye Privacy Team,

I have been informed as follows in an email dated 9 April 2025 from a Data Assurance Compliance Officer at the DVLA:

"ParkingEye have advised that they received an appeal stating that you would not identify the driver of the vehicle at the time."

This amounts to ParkingEye disclosing to a third party, namely the DVLA, part of the content of my private appeal, despite the DVLA not being a party to the dispute. This disclosure was made without my knowledge or consent and was without good cause. It contravenes the principles of data minimisation and purpose limitation under UK GDPR Article 5(1)(b) and (c), and in the event that I do not receive your apology for this clear breach I reserve the right to raise this matter separately with the Information Commissioner’s Office (ICO).

I also request full copies of all correspondence relating in any way to PCN [***] that you have had with the DVLA or any other party.

Once again I am clicking the button on your submission form saying "I confirm that I have read and accept the privacy policy and consent to my data being processed and shared, as outlined in the policy, for the purpose of reviewing and responding to my enquiry", but the only reason I am clicking it is because you have chosen to configure your software so as not to accept complaints from people who don't. My clicking of the button should not be interpreted as having an significance, and I do not confirm that I have read any policy.

Yours sincerely,

[***]
« Last Edit: April 11, 2025, 10:01:20 am by carriep »
Like Like x 1 View List

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
As well as contacting Parking Eye's privacy desk (message not acknowledged) and sending a copy to their complaints desk (message auto-acknowledged), I have now sent a followup to the DVLA as follows.

My feeling is I won't get a response from Parking Eye on the data protection complaint (they haven't even sent a substantial response to my appeal yet, after 7.5 weeks) and so I will have to contact the ICO, but we shall see.


Quote
Subject: Supplementary Information -- Step Two Complaint [Ref: [***] ]

Dear DVLA Complaints Team,

Further to my Step Two complaint submitted on 9 April, reference [***], I am writing to provide supplementary information regarding a potential data protection concern that has arisen from your Step One response.

Your previous correspondence stated:

“ParkingEye have advised that they received an appeal stating that you would not identify the driver of the vehicle at the time.”

This indicates that ParkingEye disclosed the content of my private appeal to the DVLA. The DVLA is not a party to the dispute and has no adjudicative role in the appeal. This disclosure occurred without my knowledge or consent and was not necessary for the DVLA to assess whether ParkingEye had complied with its KADOE obligations.

This disclosure appears to contravene the data minimisation and purpose limitation principles under UK GDPR Article 5(1)(b) and (c). It also raises questions under the transparency and fairness requirements of Articles 12 to 14. I believe this disclosure constitutes a further misuse of my personal data, beyond the original misuse that formed the basis of my Step Two complaint.

Please ensure this concern is added to the ongoing investigation. I realise the DVLA is not responsible for parties that send information to it in breach of privacy rights, but nonetheless I am bringing this matter to your attention, because it is further evidence as to Parking Eye's contempt for the law. I have written to Parking Eye's data protection officer and in the event of an unsatisfactory response, or no response, I shall escalate the matter to the Information Commissioner’s Office (ICO).

Yours sincerely,

[***]
Registered keeper of vehicle [***]
12 April 2025
Like Like x 1 View List

carriep

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
I have received a response from Parking Eye's privacy team as follows. The funniest bit is where they say that if I want to know about my rights I should go to their website. The more important bit is where they're blaming the DVLA for their own sending information to the DVLA that they shouldn't have.

I also enclose a copy of the response I have sent them.

Quote
Dear [***],

Thank you for your correspondence.

To comply with DVLA and our KADOE agreement the DVLA are able conduct audits of our practices and processes, to ensure that we are conducting our business in a compliant manner. Failure to comply with these obligations would result in us not being able to lawfully operate.

The DVLA requested information from us regarding the Parking Charge as you submitted a complaint to the DVLA, and as such, to remain compliant we provided the DVLA with the information they requested.

Please be advised that your full Subject Access Request has been received and we can confirm that this will be issued within the applicable timeframe as per our GDPR obligations.

For further information about your rights as a data subject, plus information about the categories of data we process, data transfers, the legal basis for our processing, and the purposes of processing, please visit: https://www.parkingeye.co.uk/privacy-policy/
 
Yours sincerely,

Parkingeye Privacy Team


My response:


Quote
Dear ParkingEye Privacy Team,

Is this a formal response to my privacy complaint? Please let me know, because if it is I shall escalate this matter to the ICO. To say that someone requested information from you is no defence against a claim of breaching a subject's privacy rights by sending it. If you do not acknowledge this request, I am sure the ICO will be able to assist.

Yours sincerely,

[***]

b789

  • Hero Member
  • *****
  • Posts: 4868
  • Karma: +208/-5
    • View Profile
    • GullibleTree
Their reply attempts to justify the disclosure by pointing to their obligations under the DVLA's audit framework and their KADOE agreement, but it does not adequately address your specific complaint — which is that:

1. They disclosed the content of your appeal, not just confirmation that an appeal was made or a general procedural update.
2. They did not demonstrate the necessity or proportionality of that disclosure in relation to the DVLA's stated purpose — i.e. checking KADOE compliance.
3. They have not identified a lawful basis under UK GDPR Article 6 for sharing narrative content that is plainly not necessary for a KADOE audit.

Even if the DVLA asked, that does not absolve ParkingEye of their obligations under data minimisation (Art. 5(1)(c)) and purpose limitation (Art. 5(1)(b)). ParkingEye remains the controller of your appeal data and is still required to ensure that only strictly necessary data is shared externally. That obligation does not disappear just because a government agency makes a request.

The ICO requires that you give the data controller a chance to resolve the matter first before escalating. That means your next step is to reply to ParkingEye, challenging their justification and giving them one final opportunity to respond properly. This satisfies the ICO's requirement to attempt resolution directly.

In order to be able to escalate this to the ICO, you need to send the following to :

Quote
Subject: Re: Unlawful Disclosure of Personal Data to DVLA – Response Inadequate
Dear ParkingEye Privacy Team,

Thank you for your response.

I must make clear that your reply does not resolve my complaint, which concerns your decision to disclose the content of my appeal to the DVLA, not whether you were entitled to respond to their inquiry generally.

You have not explained:

• What lawful basis under Article 6 of UK GDPR you relied on to disclose narrative content from my appeal;
• Why that disclosure was necessary or proportionate for the DVLA’s oversight role under the KADOE agreement;
• How the DVLA’s request for general information (e.g., whether an appeal was made) justified quoting or paraphrasing statements that I made in confidence during an appeal process.

The DVLA is not a party to the dispute and has no adjudicative function. While they may audit process compliance under the KADOE agreement, that does not relieve you of your duties as data controller to comply with the principles of purpose limitation and data minimisation under Articles 5(1)(b) and (c) of the UK GDPR.

Unless you can provide a lawful basis and justification for disclosing that specific information, I will consider this matter unresolved and reserve the right to refer it to the Information Commissioner’s Office (ICO).

Please treat this as a continuation of my formal complaint and provide a full response within 14 days.

Yours sincerely,

[Your Name]

Once you receive their response — or if they fail to respond within the time you’ve set — you will be able to escalate to the ICO, including a copy of your full exchange to show that you attempted resolution.
Never argue with stupid people. They will drag you down to their level and then beat you with experience” - Mark Twain