Every field a product collects becomes a new data field to protect and explain later. Privacy by design means asking “do we really need this?” first.
Where does data minimisation start?
If a form does not need a phone number, do not add the field. If a report can work with a customer number instead of a name, do not expose personal data. When unnecessary data is never collected, access, retention and deletion processes stay simple too.
Decisions that can become product
- Setting the default to share less data.
- Applying role-based visibility and masking.
- Defining retention together with the technical workflow.
- Turning export and deletion requests into an operational feature.
- Limiting third-party integrations by purpose and scope.
Law and product at the same desk
The text can be written later, but data flows, permissions and retention decisions may not change so easily afterwards. At WYN we prefer to bring personal data questions into brief and architecture decisions.
Source / further readingWYN working approachThis article does not copy the original content of the source; it is WYN’s practical interpretation. For current headlines, check the publication date and the source page separately.