liveBook · Manning

Privacy-by-design

As explained in The Art of AI Product Development

Privacy-by-design is an approach that embeds privacy protections into the architecture and operation of systems from the outset.

Privacy by design embeds privacy protections into an AI system’s architecture and operation from the outset. B2C products prioritize personal-data protection, while B2B deployments also protect intellectual property, trade secrets, and data sovereignty. section 11.2

Apply privacy by design through principles that anticipate exposure rather than repair it afterward:

  • Assess privacy risks early with privacy impact assessments before deployment, addressing data leaks and unintended access. section 11.2.2
  • Make privacy the default by anonymizing or redacting personally identifiable information and proprietary metrics without requiring user action. section 11.2.2
  • Embed controls into the architecture through anonymized training and evaluation data, data minimization, and, where suitable, federated learning. section 11.2.2
  • Preserve functionality and performance so privacy strengthens the system rather than forcing a zero-sum trade-off. section 11.2.2

Recommendation system

Before generating recommendations, anonymize or redact sensitive data by default. Offer transparent choices when including additional data could create more value, and expose only the information needed for each recommendation. section 11.2.2

Figure 11.6 The seven principles of privacy-by-design
A diagram of privacy by design

AI-generated content may be incorrect.

Use the figure to review the seven privacy-by-design principles as a complete checklist. section 11.2.2

How The Art of AI Product Development covers it

How deep it goes
Defines principles and concrete controls, but stops short of detailed implementation for the complete seven-principle framework.
Examples
Uses recommendation generation, anonymized model data, redacted sensitive fields, privacy impact assessments, and federated learning as concrete examples.
What it assumes
Assumes responsibility for nonpublic data and distinguishes personal privacy concerns from enterprise IP, trade-secret, and sovereignty concerns.
What you can do after
Build privacy controls into AI systems, assess exposure early, minimize data use, and configure protective defaults.
How it connects
Connects privacy with data minimization, anonymization, federated learning, privacy impact assessments, AI governance, compliance, and data sovereignty.

Also explained in

Compare how 3 books explain privacy-by-design →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Art of AI Product Development. The section links point to the parts of the book it draws on.