project members and relevant and other stakeholders for data stakeholders. collection, use, disclosure, and/or elsewhere as applicable 6.2–Open to Review: The design and operation of software systems SHALL describe any measurements should demonstrably satisfy the incorporated in the software, or strongest privacy laws, contracts, monitoring software, or otherwise to policies and industry norms (as measure the usage and effectiveness required). of provided privacy options and controls, and to ensure continuous 6.3–Open to Emulation: The improvement. design and operation of information SHALL describe placement of privacy technologies and systems should settings, privacy controls, privacy be open to scrutiny, improvement, policy(ies), and accessibility, praise, and emulation by others. prominence, clarity, and intended effectiveness. 7. Respect for User 7.1–Anticipate and Inform: SHALL describe user privacy options Privacy Software should be designed with (including access), controls, user user/data subject privacy interests privacy preferences/settings, UI/UX in mind, and convey privacy supports, and user-centric privacy attributes (where relevant) in a model. timely, useful, and effective way. SHALL describe notice, consent, and 7.2–Support Data Subject Input other privacy interactions at the and Direction: Technologies, EARLIEST possible point in a data operations and networks should transaction exchange with a user/data allow users/data subjects to subject or her/his automated agent(s) express privacy preferences and or device(s). controls in a persistent and effective way. 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.
project members and relevant stakeholders. 6.2–Open to Review: The design and operation of software systems should demonstrably satisfy the strongest privacy laws, contracts, policies and industry norms (as required). 6.3–Open to Emulation: The design and operation of information technologies and systems should be open to scrutiny, improvement, praise, and emulation by others. and other stakeholders for data collection, use, disclosure, and/or elsewhere as applicable SHALL describe any measurements incorporated in the software, or monitoring software, or otherwise to measure the usage and effectiveness of provided privacy options and controls, and to ensure continuous improvement. SHALL describe placement of privacy settings, privacy controls, privacy policy(ies), and accessibility, prominence, clarity, and intended effectiveness. 7. Respect for User Privacy 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. 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. 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. SHALL describe user privacy options (including access), controls, user privacy preferences/settings, UI/UX supports, and user-centric privacy model. SHALL describe notice, consent, and other privacy interactions at the EARLIEST possible point in a data transaction exchange with a user/data subject or her/his automated agent(s) or device(s).
pbd-se-v1_0-wd04R2-sabo.docx