Auditing Apple's DifferentialPrivacy.framework: Implementation Bugs, Misconfigurations, and Practical Risks
Rishav Chourasia, Ergute Bao, Uzair Javaid, Xiaokui Xiao

TL;DR
This paper audits Apple's DifferentialPrivacy.framework, revealing implementation bugs, misconfigurations, and privacy violations across most mechanisms, raising concerns about the actual privacy guarantees in practice.
Contribution
It provides the first comprehensive reverse engineering and testing of Apple's DP implementation, exposing critical vulnerabilities and misconfigurations.
Findings
Multiple mechanisms fail to meet their DP guarantees due to insecure samplers.
Secure aggregation configurations often disable local DP, exposing raw data.
Leaks of private information such as Safari domains and keyboard signals were identified.
Abstract
Since 2016, Apple has claimed that device analytics collected to improve user experience are protected by differential privacy (DP). Apple's DifferentialPrivacy framework is deployed across its operating systems and handles sensitive signals such as Safari domains, keyboard events, photo attributes, and health-related reports. Because Apple has not open-sourced its privatization algorithms, these privacy claims have been difficult to verify independently. We present a client-side audit of Apple's DP framework on macOS Sonoma 14.2 and Sequoia 15.6. We reverse engineer the shipped binaries, recover Objective-C interfaces, build runtime harnesses that execute Apple's deployed mechanisms, and test whether their outputs match the advertised privacy guarantees. Our audit covers nearly all active deployed mechanisms, including Count Median Sketch, Hadamard-CMS, randomized-response mechanisms,…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
