When compliance causes confusion
Privacy is often treated as a legal checkbox; an afterthought that’s handled by adding a terms and conditions page or writing a privacy policy. But for users, it’s much more important than that. Privacy is something they experience directly when they share data, give consent, or try to have their information deleted.
These experiences are shaped by design choices. When legal and product teams aren’t working closely together, things can break down:
- Deletion requests can be missed because systems don’t give teams visibility
- Consent is collected in ways that are unclear, or not collected at all
- Privacy policies are hard to find or too complex for the average user to understand
- Users lose confidence or file complaints
- Teams disagree on what’s required and projects stall
Non-compliance due to the above breakdowns can be incredibly costly, from a brand reputation perspective and financially, if you suffer legal consequences. It’s important to note, these problems don’t just affect industries with strict regulation, like healthcare or finance, too. Any product that collects user data needs to get this right. Good design can’t fix compliance alone, but it can make the rules easier to follow, reduce friction, and help users feel informed and in control.


