Privacy and data protection work runs on a vocabulary that sounds like plain English but carries precise legal meaning, and the gap between the two is where projects go wrong. This glossary gives short, plain definitions of the terms security, identity, engineering and procurement teams meet most often when they work with privacy and legal colleagues: the roles (controller, processor, data subject, DPO), the principles (purpose limitation, data minimisation, storage limitation, accountability), the lawful bases, the rights people hold, the assessments (DPIA, legitimate interests assessment, transfer impact assessment), breach terms, and the mechanisms for moving data across borders. Where a term is defined in the EU General Data Protection Regulation (GDPR), the entry says so and paraphrases the definition from the official text; other laws such as the UK GDPR and US state privacy laws use similar but not identical wording. Each entry links to a deeper NHI Mgmt Group guide where one exists. This page explains terms; it is not legal advice. For how these pieces fit into a working programme, start with the Privacy Programme Guide for Security Teams.
A
- Accountability
- The GDPR principle (Article 5(2)) that the controller is responsible for complying with the data protection principles and must be able to demonstrate that compliance. In practice it means evidence: records of processing, DPIAs, policies, contracts, training records and logs that show the principles are applied, not just stated.
- Adequacy decision
- A decision by the European Commission that a third country, territory or sector ensures an adequate level of data protection. Under GDPR Article 45(1), transfers to an adequate destination need no specific authorisation. See the EU-US Data Privacy Framework Guide.
- Anonymisation
- Processing data so that individuals can no longer be identified by anyone, using any means reasonably likely to be used. Truly anonymous data falls outside data protection law, but the bar is high: linking, inference and small populations often allow re-identification. See the Anonymisation and Re-identification Risk Guide.
- Automated individual decision-making
- A decision about a person made solely by automated means, including profiling, that produces legal or similarly significant effects. GDPR Article 22 gives people rights in relation to such decisions. See the GDPR Article 22 Automated Decision-Making Guide.
B to C
- Binding corporate rules (BCRs)
- GDPR Article 4 defines them as personal data protection policies adhered to by a controller or processor for transfers within a group of companies or enterprises. Under Article 47, a supervisory authority approves them if they are legally binding, give data subjects enforceable rights and meet set content requirements. See the Binding Corporate Rules (BCRs) Guide.
- Biometric data
- Personal data resulting from specific technical processing of a person's physical, physiological or behavioural characteristics that allows or confirms their unique identification, such as facial images or fingerprint templates (GDPR Article 4). When used to uniquely identify someone it is special category data. See the Biometric Privacy Laws Map.
- Consent
- Under GDPR Article 4, any freely given, specific, informed and unambiguous indication of the data subject's wishes, by a statement or clear affirmative action. The GDPR recitals add that silence, pre-ticked boxes or inactivity do not constitute consent. It is one of six lawful bases, not the default one. See Consent vs Legitimate Interest.
- Consent management platform (CMP)
- Software that presents consent choices to users (often for cookies and trackers), records the choice, and signals it to the tags and systems that must respect it. A CMP is only as good as the enforcement behind it. See the Consent Management Guide: Cookies, CMPs and GPC.
- Consent record
- The evidence that a person gave consent: who, when, what they were told, what they agreed to, and how. Because the controller must be able to demonstrate consent, missing records usually mean no valid consent. See the Consent Records Guide.
- Controller
- The person, public authority, agency or other body that, alone or jointly with others, determines the purposes and means of processing personal data (GDPR Article 4). The controller carries most of the obligations. Two or more organisations that decide purposes and means together are joint controllers. See the Controller vs Processor Guide.
- Cookie and tracker rules
- Rules on storing or reading information on a user's device, such as cookies, pixels and SDKs, which in the EU come mainly from the ePrivacy Directive rather than the GDPR. They usually require consent for anything not strictly necessary. See the Cookie and Tracking Technology Compliance Guide.
D
- Data concerning health
- Personal data related to a person's physical or mental health, including the provision of health care services, that reveals information about their health status (GDPR Article 4). It is special category data. See the Health Data Privacy Beyond HIPAA Guide (My Health My Data).
- Data minimisation
- The GDPR principle that personal data must be adequate, relevant and limited to what is necessary for the purposes. For engineers it means fewer fields, shorter retention and narrower access by default. See Data Minimisation.
- Data portability
- The right under GDPR Article 20 to receive personal data you provided to a controller in a structured, commonly used and machine-readable format and to transmit it to another controller, directly where technically feasible. It applies only where processing is based on consent or contract and carried out by automated means.
- Data protection by design and by default
- The requirement to build data protection into systems and processes from the start, and to make the most protective settings the default, so that only the personal data necessary for each purpose is processed. See the Privacy by Design Guide for Engineering Teams.
- Data protection impact assessment (DPIA)
- An assessment, required by GDPR Article 35 before processing that is likely to result in a high risk to people's rights and freedoms, particularly when using new technologies. Article 35(3) makes it mandatory for systematic automated evaluation with significant effects, large-scale processing of special category or criminal offence data, and large-scale systematic monitoring of public areas. See the DPIA Guide: Running a Data Protection Impact Assessment and the DPIA Template.
- Data protection officer (DPO)
- An expert in data protection law and practice who advises and monitors the organisation. Under GDPR Article 37(1), a DPO must be designated by public authorities (except courts acting in their judicial capacity), and by organisations whose core activities involve large-scale regular and systematic monitoring or large-scale processing of special category or criminal offence data. See DPO vs CPO.
- Data subject
- The identified or identifiable living person the personal data relates to: a customer, employee, patient, website visitor or anyone else.
- Data subject request (DSAR)
- A request by a person to exercise one of their rights, most often the right of access (a data subject access request). Identity verification is the security team's main contribution: too weak and you disclose data to an impostor, too strong and you block a lawful request. See the DSAR Guide: Handling Data Subject Requests and the Data Subject Request Verification Procedure Template.
- Derogations
- Narrow exceptions in GDPR Article 49 that allow a transfer without an adequacy decision or appropriate safeguards, for example explicit consent after the person has been told of the risks, performance of a contract, important public interest, or legal claims. They are for specific situations, not routine transfers.
E to L
- Encryption
- Transforming data so it can only be read with a key. GDPR Article 32 names pseudonymisation and encryption of personal data as examples of measures appropriate to the risk. Encryption reduces breach impact only if the keys are managed separately from the data. See Encryption at Rest vs In Transit vs In Use.
- Erasure (right to be forgotten)
- The right under GDPR Article 17, titled "Right to erasure ('right to be forgotten')", to have personal data deleted in defined circumstances. Backups, logs, analytics stores and AI training data make erasure hard in practice. See the Data Retention and Secure Deletion Guide.
- Genetic data
- Personal data relating to a person's inherited or acquired genetic characteristics that gives unique information about their physiology or health, usually from analysis of a biological sample (GDPR Article 4). It is special category data.
- Integrity and confidentiality
- The GDPR security principle: personal data must be processed with appropriate security, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage. Article 32 expands it. See the GDPR Article 32 Security of Processing Guide.
- Lawful basis
- One of the six grounds in GDPR Article 6(1) that make processing lawful: consent, contract (or steps before a contract at the person's request), legal obligation, vital interests, public interest or official authority, and legitimate interests. Every processing activity needs one, chosen before processing starts.
- Lead supervisory authority
- For cross-border processing, the supervisory authority of the controller's or processor's main or single establishment in the EU (GDPR Article 56). It acts as the sole point of contact for that processing.
- Legitimate interests
- The lawful basis in GDPR Article 6(1)(f): processing necessary for the legitimate interests of the controller or a third party, unless overridden by the person's interests or rights, in particular where the person is a child. Public authorities cannot rely on it when performing their tasks.
- Legitimate interests assessment (LIA)
- A documented three-part test of purpose, necessity and balancing used to show that legitimate interests is a valid basis for a particular processing activity. See the Legitimate Interests Assessment Template.
M to P
- Main establishment
- For a controller with establishments in more than one EU member state, the place of its central administration in the Union, unless decisions on purposes and means are taken and enforced in another EU establishment (GDPR Article 4). It decides which authority leads.
- Personal data
- Any information relating to an identified or identifiable natural person (GDPR Article 4). Identifiable includes indirect identification through identifiers such as a name, an identification number, location data or an online identifier. IP addresses, device IDs, account IDs and API logs tied to users are often personal data. US laws often use "personal information" with similar breadth. See Data Privacy vs Data Security.
- Personal data breach
- A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data (GDPR Article 4). Not every security incident is one, and not every breach is a hack: a misdirected email counts. See the Data Breach Notification Checklist.
- Breach notification (72 hours)
- Under GDPR Article 33(1), the controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in a risk to people. Article 34 requires telling affected individuals without undue delay where the breach is likely to result in a high risk, and Article 33(5) requires every breach to be documented. See the Breach Notification Laws by Country Guide.
- Prior consultation
- The GDPR Article 36 duty to consult the supervisory authority before processing where a DPIA shows the processing would result in a high risk in the absence of measures to mitigate it.
- Privacy-enhancing technologies (PETs)
- Techniques that let organisations use data while exposing less of it, such as pseudonymisation, differential privacy, homomorphic encryption, secure multi-party computation, federated learning and trusted execution environments. See the Privacy-Enhancing Technologies Guide.
- Privacy notice
- The external statement telling people what personal data is collected, why, on what lawful basis, who receives it, how long it is kept and what rights they have. GDPR Articles 13 and 14 set what must be provided. See Privacy Notice vs Privacy Policy.
- Processing
- Any operation or set of operations performed on personal data, whether or not by automated means, including collection, recording, storage, retrieval, use, disclosure, erasure and destruction (GDPR Article 4). Almost anything a system does with personal data, including logging it, is processing.
- Processor
- A person or body that processes personal data on behalf of the controller (GDPR Article 4): cloud providers, SaaS vendors, payroll bureaux and many managed service providers. Under GDPR Article 28(3), the processor must make available to the controller all information necessary to demonstrate compliance and tell the controller if an instruction appears to infringe the Regulation. See the GDPR Article 28 Processor Guide and the Data Processor Due Diligence Questionnaire Template.
- Profiling
- Any automated processing of personal data that uses it to evaluate personal aspects of a person, in particular to analyse or predict performance at work, economic situation, health, preferences, interests, reliability, behaviour, location or movements (GDPR Article 4).
- Pseudonymisation
- Processing personal data so it can no longer be attributed to a specific person without additional information, provided that information is kept separately and protected (GDPR Article 4). Pseudonymised data is still personal data. See Data Masking vs Anonymisation vs Pseudonymisation.
- Purpose limitation
- The GDPR principle that personal data must be collected for specified, explicit and legitimate purposes and not further processed in a way incompatible with them. Reusing production data for testing or AI training is a common purpose limitation question. See the AI and GDPR Guide.
R to S
- Recipient
- A person or body to which personal data is disclosed, whether a third party or not (GDPR Article 4). Privacy notices and records of processing must list recipients or categories of recipients.
- Records of processing activities (ROPA)
- The register required by GDPR Article 30 describing each processing activity: purposes, categories of data and data subjects, recipients, transfers and, where possible, erasure time limits and security measures. Organisations with fewer than 250 employees are exempt unless the processing is likely to result in a risk, is not occasional, or involves special category or criminal offence data. See the Data Mapping and ROPA Guide.
- Representative
- A person or body established in the EU, designated in writing by a controller or processor outside the EU, who represents it on its GDPR obligations (GDPR Article 4). Needed when Article 3(2) brings a non-EU organisation into scope.
- Restriction of processing
- Marking stored personal data so its future processing is limited (GDPR Article 4). The right to restriction (Article 18) lets a person ask for data to be kept but not used, for example while accuracy is disputed.
- Retention schedule
- The documented list of how long each category of data is kept and what happens at the end. It is how storage limitation is put into practice. See the Data Retention and Disposal Policy Template.
- Right of access
- The right under GDPR Article 15 to confirm whether a controller processes your personal data and to receive a copy with supporting information. The most frequently exercised data subject right.
- Right to object
- The right under GDPR Article 21 to object to processing in certain circumstances, including processing based on legitimate interests or public interest, and to direct marketing.
- Special category data
- The personal data listed in GDPR Article 9(1): racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data used to uniquely identify a person, data concerning health, and data concerning sex life or sexual orientation. Processing is prohibited unless an Article 9 condition applies, in addition to a lawful basis. See the Special Category Data Guide.
- Standard contractual clauses (SCCs)
- Standard data protection clauses adopted by the European Commission, one of the appropriate safeguards listed in GDPR Article 46(2) for transfers to countries without an adequacy decision. They are signed between exporter and importer and are usually backed by a transfer impact assessment. See the Standard Contractual Clauses (SCCs) Guide.
- Storage limitation
- The GDPR principle that personal data must be kept in a form that permits identification for no longer than necessary for the purposes. Logs, backups and data lakes are where it is most often broken.
- Supervisory authority
- An independent public authority established by an EU member state to monitor application of the GDPR (Article 4, Article 51). Outside the EU the equivalent is often called a data protection authority or privacy regulator. See the Cyber and Privacy Regulator Directory.
T to Z
- Territorial scope
- Where the GDPR applies. Under Article 3(2) it reaches controllers and processors outside the EU when they process personal data of people in the Union in connection with offering them goods or services, or monitoring their behaviour within the Union. See the Global Privacy Regulatory Map.
- Third party
- A person or body other than the data subject, the controller, the processor and the people who, under their direct authority, are authorised to process personal data (GDPR Article 4).
- Transfer (international transfer)
- Making personal data available to an organisation in a country outside the GDPR area, including by remote access. GDPR Article 44 allows transfers only if the Chapter V conditions are met, so that the level of protection is not undermined. See China Cross-Border Data Transfers for a non-EU regime.
- Transfer impact assessment (TIA)
- A documented assessment of whether the law and practice of the destination country, especially public authority access, would undermine the safeguards used for a transfer, and what supplementary measures are needed. See the Transfer Impact Assessment (TIA) Template.
- Transfer mechanism
- The legal route that makes an international transfer lawful. Under the GDPR the options, in order, are an adequacy decision (Article 45), appropriate safeguards such as standard contractual clauses, binding corporate rules, codes of conduct or certification (Article 46), and, for specific situations only, derogations (Article 49). See SCCs vs Binding Corporate Rules.
- Transparency
- Part of the first GDPR principle (lawfulness, fairness and transparency): people must be told clearly and accessibly how their data is used. Articles 12 to 14 set out how and what. A system that collects data nobody was told about breaks it, whatever its security.
- Universal opt-out mechanism
- A browser or device signal, such as Global Privacy Control, that several US state privacy laws require businesses to honour as a request to opt out of sale, sharing or targeted advertising. See the Universal Opt-Out Mechanism Laws Guide.
Standards and references
- EUR-Lex: Regulation (EU) 2016/679, General Data Protection Regulation.
- ICO: Personal data breaches, a guide.
- ICO: What needs to be included in the contract.
- ISO: ISO/IEC 27701:2025 Privacy information management systems.
- NIST: SP 800-226 Guidelines for Evaluating Differential Privacy Guarantees.
- CIS: Control 3 Data Protection.
For identity and machine identity terms, see the NHI and IAM Glossary. Related NHI Mgmt Group resources: Privacy Programme Guide for Security Teams · UK GDPR and Data Protection Act 2018 Guide · GRC and Cyber Compliance Glossary · Agentic AI Glossary