how-to

Secure Storage for Journalists and Sensitive Document Work

If your work involves sensitive sources, confidential documents, or protected research, your file storage choice has real-world safety consequences.

Most guides on digital security for journalists focus on communication: encrypted messaging, secure email, using Signal for source contacts. Those tools matter. But there’s a parallel question that gets less attention: where are you actually keeping the files?

A source document. Interview recordings. A draft investigation. Notes from a background conversation. These don’t just travel between people — they sit somewhere, backed up and accessible, on systems you need to trust with material that could expose a source, end a career, or create legal liability for the people who trusted you with the information.

This guide focuses on file storage specifically: what the risks are, what to look for in a storage service, and how to think through the choice.


Why File Storage Is Different for This Kind of Work

Journalists, researchers, lawyers, activists, and human rights workers share a category of risk that most people don’t have to think about: adversarial access.

For most people, the main storage risks are accidental loss, ransomware, and the theoretical possibility of corporate data sharing. For people doing sensitive work, the threat model includes more:

  • Government legal process: Subpoenas, court orders, national security letters, and law enforcement warrants. Cloud providers in many jurisdictions — particularly the US, UK, and Australia — can be compelled to produce customer data under existing law. The question isn’t whether the provider wants to protect you; it’s whether they can.
  • Corporate espionage: Corporations subject to investigative reporting have resources and legal departments. Litigation against journalists has included discovery demands targeting their notes and source communications.
  • Targeted hacking: Sophisticated state and non-state actors regularly target journalists and human rights workers. In 2026, spyware designed to compromise cloud storage credentials remains an active threat.
  • Platform changes: A storage provider can change its terms, merge with another company, get acquired, or change its legal jurisdiction. What’s private today may not be tomorrow.

None of this means using a standard consumer cloud service is automatically wrong. It means understanding what standard consumer services are and aren’t designed to protect against.


The Gap in Most Cloud Storage Contracts

Standard cloud storage services — Google Drive, iCloud, Microsoft OneDrive, Dropbox — are built around a consumer use case. Their security model is designed to protect against account takeover and casual unauthorized access. It is not designed to protect against government legal process.

All of these providers have published transparency reports disclosing how often they receive government requests and how often they comply. The numbers vary, but all of them comply with lawful legal orders in their respective jurisdictions. That is not a criticism — it’s how legal systems work. But it means that if a government entity with appropriate jurisdiction issues a lawful demand, the provider will produce your files.

The implication: if your storage service operates under US, UK, Australian, or EU jurisdiction (and most consumer services do), and a government entity with authority in that jurisdiction issues a legal demand, your files are reachable.

There’s also a secondary concern: legal process can be used by parties other than governments. Civil discovery in litigation can reach cloud storage. A corporation pursuing a journalist through litigation can, in some circumstances, seek discovery of storage accounts. This has happened.


What Encryption Actually Protects

The word “encrypted” is used loosely enough to be nearly meaningless in most consumer contexts. What matters is: encrypted at which point, by whom, with keys held where?

There are two fundamentally different models:

Server-side encryption: The provider encrypts your files before storing them on disk. This protects against a scenario where a hard drive is physically stolen. It does not protect against a legal demand to the provider, because the provider holds the decryption keys. The provider can decrypt your files and produce them.

Client-side (zero-knowledge) encryption: Encryption happens on your device before the files reach the provider’s servers. The provider stores ciphertext it cannot read. Even if compelled, the provider cannot produce the plaintext of your files — only the encrypted blob. Legal demands become much less useful, though metadata (what files exist, when they were accessed, from which IP addresses) may still be producible.

For most people, server-side encryption is adequate. For journalists, activists, lawyers, and researchers working with genuinely sensitive material, the distinction matters enormously.


What to Look for in a Storage Provider

When evaluating a provider for sensitive document storage, here’s what to check:

Jurisdiction: Where is the company incorporated? Where are the servers? Both matter. A company incorporated in a jurisdiction with strong privacy laws, with servers in that same jurisdiction, provides stronger legal protection than a US-incorporated company with US servers.

Encryption model: Server-side or client-side? If the provider can comply with a legal demand by handing over your files, that tells you something. Zero-knowledge providers can honestly say they cannot produce file contents, only encrypted data.

Data practices: Does the provider use your files for advertising, analytics, or AI training? A provider whose business model involves processing your content introduces additional risk surfaces: more people with access, more infrastructure with your data in it.

Legal history: Has the provider been compelled to produce data before? Transparency reports document this. Zero-knowledge providers that have received legal demands and been unable to produce file contents are demonstrating rather than merely claiming their protection model.

Account deletion: What happens to your files if you delete your account? How long does the provider retain data after account closure? Under what circumstances does the provider retain data after a user deletes it?


Practical Steps for Sensitive File Storage

Separate your storage by sensitivity level. Not everything needs the same protection. Research on publicly available topics, published articles, and general organizational files don’t require the same treatment as source communications, unpublished investigations, or documents that could identify a source.

Use a dedicated account for sensitive work. A storage account tied to your professional work identity and email is a different target than a personal account with years of family photos. Separating them reduces what an adversary gains from compromising one.

Understand what metadata your provider retains. Even zero-knowledge providers typically retain some metadata: file sizes, timestamps, access logs, IP addresses. This information can be meaningful in certain legal contexts. Ask what your provider logs and for how long.

Keep local copies of irreplaceable material. Cloud storage can fail, get hacked, or be compelled. For genuinely critical materials, a local encrypted backup on hardware you control is a parallel protection. Tools like VeraCrypt allow you to create encrypted containers on local drives that can’t be compelled from a provider.

Know your provider’s legal response process. If a legal demand arrives, does your provider notify you before complying (if legally permitted to do so)? Does the provider fight clearly overbroad requests? Does the provider have a legal team and a track record? This isn’t information you’ll need most of the time, but it matters when you do.


The Self-Hosting Consideration

Self-hosted storage — running your own Nextcloud instance on your own hardware, for example — appears to solve the third-party provider problem: if there’s no provider, there’s no one to serve a legal demand on.

The reality is more complicated. First, self-hosted infrastructure is only as secure as your ability to maintain it. Security updates, correct configuration, and protection against account takeover require ongoing effort. The May 2026 Nextcloud GmbH breach — which exposed 367,000 records from an improperly secured database — happened to the company’s own infrastructure, not user instances. User instances have their own history of exposure through misconfiguration and unpatched vulnerabilities.

Second, self-hosted infrastructure may still be reachable by legal process if it operates in the same jurisdiction as you do. The legal demand goes to you as the operator rather than to a third-party provider.

Third, self-hosted infrastructure tied to a physical location (your home, your office) has physical security implications.

Self-hosting can be appropriate for certain threat models, particularly if you have the technical expertise to maintain it securely. It shouldn’t be treated as inherently more private than a well-managed zero-knowledge cloud service.


When File Storage Isn’t Enough

File storage is one layer of a broader security posture. For work involving confidential sources or genuinely sensitive material, it’s part of a stack that should also include:

  • Encrypted communication for source contacts (Signal, SecureDrop)
  • Device security (full disk encryption, strong device passwords, up-to-date OS)
  • Account security (strong unique passwords, hardware security keys for two-factor authentication)
  • Network security (understanding what your ISP can see, using a VPN or Tor where appropriate)
  • OpSec habits (what you share on social media, who knows what you’re working on)

The Freedom of the Press Foundation maintains an up-to-date security training resource. Reporters Without Borders publishes guidance for journalists in hostile environments. These are worth consulting for a threat model that goes beyond everyday privacy risks.


The Short Version

For most journalists, researchers, and activists, the minimum reasonable baseline for sensitive file storage looks like this:

  1. A dedicated storage account separate from personal files
  2. A provider whose business model is storage subscriptions, not advertising or data processing
  3. Clear knowledge of what jurisdiction your provider operates under
  4. An understanding of whether encryption is server-side or client-side, and what that means for legal demands
  5. Local encrypted backups of irreplaceable materials

The right answer for any specific situation depends on your threat model — who is the realistic adversary, with what capabilities and legal reach? A local reporter covering city hall has different risks than a journalist investigating a foreign intelligence service.

But the minimum version — using a storage service that is clear about what it doesn’t do with your data, in a jurisdiction you understand, with strong encryption — is accessible to everyone and dramatically better than keeping source documents in a Gmail-linked Drive account.

Review what daftei stores and doesn’t store before uploading sensitive documents.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts