Portability right - a gap between concept and implementation reality
summary
Report finds six concrete failure modes for GDPR portability and shows surprising gaps between claims and reality: WhatsApp backup key discrepancy where device-only encryption contradicts documented Google Drive exports; Facebook takeout lacks identifiers so social graphs aren’t portable; routine 30‑day delays, fragmented request channels, and irrelevant data dumps. Recommends standardized machine-readable takeouts, DevRegOps (embed compliance into event-driven pipelines), treat portability requests as events to assemble selective exports across AWS, Firebase, Salesforce, Algolia, and push from declarations to enforced implementations.
AI-written summary · about
chapters (4)
- 0:00Start
- 11:13DevRegOps approach is the key
- 19:42Concrete illustration of a DevRegOps usecase applied to Data Portability
- 22:46The rise of a new ecosystem of DevRegOps tools and methods
related talks
38mThe Reality of Porting Kubernetes Apps Across Cloud Providers
41mExtreme Software Portability as an Art Form
54mCredential Sharing As A Service: The Dark Side Of No Code
37mCompliance & Regulatory Standards Are NOT Incompatible with Modern Development..
44mDeveloper Productivity Shouldn’t Breach Security
26mChallenges of Large Enterprises in Moving to the Public Cloud
41mPlanning for Retirement: How Can We Prepare for Software’s...
10mLightning Talk: Progress Over Purity: Sovereignty That Actually Ships