Privacy by Design Review for New Features
Check a feature design before it is built.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review a planned feature for privacy. Feature description and user flow: [FEATURE]. Data collected and stored: [DATA]. Third parties involved: [THIRD_PARTIES]. Target users: [USERS]. Produce a review with a checklist: data minimisation, purpose limitation, defaults, transparency, user controls, retention, access, security, vendor sharing, children's data, and deletion. For each item rate the design as meets, partially meets, or does not meet, with the evidence from my description and the change to make. Include alternative designs that collect less data and a short list of questions for the product team. Add acceptance criteria that engineers can test. Mark legal conclusions [VERIFY] and recommend review by privacy counsel for [JURISDICTION]. Add a quick-start version of the review as a ten-question form for small changes, and a rule for which changes require the full review. Provide a template for recording decisions and a method for tracking whether the requested changes were implemented before launch, with an owner and a date. Everything should help me defend and recover. If I ask for something that could be used to harm others, decline it and suggest a safer defensive route.
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.