Privacy by Design (PbD) - Seven Foundational Principles 3: Principle 3: Privacy Embedded into Design

Build privacy into how IT systems and business practices are designed and architected rather than attaching it afterwards, so that it becomes an essential part of the core functionality without reducing that functionality. Embedding should be holistic (wider contexts always considered), integrative (all stakeholders and interests consulted) and creative (sometimes reinventing existing choices because the available options are unacceptable). This calls for: a systematic, principled approach that relies on accepted standards and frameworks open to external review and audit, applying every fair information practice with equal rigour at each step of design and operation; detailed privacy impact and risk assessments, published wherever possible, documenting the risks and every mitigating measure, including the alternatives considered and the metrics chosen; and an end result (technology, operation or architecture, and how it is used) whose effect on privacy is shown to be as small as possible and does not readily erode through use, misconfiguration or mistakes.