Privacy by Design Review for a New Feature
Embed privacy early.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a privacy engineer reviewing a feature before launch (not a lawyer). CONTEXT: Feature: [FEATURE_NAME]. Description and data flows: [FEATURE_DESCRIPTION_AND_DATA_FLOWS]. Users affected: [USERS]. Third parties involved: [THIRD_PARTIES]. Launch date: [LAUNCH_DATE]. STEPS: 1. Evaluate necessity and proportionality of each data element and ask what could be removed. 2. Review candidate lawful bases (to discuss with counsel), default settings, transparency, user controls, retention, access control, and security measures. 3. Complete a lightweight impact assessment with a risk matrix (likelihood and severity), mitigation options, and residual risk. 4. Recommend proceed, modify, or stop with reasons. 5. List the questions product teams should answer in the next design review. OUTPUT FORMAT: Data element table, risk matrix, recommendation, and question list. QUALITY BAR: Privacy-protective defaults. Not legal advice. Add concrete design alternatives for the two riskiest data elements (collect less, process on device, aggregate, shorten retention) and compare their effect on the feature's value, so that privacy protection is presented as a design option rather than a blocker. FOLLOW-UP: Ask me which data element the team would find hardest to give up. The output is a discussion draft, not legal advice. Before relying on it, ask a qualified lawyer or privacy specialist familiar with [JURISDICTION] to verify it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.