What to keep local, and what to keep in the cloud

Privacy 18 September 2026

These solve different problems, which is why picking one exclusively goes wrong

Cloud storage solves accessibility and shared collaboration: the same file, available from any device, editable by more than one person, safe from a single device's hardware failure. Local storage solves something cloud storage structurally cannot: a document that only exists where you put it, never passing through a third party's servers, never subject to that provider's account policies, breach history, or terms of service changes.

Treating one as a strictly better version of the other is where the actual mistakes come from — either everything ends up in the cloud, including things that arguably shouldn't be, or everything stays local, including things that genuinely need to be shared and backed up.

The honest question for anything sensitive: what happens if this account is breached

Every cloud provider, including the large, well-resourced ones, has had account compromises, and a well-secured provider is not the same thing as a guarantee. For a document where the honest answer to “what happens if someone else reads this” is genuinely bad — tax records with full identification numbers, medical documents, signed contracts with sensitive terms — that risk is worth weighing deliberately rather than defaulting to wherever the rest of your files already live.

This doesn't mean avoiding the cloud entirely for sensitive documents. It means being intentional: encrypting a file before it goes into cloud storage, or keeping the single most sensitive category local and backed up separately, while letting everything else use the convenience the cloud is actually good at providing.

For remote work specifically, this decision is being made more often than people notice

Working across a laptop, a phone, and sometimes a shared or public computer means a document syncing to the cloud is often the only realistic way to have it available where it's needed. That's a legitimate reason to use cloud storage, not a compromise to feel bad about — the risk that actually matters is a document syncing somewhere without anyone having decided that on purpose.

A quick, practical check: open whatever cloud storage app is installed and look at what's actually in the auto-sync folder. It is extremely common to find things there — a scanned ID, an old tax form, a signed lease — that ended up in the synced folder by default, without anyone deciding that specific document should live in the cloud.

A workable rule of thumb

If a document needs to be accessed from more than one device, or collaborated on with someone else, and losing it to a device failure would be a real problem, the cloud is doing its job. If a document is highly sensitive, rarely needs to move, and the cost of it leaking somewhere is high, local storage with its own separate backup — not synced anywhere — is the safer default.

The documents that deserve the most thought are the ones that are both: sensitive and needed on more than one device. For those, the honest answer is usually cloud storage with encryption applied before it goes up, rather than picking one side of the local-versus-cloud question and hoping it covers every case.