mukul975 avatar

data-subject-rights-skills

15 DSAR and data subject rights skills: access, erasure, portability, rectification, objection, opt-out signals

version
1.0.0
GitHub stars
340

Install

/plugin install data-subject-rights-skills@privacy-data-protection-skills

Run it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.

Contents

Discovered from source

Skills 15

Managing Automated Decision-Making and Profiling Rights

Overview

GDPR Article 22 provides data subjects with the right not to be subject to decisions based solely on automated processing, including profiling, which produce legal effects concerning them or similarly significantly affect them. This skill covers the identification of automated decision-making, implementation of meaningful human intervention, explanation of logic, and contestation procedures.

Legal Foundation

GDPR Article 22 — Automated Individual Decision-Making, Including Profiling

  1. Art. 22(1) — The data subject has the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning them or similarly significantly affects them.

  2. Art. 22(2) — Exceptions: Art. 22(1) does not apply if the decision:

    • (a) is necessary for entering into, or performance of, a contract between the data subject and the controller
    • (b) is authorised by Union or Member State law which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests
    • (c) is based on the data subject's explicit consent
  3. Art. 22(3) — Where exceptions (a) or (c) apply, the controller must implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to:

    • Obtain human intervention on the part of the controller
    • Express their point of view
    • Contest the decision
  4. Art. 22(4) — Decisions under Art. 22(2) shall not be based on special categories of data under Art. 9(1) unless Art. 9(2)(a) or (g) applies and suitable measures to safeguard the data subject's rights and freedoms and legitimate interests are in place.

Definition of Profiling (Art. 4(4))

"Profiling" means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location, or movements.

EDPB Guidelines on Automated Decision-Making and Profiling (WP251 rev.01)

The Article 29 Working Party (now EDPB) Guidelines adopted on 6 February 2018 provide authoritative interpretation, distinguishing:

  • Simple profiling: Automated processing to classify individuals (e.g., marketing segmentation) — may not trigger Art. 22 if no legal/significant effect.
  • Profiling-based decision: Using profiling output to make a decision about an individual — triggers Art. 22 if solely automated with legal/significant effect.
  • Solely automated decision with profiling: Full Art. 22 scope — e.g., automated credit scoring leading to loan rejection.

Identifying Art. 22 Decisions

Assessment Criteria

For each automated processing activity, assess:

  1. Is the decision solely automated? No meaningful human intervention in the decision process. Per WP251 rev.01, human involvement must be more than a rubber stamp — the reviewer must have authority, competence, and genuinely consider the automated output before reaching their own decision.

  2. Does the decision produce legal effects? Examples: denial of a loan application, termination of a contract, refusal of social security benefit, denial of entry to a country.

  3. Does the decision similarly significantly affect the data subject? Examples: automatic rejection of an online credit application, automated recruitment screening that excludes candidates, differential pricing that materially affects purchasing power, automated insurance risk assessment resulting in premium increases exceeding 20%.

Meridian Analytics Ltd — Automated Processing Inventory

Processing ActivitySolely AutomatedLegal/Significant EffectArt. 22 AppliesException
Client risk scoring for onboardingYesYes — determines service accessYesArt. 22(2)(a) — Necessary for contract
Anomaly detection in usage patternsYesNo — triggers human review onlyNoN/A
Automated invoice processingYesNo — administrative functionNoN/A
Marketing segment assignmentYesNo — does not produce legal or similarly significant effectsNoN/A
Fraud probability scoringYesYes — may result in account suspensionYesArt. 22(2)(a) — Necessary for contract

Human Intervention Requirements

Meaningful Human Oversight Standard

Per WP251 rev.01, paragraph 21, human intervention must meet all of the following criteria:

  1. Authority: The reviewer has the organisational authority to alter or override the automated decision.
  2. Competence: The reviewer has the technical understanding and domain knowledge to evaluate the automated output, including awareness of the model's limitations and error rates.
  3. Genuine consideration: The reviewer actually analyses the automated output and the data subject's specific circumstances, rather than routinely endorsing the automated recommendation.

Implementation at Meridian Analytics Ltd

For each Art. 22 decision:

  1. Designated reviewers: Assign trained staff (minimum 2 per decision type) with explicit authority to override automated outcomes.
  2. Review interface: Provide a dashboard displaying:
    • The automated decision and confidence score
    • Key input factors and their contribution to the decision
    • Historical accuracy rate of the model for similar cases
    • Data subject's profile summary
    • Override history for similar decisions
  3. Review SLA: All Art. 22 decisions must be reviewed within 48 hours of the automated output.
  4. Override documentation: Every override must be documented with the reviewer's name, date, reasoning, and alternative outcome.
  5. Quarterly audit: Review override rates, reviewer engagement metrics, and outcome distributions to verify meaningful human involvement.

Logic Explanation Requirements

What Must Be Explained (Art. 15(1)(h))

When a data subject exercises their right of access regarding automated decision-making, the controller must provide:

  1. The existence of the automated decision: Confirm that automated decision-making, including profiling, is taking place.
  2. Meaningful information about the logic involved: Not the source code or algorithm weights, but a functional description that a non-technical person can understand:
    • What data inputs are used
    • How those inputs are weighted or combined
    • What thresholds or rules determine the outcome
    • General accuracy and error rates
  3. The significance and envisaged consequences: What the decision means for the data subject in practical terms.

Example Logic Explanation — Client Risk Scoring

"Meridian Analytics Ltd uses an automated risk scoring system to assess new client applications. The system evaluates the following factors:

  • Company registration data: Age of the company, registered jurisdiction, and filing history (weighted approximately 30% of the overall score).
  • Financial indicators: Reported revenue, credit reference agency data, and payment history from public sources (weighted approximately 40%).
  • Industry risk classification: The sector in which the applicant operates, mapped against a regulatory risk index (weighted approximately 20%).
  • Behavioural signals: Patterns in the application process itself, such as consistency of provided information (weighted approximately 10%).

The system produces a risk score from 0 to 100. Applications scoring below 35 are automatically flagged for enhanced due diligence review by a human analyst. Applications scoring below 15 are automatically declined, subject to review by a Senior Compliance Analyst within 48 hours.

This system has an overall accuracy rate of 91.3% based on quarterly validation against actual client outcomes. The false positive rate (incorrectly flagging low-risk clients as high-risk) is 6.2%, and the false negative rate (failing to flag genuinely high-risk clients) is 2.5%.

If your application is declined or flagged, you have the right to request human review, express your point of view, and contest the decision."

Contestation Mechanism

Step 1: Receive Contestation

  1. Log with reference ADM-YYYY-NNNN.
  2. Record: the automated decision contested, the data subject's grounds for contestation, and any additional information provided.

Step 2: Assign Human Reviewer

  1. Assign a reviewer who was NOT involved in the original automated decision.
  2. The reviewer must have authority, competence, and independence.
  3. Provide the reviewer with:
    • The original automated decision and its basis
    • The data subject's contestation and supporting information
    • Relevant data inputs and model outputs
    • Historical precedents for similar contestations

Step 3: Review and Decide

  1. The reviewer must genuinely reconsider the decision on its merits.
  2. The reviewer may:
    • Uphold the original automated decision (with documented reasoning)
    • Modify the decision (partially or fully in the data subject's favour)
    • Overturn the decision entirely
  3. Document the review outcome with full reasoning.

Step 4: Communicate the Outcome

  1. Notify the data subject within 30 calendar days of the contestation.
  2. The notification must include:
    • The outcome of the review
    • The reasoning behind the decision
    • If the decision is upheld: the data subject's right to lodge a complaint with the supervisory authority (Art. 77) and seek a judicial remedy (Art. 79)
    • If the decision is modified or overturned: the practical next steps

Step 5: Systemic Review

  1. Log the contestation outcome for model monitoring purposes.
  2. If contestation rates exceed 10% for any decision type in a quarter, trigger a model review.
  3. If overturn rates exceed 15%, escalate to the Data Protection Officer for assessment of whether the model requires retraining or decommissioning.

Managing CCPA Consumer Requests

Overview

The California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), grants California consumers specific rights regarding their personal information. This skill provides the operational workflow for handling CCPA consumer requests, including the right to know, right to delete, right to correct, right to opt-out of sale/sharing, and the right to limit use of sensitive personal information.

Legal Foundation

CCPA / CPRA Core Provisions

Right to Know (Cal. Civ. Code Section 1798.100, 1798.110, 1798.115)

Consumers have the right to request that a business disclose:

  • The categories of personal information collected (Section 1798.110(a)(1))
  • The categories of sources from which personal information is collected (Section 1798.110(a)(2))
  • The business or commercial purpose for collecting, selling, or sharing personal information (Section 1798.110(a)(3))
  • The categories of third parties to whom personal information is disclosed (Section 1798.110(a)(4))
  • The specific pieces of personal information the business has collected about the consumer (Section 1798.110(a)(5))
Right to Delete (Cal. Civ. Code Section 1798.105)

Consumers have the right to request that a business delete any personal information about the consumer which the business has collected. The business must delete the consumer's personal information from its records, notify service providers and contractors to delete, and notify third parties who purchased or received the information to delete.

Exceptions to deletion (Section 1798.105(d)):

  1. Complete a transaction or provide a requested service
  2. Detect security incidents or protect against fraud
  3. Debug to identify and repair errors
  4. Exercise free speech or another legal right
  5. Comply with the California Electronic Communications Privacy Act
  6. Engage in research in the public interest (with consumer consent)
  7. Enable solely internal uses reasonably aligned with consumer expectations
  8. Comply with a legal obligation
  9. Otherwise use the information internally in a lawful manner compatible with collection context
Right to Opt-Out of Sale/Sharing (Cal. Civ. Code Section 1798.120, 1798.135)

Consumers have the right to direct a business that sells or shares their personal information to third parties to stop selling or sharing that personal information. A business must provide a clear and conspicuous "Do Not Sell or Share My Personal Information" link on its website.

Right to Non-Discrimination (Cal. Civ. Code Section 1798.125)

A business shall not discriminate against a consumer because the consumer exercised any of their CCPA rights, including by:

  • Denying goods or services
  • Charging different prices or rates
  • Providing a different level or quality of goods or services
  • Suggesting the consumer will receive different treatment
Right to Correct (Cal. Civ. Code Section 1798.106)

Added by CPRA: consumers have the right to request correction of inaccurate personal information.

Right to Limit Use of Sensitive Personal Information (Cal. Civ. Code Section 1798.121)

Added by CPRA: consumers have the right to limit a business's use of their sensitive personal information to purposes necessary to perform the services or provide the goods requested.

CCPA Consumer Request Workflow

Step 1: Receive the Request

CCPA requires at least two methods for submitting requests:

  • Toll-free telephone number
  • Website form or email address
  • If the business operates exclusively online, only the email method is required
  1. Log with reference CCPA-YYYY-NNNN.
  2. Record the request type (know, delete, correct, opt-out, limit).
  3. Record the channel of receipt.
  4. Acknowledge receipt within 10 business days.

Step 2: Verify the Consumer's Identity

CCPA regulations (11 CCR Section 7060-7064) require verification proportional to the type of request:

Request TypeVerification StandardMethod
Right to know — categoriesReasonable degree of certaintyMatch at least 2 data points (name + email, name + account number)
Right to know — specific piecesReasonably high degree of certaintyMatch at least 3 data points + signed declaration under penalty of perjury
Right to deleteReasonable degree of certaintyMatch at least 2 data points
Right to correctReasonable degree of certaintyMatch at least 2 data points
Right to opt-out of saleNo verification required (unless fraudulent)Confirm association with the business

If the consumer has a password-protected account, the business may verify through the existing authentication process.

Step 3: Process the Request

Right to Know
  1. Identify all personal information collected in the preceding 12 months.
  2. Compile response organised by CCPA categories:
    • Identifiers (name, address, email, SSN, driver's licence, passport, IP address, account name)
    • Customer records (financial information, insurance, education, employment)
    • Protected classification characteristics (age, race, sex, religion, disability)
    • Commercial information (purchase history, consumption tendencies)
    • Biometric information
    • Internet or other electronic network activity (browsing history, search history, interaction with website/app)
    • Geolocation data
    • Audio, electronic, visual, thermal, olfactory, or similar information
    • Professional or employment-related information
    • Education information (non-FERPA)
    • Inferences drawn from the above to create a consumer profile
    • Sensitive personal information (SSN, financial account, precise geolocation, racial/ethnic origin, religious beliefs, health data, sex life/orientation)
  3. Disclose the categories of sources, business purposes, and third parties for each category.
Right to Delete
  1. Verify the request per Step 2.
  2. Assess whether any exceptions under Section 1798.105(d) apply.
  3. If no exception, delete personal information from all systems.
  4. Notify service providers and contractors to delete.
  5. Notify third parties who purchased or received the information to delete.
Right to Opt-Out of Sale/Sharing
  1. No identity verification required (process immediately).
  2. Cease selling and sharing the consumer's personal information within 15 business days.
  3. Do not sell/share for at least 12 months unless consumer provides subsequent authorization.
  4. Apply to all future sale/sharing activities.

Step 4: Respond to the Consumer

Request TypeResponse DeadlineFormat
Right to know45 calendar days (extendable by 45 additional days with notice)Written (email or postal), in a portable and readily useable format
Right to delete45 calendar days (extendable by 45 additional days)Written confirmation
Right to correct45 calendar days (extendable by 45 additional days)Written confirmation
Right to opt-out15 business daysWritten confirmation
Right to limit sensitive PI15 business daysWritten confirmation

Step 5: Document and Retain

  1. Record the request, verification process, response, and outcome.
  2. Retain records for 24 months per CCPA regulations (11 CCR Section 7101).
  3. If the business receives 10 million or more consumer records annually, compile and publish annual metrics (number of requests received, complied with, denied, median response time).

Non-Discrimination Requirements

When a consumer exercises any CCPA right, the business must not:

  • Deny goods or services
  • Charge different prices (unless reasonably related to the value provided by the consumer's data)
  • Provide a different level or quality of goods or services
  • Suggest the consumer will receive a different price or quality

Financial incentive programmes (e.g., loyalty programmes) must be disclosed in the privacy notice and require consumer opt-in consent. The incentive must be reasonably related to the value of the consumer's data.

Implementing CPRA Opt-Out Preference Signals

Overview

CPRA Section 1798.135 requires businesses to treat opt-out preference signals (such as Global Privacy Control / GPC) as valid consumer requests to opt out of the sale and sharing of personal information. This skill covers the technical detection of GPC signals, automated honoring workflows, cross-device consistency requirements, and the interaction between browser-level signals and explicit consumer choices.

Legal Foundation

CPRA Section 1798.135 — Methods of Limiting Sale, Sharing, and Use

  1. Section 1798.135(a) — A business that sells or shares consumers' personal information shall provide a clear and conspicuous link on its homepage titled "Do Not Sell or Share My Personal Information."

  2. Section 1798.135(b)(1) — A business that sells or shares personal information shall treat the consumer's use of an opt-out preference signal as a valid request to opt out under Section 1798.120.

  3. Section 1798.135(b)(3) — A business that complies with subsection (b)(1) is not required to post the "Do Not Sell or Share My Personal Information" link on its homepage, provided it instead posts a link to a page describing the consumer's opt-out rights.

  4. Section 1798.135(e) — A business may not interpret the absence of an opt-out preference signal as consent to sell or share personal information.

CCPA Regulations (11 CCR Section 7025)

  • Section 7025(a) — A business shall process an opt-out preference signal as a valid request to opt out of sale/sharing for that browser or device, and, if known, the consumer.
  • Section 7025(b) — If the business is unable to identify the consumer, the opt-out shall apply to the browser or device from which the signal was sent.
  • Section 7025(c) — The business shall not require the consumer to provide additional information to opt out via a preference signal, unless necessary to verify the consumer's identity.
  • Section 7025(d) — If a conflict exists between the opt-out preference signal and a consumer's business-specific privacy setting, the business shall process the opt-out preference signal but may notify the consumer of the conflict and provide the consumer the opportunity to confirm their intention.

Global Privacy Control (GPC) Specification

GPC is an HTTP header and JavaScript API signal that communicates a user's privacy preferences:

  • HTTP header: Sec-GPC: 1
  • JavaScript API: navigator.globalPrivacyControl === true
  • DNT header: GPC is distinct from the deprecated Do Not Track (DNT) header. GPC has legal effect under CPRA and Colorado Privacy Act; DNT does not.

Technical Implementation

Step 1: Detect the GPC Signal

Server-Side Detection

Check for the GPC HTTP header on every incoming request:

HTTP Header: Sec-GPC: 1

If the header is present and its value is 1, the user has activated GPC.

Client-Side Detection (JavaScript)

For single-page applications or client-side consent management:

if (navigator.globalPrivacyControl === true) {
    // GPC signal detected — treat as opt-out of sale/sharing
}

Step 2: Map GPC Signal to Consumer

ScenarioAction
Consumer is logged in (authenticated)Apply opt-out to the consumer's account across all devices
Consumer is not logged in but has cookiesApply opt-out to the browser/device
Consumer is anonymous (no identification)Apply opt-out to the current browsing session and device

Step 3: Automated Honoring

When a GPC signal is detected, the following actions must be executed automatically:

  1. Suppress third-party tracking scripts: Do not load advertising pixels, third-party analytics trackers, or cross-site tracking scripts.
  2. Disable advertising cookies: Do not set or read cookies used for targeted advertising or cross-context behavioral advertising.
  3. Exclude from data sharing: Do not include the user's data in any data-sharing arrangements with third parties for advertising or monetisation purposes.
  4. Exclude from sale: Do not sell the user's personal information to any third party.
  5. Update consent management platform: Set the user's sale/sharing preference to "opted-out" in the CMP.

Step 4: Consent Management Platform (CMP) Integration

The CMP must be configured to:

  1. Detect GPC on page load: Before any third-party scripts are loaded.
  2. Suppress consent banner sale/sharing options: If GPC is detected, automatically set the sale/sharing toggle to "opted-out" and suppress any request for consent to sell/share.
  3. Allow explicit re-consent: If the consumer explicitly chooses to opt back in through the business's privacy settings, this explicit choice overrides the GPC signal for that business only.
  4. Log the signal: Record the GPC signal detection for compliance audit purposes.

Step 5: Cross-Device Consistency

Consumer StatusCross-Device Behaviour
Authenticated (logged-in account)GPC signal from one device triggers account-level opt-out across all devices
UnauthenticatedGPC signal applies only to the device/browser from which it was sent
Consumer later logs in from GPC-enabled deviceAccount-level opt-out is applied retroactively

Step 6: Conflict Resolution

When a conflict exists between the GPC signal and the consumer's explicit business-specific setting:

[GPC Signal Detected: Opt-Out]
         │
         ▼
[Does consumer have an explicit business-specific setting?]
   │
   ├── No explicit setting ──► Honor GPC signal (opt-out)
   │
   ├── Explicit opt-in to sale/sharing ──► [Conflict]
   │     └── Honor GPC signal (opt-out applies)
   │         Optionally: display notification
   │         "Your browser is sending a Global Privacy Control signal.
   │          We have applied this as an opt-out of sale/sharing.
   │          You previously opted in to sale/sharing on this site.
   │          If you wish to maintain your opt-in, please confirm
   │          in your privacy settings."
   │
   └── Explicit opt-out ──► No conflict (both agree on opt-out)

Step 7: Documentation and Audit

  1. Log every GPC signal detection with timestamp, IP hash, device identifier, and authenticated status.
  2. Log every opt-out action taken in response to a GPC signal.
  3. Maintain records for 24 months per CCPA regulation requirements.
  4. Include GPC signal handling in quarterly privacy compliance audits.
  5. Test GPC detection quarterly using browsers with GPC enabled (Firefox, Brave, DuckDuckGo).

Monitoring and Testing

Monthly Verification Checklist

  • GPC header detection confirmed operational (test with Sec-GPC: 1)
  • JavaScript API detection confirmed operational (test with navigator.globalPrivacyControl)
  • Third-party tracking scripts are suppressed when GPC is detected
  • Advertising cookies are not set when GPC is detected
  • CMP correctly reflects GPC opt-out status
  • Cross-device consistency confirmed for authenticated users
  • Conflict resolution functioning as designed
  • Audit logs recording GPC detections

Executing Data Portability Requests

Overview

The right to data portability under GDPR Article 20 allows data subjects to receive their personal data in a structured, commonly used, and machine-readable format, and to transmit that data to another controller without hindrance. This skill provides the complete workflow for assessing scope, extracting data, formatting output, and facilitating direct transfers.

Legal Foundation

GDPR Article 20 — Right to Data Portability

  1. Art. 20(1) — The data subject has the right to receive the personal data concerning them, which they have provided to a controller, in a structured, commonly used and machine-readable format, and has the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, where:

    • (a) the processing is based on consent under Art. 6(1)(a) or Art. 9(2)(a), or on a contract under Art. 6(1)(b); AND
    • (b) the processing is carried out by automated means.
  2. Art. 20(2) — The data subject has the right to have the personal data transmitted directly from one controller to another, where technically feasible.

  3. Art. 20(3) — The exercise of portability shall not adversely affect the rights and freedoms of others.

  4. Art. 20(4) — The right to portability shall not apply to processing necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.

Scope: What Data Is Portable

Per EDPB (formerly WP29) Guidelines on the right to data portability (WP242 rev.01), portable data includes:

  1. Data provided by the data subject: Information actively and knowingly provided (e.g., account details, form submissions, uploaded content).
  2. Observed data: Data generated by the data subject's activity (e.g., search history, location data, activity logs, raw sensor data from connected devices).
  3. NOT included — Inferred or derived data: Data created by the controller through analysis (e.g., credit scores, profiling segments, algorithmic assessments). These are the controller's intellectual output.

Legal Basis Filter

Portability applies ONLY where the legal basis for processing is:

  • Art. 6(1)(a) — Consent
  • Art. 9(2)(a) — Explicit consent (for special category data)
  • Art. 6(1)(b) — Performance of a contract

Portability does NOT apply to data processed under:

  • Art. 6(1)(c) — Legal obligation
  • Art. 6(1)(d) — Vital interests
  • Art. 6(1)(e) — Public interest / official authority
  • Art. 6(1)(f) — Legitimate interests

Portability Request Workflow

Step 1: Receive and Validate the Request

  1. Log the request with reference PORT-YYYY-NNNN.
  2. Verify the requester's identity (tiered verification as per DSAR process).
  3. Determine whether the request is for:
    • (a) Self-export: Data subject wants to receive their data directly.
    • (b) Direct transfer: Data subject wants data transmitted to another controller.
  4. If direct transfer, obtain the receiving controller's details:
    • Organisation name and registered address
    • Technical contact email
    • API endpoint or secure transfer mechanism (if available)
    • Data format preference

Step 2: Scope Assessment

  1. Identify all personal data the subject has provided or that has been observed through their use of the service.
  2. Filter by legal basis — include only data processed under consent (Art. 6(1)(a)/Art. 9(2)(a)) or contract (Art. 6(1)(b)).
  3. Exclude inferred or derived data (profiling scores, analytics outputs, internal assessments).
  4. Exclude data that would adversely affect the rights and freedoms of others (Art. 20(3)) — redact third-party personal data from exported datasets.
  5. Confirm that processing is carried out by automated means (manual paper files are excluded).

Step 3: Data Extraction

  1. Query all relevant systems for the in-scope data:
    • Customer account database
    • Transaction/order history
    • User-generated content (uploads, posts, messages authored by the subject)
    • Service interaction logs (observed data)
    • Preference and settings data
    • Connected device data (if applicable)
  2. Apply the scope filter from Step 2.
  3. De-duplicate records across systems.
  4. Validate data integrity (checksums, record counts).

Step 4: Format the Data

Meridian Analytics Ltd supports the following machine-readable formats:

FormatMIME TypeUse CaseSchema
JSONapplication/jsonDefault — structured, widely supportedSchema documented in API specification
CSVtext/csvTabular data, spreadsheet-compatibleHeader row with field names, UTF-8 encoding, RFC 4180 compliant
XMLapplication/xmlEnterprise integration, legacy systemsXSD schema provided with export

Format selection priority:

  1. If the data subject specified a preferred format, use it (if supported).
  2. If the receiving controller specified a format, use it.
  3. Default to JSON.

Data packaging:

  • Each data category is exported as a separate file (e.g., account_data.json, transactions.csv, content_uploads.json).
  • A manifest file (manifest.json) lists all included files, record counts, date ranges, and checksums.
  • Files are packaged into a single ZIP archive with AES-256 encryption.

Step 5: Execute Direct Transfer (If Applicable)

If the data subject requested direct controller-to-controller transfer under Art. 20(2):

  1. Verify the receiving controller's identity and authorisation.
  2. Establish a secure transfer channel:
    • Option A — API transfer: If the receiving controller provides an API endpoint, transmit via HTTPS with mutual TLS authentication.
    • Option B — SFTP transfer: Establish an SFTP connection with SSH key authentication.
    • Option C — Secure file exchange: Upload the encrypted archive to a secure portal and provide time-limited access credentials to the receiving controller.
  3. Obtain transfer confirmation (HTTP 200/201 response, SFTP receipt confirmation, or download confirmation).
  4. If direct transfer is not technically feasible, notify the data subject and provide the data directly to them instead, per Art. 20(2).

Step 6: Deliver to Data Subject (Self-Export)

  1. Upload the encrypted archive to the secure download portal.
  2. Send notification to the data subject with:
    • Secure download link (72-hour expiry)
    • Decryption password (sent via separate channel — SMS or secondary email)
    • Manifest summary (file list, record counts)
    • Instructions for opening the archive
  3. Record the delivery confirmation.

Step 7: Close and Document

  1. Update the portability request register with:
    • Completion date
    • Data categories exported
    • Format used
    • Transfer method (self-export or direct transfer)
    • Recipient controller (if direct transfer)
  2. Retain the processing record for 3 years.
  3. The export does NOT require deletion of the original data — portability is an additional right, not a replacement for erasure.

Response Timeline

  • Standard deadline: 30 calendar days from receipt of the request.
  • Extension: Up to 60 additional days for complex requests (Art. 12(3)).
  • No fee: The first copy must be provided free of charge. Additional copies may incur a reasonable fee under Art. 12(5).

Providing Direct Collection Information

Overview

GDPR Article 13 requires controllers to provide specific information to data subjects at the time personal data is collected directly from them. This information must be provided at the point of collection, not afterwards. This skill provides the complete checklist of required elements, guidance on layered notice design, and templates for common collection scenarios.

Legal Foundation

GDPR Article 13 — Information to Be Provided Where Personal Data Are Collected from the Data Subject

Art. 13(1) — First Layer (Mandatory at Point of Collection)

Where personal data relating to a data subject are collected from the data subject, the controller shall, at the time when personal data are obtained, provide the data subject with all of the following information:

ElementArticleDescription
Controller identityArt. 13(1)(a)Identity and contact details of the controller and, where applicable, of the controller's representative
DPO contactArt. 13(1)(b)Contact details of the data protection officer, where applicable
Purposes and legal basisArt. 13(1)(c)The purposes of the processing and the legal basis under Art. 6
Legitimate interestsArt. 13(1)(d)Where processing is based on Art. 6(1)(f), the legitimate interests pursued by the controller or by a third party
RecipientsArt. 13(1)(e)The recipients or categories of recipients of the personal data, if any
International transfersArt. 13(1)(f)Where applicable, that the controller intends to transfer data to a third country or international organisation, the existence or absence of an adequacy decision, or reference to appropriate safeguards and means of obtaining a copy or where they have been made available
Art. 13(2) — Second Layer (Necessary for Fair Processing)

In addition to the information referred to in paragraph 1, the controller shall, at the time when personal data are obtained, provide the data subject with the following further information necessary to ensure fair and transparent processing:

ElementArticleDescription
Retention periodArt. 13(2)(a)The period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period
Data subject rightsArt. 13(2)(b)The existence of the right to request access, rectification, erasure, restriction, object, and portability
Right to withdraw consentArt. 13(2)(c)Where processing is based on Art. 6(1)(a) or Art. 9(2)(a), the right to withdraw consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal
Right to complainArt. 13(2)(d)The right to lodge a complaint with a supervisory authority
Statutory/contractual requirementArt. 13(2)(e)Whether the provision of personal data is a statutory or contractual requirement, or a requirement necessary to enter into a contract, and whether the data subject is obliged to provide the data and the possible consequences of failure to provide
Automated decision-makingArt. 13(2)(f)The existence of automated decision-making including profiling, meaningful information about the logic, significance, and envisaged consequences
Further processingArt. 13(2)(g)Where the controller intends to further process for a purpose other than the original, provide information on that other purpose and any relevant further information under Art. 13(2)

Timing (Art. 13(1) First Sentence)

All Art. 13 information must be provided at the time when personal data are obtained — before or at the moment of collection, not after.

Exemption (Art. 13(4))

Art. 13(1)-(3) shall not apply where and insofar as the data subject already has the information.

Layered Notice Design for Direct Collection

Principle

The EDPB Guidelines on Transparency (WP260 rev.01) recommend a layered approach for direct collection to balance completeness with usability:

Layer 1: Just-In-Time Notice

Displayed directly at the point of data collection (e.g., on the form, above the submit button, within the app screen):

Required elements at minimum:

  1. Controller identity (name)
  2. Each specific purpose for which data is being collected
  3. Any processing that may be unexpected or objectionable
  4. Link to the full privacy notice (Layer 2)

Format guidance:

  • Maximum 150 words
  • Visible without scrolling on the collection interface
  • No click-through required to see the core information
  • Use icons where appropriate (per Art. 12(7))

Layer 2: Full Privacy Notice

Linked from Layer 1, containing ALL Art. 13(1)(a)-(f) and Art. 13(2)(a)-(g) elements.

Layer 3: Detailed Supplementary Information

Available on request or via contextual links:

  • Full legitimate interest assessments
  • Complete international transfer mechanism documentation
  • Detailed automated decision-making logic explanations

Collection Scenario Templates

Scenario 1: Online Registration Form

Collection point: Account registration page Data collected: Name, email, password, company name, job title Purpose: Account creation and service provision

Just-in-time notice text:

Meridian Analytics Ltd will use the information you provide to create and manage your account and deliver our analytics services. We may also use your email to send you service-related communications. Read our full privacy notice for details on how we use your data, who we share it with, and your rights.

Scenario 2: Newsletter Signup

Collection point: Newsletter subscription form Data collected: Email address, name (optional) Purpose: Marketing communications

Just-in-time notice text:

By subscribing, you consent to Meridian Analytics Ltd sending you marketing emails about our products and services. You can unsubscribe at any time by clicking the link in any email. We will not share your email address with third parties for marketing. Read our full privacy notice.

Scenario 3: Contact Form / Support Request

Collection point: Contact us / support form Data collected: Name, email, company, message content Purpose: Responding to enquiry

Just-in-time notice text:

Meridian Analytics Ltd will use the details you provide to respond to your enquiry. We will retain your message for 3 years to maintain service quality. Read our full privacy notice.

Scenario 4: Event Registration

Collection point: Event/webinar registration form Data collected: Name, email, company, dietary requirements (if in-person) Purpose: Event management and follow-up

Just-in-time notice text:

Meridian Analytics Ltd will use your details to manage your event registration and send you event-related communications. If you provide dietary requirements, this information will be processed under your explicit consent and shared only with the catering provider for this event. Read our full privacy notice.

Compliance Checklist

For every new data collection point, verify:

  • Art. 13(1)(a): Controller name and contact details displayed
  • Art. 13(1)(b): DPO contact details accessible (directly or via link to full notice)
  • Art. 13(1)(c): Each purpose and legal basis stated
  • Art. 13(1)(d): Legitimate interests specified (if Art. 6(1)(f) relied upon)
  • Art. 13(1)(e): Recipients identified (directly or via link to full notice)
  • Art. 13(1)(f): International transfer information provided (if applicable)
  • Art. 13(2)(a): Retention period or criteria stated
  • Art. 13(2)(b): Data subject rights listed with exercise mechanism
  • Art. 13(2)(c): Right to withdraw consent stated (if consent-based)
  • Art. 13(2)(d): Right to complain to ICO stated
  • Art. 13(2)(e): Whether provision is required and consequences of non-provision
  • Art. 13(2)(f): Automated decision-making disclosure (if applicable)
  • Information provided at or before the moment of collection
  • Layered approach: just-in-time notice + link to full notice
  • Language is clear, plain, and appropriate for the audience
  • Notice is visible without requiring additional clicks or scrolling

Building a Universal DSAR Intake System

Overview

A universal DSAR intake system centralises the receipt, verification, routing, and tracking of all data subject rights requests across multiple channels. This skill provides the architectural design, identity verification framework, routing logic, SLA management, and response generation capabilities needed to operate a compliant and efficient rights request management programme.

System Architecture

Multi-Channel Intake

The intake system must accept requests from all channels through which data subjects may contact the organisation:

ChannelIntake MethodProcessing
Web formDedicated privacy rights portal at meridiananalytics.co.uk/privacy/rightsAutomated capture, structured data, immediate acknowledgement
Emaildsar@meridiananalytics.co.uk (dedicated monitored inbox)Semi-automated: email parser extracts key fields, manual triage
TelephonePrivacy hotline: +44 20 7946 0958 (staffed Mon-Fri 09:00-17:00 GMT)Agent-assisted: agent completes intake form during call
Postal mailData Protection Office, 47 Canary Wharf Tower, London E14 5ABManual: scanned, digitised, entered into system within 2 business days
In-personReception desk at registered officeAgent-assisted: staff member completes intake form
Social mediaDirect messages on official channelsRedirect to formal channel; do not process rights requests via social media

Central Request Register

All requests from all channels feed into a single central register with the following record structure:

FieldDescription
ReferenceAuto-generated: [TYPE]-YYYY-NNNN (e.g., DSAR-2026-0142)
Receipt dateUTC timestamp of initial receipt
ChannelSource channel
Request typeAccess (Art. 15), Erasure (Art. 17), Portability (Art. 20), Restriction (Art. 18), Rectification (Art. 16), Object (Art. 21), Marketing opt-out (Art. 21(2)), Automated decision (Art. 22), CCPA know, CCPA delete, CCPA opt-out
Data subject nameAs provided by requester
Data subject identifiersEmail, account number, other identifiers provided
Verification statusPending / Verified / Failed
Verification tierLow / Medium / High
AssigneePrivacy team member responsible
PriorityStandard / Complex / Urgent
StatusReceived / Acknowledged / Verifying / Processing / QA Review / Delivered / Closed
DeadlineCalculated response deadline
ExtensionWhether extension has been applied
NotesFree text for processing notes

Identity Verification Framework

Tiered Verification

TierWhen AppliedRequirementsClock Behaviour
Tier 1 — Low RiskRequest from authenticated account (logged-in portal, verified email)Confirm account ownership via existing authenticationClock starts immediately
Tier 2 — Medium RiskRequest from known email address (matches records) but not authenticatedProvide 2 of: date of birth, account number, postal code, last 4 digits of payment methodClock starts on verification
Tier 3 — High RiskRequest from unknown channel, or request on behalf of another personGovernment-issued photo ID + one additional identifier. Third-party requests: signed authorisation from data subject + ID for bothClock starts on verification

Verification Workflow

[Request Received]
         │
         ▼
[Determine Verification Tier]
   │
   ├── Authenticated channel? ──► Tier 1 (auto-verified)
   ├── Known identifier matches? ──► Tier 2 (request 2 data points)
   └── Unknown channel / third party? ──► Tier 3 (request ID + authorisation)
         │
         ▼
[Verification Request Sent (within 3 business days)]
         │
         ▼
[Verification Response Received?]
   ├── Yes ──► [Data Points Match?]
   │             ├── Yes ──► Mark Verified, start clock
   │             └── No ──► Request additional info (one retry)
   │                          ├── Second attempt matches ──► Verified
   │                          └── Second attempt fails ──► Close as Unverified
   │
   └── No response (30 days) ──► Close as Abandoned

Routing Logic

Automated Request Classification

Upon intake, the system classifies and routes requests based on:

  1. Request type (extracted from web form selection or email keywords):

    • Access/DSAR → DSAR team
    • Erasure/Deletion → Erasure team
    • Portability/Export → Portability team
    • Marketing opt-out → Marketing Operations (immediate processing)
    • CCPA requests → US Privacy team
    • Regulatory complaint → DPO + Legal
  2. Complexity assessment:

    • Standard: single request type, single jurisdiction, < 5 data systems
    • Complex: multiple request types, cross-border, > 5 data systems, or involving exemptions
    • Urgent: regulatory enquiry, legal deadline, or data subject facing imminent harm
  3. Jurisdiction detection:

    • UK/EU data subject → GDPR workflow (30-day deadline)
    • California resident → CCPA workflow (45-day deadline)
    • Other US state → Applicable state privacy law workflow
    • Other jurisdiction → Assess applicable law, default to GDPR standard

Routing Matrix

Request TypeAssigneePrioritySLA
DSAR (Art. 15) — StandardPrivacy AnalystStandard30 days
DSAR (Art. 15) — ComplexSenior Privacy AnalystComplex30 days (extendable to 90)
Erasure (Art. 17)Privacy AnalystStandard30 days
Portability (Art. 20)Data Engineer + Privacy AnalystStandard30 days
Rectification (Art. 16)Privacy AnalystStandard30 days
Restriction (Art. 18)Senior Privacy AnalystStandard30 days + 72h implementation
Object (Art. 21)DPOComplex30 days + immediate cessation
Marketing opt-out (Art. 21(2))Marketing OperationsUrgent24 hours
Automated decision (Art. 22)DPO + Technical LeadComplex30 days
CCPA KnowPrivacy AnalystStandard45 days
CCPA DeletePrivacy AnalystStandard45 days
CCPA Opt-OutMarketing OperationsUrgent15 business days
Regulatory complaintDPO + General CounselUrgentPer DPA deadline

SLA Tracking

Dashboard Metrics

MetricTargetMeasurement
Acknowledgement within 3 business days100%(Acknowledged requests / Total requests) within 3 business days
Response within statutory deadline100%(On-time responses / Total responses)
Average response time< 20 calendar daysSum of response days / Number of completed requests
Verification completion rate> 95%(Verified requests / Total requests requiring verification)
Extension rate< 15%(Extended requests / Total requests)
First-contact resolution (marketing opt-out)100% within 24h(Resolved within 24h / Total marketing opt-outs)

Escalation Rules

ConditionEscalation
20 days elapsed, response not deliveredAlert to assignee and team lead
25 days elapsed, response not deliveredAlert to DPO
28 days elapsed, response not deliveredAlert to DPO + General Counsel (emergency priority)
Extension notification not sent by day 28Alert to DPO (compliance risk)
Verification pending > 14 daysAlert to assignee (follow up with data subject)

Response Generation

Automated Response Components

The system generates responses by assembling modular components:

  1. Cover letter: Standard header, addressee, reference number, opening paragraph.
  2. Right-specific content: Template paragraph for each right type.
  3. Data compilation: System-generated data extract (for access requests).
  4. Supplementary information: Art. 15(1)(a)-(h) information block (for access requests).
  5. Redaction log: Automatically generated from redaction flags (for access requests with exemptions).
  6. Third-party notification log: Recipients notified under Art. 19 (for erasure/rectification/restriction).
  7. Rights information: Standard block listing the data subject's other rights and complaint mechanisms.
  8. Sign-off: DPO name and contact details.

Quality Assurance Checklist

Before any response is sent, the QA reviewer verifies:

  • Response addresses all elements of the relevant GDPR article
  • Data extract is complete (all identified systems queried)
  • Redactions are legally justified and documented
  • Response deadline has been met (or extension properly communicated)
  • Response is in clear, plain language per Art. 12
  • Delivery method is secure (encryption, secure portal, or registered post)
  • DPO sign-off obtained

Processing Data Subject Access Requests

Overview

A Data Subject Access Request (DSAR) is the right of an individual under GDPR Article 15 to obtain confirmation of whether their personal data is being processed, and if so, to access that data along with supplementary information. This skill provides a complete operational workflow for receiving, validating, processing, and responding to DSARs within the legally mandated timeframe.

Legal Foundation

GDPR Article 15 — Right of Access by the Data Subject

  1. Art. 15(1) — The data subject has the right to obtain from the controller confirmation as to whether personal data concerning them is being processed, and where that is the case, access to the personal data and the following information:

    • (a) the purposes of the processing
    • (b) the categories of personal data concerned
    • (c) the recipients or categories of recipient to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations
    • (d) where possible, the envisaged period for which the personal data will be stored, or if not possible, the criteria used to determine that period
    • (e) the existence of the right to request rectification, erasure, restriction, or to object to processing
    • (f) the right to lodge a complaint with a supervisory authority
    • (g) where the personal data are not collected from the data subject, any available information as to their source
    • (h) the existence of automated decision-making, including profiling, referred to in Art. 22(1) and (4), and meaningful information about the logic involved, significance, and envisaged consequences
  2. Art. 15(3) — The controller shall provide a copy of the personal data undergoing processing. For additional copies, the controller may charge a reasonable fee based on administrative costs.

  3. Art. 15(4) — The right to obtain a copy shall not adversely affect the rights and freedoms of others.

GDPR Article 12 — Transparent Communication

  • Art. 12(3) — Response deadline: without undue delay and in any event within one month of receipt. That period may be extended by two further months where necessary, taking into account the complexity and number of requests. The controller shall inform the data subject of any such extension within one month of receipt, together with the reasons for the delay.
  • Art. 12(5) — Where requests are manifestly unfounded or excessive (particularly due to repetitive character), the controller may either charge a reasonable fee or refuse to act. The controller bears the burden of demonstrating the manifestly unfounded or excessive character.

DSAR Processing Workflow

Step 1: Receive and Log the Request

  1. Record the request in the DSAR tracking register with a unique reference number (format: DSAR-YYYY-NNNN).
  2. Capture the channel of receipt (email, web form, postal mail, telephone, in-person).
  3. Timestamp the receipt to the minute using UTC.
  4. Assign the request to the designated DSAR processing team member.
  5. Send an acknowledgement to the data subject within 3 business days confirming receipt and reference number.

Step 2: Verify the Identity of the Requester

  1. Low-risk verification (request received from a verified account, e.g., logged-in customer portal): Confirm account ownership via existing authentication.
  2. Medium-risk verification (request received via email matching records): Request two of the following — date of birth, account number, postal code associated with the account, last four digits of payment method.
  3. High-risk verification (request from unrecognised channel or on behalf of another person): Require government-issued photo ID plus one additional identifier. For third-party requests (e.g., solicitor acting on behalf), require written authorisation signed by the data subject plus proof of identity for both the representative and the data subject.
  4. If identity cannot be verified, inform the requester within 10 business days that additional proof is required. The 30-day response clock pauses until verification is complete per EDPB Guidelines 01/2022 paragraph 64.

Step 3: Assess the Request Scope

  1. Determine whether the request covers all personal data or a specific subset.
  2. Identify all data processing systems where the subject's data may reside:
    • CRM systems (e.g., Salesforce, HubSpot)
    • HR/payroll systems (for employee DSARs)
    • Marketing automation platforms
    • Customer support ticket systems
    • Analytics and logging platforms
    • Backup and archival systems
    • Third-party processor systems
  3. Document any data that falls under exemptions (see Step 5).
  4. Where the controller processes a large quantity of data, request that the data subject specify the information or processing activities to which the request relates, per Recital 63.

Step 4: Calculate the Response Deadline

  1. Standard deadline: 30 calendar days from the day after receipt of the request (or from the day after identity verification is completed, if verification was required).
  2. Extension: Where the request is complex or where there are numerous requests, extend by up to two additional months (total maximum: 90 calendar days). Notify the data subject of the extension and reasons within the initial 30-day period.
  3. Weekend/holiday rule: If the deadline falls on a weekend or public holiday in the controller's jurisdiction, the deadline moves to the next business day per Regulation (EEC, Euratom) No 1182/71.

Step 5: Apply Exemptions Under Art. 15(4)

Review whether any of the following exemptions apply:

  1. Rights and freedoms of others — Art. 15(4): Redact or withhold data where disclosure would adversely affect the rights and freedoms of other individuals (e.g., third-party personal data, trade secrets of third parties).
  2. Legal privilege — Data protected by legal professional privilege or litigation privilege.
  3. Confidential references — References given in confidence for education, training, or employment purposes (applicable under UK GDPR supplementary provisions).
  4. Management forecasting — Data processed for management forecasting or planning where disclosure would prejudice the business (applicable under certain Member State derogations).
  5. Negotiations — Data consisting of records of intentions in relation to negotiations with the data subject where disclosure would prejudice those negotiations.

Document each exemption applied with specific justification.

Step 6: Compile the Response

  1. Gather all personal data from identified systems.
  2. Organise data by category:
    • Identity data (name, date of birth, contact details)
    • Financial data (transaction records, payment methods)
    • Technical data (IP addresses, device identifiers, cookies)
    • Usage data (service interaction records, preferences)
    • Communications data (support tickets, correspondence)
    • Profiling data (segments, scores, automated decisions)
  3. Prepare the supplementary information required under Art. 15(1)(a)-(h).
  4. Apply redactions for exempted data with clear notation that redactions have been made and the legal basis for each.
  5. Format the response in a commonly used electronic format (PDF for the cover letter, structured data in CSV/JSON where applicable).

Step 7: Quality Assurance Review

  1. Verify completeness: all identified systems have been queried and results compiled.
  2. Verify accuracy: spot-check data against source systems.
  3. Verify redactions: confirm each redaction is legally justified and documented.
  4. Verify the response addresses all elements of Art. 15(1)(a)-(h).
  5. Obtain sign-off from the Data Protection Officer or designated privacy lead.

Step 8: Deliver the Response

  1. Transmit the response via a secure channel:
    • Encrypted email (TLS 1.2+ in transit, AES-256 encrypted attachment)
    • Secure download portal with time-limited access link (72-hour expiry)
    • Registered postal mail with delivery confirmation (for non-electronic requests)
  2. Record the delivery date, method, and confirmation of receipt.
  3. Update the DSAR register with the closure date and outcome.

Step 9: Post-Response Actions

  1. Retain the DSAR processing record (request, internal notes, redaction justifications, copy of response) for a minimum of 3 years to demonstrate compliance.
  2. If the data subject is dissatisfied, inform them of their right to lodge a complaint with the relevant supervisory authority under Art. 77.
  3. Feed any systemic issues identified during the DSAR process into the organisation's data governance improvement programme.

Fee and Refusal Provisions

Reasonable Fee (Art. 12(5)(a))

A controller may charge a reasonable fee taking into account the administrative costs of providing the information or communication or taking the action requested where:

  • The request is manifestly unfounded (e.g., the requester has explicitly stated they intend to cause disruption), or
  • The request is excessive (e.g., the same individual submits a fourth identical DSAR within a 12-month period without any change in processing activities).

The fee at Meridian Analytics Ltd is calculated as: GBP 10.00 base fee + GBP 0.10 per page exceeding 500 pages of output.

Refusal to Act (Art. 12(5)(b))

The controller may refuse to act on the request where it is manifestly unfounded or excessive, but must:

  1. Inform the data subject of the reasons for refusal.
  2. Inform the data subject of their right to lodge a complaint with the supervisory authority.
  3. Inform the data subject of their right to seek a judicial remedy.
  4. Document the refusal decision and its justification.

EDPB Guidance References

  • EDPB Guidelines 01/2022 on data subject rights — Right of access: Clarifies scope, means of access, third-party data handling, and relationship with other GDPR rights.
  • EDPB Guidelines on Transparency (WP260 rev.01): Provides guidance on the Art. 12 requirements for concise, transparent, intelligible, and easily accessible communication.

Providing Indirect Collection Information

Overview

GDPR Article 14 applies when a controller obtains personal data from a source other than the data subject — such as from third-party data brokers, publicly available sources, other controllers, or through automated observation by third parties. The controller must still provide the data subject with comprehensive information about the processing, but the timing and content requirements differ from Art. 13.

Legal Foundation

GDPR Article 14 — Information Where Personal Data Have Not Been Obtained from the Data Subject

Required Information (Art. 14(1)-(2))

All elements required under Art. 13(1)(a)-(f) and Art. 13(2)(a)-(g) PLUS:

ElementArticleDescription
Categories of personal dataArt. 14(1)(d)The categories of personal data concerned (not required under Art. 13 because the subject already knows what they provided)
Source of dataArt. 14(2)(f)From which source the personal data originate, and if applicable, whether it came from publicly accessible sources
Timing Requirements (Art. 14(3))

The controller must provide the information:

  1. Art. 14(3)(a) — Default: Within a reasonable period after obtaining the personal data, but at the latest within one month, having regard to the specific circumstances in which the personal data are processed.
  2. Art. 14(3)(b) — Communication with data subject: If the personal data are to be used for communication with the data subject, at the latest at the time of the first communication to that data subject.
  3. Art. 14(3)(c) — Disclosure to another recipient: If a disclosure to another recipient is envisaged, at the latest when the personal data are first disclosed.

The earliest applicable deadline governs.

Exemptions Under Art. 14(5)

Art. 14(1)-(4) shall not apply where and insofar as:

  1. Art. 14(5)(a) — Data subject already has the information: The data subject already has the information.
  2. Art. 14(5)(b) — Impossible or disproportionate effort: The provision of such information proves impossible or would involve a disproportionate effort, in particular for processing for archiving purposes in the public interest, scientific or historical research, or statistical purposes under Art. 89(1). In such cases, the controller must take appropriate measures to protect the data subject's rights and freedoms, including making the information publicly available.
  3. Art. 14(5)(c) — Union or Member State law: Obtaining or disclosure is expressly laid down by Union or Member State law which provides appropriate measures to protect the data subject's legitimate interests.
  4. Art. 14(5)(d) — Professional secrecy: The personal data must remain confidential subject to an obligation of professional secrecy regulated by Union or Member State law, including a statutory obligation of secrecy.

Common Indirect Collection Scenarios at Meridian Analytics Ltd

ScenarioData SourceCategoriesTiming Obligation
Client employee data received from employer clientEmployer (another controller)Name, email, job title, access permissionsWithin 1 month of receipt, or at first communication
Companies House / public registry dataPublicly accessible sourceDirector names, registered address, filing historyWithin 1 month; note public source in notice
Credit reference agency dataCredit reference agency (Experian, Equifax)Credit score, payment history, financial indicatorsAt first communication or within 1 month
Referral from existing clientExisting clientName, email, companyAt first communication with referred person
Data enrichment from third-party providerData enrichment providerFirmographic data, industry classificationWithin 1 month of enrichment

Indirect Collection Information Workflow

Step 1: Identify Indirect Data Acquisition

  1. Map all sources of personal data that are not the data subjects themselves.
  2. For each source, document:
    • Source identity and type (controller, publicly accessible, data broker)
    • Categories of personal data received
    • Legal basis for receiving the data
    • Date of receipt
    • Purpose of processing

Step 2: Determine the Timing Obligation

Apply the earliest applicable deadline from Art. 14(3)(a)-(c):

[Data Received from Third Party]
         │
         ▼
[Will data be used to contact the subject?]
   ├── Yes ──► Notify at or before first communication
   └── No ──► [Will data be disclosed to another recipient?]
               ├── Yes ──► Notify before or at disclosure
               └── No ──► Notify within reasonable period (max 1 month)

Step 3: Prepare the Art. 14 Notice

The notice must contain all elements specified in Art. 14(1) and (2). Use the following structure:

  1. Controller identity: Meridian Analytics Ltd, 47 Canary Wharf Tower, London E14 5AB
  2. DPO contact: Dr Sarah Chen, dpo@meridiananalytics.co.uk
  3. Purposes and legal basis: State each purpose and its legal basis
  4. Categories of personal data: List the categories obtained (since the subject did not provide them directly)
  5. Recipients: Identify recipients or categories
  6. International transfers: Describe any transfers and safeguards
  7. Retention period: State period or criteria
  8. Data subject rights: List all applicable rights
  9. Right to withdraw consent: If applicable
  10. Right to complain: ICO details
  11. Source of data: Identify the source and whether it is publicly accessible
  12. Automated decision-making: If applicable
  13. Further processing: If applicable

Step 4: Assess Exemptions

Before deciding not to provide Art. 14 information, assess each exemption strictly:

ExemptionAssessmentDocumentation Required
Art. 14(5)(a) — Already has infoVerify the subject has received materially equivalent information from another sourceRecord the source and date of prior information
Art. 14(5)(b) — Impossible/disproportionate effortConduct and document proportionality assessment considering: number of data subjects, age of data, compensatory measures availableWritten proportionality assessment, approved by DPO, with compensatory measures (e.g., publish information on website)
Art. 14(5)(c) — Law requires acquisitionIdentify the specific legal provisionCitation of the provision
Art. 14(5)(d) — Professional secrecyIdentify the statutory obligation of secrecyCitation of the provision

The EDPB Guidelines on Transparency (WP260 rev.01) state that the Art. 14(5)(b) exemption should be interpreted restrictively and that the mere inconvenience or cost of providing information is not sufficient to constitute "disproportionate effort."

Step 5: Deliver the Notice

  1. Email: If the subject's email address is available, send the Art. 14 notice by email.
  2. Postal mail: If only a postal address is available, send by first-class post.
  3. Combined with first communication: Where the first communication is an email or letter, include the Art. 14 information in or with that communication.
  4. Published notice: Where the Art. 14(5)(b) exemption applies and compensatory measures are required, publish the information on the controller's website.

Step 6: Document and Record

  1. Record the date of each Art. 14 notification.
  2. Record the method of delivery.
  3. Record any exemption relied upon and its justification.
  4. Retain the record for 3 years.

Managing Direct Marketing Objection

Overview

The right to object to direct marketing under GDPR Article 21(2)-(3) is an absolute right — there is no balancing test, no compelling grounds exception, and no basis on which the controller can refuse. When a data subject objects to processing for direct marketing purposes, the controller must cease that processing immediately. This skill provides the complete operational procedure for handling marketing objections across all channels.

Legal Foundation

GDPR Article 21(2)-(3) — Direct Marketing Objection

  1. Art. 21(2) — Where personal data are processed for direct marketing purposes, the data subject has the right to object at any time to processing of personal data concerning them for such marketing, which includes profiling to the extent that it is related to such direct marketing.

  2. Art. 21(3) — Where the data subject objects to processing for direct marketing purposes, the personal data shall no longer be processed for such purposes.

Key Characteristics

  • Absolute right: No balancing test. No compelling grounds exception. No fee. No refusal possible.
  • Immediate effect: Processing for direct marketing must cease as soon as the objection is received.
  • Scope: Covers ALL forms of direct marketing including email, SMS, telephone, postal mail, targeted online advertising, and profiling for marketing segmentation.
  • Includes profiling: Any profiling conducted for the purpose of direct marketing must also cease.

Privacy and Electronic Communications Regulations 2003 (PECR)

  • Regulation 22 — Unsolicited communications by electronic mail: requires prior consent for marketing emails to individuals (unless soft opt-in exception applies).
  • Regulation 21 — Unsolicited calls for direct marketing: requires compliance with the Telephone Preference Service (TPS).

ePrivacy Directive 2002/58/EC (as amended by 2009/136/EC)

  • Article 13 — Unsolicited communications: consent required for electronic marketing communications, with limited exception for existing customer relationships.

Direct Marketing Objection Workflow

Step 1: Receive the Objection

Objections may arrive through any channel:

ChannelExampleHandling
Email unsubscribe linkClick on "Unsubscribe" in marketing emailAutomated processing within 24 hours
Reply to marketing email"Please stop emailing me"Manual triage, process within 24 hours
Web formPrivacy preference centre opt-outAutomated processing immediately
Telephone"Take me off your mailing list"Agent records objection, process within 24 hours
Written letter"I object to you using my data for marketing"Process within 48 hours of receipt
Social media messageDirect message requesting marketing cessationProcess within 48 hours of receipt
Verbal (in-person)"Stop sending me marketing"Staff member records objection, process within 24 hours
  1. Log with reference MKT-YYYY-NNNN.
  2. Record the channel, timestamp, and scope of the objection.
  3. No identity verification is required beyond confirming the identity matches the marketing recipient (e.g., the email address matches the unsubscribe request).

Step 2: Determine the Scope

  1. Full opt-out: Data subject objects to ALL direct marketing — cease all marketing processing.
  2. Partial opt-out: Data subject objects to specific channels only (e.g., "stop calling me but email is fine") — cease the specified channels.
  3. If unclear: Treat as a full opt-out. Contact the data subject to clarify preferences only after cessation.

Step 3: Immediate Cessation

Within 24 hours of receiving the objection:

  1. Email marketing: Remove from all active email marketing lists, suppress email address.
  2. SMS marketing: Remove from SMS distribution lists, suppress mobile number.
  3. Telephone marketing: Add to internal do-not-call list, register with Telephone Preference Service (TPS) if applicable.
  4. Postal marketing: Remove from postal mailing lists, add to internal do-not-mail list.
  5. Online targeted advertising: Remove from remarketing audiences, customer match lists, and lookalike audience seed lists.
  6. Profiling for marketing: Cease all profiling activities related to marketing segmentation for this individual. Remove from marketing segments.

Step 4: Suppression List Management

A suppression list is essential to prevent re-subscription or re-targeting:

  1. Add the data subject's identifiers to the marketing suppression list:
    • Email address (store as SHA-256 hash for matching against future lists)
    • Phone number (store as SHA-256 hash)
    • Postal address (store normalised address components)
    • Customer ID
  2. The suppression list entry must be retained indefinitely (or until the data subject explicitly consents to marketing again) to prevent re-contact.
  3. The suppression list must be checked before every marketing campaign distribution:
    • Email campaigns: check suppression list before send
    • SMS campaigns: check suppression list before send
    • Postal campaigns: check suppression list before print/dispatch
    • Online advertising: exclude suppression list from audience uploads
  4. New data imports must be screened against the suppression list before any marketing processing.

Step 5: Cross-Channel Enforcement

Ensure the objection is enforced across ALL marketing channels and systems:

SystemActionOwner
Email platform (Mailchimp)Unsubscribe + add to suppression segmentMarketing Operations
SMS platformOpt-out + add to suppression listMarketing Operations
CRM (Salesforce)Set marketing_opt_out = TRUE, update consent recordCRM Administrator
Advertising platforms (Google Ads, Meta Ads)Remove from customer match and remarketing audiencesDigital Marketing
Analytics platformExclude from marketing attribution and segment analysisData Analytics
Data warehouseUpdate marketing consent flag, trigger downstream syncData Engineering
Third-party data brokersIssue suppression notificationData Partnerships

Step 6: Third-Party Notification

  1. Identify all third parties who process the data subject's data for direct marketing purposes on behalf of Meridian Analytics Ltd (e.g., marketing agencies, advertising platforms, data enrichment providers).
  2. Send suppression instructions to each third party within 48 hours.
  3. Request confirmation of suppression within 14 calendar days.
  4. Log all notifications and confirmations.

Step 7: Confirm to the Data Subject

Send confirmation within 14 calendar days (best practice, well within the 30-day Art. 12 deadline):

  1. Confirm that all direct marketing processing has ceased.
  2. Specify the channels suppressed.
  3. Confirm that a suppression record has been created.
  4. If any non-marketing processing continues under a different legal basis, inform the data subject.
  5. Provide contact details for further enquiries.

Step 8: Ongoing Compliance

  1. Pre-campaign check: Before every marketing campaign, the suppression list must be applied.
  2. New data imports: All new customer data must be screened against the suppression list before any marketing processing.
  3. Quarterly audit: Review suppression list completeness and effectiveness. Test that suppressed individuals do not receive marketing communications.
  4. Staff training: All marketing team members must be trained on the absolute nature of the Art. 21(2) right and the suppression list process.

Responding to Regulatory Complaints

Overview

Under GDPR Article 77, data subjects have the right to lodge a complaint with a supervisory authority (Data Protection Authority / DPA) if they consider that the processing of their personal data infringes the GDPR. When a DPA receives a complaint and contacts the controller, the controller must respond promptly, cooperate fully, and demonstrate compliance. This skill provides the operational procedure for managing regulatory complaints from receipt through resolution.

Legal Foundation

GDPR Article 77 — Right to Lodge a Complaint

Every data subject has the right to lodge a complaint with a supervisory authority, in particular in the Member State of their habitual residence, place of work, or place of the alleged infringement, if the data subject considers that the processing of personal data relating to them infringes the GDPR.

GDPR Article 31 — Cooperation with the Supervisory Authority

The controller and the processor, and where applicable the controller's or the processor's representative, shall cooperate, on request, with the supervisory authority in the performance of its tasks.

GDPR Article 58 — Powers of Supervisory Authorities

Supervisory authorities have investigative powers (Art. 58(1)), corrective powers (Art. 58(2)), and authorisation and advisory powers (Art. 58(3)), including the power to:

  • Order the controller to provide information (Art. 58(1)(a))
  • Carry out investigations in the form of data protection audits (Art. 58(1)(b))
  • Issue warnings, reprimands, and orders (Art. 58(2)(a)-(d))
  • Impose administrative fines (Art. 58(2)(i) and Art. 83)

GDPR Article 78 — Right to an Effective Judicial Remedy Against a Supervisory Authority

Data subjects (and controllers) have the right to an effective judicial remedy against legally binding decisions of a supervisory authority.

Regulatory Complaint Response Workflow

Step 1: Receive and Log the Complaint

  1. Log the complaint with reference REG-YYYY-NNNN.
  2. Record:
    • Supervisory authority (e.g., ICO, CNIL, BfDI, DPC)
    • DPA reference number
    • Date of DPA correspondence
    • Complainant identity (if disclosed by the DPA)
    • Summary of the complaint allegations
    • DPA's specific requests or questions
    • Response deadline set by the DPA
  3. Immediately notify the Data Protection Officer.
  4. Escalate to the General Counsel if the complaint involves potential enforcement action or fines.

Step 2: Internal Escalation

Complaint SeverityEscalation LevelResponse LeadTimeline
Routine (individual rights exercise issue)DPOPrivacy AnalystDPA deadline (typically 28 days)
Significant (systemic compliance issue)DPO + General CounselDPODPA deadline, with internal briefing within 48 hours
Critical (potential enforcement/fine)DPO + General Counsel + CEODPO + External CounselDPA deadline, with board notification within 24 hours

Step 3: Internal Investigation

  1. Review the complaint allegations against internal records:
    • DSAR/rights request register (was the request handled correctly?)
    • Processing records (Art. 30 register)
    • Consent records
    • Data breach register
    • Privacy impact assessments
  2. Interview relevant staff members and document their accounts.
  3. Collect all supporting evidence (emails, system logs, decision records).
  4. Identify any compliance gaps or procedural failures.
  5. Assess whether the complaint is substantiated, partially substantiated, or unsubstantiated.

Step 4: Prepare the Response

The DPA response must be:

  • Factual: Address each specific allegation or question raised by the DPA.
  • Evidenced: Attach supporting documentation.
  • Cooperative: Demonstrate willingness to engage per Art. 31.
  • Proportionate: Address the complaint scope without volunteering unrelated issues.
Response Structure
  1. Acknowledgement: Confirm receipt of the DPA's correspondence, cite the DPA reference number.
  2. Background: Provide a brief factual overview of the processing activity and the controller's relationship with the complainant.
  3. Response to each allegation: Address each point raised by the DPA with facts and evidence.
  4. Compliance evidence: Attach relevant documentation (privacy notice, consent records, DSAR response copies, DPIAs, processing records).
  5. Remediation: If any issue is identified, describe the remediation steps taken or planned, with timelines.
  6. Cooperation: Confirm willingness to provide any further information the DPA requires.

Step 5: DPO Review and Approval

  1. The DPO reviews the draft response for accuracy and completeness.
  2. If the complaint involves potential enforcement, external legal counsel reviews the response.
  3. Obtain sign-off from the appropriate authority level per Step 2.
  4. Submit the response to the DPA before the deadline.

Step 6: Remediation Tracking

If the investigation identifies compliance gaps:

  1. Create remediation actions with:
    • Description of the gap
    • Root cause analysis
    • Corrective action
    • Owner (name and role)
    • Target completion date
    • Verification method
  2. Track remediation in the compliance action tracker.
  3. Report progress to the DPO monthly until all actions are closed.
  4. Include remediation status in the next DPA communication if the DPA follows up.

Step 7: DPA Decision and Follow-Up

DPA OutcomeController Action
Complaint dismissed / no further actionFile and close. Update complaint register.
Informal resolution recommendedImplement DPA's recommendations. Confirm completion to DPA.
Formal reprimand issued (Art. 58(2)(b))Record on compliance register. Implement required changes. Report to board.
Order to comply issued (Art. 58(2)(c)-(g))Implement the order within the specified timeframe. Confirm compliance to DPA.
Administrative fine imposed (Art. 83)Engage external legal counsel. Assess appeal options (Art. 78). Pay or appeal within deadline.
Investigation initiatedCooperate fully. Appoint response team. Preserve all relevant records.

Step 8: Close and Record

  1. Update the complaint register with the final outcome.
  2. Record any lessons learned.
  3. Feed findings into the compliance improvement programme.
  4. Retain all complaint documentation for 6 years from the date of the DPA's final decision.
  5. Report complaint outcomes in the annual privacy compliance report to the board.

DPA-Specific Response Requirements

ICO (United Kingdom)

  • The ICO typically sends a preliminary enquiry letter requesting the controller's account of events.
  • Standard response timeframe: 28 calendar days.
  • Correspondence via the ICO's online case management portal or email.
  • The ICO may request a formal response under section 142 of the Data Protection Act 2018 (assessment notice).

CNIL (France)

  • Initial questionnaire or formal mise en demeure.
  • Response timeframe specified in the correspondence (typically 1-3 months).
  • Formal responses must be in French.

DPC (Ireland)

  • Relevant for organisations with main establishment in Ireland (one-stop-shop mechanism under Art. 56).
  • Response timeframe specified in the correspondence.

Handling Right to Restriction Requests

Overview

The right to restriction of processing under GDPR Article 18 allows data subjects to request that a controller limits the processing of their personal data in specific circumstances. When restriction is applied, data may be stored but not otherwise processed without the data subject's consent or for limited specified purposes. This skill provides the complete workflow for assessing, implementing, and managing restriction requests.

Legal Foundation

GDPR Article 18 — Right to Restriction of Processing

Four Grounds for Restriction Under Art. 18(1)
  1. Art. 18(1)(a) — Accuracy contested: The data subject contests the accuracy of the personal data, for a period enabling the controller to verify the accuracy of the personal data.
  2. Art. 18(1)(b) — Unlawful processing, erasure opposed: The processing is unlawful and the data subject opposes the erasure of the personal data and requests the restriction of their use instead.
  3. Art. 18(1)(c) — Erasure opposition for legal claims: The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise, or defence of legal claims.
  4. Art. 18(1)(d) — Objection pending verification: The data subject has objected to processing under Art. 21(1) pending the verification whether the legitimate grounds of the controller override those of the data subject.

Processing Permitted During Restriction (Art. 18(2))

When processing has been restricted, the personal data may only be processed:

  • With the data subject's consent, OR
  • For the establishment, exercise, or defence of legal claims, OR
  • For the protection of the rights of another natural or legal person, OR
  • For reasons of important public interest of the Union or a Member State.

GDPR Article 19 — Notification Obligation

The controller must notify each recipient to whom the personal data have been disclosed of the restriction, unless this proves impossible or involves disproportionate effort.

Lifting the Restriction (Art. 18(3))

A data subject who has obtained restriction of processing shall be informed by the controller before the restriction of processing is lifted.

Restriction Processing Workflow

Step 1: Receive and Log the Request

  1. Log the request with reference RST-YYYY-NNNN.
  2. Record the channel, timestamp (UTC), and identity of the requester.
  3. Send acknowledgement within 3 business days.
  4. Verify identity using tiered verification.

Step 2: Identify the Ground for Restriction

Determine which of the four grounds applies:

GroundTriggerDurationResolution
Art. 18(1)(a) — Accuracy contestedData subject disputes data accuracyUntil accuracy verifiedVerified accurate: lift restriction. Verified inaccurate: rectify under Art. 16 and lift.
Art. 18(1)(b) — Unlawful processing, erasure opposedProcessing found unlawful but subject prefers restriction over deletionIndefinite until subject consents to erasure or processing becomes lawfulSubject requests erasure or lawful basis established.
Art. 18(1)(c) — Needed for legal claimsController no longer needs data but subject requires it for legal proceedingsDuration of legal proceedingsLegal proceedings concluded or subject no longer requires data.
Art. 18(1)(d) — Objection pendingSubject objects under Art. 21(1), assessment pendingUntil Art. 21 assessment completeLegitimate grounds assessment: controller overrides = lift restriction + inform subject. Subject's grounds prevail = erase under Art. 17(1)(c).

Step 3: Implement Technical Restriction

Apply a technical flagging mechanism to prevent processing of the restricted data:

Database-Level Flags
  1. Set a restriction_flag field to TRUE on all records associated with the data subject.
  2. Set a restriction_date timestamp.
  3. Set a restriction_ground value (one of: accuracy_contested, unlawful_opposed, legal_claims, objection_pending).
  4. Set a restriction_reference value linking to the request (RST-YYYY-NNNN).
Application-Level Controls
  1. Query filters: Modify application queries to exclude records where restriction_flag = TRUE from all standard processing operations.
  2. API access controls: Return HTTP 423 (Locked) or filtered results when restricted data is requested through APIs used for standard processing.
  3. Batch processing exclusions: Add restriction checks to all ETL, reporting, and analytics pipelines.
  4. User interface masking: Display restricted records with a visual indicator (e.g., "RESTRICTED — Processing Limited") in internal tools. Prevent editing or use of restricted data.
Storage Isolation (Recommended for High-Risk Data)
  1. Move restricted records to a separate restricted data store or partition.
  2. Apply access controls limiting access to the DPO and Legal team only.
  3. Log all access to restricted data with justification.

Step 4: Permitted Processing Assessment

When any team needs to process restricted data, they must complete a permitted processing assessment:

  1. Consent: Has the data subject provided specific consent for this particular processing activity during the restriction period? Document the consent.
  2. Legal claims: Is the processing necessary for the establishment, exercise, or defence of legal claims by the controller or a third party? Identify the specific claim.
  3. Protection of rights: Is the processing necessary to protect the rights of another natural or legal person? Identify the person and right.
  4. Public interest: Is the processing required for reasons of important public interest? Identify the specific public interest basis.

Any processing of restricted data outside these four purposes is a compliance violation.

Step 5: Notify Third-Party Recipients (Art. 19)

  1. Identify all recipients to whom the restricted data was previously disclosed.
  2. Send restriction notification to each recipient:
    • Data subject reference (pseudonymised)
    • Data categories subject to restriction
    • Restriction ground (without disclosing details that would identify the subject's reason)
    • Instruction to cease processing except for permitted purposes
    • Request confirmation within 14 calendar days
  3. Log all notifications and confirmations.

Step 6: Monitor and Resolve

  1. Set a review date based on the restriction ground:
    • Accuracy contested: Review within 15 business days (or as long as accuracy verification requires).
    • Unlawful processing: Review quarterly or upon data subject request.
    • Legal claims: Review upon conclusion of legal proceedings (liaise with Legal team quarterly).
    • Objection pending: Complete Art. 21 assessment within 20 business days.
  2. When the restriction is to be lifted:
    • Notify the data subject before lifting (Art. 18(3)) with at least 7 calendar days' notice.
    • State the reason the restriction is being lifted.
    • Inform the data subject of their rights (including the right to object or request erasure).
  3. Remove technical flags and restore normal processing access.
  4. Notify third-party recipients that the restriction has been lifted.

Step 7: Document and Close

  1. Update the restriction register with:
    • Restriction applied date
    • Ground
    • Technical measures implemented
    • Third parties notified
    • Resolution date and outcome
    • Pre-lifting notification date
  2. Retain the record for 3 years following resolution.

Response Timeline

  • Standard deadline: 30 calendar days from receipt of the request.
  • Extension: Up to 60 additional days for complex cases (Art. 12(3)).
  • Technical implementation: Restriction flags must be applied within 72 hours of the decision to restrict, regardless of the response deadline.

Implementing Right to Erasure Workflow

Overview

The right to erasure under GDPR Article 17 allows data subjects to request the deletion of their personal data. This right is not absolute — it is subject to specific grounds for erasure and a set of exceptions. This skill provides the complete operational procedure for receiving, assessing, executing, and confirming erasure requests.

Legal Foundation

GDPR Article 17 — Right to Erasure ('Right to be Forgotten')

Six Grounds for Erasure Under Art. 17(1)

The data subject has the right to obtain erasure where one of the following grounds applies:

  1. Art. 17(1)(a) — Purpose fulfilment: The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.
  2. Art. 17(1)(b) — Consent withdrawal: The data subject withdraws consent on which the processing is based under Art. 6(1)(a) or Art. 9(2)(a), and there is no other legal ground for the processing.
  3. Art. 17(1)(c) — Successful objection: The data subject objects pursuant to Art. 21(1) and there are no overriding legitimate grounds for the processing, or the data subject objects to processing for direct marketing under Art. 21(2).
  4. Art. 17(1)(d) — Unlawful processing: The personal data have been unlawfully processed.
  5. Art. 17(1)(e) — Legal obligation: The personal data have to be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.
  6. Art. 17(1)(f) — Child's data (information society services): The personal data have been collected in relation to the offer of information society services referred to in Art. 8(1).
Five Exceptions Under Art. 17(3)

Erasure does NOT apply to the extent that processing is necessary for:

  1. Art. 17(3)(a) — Freedom of expression and information: Exercising the right of freedom of expression and information.
  2. Art. 17(3)(b) — Legal obligation: Compliance with a legal obligation which requires processing by Union or Member State law to which the controller is subject, or for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.
  3. Art. 17(3)(c) — Public health: Reasons of public interest in the area of public health in accordance with Art. 9(2)(h) and (i), and Art. 9(3).
  4. Art. 17(3)(d) — Archiving/research: Archiving purposes in the public interest, scientific or historical research purposes, or statistical purposes in accordance with Art. 89(1), in so far as the right to erasure is likely to render impossible or seriously impair the achievement of the objectives of that processing.
  5. Art. 17(3)(e) — Legal claims: The establishment, exercise, or defence of legal claims.

GDPR Article 19 — Notification Obligation

The controller shall communicate any erasure of personal data to each recipient to whom the personal data have been disclosed, unless this proves impossible or involves disproportionate effort. The controller shall inform the data subject about those recipients if the data subject requests it.

Erasure Processing Workflow

Step 1: Receive and Log the Erasure Request

  1. Log the request with a unique reference (format: ERA-YYYY-NNNN).
  2. Record the channel, timestamp (UTC), and identity of the requester.
  3. Send acknowledgement within 3 business days.
  4. Verify identity using the same tiered approach as DSAR processing (low/medium/high risk).

Step 2: Identify the Ground for Erasure

  1. Review the request to determine which of the six grounds under Art. 17(1)(a)-(f) the data subject is invoking.
  2. If the data subject has not specified a ground, assess which ground(s) are applicable based on the facts.
  3. Document the identified ground(s) in the processing record.

Step 3: Check for Applicable Exceptions

For each ground identified, evaluate whether any of the five exceptions under Art. 17(3)(a)-(e) apply:

ExceptionAssessment QuestionCommon Scenarios at Meridian Analytics Ltd
Freedom of expression (a)Is this data published as part of journalism or public discourse?Published research reports, public-facing analytics
Legal obligation (b)Is there a statutory retention requirement?Financial records under Companies Act 2006 (6 years), tax records under HMRC requirements (6 years), anti-money laundering records under MLR 2017 (5 years)
Public health (c)Is this data necessary for public health purposes?Rare — applies to health data processors
Archiving/research (d)Would erasure render research impossible or seriously impaired?Anonymised datasets used in published research
Legal claims (e)Are there pending or anticipated legal proceedings involving this data?Active disputes, regulatory investigations, litigation hold data

Step 4: Deletion vs Anonymization Decision Tree

[Erasure Ground Established & No Exception Applies]
         │
         ▼
[Can data be permanently deleted from all systems?]
   │
   ├── Yes ──► [PERMANENT DELETION]
   │            - Remove from primary databases
   │            - Remove from backup systems within next backup cycle
   │            - Remove from third-party processors (Art. 19)
   │            - Purge from caches, logs, and temporary storage
   │            - Verify deletion across all systems
   │
   └── No ──► [Assess why deletion is not possible]
               │
               ├── Technical constraint (embedded in backup tapes)
               │     └── [ANONYMIZE + schedule deletion at next backup rotation]
               │         [Maximum retention of backup: 90 days at Meridian Analytics Ltd]
               │
               ├── Partial exception applies (some data needed for legal obligation)
               │     └── [PARTIAL DELETION + ANONYMIZATION]
               │         [Delete data not subject to exception]
               │         [Retain excepted data with restricted access]
               │         [Anonymize where possible]
               │
               └── Data is intermingled with other subjects' data
                     └── [TARGETED ANONYMIZATION]
                         [Replace identifiers with irreversible pseudonyms]
                         [Remove all direct identifiers]
                         [Verify re-identification risk < 0.05%]

Step 5: Execute the Erasure

  1. Primary systems: Execute deletion queries/commands across all identified data stores.
  2. Backup systems: Flag data for deletion at next backup rotation cycle (document the expected completion date, maximum 90 days).
  3. Third-party processors: Issue erasure instructions to all processors under Art. 28 agreements. Record the instruction date and request confirmation of completion.
  4. Caches and temporary storage: Purge application caches, CDN caches, and temporary files.
  5. Search engine de-indexing: Where personal data was made public (Art. 17(2)), submit de-indexing requests to search engines.

Step 6: Notify Third-Party Recipients (Art. 19)

  1. Identify all recipients to whom the personal data was disclosed (reference the Art. 30 records of processing).
  2. Send erasure notification to each recipient with:
    • The data subject reference (anonymised)
    • The specific data to be erased
    • The legal basis for the erasure request
    • A deadline for confirmation of erasure (14 calendar days)
  3. Record each notification and the recipient's confirmation.
  4. If the data subject requests it, provide the list of recipients notified.

Step 7: Verify and Confirm

  1. Run verification checks across all systems to confirm data has been erased or anonymised.
  2. Obtain confirmation from all third-party processors.
  3. Compile the erasure completion record.
  4. Send confirmation to the data subject within the 30-day response deadline, including:
    • Confirmation that erasure has been completed
    • Any partial exceptions applied (with legal basis)
    • Expected completion date for backup system erasure (if applicable)
    • List of third parties notified (if requested)

Step 8: Record Retention

  1. Retain the erasure processing record (request details, assessment, execution log, confirmations) for 3 years.
  2. The record must NOT contain the erased personal data itself — only metadata about the erasure process.
  3. Store a suppression record (minimum identifiers needed to recognise future requests from the same individual and prevent re-collection) where appropriate.

Response Timeline

  • Standard deadline: 30 calendar days from receipt (or from identity verification).
  • Extension: Up to 60 additional days for complex requests (Art. 12(3)), with notification to the data subject within the initial 30-day period.
  • Backup erasure: Must be completed within the next full backup rotation cycle (maximum 90 days at Meridian Analytics Ltd), documented in the response.

Handling Right to Object to Processing

Overview

The right to object under GDPR Article 21(1) allows data subjects to object to processing based on legitimate interests (Art. 6(1)(f)) or public interest/official authority (Art. 6(1)(e)), including profiling based on those provisions. Upon objection, the controller must cease processing unless it demonstrates compelling legitimate grounds that override the interests, rights, and freedoms of the data subject, or processing is necessary for legal claims.

Legal Foundation

GDPR Article 21 — Right to Object

  1. Art. 21(1) — The data subject has the right to object, on grounds relating to their particular situation, to processing based on Art. 6(1)(e) (public interest) or Art. 6(1)(f) (legitimate interests), including profiling based on those provisions. The controller shall no longer process the personal data unless it demonstrates compelling legitimate grounds for the processing which override the interests, rights, and freedoms of the data subject, or for the establishment, exercise, or defence of legal claims.

  2. Art. 21(2)-(3) — [Covered separately in managing-direct-marketing-objection skill]

  3. Art. 21(4) — At the latest at the time of the first communication with the data subject, the right to object shall be explicitly brought to the attention of the data subject and shall be presented clearly and separately from any other information.

  4. Art. 21(5) — In the context of the use of information society services, the data subject may exercise their right to object by automated means using technical specifications.

  5. Art. 21(6) — Where personal data are processed for scientific or historical research purposes or statistical purposes under Art. 89(1), the data subject has the right to object unless the processing is necessary for the performance of a task carried out for reasons of public interest.

Relationship with Art. 17(1)(c) — Erasure Following Objection

Where the data subject successfully objects and there are no overriding legitimate grounds, the data subject also has the right to erasure under Art. 17(1)(c).

Objection Processing Workflow

Step 1: Receive and Log the Objection

  1. Log with reference OBJ-YYYY-NNNN.
  2. Record the specific processing activities objected to.
  3. Record the data subject's particular situation and grounds.
  4. Acknowledge receipt within 3 business days.
  5. Verify identity.
  6. Immediately cease the objected-to processing pending the compelling grounds assessment (apply restriction under Art. 18(1)(d)).

Step 2: Identify the Processing and Its Legal Basis

  1. Identify all processing activities covered by the objection.
  2. Confirm that the legal basis for each activity is either:
    • Art. 6(1)(e) — Public interest / official authority, or
    • Art. 6(1)(f) — Legitimate interests
  3. If the processing is based on a different legal basis (consent, contract, legal obligation), the right to object under Art. 21(1) does not apply. Inform the data subject of the applicable basis and suggest the appropriate right (e.g., withdrawal of consent under Art. 7(3)).

Step 3: Compelling Legitimate Grounds Assessment

The controller must demonstrate that its legitimate grounds for processing are compelling and override the data subject's interests, rights, and freedoms. This is a higher bar than the standard legitimate interest assessment under Art. 6(1)(f).

Assessment Framework
FactorController's PositionData Subject's Position
Nature of the dataWhat categories? How sensitive?Privacy impact of continued processing
Processing purposeHow critical is this processing to the controller's operations?Alternative means available to the controller?
Impact on data subjectMinimal, moderate, or significant?What specific harm or distress does the subject describe?
Number of affected individualsDoes cessation affect only this subject or others?Individual circumstances cited by the subject
Safeguards in placeWhat measures mitigate the impact on the subject?Are safeguards sufficient from the subject's perspective?
VulnerabilityN/AIs the data subject in a vulnerable situation (child, employee, patient)?
Legal claimsIs the data needed for establishment, exercise, or defence of legal claims?Is the subject's objection related to a legal dispute?
Decision Criteria
  • Compelling grounds established: The controller can continue processing, but must document the assessment in full and inform the data subject of the outcome and their right to complain.
  • Compelling grounds NOT established: The controller must cease processing and inform the data subject. The data subject may also request erasure under Art. 17(1)(c).
  • Legal claims exception: Processing may continue if necessary for legal claims, even without compelling grounds for the main processing purpose.

Step 4: Implement the Decision

If Objection Upheld (No Compelling Grounds)
  1. Cease all objected-to processing activities immediately.
  2. Remove data from processing pipelines, analytics, and any automated systems.
  3. Retain data only in restricted storage (if needed for legal compliance or other valid legal bases).
  4. Notify third-party recipients under Art. 19.
  5. Inform the data subject of their right to request erasure under Art. 17(1)(c).
  6. Update privacy notices and records of processing to reflect the change.
If Objection Overridden (Compelling Grounds)
  1. Resume the objected-to processing (or confirm it was never ceased, if the assessment was completed within the initial processing cycle).
  2. Document the compelling legitimate grounds assessment in full.
  3. Notify the data subject:
    • The specific compelling grounds identified
    • Why those grounds override the data subject's interests
    • The data subject's right to lodge a complaint with the supervisory authority (Art. 77)
    • The data subject's right to a judicial remedy (Art. 79)

Step 5: Document and Close

  1. Record the full assessment in the objection register.
  2. Retain the record for 3 years.
  3. If the objection is upheld, ensure all downstream systems reflect the cessation of processing.
  4. Feed findings into the legitimate interest assessment register to inform future Art. 6(1)(f) reliance.

Response Timeline

  • Standard deadline: 30 calendar days from receipt.
  • Extension: Up to 60 additional days for complex cases.
  • Processing cessation: Must be implemented immediately upon receipt of the objection, pending the compelling grounds assessment. Processing may only resume if compelling grounds are demonstrated.

Processing Right to Rectification

Overview

The right to rectification under GDPR Article 16 gives data subjects the right to have inaccurate personal data corrected without undue delay, and to have incomplete personal data completed. This skill provides the complete workflow for receiving, verifying, implementing, and confirming rectification requests.

Legal Foundation

GDPR Article 16 — Right to Rectification

The data subject has the right to obtain from the controller without undue delay the rectification of inaccurate personal data concerning them. Taking into account the purposes of the processing, the data subject has the right to have incomplete personal data completed, including by means of providing a supplementary statement.

GDPR Article 19 — Notification Obligation

The controller shall communicate any rectification to each recipient to whom the personal data have been disclosed, unless this proves impossible or involves disproportionate effort. The controller shall inform the data subject about those recipients if the data subject requests it.

GDPR Article 5(1)(d) — Accuracy Principle

Personal data shall be accurate and, where necessary, kept up to date. Every reasonable step must be taken to ensure that personal data that are inaccurate, having regard to the purposes for which they are processed, are erased or rectified without delay.

Rectification Processing Workflow

Step 1: Receive and Log the Request

  1. Log the request with reference REC-YYYY-NNNN.
  2. Record the specific data the subject claims is inaccurate or incomplete.
  3. Record what the subject asserts the correct or complete data should be.
  4. Record any supporting evidence provided.
  5. Send acknowledgement within 3 business days.
  6. Verify identity using tiered verification.

Step 2: Identify Affected Data

  1. Locate the specific data items cited as inaccurate across all systems:
    • CRM and customer database
    • Marketing platforms
    • Analytics systems
    • Third-party processors
    • Backup systems
  2. Document the current value of each data item.
  3. Document the correction requested for each item.

Step 3: Verify the Correction

Two types of rectification require different verification:

Type A: Correction of Inaccurate Data
Data CategoryVerification MethodExample
Name / spellingAccept subject's assertion unless reason to doubtSubject states name is "MacLeod" not "McLeod" — accept
Date of birthRequest documentary evidence (passport, birth certificate)Subject provides passport scan showing correct DOB
AddressAccept subject's assertion for current address; verify historical addresses against postal records if relevantSubject provides utility bill as confirmation
Employment detailsAccept subject's assertion or verify with employer (with subject's consent)Subject states correct job title
Financial dataVerify against source records (bank statements, invoices)Cross-reference with payment processor records
Technical data (IP, device)Assess whether correction is factually possible — these are system-generated observationsIf system logs show IP X, correction may not be appropriate unless a logging error occurred
Type B: Completion of Incomplete Data
  1. Assess whether the additional data is relevant to the purposes of processing.
  2. If relevant, add the supplementary data.
  3. If not relevant (i.e., the additional data is not necessary for any processing purpose), the controller may decline to add it but should inform the subject of the reason.

Step 4: Decision

ScenarioAction
Verification confirms inaccuracyRectify the data across all systems
Verification is inconclusiveApply restriction under Art. 18(1)(a) while investigation continues
Verification confirms data is accurateInform the subject that the data has been verified as accurate; note the subject's objection; offer the right to add a supplementary statement
Completion request is relevantAdd the supplementary data
Completion request is not relevant to processing purposesDecline with explanation

Step 5: Implement the Rectification

  1. Update the data across all primary systems simultaneously (or as close to simultaneously as technically feasible).
  2. Update any derived data or reports that incorporate the inaccurate data.
  3. Flag data in backup systems for correction at next rotation.
  4. Document:
    • Original value
    • Corrected value
    • Date of rectification
    • Systems updated
    • Person who implemented the change

Step 6: Notify Recipients Under Art. 19

  1. Identify all recipients who received the inaccurate data (reference Art. 30 records).
  2. Send rectification notification to each recipient:
    • The specific data that has been corrected (without disclosing the subject's identity where possible)
    • The corrected value
    • Instruction to update their records accordingly
    • 14-day confirmation deadline
  3. Log all notifications and confirmations.

Step 7: Confirm to the Data Subject

Within the 30-day response deadline, send confirmation including:

  • The specific data items that have been rectified
  • The corrected values now held
  • Confirmation that all systems have been updated
  • Expected completion date for backup system corrections (if applicable)
  • List of third-party recipients notified (if requested by the subject)
  • If any part of the rectification was declined, the reasons and the subject's right to complain

Response Timeline

  • Standard deadline: 30 calendar days from receipt of the request.
  • Extension: Up to 60 additional days for complex cases (Art. 12(3)).
  • Implementation target: Rectification should be applied to primary systems within 5 business days of the verification decision, even if the formal response is still being prepared.

Implementing Transparent Communication

Overview

GDPR Article 12 establishes the overarching framework for how controllers must communicate with data subjects about data protection matters. All information under Articles 13-14 and all communications under Articles 15-22 and 34 must be provided in a concise, transparent, intelligible, and easily accessible form, using clear and plain language. This skill covers the operational requirements for achieving transparent communication.

Legal Foundation

GDPR Article 12 — Transparent Information, Communication and Modalities

  1. Art. 12(1) — The controller shall take appropriate measures to provide any information referred to in Articles 13 and 14 and any communication under Articles 15 to 22 and 34 in a concise, transparent, intelligible and easily accessible form, using clear and plain language, in particular for any information addressed specifically to a child. The information shall be provided in writing, or by other means, including, where appropriate, by electronic means. When requested by the data subject, the information may be provided orally, provided that the identity of the data subject is proven by other means.

  2. Art. 12(2) — The controller shall facilitate the exercise of data subject rights under Articles 15 to 22. The controller shall not refuse to act on the request of the data subject unless it demonstrates that it is not in a position to identify the data subject.

  3. Art. 12(3) — Response timeline: without undue delay and in any event within one month of receipt. Extension by two further months where necessary. Notification of extension within one month with reasons.

  4. Art. 12(4) — If the controller does not take action on the request, inform the data subject without delay and at the latest within one month: reasons for not taking action, possibility of lodging a complaint with a supervisory authority, and seeking a judicial remedy.

  5. Art. 12(5) — Information under Articles 13 and 14 and any communication and actions under Articles 15 to 22 and 34 shall be provided free of charge. Where requests are manifestly unfounded or excessive, the controller may charge a reasonable fee or refuse to act.

  6. Art. 12(6) — Where the controller has reasonable doubts about the identity of the natural person making the request, it may request the provision of additional information necessary to confirm identity.

  7. Art. 12(7) — Information to be provided under Articles 13 and 14 may be provided in combination with standardised icons.

Transparency Requirements

Plain Language Standard

Per EDPB Guidelines on Transparency (WP260 rev.01):

  1. Concise: Eliminate unnecessary detail. Separate essential from supplementary information using layered notices.
  2. Transparent: No hidden information. All material processing details must be disclosed.
  3. Intelligible: Written at a reading level accessible to the average member of the intended audience. For general public notices, target an 8th-grade reading level (Flesch-Kincaid Grade Level 8 or below).
  4. Easily accessible: Available without the data subject having to search for it. Prominently placed, not buried in terms and conditions.
  5. Clear and plain language: No legal jargon, no technical terminology without explanation, no double negatives, no ambiguous phrasing.

Language Requirements

ScenarioLanguage Obligation
Service offered in one EU/EEA Member StateLanguage of that Member State
Service offered across multiple Member StatesLanguage of each Member State where the service is actively offered
Service specifically targeting a linguistic minorityConsider providing in that language
Children as intended audienceLanguage and vocabulary appropriate for the age group

Layered Notice Approach

The EDPB recommends a layered approach to provide transparency without overwhelming the data subject:

Layer 1: Short Notice (Immediate Point of Collection)

Displayed at the point of data collection. Contains the most critical information:

  • Identity of the controller
  • Purpose(s) of the processing
  • Description of data subject rights
  • Information about the most impactful processing (e.g., profiling, international transfers)
  • Link to full privacy notice

Format: 150-300 words. Visible without scrolling. No click-through required.

Layer 2: Full Privacy Notice

The complete privacy notice containing all information required under Art. 13 or Art. 14. Accessible from Layer 1 via a clear link.

Format: Structured with clear headings, table of contents, expandable sections where appropriate. Written in plain language throughout.

Layer 3: Supplementary Detail

Detailed information for specific processing activities, available on request or through contextual links:

  • Legitimate interest assessments
  • International transfer mechanisms and safeguards
  • Data retention schedule detail
  • Automated decision-making logic explanations

Response Timeline Management

ActionDeadlineExtensionNotification
Acknowledge receipt of request3 business days (best practice)N/ASend acknowledgement with reference number
Respond to data subject right request30 calendar days from receiptUp to 60 additional daysNotify within initial 30 days with reasons
Respond to identity verification request30 calendar days from verification completionUp to 60 additional daysNotify within initial 30 days
Inform of refusal to act30 calendar days from receiptN/AMust include: reasons, right to complain, right to judicial remedy

Fee and Refusal Framework

When a Fee May Be Charged (Art. 12(5)(a))

A reasonable fee based on administrative costs may be charged where requests are:

  • Manifestly unfounded: The requester has stated a disruptive intent, or there is no legitimate purpose for the request.
  • Excessive: Due to repetitive character (e.g., the same request submitted repeatedly without any change in processing).

Meridian Analytics Ltd fee schedule: GBP 10.00 base fee + GBP 0.10 per page exceeding 500 pages.

When Refusal Is Permitted (Art. 12(5)(b))

The controller may refuse to act where the request is manifestly unfounded or excessive, but must:

  1. Inform the data subject of the reasons for not taking action.
  2. Inform of the possibility to lodge a complaint with the ICO.
  3. Inform of the right to a judicial remedy.

The burden of proof for demonstrating that a request is manifestly unfounded or excessive lies with the controller.

Communication Templates

Acknowledgement Elements

Every acknowledgement must include:

  1. The reference number assigned to the request
  2. The date the request was received
  3. The type of right being exercised
  4. The expected response date (30 calendar days)
  5. Contact details for the DPO for any queries
  6. A statement that the request is being processed free of charge (unless fee/refusal applies)

Refusal Elements

Every refusal must include:

  1. The specific reason(s) for refusing to act
  2. The evidence supporting the manifestly unfounded or excessive determination
  3. The data subject's right to lodge a complaint with the Information Commissioner's Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, telephone 0303 123 1113
  4. The data subject's right to seek a judicial remedy under Article 79

Extension Notification Elements

  1. Confirmation that the request is being processed
  2. The specific reason(s) for the extension (complexity, volume, concurrent requests)
  3. The extended deadline date
  4. Contact details for queries about the delay

Sponsors

Details

Marketplace
mukul975/Privacy-Data-Protection-Skills
Source
plugins/data-subject-rights-skills
Author
Mahipal
Category
Compliance
License
Apache-2.0
Keywords
dsar, data-subject-rights, access-request, erasure, portability

More from mukul975/Privacy-Data-Protection-Skills

All 21