Building private products
summary
WhatsApp runs on 2 billion users sending 100 billion messages a day and claims privacy as a product feature. It ships end-to-end encryption using the Signal protocol and built end-to-end encrypted backups by storing backup keys in server-side HSMs + OPAQUE so WhatsApp can facilitate restores without learning keys. It prototypes privacy tokens to prove relationships to the server without storing interaction graphs. Workarounds include Rust, fuzzing and static analysis for client memory safety; challenges are payload bloat, multi-device token sync and usability of key recovery.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:36WhatsApp privacy principles
- 7:56End-to-end encrypted backups
- 11:53Privacy tokens for access
- 15:54Security foundation for privacy
- 18:27Future directions
related talks
19mPrivate Calling at WhatsApp
23mWhatsApp Private Processing
01h 07mBuilding Rock-Solid Encrypted Applications
24mWhatsApp with privacy? Privacy issues with IM E2EE in the Multi-device setting
03mHighlights - Whats up WhatsApp? 2 Years After
39mUsing WhatsApp as a Command Line ( Breaking out of the walled Garden)
19mPrekey Pogo: Investigating Security and Privacy Issues in WhatsApp's Handshake Mechanism
32m(In)Secure Messaging Apps: A Lateral Movement Into Your Privacy
