6.1–Open Collaboration: Privacy requirements, risks, Records retained of key project implementation methods and outcomes should be consultations and decisions documented throughout the development lifecycle and communicated to project members and stakeholders. 6.2–Open to Review: The design and operation of software Where relevant, documentation should systems should demonstrably satisfy the strongest support compliance and other privacy laws, contracts, policies and norms (as reporting/diligence/validation required). requirements the software product is to be used 6.3–Open to Emulation: The design and operation of by other systems, relevant privacy-enhanced information technologies and documentation should be available systems should be open to scrutiny, praise and emulation by all. 7. Respect for User* Privacy Keep it User-Centric *User = Data Subject – Attention to effective UI/UX Design 7.1–Anticipate and Inform: Software should be designed with user/data subject privacy interests in mind, and convey privacy attributes (where relevant) in a timely, useful, and effective way. Privacy options and controls are 7.2–Support Data subject Input and Direction: available, prominent, clear and effective Technologies, operations and networks should allow users/data subjects to express privacy preferences and controls in a persistent and effective way. Record of personal data uses is 7.3–Encourage Direct User/Subject Access: Software available to data subjects systems should be designed to provide data subjects direct access to data held about them, and an account of uses and disclosures.
6.1–Open Collaboration: Privacy requirements, risks, implementation methods and outcomes should be documented throughout the development lifecycle and communicated to project members and stakeholders. Records retained of key project consultations and decisions 6.2–Open to Review: The design and operation of software systems should demonstrably satisfy the strongest privacy laws, contracts, policies and norms (as required). Where relevant, documentation should support compliance and other reporting/diligence/validation requirements 6.3–Open to Emulation: The design and operation of privacy-enhanced information technologies and systems should be open to scrutiny, praise and emulation by all. the software product is to be used by other systems, relevant documentation should be available 7. Respect for User* Privacy – Keep it User-Centric *User = Data Subject 7.1–Anticipate and Inform: Software should be designed with user/data subject privacy interests in mind, and convey privacy attributes (where relevant) in a timely, useful, and effective way. Attention to effective UI/UX Design 7.2–Support Data subject Input and Direction: Technologies, operations and networks should allow users/data subjects to express privacy preferences and controls in a persistent and effective way. Privacy options and controls are available, prominent, clear and effective 7.3–Encourage Direct User/Subject Access: Software systems should be designed to provide data subjects direct access to data held about them, and an account of uses and disclosures. Record of personal data uses is available to data subjects
20140411%20-%20Operationalizing%20PbD%20Principles%20-%20Overview_v42.docx