Make data collection purposeful, access limited, and retention understandable from the first product decisions.
- privacy by design
- data protection
- application privacy
- data minimization
Collect only what the workflow needs
For each field, document its purpose, who uses it, and how long it remains necessary. Avoid keeping sensitive data simply because storage is inexpensive.
Cloud, Data & SecurityCloud, Data & Security
Thoughtful decisions compound over time.
Practical product work brings technical choices back to the people and workflows they are meant to serve.
Build controls into normal operations
Limit access by role, protect data in transit and at rest, and make retention and deletion behavior explicit. Review logs and exports too, since they can become overlooked copies.
Review changes before release
New integrations, analytics, or AI features can change privacy risk. A design review helps teams identify data flows and appropriate safeguards before those flows become difficult to unwind.
Practical application
For each customer field, document the purpose, permitted roles, retention period, and deletion path. Review exports, analytics, logs, and third-party integrations because sensitive data often persists outside the primary database.
