PRI-29.1: Continued Use of Personal Data (PD)
Mechanisms exist to govern the continued use of Personal Data (PD) as it is collected, received, processed, stored, transmitted, shared and/or updated until: (1) Disposal of PD occurs when there is no longer a legitimate business purpose; (2) Disposal of PD occurs when the data retention timeline for the use case is met; and/or (3) Continued use of PD is prohibited upon withdrawal of data subject consent.
Renumbered: Formerly PRI-03.9 in SCF 2025.4.
Control Question: Does the organization govern the continued use of Personal Data (PD) as it is collected, received, processed, stored, transmitted, shared and/or updated until: (1) Disposal of PD occurs when there is no longer a legitimate business purpose; (2) Disposal of PD occurs when the data retention timeline for the use case is met; and/or (3) Continued use of PD is prohibited upon withdrawal of data subject consent?
General (3)
| Framework | Mapping Values |
|---|---|
| APEC Privacy Framework 2015 | 4 4(b) |
| ISO 29100 2024 | 6.6 |
| OECD Privacy Principles | 4 |
US (4)
| Framework | Mapping Values |
|---|---|
| USA Federal Data Privacy Framework 2023 | III.14.c.i |
| USA California CCPA 2025 | 7022(f)(3) 7027(b) 7027(g)(1) |
| USA Texas CDPA 2025 | 541.052(a) 541.052(f)(2) |
| USA Virginia CDPA 2023 | 59.1-578.F.1.d |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA EU GDPR 2016 | Article 18.2 |
| EMEA Italy PDPC 2018 | Article 99(1) |
APAC (4)
| Framework | Mapping Values |
|---|---|
| APAC Hong Kong PDO 2022 | Schedule 1 - 2(1)(b)(i) Schedule 1 - 2(1)(b)(ii) |
| APAC India DPDPA 2023 | 5(2)(b) 9(2) 9(3) |
| APAC Japan APPI 2020 | IV.1.30(2) IV.1.30(4) IV.1.30(6) IV.1.30(7) IV.1.31 |
| APAC Singapore PDPA 2012 | 4.2.19(a) 9.3.47(3) |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Bahamas DPA 2003 | IV.35(1) IV.35(1)(a) IV.35(1)(b) IV.36(1) |
| Americas Chile Act 19628 1999 | I.9 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Privacy (PRI) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PRI domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with PRI domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRI domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Data privacy management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Data privacy management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ The data privacy program is developed to work with IT and cybersecurity staff to ensure that applicable statutory, regulatory and/or contractual data privacy obligations for Personal Data (PD) are properly identified and implemented.
Level 3 — Well Defined
Privacy (PRI) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with PRI domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with PRI domain capabilities are well-documented and kept current by process owners. ▪ A data privacy team, or similar function, is appropriately staffed and supported to implement and maintain PRI domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of data privacy operations (e.g., privacy notice management software and customer management solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with PRI domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to govern the continued use of Personal Data (PD) as it is collected, received, processed, stored, transmitted, shared and/or updated until: (1) Disposal of PD occurs when there is no longer a legitimate business purpose; (2) Disposal of PD occurs when the data retention timeline for the use case is met; and/or (3) Continued use of PD is prohibited upon withdrawal of data subject consent.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- PRI-29.1_A01 a process exists to notify affected the Personal Data Process Manager, or similar role, when a data subject withdraws consent.
- PRI-29.1_A02 a process exists to cease processing Personal Data (PD), once notification of consent revocation is received.
Technology Recommendations
Micro/Small
- Document the basis for continued use of personal data
Small
- Policy defining conditions for continued PD use after initial purpose
Medium
- Formal continued use assessment process
- Documentation of continued use justification
Large
- Enterprise privacy review process for continued PD use
- Legal basis documentation
Enterprise
- Enterprise privacy management platform with continued use workflows
- Legal basis tracking (e.g., OneTrust)