Privacy Req 7
<< Back to Baseline Functional Requirements Index
PRIVACY-7. USER DATA CONTROL
“Appropriate” broadly means mechanisms for management of personal information should be effective, easy to use, and accessible. (See USABLE-1 (USABILITY PRACTICES), USABLE-3 (PLAIN LANGUAGE), and USABLE-5 (ACCESSIBILITY) for guidance on the usability of such mechanisms.)
"Deletion” generally refers to removal of the data from availability. Data disposal, its complete removal from the complying entity's own systems and control, may depend on the legal and contractual requirements applicable to the data; see PRIVACY-14 (DATA RETENTION AND DISPOSAL).
Note: Intermediaries may not have direct control over the information that flows through their systems, but should deploy mechanisms that support endpoints' ability to conform to this Requirement. See INTEROP-6 (THIRD-PARTY COMPLIANCE).
See the IDESG Functional Model for definition of Transaction Intermediation for the scope of “intermediaries.” The functional model describes Transaction Intermediation as “Processes and procedures that limit linkages between transactions and facilitate credential portability." This includes functions defined as “Blinding,” “Pseudonymization/Anonymization,” and “Exchange.”
Further reference materials to aid organizations interested in conforming to these Requirements can be found at the wiki page Supplemental Privacy Guidance; this has been archived at https://workspace.idesg.org/kws/public/download.php/56/Supplemental-Privacy-Guidance.docx
APPLIES TO ACTIVITIES