Legal
Where your manuscript physically goes, who can read it, what encrypted at rest really means, and what happens when an account is closed.
This article recommends no product, including ours.
"The cloud" is a marketing word for a specific and quite ordinary thing: a computer in a building, owned by a company, running software that company controls. Once you know what actually happens to a file when it goes there, the privacy questions answer themselves.
You press save. The file — or a change to it — travels over the internet to a data center and is written to a disk there. Usually several disks, in more than one location, because redundancy is the whole selling point.
Three things follow immediately, and they're the source of most of the confusion:
Copies multiply. Your file now exists in the original location, in replicas across regions, in backup snapshots, and in caches. This is a feature. It is also why "delete" is a more complicated verb than it looks.
Transit and storage are different problems. Everyone encrypts in transit now (that's the padlock). What happens to the file once it lands is the actual question.
The provider's software touches the file. To index it for search, generate a preview thumbnail, run a virus scan, or render it in your browser, something on their side has to read the contents. This isn't sinister; it's how the features work. But it means "nobody can read it" is not accurate for most consumer cloud storage.
Providers say "your data is encrypted." Almost always true, and almost always answering a different question than the one you asked.
Encrypted in transit. Protects the file while it travels. Standard everywhere. Irrelevant to what the provider can do once it arrives.
Encrypted at rest. The disks in the data center are encrypted. This protects against someone stealing a physical drive. It does not protect against the provider, because the provider holds the keys and decrypts on demand — which it must, in order to show you your document.
End-to-end encrypted (zero-knowledge). The file is encrypted on your device, before it leaves, with a key the provider does not have. The provider stores an unreadable blob.
The whole question is: who holds the key?
If the provider holds it, the provider can read your manuscript — whether or not they ever do, whether or not their policies permit it, and whether or not any employee ever wants to. Capability and intent are different things, and only one of them is a technical property.
A quick tell: if the service can show you a preview of your document in a browser, or search inside your files, or recover your data after you forget your password, it is not end-to-end encrypted. Those features are impossible without the key.
| Who | Under what conditions |
|---|---|
| You | Always |
| The provider's systems | Routinely — indexing, previews, malware scanning, feature delivery |
| Provider employees | Under internal controls, which vary in strictness and are rarely public |
| Anyone you shared a link with | Including anyone they forwarded it to. "Anyone with the link" is genuinely anyone |
| Law enforcement | Via legal process. Providers publish transparency reports; the numbers are not small |
| A civil litigant | Via discovery or subpoena |
| An acquirer | If the company is bought, your data is part of what was bought |
| An attacker | If there's a breach, or if your account is compromised |
None of this makes cloud storage a bad choice. It makes it a known choice — appropriate for material where none of the above matters, and worth thinking about for material where some of it does.
The license you agreed to in 2021 is not necessarily the one governing your files today. Providers update terms; continued use is acceptance. Settings you chose — particularly opt-outs from data use — do not always survive a policy revision. Worth re-checking once a year, particularly on any tool holding unpublished work.
Rarer than people fear, disastrous when it happens. Accounts are suspended for suspected terms violations, payment failures, automated flags, and occasionally mistakes. Recovery processes exist and are often slow and unsatisfying.
Relevant to authors in an unglamorous way: your account is your identity across many services. Losing the email account can cascade into losing several storage accounts at once.
The mitigation is boring and effective — a copy that isn't in that ecosystem.
Companies close, get acquired, sunset products. Usually there's an export window. Sometimes the export produces a format nothing else can read, which is technically an export and practically a loss. This is the "Long Now" problem discussed in Local-First Software for Writers.
Deletion in a distributed system means "mark as deleted and stop showing it." The actual removal from backups and replicas happens on a retention schedule, typically measured in weeks to months. Reputable providers document this. It is not a conspiracy; it's how recoverable systems work. But "I deleted it" and "it is gone" are separated by a period of time you don't control.
This is the one that's changed most recently. Whether content is used to train or improve models depends on the specific service, the specific plan, and the current terms. Business and enterprise tiers frequently have different — usually stricter — terms than the consumer version of the identical product.
Do not assume the answer carries across a company's products, or across tiers of the same product.
An honest counterweight, because the answer isn't "don't use the cloud."
Those are large benefits, and an author who abandons the cloud without replacing them ends up in a worse position, not a better one.
The useful question isn't cloud or local. It's which things, and why.
Cloud is fine for: published books, blurbs and descriptions, cover files already public on retail pages, buy links, your public bio, correspondence, anything you'd cheerfully publish tomorrow.
Worth keeping local, with an encrypted off-site copy: unpublished manuscripts, unreleased covers and series plans, work under submission or exclusive terms, anything tied to a pen name you haven't linked publicly, contracts and financial records.
If you want cloud convenience for sensitive material: encrypt it yourself before it goes up. Encrypting a folder locally and syncing the encrypted container gives you the redundancy without giving anyone the contents. It costs you the preview and the search, and that's the trade.
If you can't answer those five for the place your manuscript currently lives, that's the afternoon's work.
Verified 9 August 2026. Provider terms and architectures change; check the current documentation for the specific service and plan you use.
Free · No account · The whole Publishing Manual
The whole Publishing Manual, free and online: checklists, templates and decision trees for every stage, with platform figures verified against the Publishing Database.