Privacy Awareness Week 2026: Trust is built when things go wrong
Privacy Awareness Week 2026: Trust is built when things go wrong
How cyber and data teams support effective privacy complaint resolution
When talking about privacy, the focus is often on protection - strong policies, staff training, security controls and compliance frameworks designed to stop things going wrong in the first place. Yet privacy is often scrutinised when these protections are tested, such as when an individual raises a concern about how their personal information has been handled. In those moments, trust is built through the organisation’s ability to respond clearly, consistently, and credibly. This heavily relies on the strength of cyber security and data governance foundations supporting the response.
Building on last year’s focus on shared responsibility, the theme for Privacy Awareness Week 2026, ‘Trust is built here. In every privacy complaint. In every resolution,’ turns attention to how privacy obligations are met in practice. When individuals make requests or raise concerns, organisations are required to demonstrate accountability, transparency, and sound, consistent decision‑making. Effective privacy protection in practice relies on strong governance, clear processes, and the operational capability to respond well when things go wrong.
Privacy complaints as moments of trust
Privacy complaints are often viewed as a legal or regulatory issue, something to be managed by specialist teams once a problem has already occurred. In practice, they start as moments of accountability as part of business-as-usual operations. A privacy complaint may ask an organisation to explain:
- What personal information does it hold
- How and why it has been used or shared
- Who had access to it
- Whether appropriate safeguards were in place
- What steps will be taken to address the concern.
These questions require evidence and consistent decision‑making. Organisations that respond well tend to resolve complaints more quickly, reduce escalation risk and preserve trust - even where mistakes have been made. Those who stumble often do so because they lack readiness.
What it means to be “complaint‑ready”
Being “complaint‑ready” means ensuring that privacy obligations are operationalised for when concerns are raised so that the organisation is equipped to respond.
In practice, complaint readiness depends on three things:
- Evidence to support what happened
- Visibility into personal data and its use
- Governance that enables timely and defensible decisions.
This is where cyber security and data teams play a critical role.
Cyber security’s role in providing evidence and assurance
Effective privacy complaint resolution relies heavily on cyber security capabilities that are often taken for granted until they are urgently needed.
When a complaint is raised, organisations may need to demonstrate:
- Who accessed personal information, and when
- Whether access was authorised
- How information was protected
- Whether an incident occurred, and how it was contained
- What controls were operating at the time.
Security logs, access records, audit trails, and incident timelines provide a factual basis for these conversations. Without them, organisations are left relying on assumptions, incomplete information or broad assurances. Strong cyber security practices support complaint resolution by enabling organisations to respond with evidence and clarity.
Data governance’s role in providing context and assurance
While cyber security provides control assurance, data governance provides contextual understanding. Privacy complaints can quickly become complex, not because of malicious activity, but because organisations cannot quickly answer basic questions about their data, such as:
- What personal information do we hold?
- Where does it reside?
- Why are we collecting it?
- How long do we keep it?
- Who is responsible for it?
Data governance frameworks, including data ownership, classification, lineage and retention, help organisations respond accurately and consistently. They reduce the risk of contradictory explanations, oversized information and data footprints, and delays in response to support clear communication with individuals.
Importantly, strong data governance also helps organisations identify whether a complaint points to a broader issue, such as unnecessary data collection, unclear consent practices, systemic inconsistency, or inconsistent retention.
Using complaints to strengthen controls and operations
Handled well, privacy complaints operate as a feedback mechanism. Patterns in complaints can highlight control weaknesses, process gaps, communication issues, or areas where governance needs to be clarified.
Organisations that treat complaints as learning opportunities are better positioned to strengthen controls, improve transparency, and reduce future risk. Those who treat them as isolated events often see the same issues recur time and time again.
Building trust through capability
No organisation is immune from privacy complaints. What distinguishes trusted organisations is not the absence of issues, but the quality of their response.
Cyber security and data governance teams are central to this capability. By working together, they enable organisations to move beyond compliance and demonstrate privacy in practice.
Privacy complaint readiness checklist
Use this checklist to sense-check whether your organisation is set up to respond clearly, fairly and credibly when a privacy complaint is raised.
| CHECKlist | |
|---|---|
| Intake and triage: Have a clear process to log the complaint, verify identity/authority (where needed), acknowledge receipt, and set response timeframes and escalation points | |
| Clarify the request: Clarify what the individual is seeking (explanation, access, correction, deletion, objection, apology, remediation) and what systems/business areas may be involved | |
| Preserve evidence: Identify and retain relevant records early (tickets, emails, chat logs, call recordings where applicable) and capture an initial timeline | |
| Be audit ready: Ensure you can quickly retrieve access logs, audit trails, privileged access records, incident notes and control evidence for the relevant period | |
| Know your data landscape: Confirm what personal information you hold, where it sits, how it flows (internally and externally), the purpose for processing, and applicable retention rules | |
| Ownership and decision rights: Assign a case owner, confirm data/system owners, and define who can approve decisions (especially disclosures, corrections, remediation, notifications) | |
| Follow a consistent assessment approach: Use a standard framework to evaluate whether controls were appropriate and whether any incident or unauthorised access occurred | |
| Communicate clearly: Provide a plain-English explanation of what happened, what data was involved, who had access (where possible), and what you’re doing about it | |
| Remediate and improve: Implement corrective actions - whether controls, training or process changes - and track them through to completion. Look for systemic issues or repeat patterns | |
| Document everything: Keep a defensible record of evidence reviewed, decisions made, rationale, actions taken, and final response. |
How BDO can help
BDO’s cyber security and data teams work closely with organisations to strengthen the foundations that support effective privacy complaint resolution. This includes helping organisations improve visibility over personal information, establish clear data ownership and governance, and ensure the right security evidence is available when concerns are raised.
To learn more about how BDO can support your organisation’s privacy, cyber security and data governance needs, contact us today.

