Cloud vs. Local: Where Should Your Words Live?

The convenience trap

Let's start with what cloud storage does well: it's everywhere. Your documents follow you from phone to laptop to tablet. Auto-save means you never lose work. Sharing is a link away. Search works across everything.

This is genuinely good engineering. And for many use cases — collaborative documents, shared spreadsheets, team wikis — cloud storage is the right answer.

But "right for collaboration" doesn't mean "right for everything." And the writing that matters most — the private kind — has fundamentally different requirements.

What the cloud knows about you

When you store a text document on a cloud service, the service knows more than you think:

The obvious

• The content of your document
• The title and file name
• When it was created and last modified

The less obvious

• How long your writing sessions last
• What time of day you write
• How often you revisit specific documents
• Your editing patterns (what you delete is revealing)
• Which devices you use and from where

The invisible

• Automated content analysis for "features" (smart suggestions, search indexing)
• Metadata aggregation across all your documents
• Cross-referencing with your other data (email, calendar, contacts)
• Potential AI training data extraction

This metadata profile exists even if the service never reads a single word you write. The patterns alone tell a story.

The ownership question

Here's a thought experiment: can you delete a cloud-synced document and be certain it's gone?

The answer, for every major cloud service, is no. Deletion means "removed from your view," not "erased from all servers, backups, CDN caches, and disaster recovery systems." Services retain data for varying periods after deletion — sometimes indefinitely for legal compliance or backup purposes.

Your local file, by contrast, exists exactly where you put it. Delete it, and it's gone. Overwrite the disk sectors, and it's forensically gone. You own the full lifecycle.

The security model comparison

Let's compare the actual threat models:

Cloud storage threats

• Data breaches — A single breach can expose millions of users' documents simultaneously
• Insider access — Employees and systems with administrative access can view your data
• Government requests — Providers can be legally compelled to hand over your files, often without notifying you
• Policy changes — Terms of service can change retroactively, granting new uses for your existing data
• AI training — Your content may feed machine learning models without explicit per-document consent
• Account compromise — A stolen password gives access to everything, from everywhere

Local storage threats

• Physical device loss — Someone steals or finds your computer
• Device failure — Hard drive dies, taking your data with it
• Malware — Software on your device could access local files
• No automatic backup — You're responsible for your own backup strategy

Notice something? Cloud threats are systemic — they affect millions of users at once and are outside your control. Local threats are individual — they affect only you and are within your control.

You can mitigate every local threat:

• Device loss → Full disk encryption (FileVault, BitLocker) + application-level encryption (AES-256)
• Device failure → Manual backups to encrypted external drives
• Malware → Standard security hygiene + encrypted vault (even malware can't read AES-256 encrypted files without your password)

You cannot mitigate cloud threats. They happen to you, not because of you.

The convenience counter-argument

"But local storage is inconvenient! I need my files everywhere!"

Valid concern. Let's quantify it:

How often do you actually write from multiple devices? For most writers, the answer is "rarely." You have a primary writing device. The "access anywhere" promise matters less than it seems — especially for private writing that you'd never want on a device you don't fully control.

What about auto-save? Writtt auto-saves locally. Your work is preserved without network dependency.

What about search? Writtt has instant local search across all documents. No cloud index needed.

What about backup? Copy your documents folder to an encrypted external drive. Or use a local sync tool that doesn't scan content. The backup doesn't need to be cloud-based.

The convenience gap between cloud and local is smaller than cloud marketing suggests. And for private writing, the security gap goes the other way entirely.

The professional dimension

For certain professions, the cloud vs. local question isn't about preference — it's about ethics and law:

• Journalists protecting confidential sources can't store notes on servers susceptible to subpoenas
• Lawyers must maintain attorney-client privilege, which cloud storage may compromise
• Therapists are ethically bound to protect patient information from third-party access
• Doctors handle some of the most sensitive personal data that exists
• Executives work with market-moving information that creates insider trading risk if leaked

For these professionals, local-first isn't a nice-to-have. It's a professional obligation.

A middle path

This isn't an absolutist argument against all cloud services. It's an argument for intentional choice:

• Collaborative, non-sensitive work → Cloud storage is fine. Google Docs for team documents, Notion for wikis, Slack for communication.
• Private, sensitive, personal writing → Local storage with encryption. Journals, drafts, clinical notes, legal notes, strategic plans.

The mistake is using the same tool for both. When everything lives in the cloud by default, you lose the ability to keep anything truly private.

The Writtt approach

Writtt makes the choice explicit. Every document is a local file. You decide what stays in the clear and what goes into the encrypted vault. There's no cloud to turn off because there's no cloud to begin with.

Is this approach for everyone? No. It's for people who've decided that some words are too important to store on someone else's server.

If that sounds like you, perhaps it's time to bring your words home.

---

Writtt is a free, open-source text editor with AES-256 encryption and zero cloud dependency. Download it here or build it from source.