Dropbox Watchdog

Search issues

Search the Dropbox Watchdog archive

All issues

Named in the NSA's PRISM slides as 'coming soon'

June 2013

MediumStatus: HistoricalProduct: Core syncYear: 2013

Among the classified NSA PRISM documents leaked by Edward Snowden, Dropbox appeared as a provider the surveillance program planned to add, listed as 'coming soon' — placing the company squarely inside the post-Snowden surveillance debate.

What happened

In June 2013 The Guardian and The Washington Post published leaked NSA materials describing PRISM, a program for collecting data from major U.S. internet companies. The slide deck, drawn from documents Edward Snowden removed shortly before leaving the agency in 2013, listed established participants such as Microsoft, Google, Apple, and Facebook — and noted that Dropbox was 'coming soon' as a future provider.

The 'coming soon' notation does not establish that Dropbox ever voluntarily joined PRISM, and the company has consistently said it does not give any government direct or unfettered access to user data. What the slide documented was the NSA's stated intention to extend collection to Dropbox. Like other U.S. companies, Dropbox can be served with legal orders, including directives under Section 702 of the FISA Amendments Act, and its server-side-key model means it is technically able to decrypt and produce files when compelled.

The disclosure landed at the worst possible moment for a company whose privacy promises were already under FTC scrutiny, and it became a fixture of the broader argument that storing unencrypted-to-the-provider data in U.S. cloud services exposes it to government surveillance.

Impact

Appearing in the PRISM slides cemented Dropbox's reputation as a surveillance liability among privacy advocates and helped drive enterprise and international customers toward providers offering client-side or zero-knowledge encryption. It set the stage for Edward Snowden's later, blunter criticism of the company and intensified scrutiny of Dropbox's board, its government-request handling, and the keys-held architecture that makes compelled decryption possible.

Dropbox's Response / Official Position

Dropbox said it had not been approached to join PRISM and that it does not provide any government with direct access to its servers or a back door. It pointed to its practice of requiring valid legal process for data requests and to its transparency reporting on the volume and types of government demands it receives.

Sources

Related guides

Spot an error, or have a source to add?
Report an error / suggest update

Related issues

Because Dash can be downloaded and set up with 'no sales or IT required,' an individual employee can connect and index an organization's apps and browser history without administrator oversight — recreating the shadow-IT data-governance risk that earlier consumer Dropbox use posed to enterprises.

Privacy & Encryption ConcernsCurrent / Ongoing Issues (2024–2026)Account Lockouts & Support Failures
Read documentation

Dropbox repeatedly assures users that AI features do not train on their data and that content is deleted within 30 days — but because these are revocable policy promises layered over server-side access rather than technical guarantees, security commentators remain skeptical that the assurances will hold.

Privacy & Encryption ConcernsCurrent / Ongoing Issues (2024–2026)
Read documentation

Through 2025 Dropbox pushed Dash to general availability with self-serve sign-up and no IT required, marketing it as an AI assistant that indexes content across all of a user's connected apps — a model that, by design, reaches far beyond the files stored in Dropbox.

Privacy & Encryption ConcernsProduct Changes & User BacklashCurrent / Ongoing Issues (2024–2026)
Read documentation

Dash connects to Google Workspace, Microsoft 365, Slack, Notion and more, and routes queries through large language models — leaving users to trust Dropbox's contractual assurances that connected and indexed data is not used to train third-party AI models.

Privacy & Encryption ConcernsCurrent / Ongoing Issues (2024–2026)Developer, API & Platform
Read documentation