What should you do with automated data subject requests?
Privacy Program Crash Test

THE CONTEXT OF THE ISSUE
To respond or to ignore — that is the question
Have you received a data subject request from PrivacyBee, Incogni, DeleteMe, Optery, or a similar platform?
These services allow individuals to send centralized requests to multiple companies to delete or access their personal data.
It may feel like spam, especially if you receive a high volume of nearly identical requests. But that’s not always the case.
Since such requests are automatically generated, the question arises: are they legally valid?
Why are automated data subject requests so hard to handle?
-
The GDPR does not contain specific instructions on how to deal with such requests. As a result, the general rule is often applied: the controller must respond within one month.01
-
Identity verification
The GDPR allows controllers to request additional information to verify the requester's identity. However, there are no clear criteria when it comes to automated requests.02 -
Excessive requests
Suppose you receive multiple repetitive requests from the same individual. In that case, the GDPR allows controllers to charge a reasonable fee or even refuse to act, but only if the requests are “manifestly unfounded” or “excessive.” The burden of proof lies with the controller.03 -
Regulation in the U.S.
This depends on the state. For example, in California, the controller is only required to respond to verifiable consumer requests. If verification is not possible, the controller may deny the request and must inform the requester accordingly.04
INSIGHTS
-
A clear action plan is the foundation of compliance
Automated requests require a prompt and coordinated response. Developing a clear internal workflow helps avoid mistakes and uncertainty. -
Let technology work for you
Automating identity verification and request handling reduces the burden on your team, prevents requests from being overlooked, and minimizes human error. -
Data protection is everyone’s responsibility
Handling these requests is not just a job for the legal team or the DPO. Train all relevant staff to recognize such requests and know the appropriate next steps. -
Documentation is your safety net
Keeping detailed records of how each request was handled can protect you during audits or legal disputes.
Respecting and facilitating individuals’ rights is not just a legal requirement; it’s essential to building lasting trust with your customers.

Automated requests are already a reality. The proper response is to act proactively.
Current and practical articles on the topic
- Data protection officer
- AI compliance officer
- Data privacy compliance
- Дія.City
- Digital Millennium copyright Act
- Торгова марка в IT
We write about what we practice
IP, GDPR, contracts and disputes, as well as the legal aspects of implementing technologies like artificial intelligence or sharing best practices for delivering practical legal solutions.