Study guide
7.1 Data Subject Access Requests & Consent/Rights Processes
Certified Information Privacy Manager CIPM
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 CIPM Exam Facts & Format 1.2 The CIPM Body of Knowledge: Six Domains & How the Exam Is Built 1.3 Study Strategy, Timeline & How to Use This Guide
2 Domain I: Developing a Privacy Program Framework
2.1 Program Scope, Strategy & Governance Model 2.2 Stakeholders, Privacy Team Structure & Common Vocabulary 2.3 Applicable Regulations, Oversight Agencies & Non-Compliance Impact 2.4 Personal Information Sources, Cross-Border Operations & AI Privacy Risk 2.5 Business Model, Operating Environment & Risk Appetite 2.6 Structuring the Privacy Team: DPO, CPO, Representatives & Resourcing 2.7 Vision, Mission & the Privacy Program Communication Plan 2.8 Policy Access, Version Control & Role-Relevant Updates 2.9 Codes of Conduct, Certifications & Self-Certification Mechanisms
3 Domain II: Establishing Program Governance
3.1 Privacy Policies & Life-Cycle Processes 3.2 Breach, Complaint, DSR & Retention Plans 3.3 Roles, Responsibilities, Metrics & Continuous Legal Monitoring 3.4 Training & Awareness Activities 3.5 Governance Bodies, Program Charter & Escalation Paths 3.6 Governing Internal & External Data Sharing and Disclosure 3.7 Retention Schedules & Defensible Disposal 3.8 Regulatory Change Monitoring & Enforcement Systems
4 Domain III: Operational Life Cycle — Assessing Data
4.1 Data Inventories, Flows & Life-Cycle Mapping 4.2 Data Discovery, System Integrations & Keeping the Inventory Current 4.3 Policy Compliance Measurement & Gap Analysis 4.4 Processor/Vendor Evaluation & Physical/Environmental Controls 4.5 Third-Party Risk Life Cycle & Sub-Processor Chains
5 Domain III (continued): Assessing Data — Technical & Physical Controls, M&A Risk
4.6 Technical Controls, Use/Retention Limits & Data Location 4.7 Physical & Environmental Controls in Depth 4.8 Mergers, Acquisitions & Divestitures Data Risk
6 Domain IV: Operational Life Cycle — Protecting Personal Data
5.1 Information Security Practices, Data Classification & Access Controls 5.2 Privacy by Design Principles & the SDLC 5.3 Organizational Guidelines for Data Use & Secondary-Use Governance 5.4 Privacy-Enhancing Technologies & Technical Control Enforcement 5.5 Technical, Administrative & Organizational Measures 5.6 Access Reviews, Monitoring & Enforcing Technical Controls
7 Domain V: Operational Life Cycle — Sustaining Program Performance
6.1 Privacy Metrics for Program Performance 6.2 Auditing the Privacy Program 6.3 Continuous Assessment: PIA, DPIA, TIA, LIA & PTA 6.4 Risk Mitigation, Post-M&A Assessment & Ethical AI Use
8 Domain VI: Operational Life Cycle — Responding to Requests & Incidents
7.1 Data Subject Access Requests & Consent/Rights Processes 7.2 Global Privacy Legislation on Data Subject Rights 7.3 Incident Handling, Breach Response & Records 7.4 Post-Incident Review & IR Plan Improvement 7.5 Privacy Notices & Transparency Obligations 7.6 Complaint Handling & Regulator Interaction 7.7 Breach Communications to Regulators, Individuals & Other Stakeholders
9 Final Review & Exam Strategy
8.1 Mixed-Domain Scenarios & Common Exam Traps 8.2 Test-Day Logistics, Score Strategy & Credential Maintenance
7.1 Data Subject Access Requests & Consent/Rights Processes
Key Takeaways Explain This Topic AI
A Data Subject Access Request (DSAR) is the individual's mechanism to exercise rights of access, deletion, rectification, portability, restriction, objection, and consent withdrawal against a controller
GDPR Article 12(3) requires controllers to respond 'without undue delay and at the latest within one month' of receipt, extendable by two further months for complex or numerous requests with notice within the first month
CCPA/CPRA gives businesses 45 days to respond to verifiable consumer requests, with a single 45-day extension permitted when reasonably necessary
Identity verification must be proportionate to the sensitivity of the data and the risk of unauthorized disclosure — over-collection of ID for verification can itself become a privacy violation
Consent is a lifecycle, not a one-time event: collect → record → manage → honor withdrawal → delete, and withdrawal must be as easy as giving consent
Last updated: August 2026
What a DSAR Is and Why It Matters
A Data Subject Access Request (DSAR) — sometimes called a subject access request (SAR) or, under the California Consumer Privacy Act (CCPA), a verifiable consumer request — is the individual's formal mechanism to exercise one or more of their statutory privacy rights against an organization that processes their personal data. Under the CIPM Body of Knowledge (BoK competency VI.A), privacy managers must ensure the organization can receive, verify, fulfill, and document these requests consistently and within statutory deadlines.
The privacy notice and internal privacy policies must transparently articulate the data subject's rights and the means of exercising them. A notice that lists rights but omits how to invoke them, or sets an internal contact address the organization does not actually monitor, is a transparency defect that regulators routinely cite.
The Rights Most Commonly Invoked
Access — confirmation that data is processed plus a copy of it (GDPR Art. 15; CCPA 'know' categories and specific pieces)
- Rectification / Correction — fixing inaccurate or incomplete data (GDPR Art. 16; CCPA right to correct)
- Erasure / Deletion — removal of data under defined conditions (GDPR Art. 17; CCPA right to delete)
- Restriction — limiting processing pending verification or contestation (GDPR Art. 18)
- Portability — receiving data in a structured, commonly used, machine-readable format (GDPR Art. 20)
- Objection — stopping processing for direct marketing or certain other grounds (GDPR Art. 21)
- Withdrawal of consent — retracting consent at any time, as easily as it was given (GDPR Art. 7(3))
Opt-out of sale or sharing — preventing the transfer of personal information for monetary or other valuable consideration (CCPA)
- Complaint — the right to lodge a complaint with a supervisory authority (GDPR Art. 77)
- The DSAR Workflow
A defensible DSAR process follows a repeatable workflow. Each stage should generate an audit record so the organization can demonstrate accountability (GDPR Art. 5(2) — the principle of accountability).
Stage Key Activity Operational Notes
1. Intake Capture the request through any channel the organization offers (web form, email, call center, in person). Do not require a specific form. GDPR Art. 12(2) says controllers must facilitate requests; refusing a request because it was 'not on the right form' is a violation.
2. Acknowledge & Log Confirm receipt, open a ticket, assign an owner, and start the statutory clock. The GDPR clock starts on receipt, not on completion of internal triage.
3. Identity Verification Confirm the requester is the data subject or their authorized agent, using proportionate means. For sensitive data, stronger verification (e.g., identity document check) is justified; for low-risk data, matching on name + account number may suffice. Do not retain the verification artifact longer than necessary.
4. Search & Locate Identify all systems holding the individual's data — CRM, HRIS, backups, email, shared drives, third-party processors, legacy systems. Scope creep and missed systems are the two most common DSAR defects. Maintain a data map / RoPA (Record of Processing Activities, GDPR Art. 30) to make this stage reliable.
5. Review & Redact Review located data for third-party rights, legal privilege, trade secrets, and applicable exemptions before production. Redacting other individuals' personal data is required under GDPR Art. 15(4) and CCPA's business-purpose exemptions.
6. Produce & Respond Deliver the response in a concise, transparent, intelligible, and easily accessible form (GDPR Art. 12(1)). Close the ticket and record the outcome. Provide the information free of charge for the first copy under GDPR; CCPA requires free responses to consumers.
Timelines and Extensions
Regime Base Deadline Extension Trigger to Start Clock
GDPR 1 month from receipt Up to 2 further months for complex or numerous requests; must inform the requester of the extension and reasons within the first month (Art. 12(3)) Receipt of the request (not completion of verification)
CCPA/CPRA 45 days One 45-day extension when reasonably necessary; must inform the consumer of the reasons and the new deadline Receipt of a verifiable consumer request
HIPAA right of access 30 days One 30-day extension with written reason Receipt of request (45 CFR 164.524(b)(2))
Fees, Exemptions, and Refusal Grounds
Under GDPR , the first copy is free (Art. 15(3)); a reasonable fee may be charged for further copies based on administrative cost, and requests that are 'manifestly unfounded or excessive, especially because of their repetitive character' may be refused or a reasonable fee charged (Art. 12(5)). Controllers may also refuse to act where compliance would adversely affect the rights and freedoms of others, or where an exemption applies (e.g., legal professional privilege, public security).
Under CCPA , businesses may not charge a fee for responding to consumer requests, but may charge a reasonable fee (calculated on a per-request basis) for costs of verifying the consumer and delivering the information if the requests are 'manifestly unfounded' in nature.
The Consent Lifecycle
For organizations that rely on consent as a lawful basis (GDPR Art. 6(1)(a)) or as a valid opt-in for sensitive data (CCPA's right to limit use of sensitive personal information), consent is not a checkbox captured once at sign-up. It is a managed lifecycle:
Loading diagram...
GDPR Article 7(3) is explicit: the data subject shall have the right to withdraw consent at any time, and it shall be as easy to withdraw as to give consent. A withdrawal flow that is buried three menus deep while the opt-in was a single prominent checkbox is non-compliant, even if the data is ultimately deleted.
Consent and Rights — Operational Comparison
- Right / Action Controller Obligation Common Operational Pitfall
- Access Provide a copy plus processing details Over-redacting so the requester cannot tell what was withheld
Rectification Correct inaccurate data without undue delay; notify recipients (Art. 19) Fixing the source system but leaving stale copies in data warehouses or processor systems
Erasure Delete unless an exemption (legal obligation, freedom of expression, public interest) applies Restoring data from backup tapes after the production deletion, without a backup-deletion procedure
Objection to direct marketing Stop processing for marketing 'at the latest at the time of the next communication' Leaving the contact in a marketing suppression list that itself is used for analytics
Withdrawal of consent Stop consent-based processing; keep only what another lawful basis requires Treating withdrawal as a full deletion request when another basis (e.g., contract) still applies
Complaint Acknowledge; provide DPA contact details in the privacy notice Failing to log complaints and trend them for program improvement
Worked Scenario
A European customer emails a retailer's general support mailbox: 'I want a copy of all the data you hold on me, and I want to withdraw my consent for marketing.' The mailbox is monitored by a tier-1 agent who has received DSAR training.
Correct handling: The agent logs the request that same day in the privacy request system, sends an acknowledgement, and routes the ticket to the privacy team. The privacy team verifies identity using a proportionate check (matching the email to the account and asking the customer to confirm the last order total — a low-friction, sufficient check because the data to be released is low-sensitivity account data, not financial or health records). The team searches the CRM, marketing platform, order system, and ticketing system using the data map, redacts other customers' personal data from email excerpts, and produces a single consolidated response within 28 days. Separately, the marketing-consent withdrawal is actioned the same week — the customer is moved to a suppression list and removed from the active marketing audience on the email service provider, with the withdrawal timestamp recorded against the consent record.
What would be wrong: Telling the customer they must re-submit on a special web form; demanding a passport scan for a low-risk account-access request (over-collection); deleting the customer's order history when only marketing consent was withdrawn (over-broad action — the order data is needed for contract performance and tax obligations); or letting the 30-day GDPR clock run while waiting for the marketing team to confirm the suppression.