Engineering a Consent Sandbox to Eliminate Annoying Pop-Ups and Dark Patterns
summary
Explains a concrete engineering path: tried sandboxed iframes (too slow), dynamic CSPs (blocks but can’t replay), then built a runtime firewall that patches all JS network APIs plus virtual documents to intercept DOM-caused requests, quarantines events locally and replays them after consent. Ships as airgap.js — a 30 KB drop-in that covers fetch XHR sendBeacon websockets image/script loads, is tested on heavy interactive sites with no noticeable overhead, and is available via the Transcend Consent Manager.
AI-written summary · about
chapters (11)
- 0:00Introduction to talk
- 1:05Broken consent experience
- 3:35Local tracking solution
- 7:27Dynamic CSP approach
- 10:17Patching network APIs
- 14:32Introducing AirGap.js
- 15:57Q&A begins
- 16:17Security applications
- 17:42Product availability
- 19:32Dark patterns explained
- 21:38Closing remarks
related talks
29mPrivacy Sandbox
24mBuilding the Privacy Sandbox
22m#notalljavascript (How to deal with 3rd party JS)
01h 11mSTANDARD FOR CONSENT: STILL A DREAM OR A SOON-TO-BE REALITY?
20mMicrointeractions for the System: Design in the Age of Techlash
13mConsent Management at Airbnb
16mOpen web standards with Privacy Sandbox
49mHow product-driven privacy ensures real compliance
