Privacy impact thinking for new features (lightweight DPIA habits)

Short answer: Before you ship a chatbot, loyalty programme, or new analytics pixel, ask what personal data flows change, who can see it, and what could go wrong—a lightweight impact habit prevents retrofits.

A full DPIA may be required sometimes; many SMEs still benefit from a one-page template.

Five questions worth answering

• What new data? content, identifiers, behavioural signals.
• Necessity: can you achieve the goal with less?
• Sharing: new subprocessors or cross-border flows?
• Risk: misuse, breach, surveillance surprises.
• Mitigations: access limits, retention caps, user controls.

When to deepen the review

Large-scale profiling, systematic monitoring of public spaces, or data matching across unrelated datasets are classic escalation triggers.

Developer collaboration

Embed privacy checks in tickets—cheaper than ripping out a feature after launch.

Frequently asked questions