DAPLE (C1) key terms

A structured analysis carried out before processing that is likely to be high risk, identifying necessity, proportionality, risks to individuals and the safeguards that reduce them.

The obligation to take active responsibility for compliance and to be able to demonstrate it through records, policies, assessments and evidence rather than mere intention.

The powers individuals hold over their personal data, typically including access, correction, erasure, restriction, portability and objection, each subject to defined conditions and deadlines.

The organisation or body that alone or jointly determines why and how personal data is processed, and therefore carries the primary legal duties.

An organisation that processes personal data on behalf of and under the documented instructions of a controller, with duties of confidentiality, security and assistance.

Two or more parties that jointly determine the purposes and means of processing, sharing responsibility and required to allocate duties transparently to individuals.

A third party engaged by a processor to carry out part of the processing, requiring controller authorisation and equivalent contractual obligations down the chain.

Processing likely to result in a significant impact on individuals, such as large-scale sensitive data, systematic monitoring or automated decisions, which triggers extra safeguards and assessments.

Sensitive personal data such as health, biometrics, ethnicity, religion, political views or sexual orientation, which needs a specific legal basis and stronger controls.

The legal ground that makes a processing activity permissible, such as consent, contract, legal obligation, vital interest, public task or legitimate interest.

The principle that personal data may only be used for the specific, explicit and legitimate purposes stated when it was collected, unless a compatible new purpose applies.

Collecting and retaining only the personal data that is adequate, relevant and necessary for the stated purpose, avoiding surplus fields and indefinite retention.

A freely given, specific, informed and unambiguous indication of agreement, withdrawable at any time and requiring evidence that it was validly obtained.

A lawful basis relying on a genuine business or third-party interest that is not overridden by individual rights, documented through a balancing assessment.

Assigning data to defined sensitivity tiers so that handling, access, retention and protection requirements are proportionate and consistently applied.

A maintained catalogue of datasets recording what personal data exists, where it resides, who owns it, how it flows and why it is held.

The formal register of processing operations, describing purposes, categories of data and individuals, recipients, transfers, retention and security measures.

Diagramming how data moves between systems, teams and external parties, capturing collection points, transfers, storage locations and onward disclosures.

A rule set defining how long each data category is kept and how it is disposed of once the purpose or legal retention period ends.

Layering independent preventive, detective and corrective controls so that the failure of one safeguard does not expose the data protected by the others.

A security model that verifies every request explicitly and grants least privilege, rather than trusting users or devices because of their network location.

Replacing direct identifiers with tokens so that data can no longer be attributed to an individual without separately secured additional information.

Irreversibly transforming data so that no individual can be identified by any means reasonably likely to be used, taking account of singling out and linkage.

Protecting stored data by converting it into unreadable ciphertext, so that lost media or unauthorised storage access does not expose the underlying content.

Protecting data while it moves across networks using protocols such as TLS, preventing interception or tampering between sender and recipient.

The lifecycle discipline of generating, storing, rotating, escrowing, revoking and destroying cryptographic keys with separation of duties and audit trails.

A tamper-resistant device that generates and stores keys and performs cryptographic operations so that key material never appears in plain form on general systems.

Designing systems so that algorithms, key lengths and providers can be replaced quickly without redesigning applications, in response to new threats or standards.

Granting each identity only the minimum access needed for its current task, for the shortest time, and removing it when no longer required.

Assigning permissions to job roles rather than individuals, so that users inherit rights through their role and access stays consistent and reviewable.

Requiring two or more independent authentication factors, such as something known plus something held, to reduce the impact of stolen credentials.

Controls over high-power accounts, including vaulting of credentials, just-in-time elevation, session recording and frequent review of administrative rights.

A security incident leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data.

The duty to inform a supervisory authority, and sometimes affected individuals, within tight deadlines when a breach is likely to create a risk to rights and freedoms.

Preparing logging, time synchronisation, evidence handling and chain-of-custody procedures in advance so incidents can be investigated and defended credibly.

A contract imposing documented instructions, security, confidentiality, sub-processor rules, assistance and deletion duties on a processor acting for a controller.

Moving personal data to another jurisdiction, permitted only where a transfer mechanism and, where required, additional safeguards and assessments are in place.

Pre-approved contractual terms used to legitimise transfers to recipients in countries without an adequacy decision, binding both parties to data protection obligations.

An analysis of the destination country's laws and practices, and of supplementary measures, to judge whether transferred data retains equivalent protection.

Embedding privacy protections into system architecture and default settings from the outset, rather than adding compliance measures after the design is fixed.

Technical methods such as differential privacy, secure multi-party computation, homomorphic encryption and synthetic data that reduce exposure of personal data during analysis.

Adding calibrated statistical noise to query results so that an individual's presence in a dataset cannot be reliably inferred, with a measurable privacy budget.