Receive and distinguish
Bring the concern and relevant case context together. Identify whether it involves a complaint, a rights request, a breach or linked work.
UK GDPR and EU GDPR workflows
Keep privacy complaints moving with clear ownership and connected case context. ResolveCX helps privacy, legal, security and customer-operations teams coordinate the work, while keeping rights requests and breach decisions on distinct paths.
GDPR complaint management software helps teams organize privacy concerns, ownership, investigation and responses. It brings case context together while keeping data protection complaints, data subject rights requests and personal data breaches distinct. Each needs its own legal assessment, responsible people and response process, rather than a single compliance countdown.
Start with the case type
A concern can lead to related work without becoming one interchangeable GDPR case. Match the trigger, legal basis and owner before setting a response target.
| Case and trigger | Timing and conditions | People and evidence |
|---|---|---|
| Data protection complaint A concern about the use of personal data. | UK section 164A: acknowledge within 30 days of receipt; appropriate steps and outcome without undue delay. EU Article 77 does not set a universal company-response deadline. | Complaint owner and privacy team: investigate, explain the outcome and keep correspondence and rationale. |
| Rights request (DSR / DSAR) A person exercises a right, such as access, correction or erasure. | Normally one month from the applicable legal start date for a response, subject to extension, identity, clarification and exception rules. Assess UK and EU rules separately. | Rights-request owner and data owners: assess the right, scope, exceptions and response; keep reasons for the decision. |
| Personal data breach A security breach affecting personal data, requiring risk assessment. | Article 33: notify without undue delay and, where feasible, within 72 hours of controller awareness, unless unlikely to result in a risk to people's rights and freedoms. | Security and privacy leads: assess risk, decide notification and record facts, effects and remedial action. |
ResolveCX case coordination
Use complaint management and case management to keep the issue and responsible teams connected. Plan the process around your operating model, with people accountable for legal decisions and outcomes.
Bring the concern and relevant case context together. Identify whether it involves a complaint, a rights request, a breach or linked work.
Keep ownership and the next action clear across customer operations, privacy, legal and security. Agree response targets around the applicable process.
Use the case history to inform investigation. People assess legal scope, exceptions, risk and the response; AI assistance does not make those decisions.
Keep the outcome and follow-up work in context. Review recurring issues and assign corrective action rather than treating case closure as proof of compliance.
AI Classification covers inbound cases, complaints and inquiries. Categories can feed configured team routing or immediate escalation, with people reviewing exceptions. Case Summarization helps handlers review available case material; check original sources for accuracy and omissions.
UK and EU scope
DPA 2018 section 164A, inserted by the Data (Use and Access) Act 2025, applies to complaints to controllers about alleged infringements of the UK GDPR or Part 3 of the DPA 2018. The complaint-handling duty came into force on June 19, 2026.
Provide a complaint route and acknowledge within 30 days of receipt. Without undue delay, take appropriate steps, including appropriate enquiries and progress information, and communicate the outcome. Thirty days is an acknowledgment period, not a universal deadline to resolve the complaint. The ICO is the UK supervisory authority.
Article 77 is the right to complain to a supervisory authority. It creates no universal company-response deadline. Assess national requirements and the organization's own process separately, and keep authority correspondence distinct from the original customer complaint.
EU national supervisory authorities handle these complaints. Where the cross-border cooperation framework applies, a lead supervisory authority works with concerned authorities. The ICO is not an EU lead authority.
Specialist review
Requests under Articles 15 to 22 include access, correction, erasure, restriction, portability and objection where applicable. Normally respond without undue delay and within one month from the applicable legal start date. A further two months may be available where necessary for complexity or the number of requests, with notice and reasons within the applicable initial month.
Assess identity, clarification, exceptions and the applicable start date separately under UK and EU law. ICO subject-access guidance allows a pause for reasonably required clarification; do not apply that UK rule automatically to EU requests. Erasure depends on legal grounds and exceptions, including legal obligations and legal claims.
Under UK and EU GDPR Article 33, controllers notify the competent authority without undue delay and, where feasible, within 72 hours of awareness, unless the breach is unlikely to result in a risk to people's rights and freedoms. Give reasons for delay. Processors notify the controller without undue delay after awareness.
Article 34 requires communication to people without undue delay where high risk is likely. Assess exceptions for qualifying protective measures, subsequent measures removing the likely high risk, or disproportionate effort with equally effective public communication. Keep the facts, effects, remedial action and decision rationale, including when notification is not required.
Incident management provides the broader operational context. Privacy and security leads own reportability decisions and any required notifications; a case timer does not make that assessment.
Explore the operating model
Case coordination connects the concern, investigation and responsible people. It is not a substitute for specialist data discovery or rights fulfillment. Bring your case types, handoffs and response requirements to a focused demonstration.
Buyer questions
It is software for coordinating privacy complaint cases, ownership, investigation and responses. ResolveCX focuses on connected complaint and case handling. Rights requests and breach cases need separate legal assessments and response processes, even when they relate to the same customer issue.
For complaints within DPA 2018 section 164A, controllers must provide a complaint route, acknowledge receipt within 30 days, take appropriate steps including appropriate enquiries, give progress information and communicate the outcome without undue delay. The acknowledgment period is not a 30-day final-resolution deadline.
Article 77 gives individuals the right to complain to a supervisory authority, including in the Member State of their habitual residence, workplace or alleged infringement. It does not create a universal company-response deadline. Organizations should distinguish their own complaint process from authority correspondence and applicable national requirements.
No. A complaint challenges how personal data is handled; a subject access request (SAR or DSAR) exercises the right of access. One message can contain both. Identify each part and apply its own process, timing and response requirements rather than closing one as if it resolves the other.
Normally one month from the applicable legal start date, without undue delay. A further two months may be available where necessary because of complexity or the number of requests, with timely notice and reasons. Assess identity, clarification and exceptions under the applicable UK or EU rules. UK subject-access clarification rules must not be assumed to apply identically in the EU. Erasure is conditional, not automatic.
No. Under Article 33, controllers notify the competent authority without undue delay and, where feasible, within 72 hours of awareness, unless the breach is unlikely to result in a risk to people's rights and freedoms. Late notifications need reasons for delay. Processors notify the controller without undue delay after awareness. Record the assessment even when authority notification is not required.
Article 34 requires communication without undue delay when a breach is likely to result in a high risk to people's rights and freedoms. Exceptions cover qualifying protective measures, subsequent measures removing the likely high risk, or disproportionate effort requiring equally effective public communication instead. The controller assesses the conditions; the supervisory authority can require communication.
No. Coordinating a case is not the same as discovering or deleting data in source systems. ResolveCX brings complaint ownership and case context together. Agree any data-system work and supported connections separately; responsible teams must assess the request, exceptions and lawful action.
Your privacy complaint workflow
Discuss how ResolveCX can support complaint ownership and case context across your UK and EU teams.
Content updated . Official sources checked October 20, 2026.
General information, not legal advice. ResolveCX supports case coordination, not a guarantee of compliance. Organizations remain responsible for legal applicability, configuration and decisions.