Consent copy framework
- Workshop rows stress-test clarity, withdrawal fairness, and evidence—not whether consent is the right lawful basis.
- Tie each surface to notices, logs, and owner sign-off before production copy ships.
- Pair with consent guide and counsel for high-risk flows.
This framework does not tell you whether consent is the correct basis for a given activity. It helps you stress-test clarity, fairness, and operability once your legal model is chosen.
| Review item | Notes / draft |
|---|---|
| Surface (URL / screen / channel) | |
| Specific purpose(s) described in plain language | |
| Data categories collected if user accepts | |
| Voluntary vs bundled choices (if applicable) | |
| Withdrawal path described + tested in product | |
| How consent is recorded (ID, timestamp, version) | |
| Linked notice URL / in-app disclosure | |
| Localization / accessibility checks | |
| Open legal questions for counsel |