Is it Controversial to Protect Privacy by Violating Privacy?
summary
Built an advanced link and document tracking system inside an end to end encrypted product that renders documents in the browser so servers never see plaintext, and it logs page-level view times plus IPs and download events. Legal basis is explicit controller consent, contractual necessity and GDPR accountability. The feature ships as manual enablement after KYC with aggregation, retention limits and an abuse report workflow. It works but creates ethical risk and relies on vendor gating and customer responsibility.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:59Background
- 1:42What is Treasury
- 3:10Encryption
- 4:38Feedback
- 5:45Transit Content Shield
- 6:09How it works
- 7:14Access log
- 8:28Privacy advocates
- 10:00Legal basis
- 14:48Controllers
- 17:58Solution
- 18:19Abuse Report
- 21:31Questions
related talks
28mBuild Privacy into Your Products and Gain User Trust
33mDesigning and Building With Privacy In Mind
25mImproving Safety with Privacy: An Exploration of Privacy...
52mDeveloping privacy
01h 02mWeaponizing Technology: Examining the Importance of Privacy...
37mDelivering High Speed with Low Risk
28mTurning Privacy Compliance into a Business-Enabler
28mPrivacy Engineering Networking Break AMA