Building protection in from the start.
WHAT IT MEANS
Considering privacy when designing, not after building.
WHY IT MATTERS
Retrofitting protection is expensive and frequently incomplete.
WHAT TO ASK AT DESIGN TIME
What data do we actually need Could we achieve this with less How long must we keep it Who needs access What happens if it leaks How will people exercise their rights
WHAT MINIMISATION LOOKS LIKE IN PRACTICE
Not collecting a field because it might be useful later Storing a derived value instead of the raw data Aggregating rather than retaining individual records
WHAT PRIVACY BY DEFAULT MEANS
The most protective settings apply unless the person chooses otherwise.
WHAT THAT LOOKS LIKE
Sharing off by default Profiles private unless made public Marketing off until opted in
WHAT TO BUILD FROM THE START
The ability to export a person's data The ability to delete it, completely Logging of access
WHY FROM THE START
Each is far harder to add later.
WHAT TO INCLUDE IN DESIGN REVIEW
A privacy question, alongside security.
WHAT TO DOCUMENT
The decisions, and what was rejected.
WHAT TO AVOID
Collecting data with no defined purpose.
WHY
It is the origin of most later problems.
