Are Writing Apps Private?
By Alexandru FilipUpdated Facts verified
Assume not, unless the app stores your work only on your own device. Anything that syncs across devices, checks grammar on a server, or renders your document in a browser necessarily has your text — that is how those features work, not a betrayal. The question worth asking is not "is it private" but "where is the authoritative copy, and who holds the key."
The longer version
The quick classification
| Type | Example behaviour | Has your text? |
|---|---|---|
| Local-only | Files on your disk, no account | No |
| Local-first with optional sync | Files on your disk, sync you can decline | Only if you enable it |
| Cloud with offline mode | Works on a plane, syncs on reconnect | Yes, always |
| Cloud-native | Document lives on their servers | Yes, always |
| Server-side analysis | Grammar and style checkers | Yes, by architecture |
An app that works on a plane is not private. Offline capability and privacy are unrelated properties, and the marketing frequently conflates them.
The tell that settles it in seconds
If the provider's servers can generate a preview of your document, search inside your files, or recover your work after you forget your password without a recovery key you hold — it is not end-to-end encrypted. All three require the provider to hold the key. Some end-to-end encrypted services, such as Proton Drive, do show previews in the browser, but they decrypt there, on your device; the provider never sees the file.
"Encrypted at rest" almost always means the provider encrypts the disks and holds the keys. It protects against a stolen server. It does not protect against the provider.
The ninety-second test
- Open the app with your work loaded
- Turn on airplane mode
- Edit, save, search, export
- Quit the app completely, reopen it still offline — is the work still there?
- Reconnect and watch whether anything uploads
Step 4 separates local-first from cloud-with-a-cache. Step 5 is the honest one.
What else they collect
Beyond your prose: document titles, word counts, timestamps that reveal your working hours, account and payment data, device identifiers, and whatever third-party analytics and crash-reporting SDKs are bundled in. An app's own privacy policy can be entirely truthful and still not describe what its four embedded SDKs send elsewhere.
The fastest structured check is the app store privacy label — Apple's "App Privacy" or Google's "Data safety." Look for "Data Used to Track You," which is the strongest signal there is.
What actually matters
Not every document needs the same treatment. A formatting tool that sees your finished, about-to-be-public book is a very different proposition from a notes app holding an unannounced series bible. Decide per document, not per principle.
Common exceptions
- Business and enterprise tiers frequently carry stricter terms than the consumer version of the same product. Do not assume the answer carries across plans.
- On-device features — local spellcheck, system text-to-speech — send nothing, whatever the surrounding app does.
- Terms change, and opt-outs do not always survive a policy update.
- Self-hosting an open-source tool changes the answer entirely.
Related questions
- What does "local-first" mean for writers?
- How can authors reduce exposure to AI training?
- Should authors use AI?
Sources
- Apple App Store privacy labels; Google Play Data safety disclosures.
- General cryptographic distinction between encryption at rest and end-to-end encryption; Proton on client-side decryption in its Drive web app.
Verified 17 November 2026.