Every secure connection starts with a handshake. But historically, that handshake has leaked your destination server's name (SNI) in plaintext to every ISP, Wi-Fi operator, and network appliance along the way. In Android 17 (API level 37), we’re addressing this long-standing privacy gap by introducing platform-wide support for ECH. This session will explore what this change means for your application's user privacy. You’ll learn: - How to use the new domain-encryption element in your Network Security Configuration to customize ECH usage globally or on a per-domain basis - What to do if you’re using standard network libraries like OkHttp or HttpEngine - What new APIs were introduced to provide ECH support (i.e. HTTPS DNS querying, etc.) - What ECH GREASE is, and why Android has enabled it by default on apps targeting API 37+