Automated scanning of private files: PhotoDNA, CSAM hash-matching, and the 2015 silence
2015 (ongoing practice)
Dropbox runs every uploaded image and video through hash-matching systems such as Microsoft's PhotoDNA to detect known child sexual abuse material — automated scanning of users' private files that the company initially refused to explain.
What happened
Like other major cloud providers, Dropbox proactively scans content uploaded to and shared on its service against hash databases of known child sexual abuse material (CSAM), using technologies including Microsoft's PhotoDNA and Google's CSAI Match alongside hash lists from the National Center for Missing & Exploited Children (NCMEC) and the Internet Watch Foundation. When a match is found, Dropbox removes access, disables the account, and reports to NCMEC as required by U.S. law.
The practice surfaced publicly in 2015 when a Dropbox user's shared link was blocked for matching a flagged file, and reporting (Gizmodo, 'Dropbox Refuses to Explain Its Mysterious Child Porn Detection Software') noted Dropbox would not detail how its detection worked. The privacy tension is structural: detecting content by fingerprint requires Dropbox to be able to inspect files server-side, which is only possible because it does not use end-to-end encryption. Critics note the same infrastructure that scans for CSAM could in principle be repurposed to other categories, and that hash-matching carries a small but non-zero false-positive risk.
Impact
The scanning is widely regarded as a justified child-safety measure, but it is also a concrete demonstration that 'your' files are routinely read and fingerprinted by automated systems the moment they touch Dropbox. It anchors the broader privacy argument that server-side access — necessary for this scanning — is what makes mass inspection, and by extension breach and surveillance, possible at all.