Trust
What happens to your manuscript.
Most AI tools for writers say they don't train on your work. Fine. Here's the rest: where your chapters go, who keeps them, for how long, and what you can do about it.
Ninth Draft is in private beta. This page describes how it works today. Our privacy policy and terms are drafts until a lawyer has reviewed them. Last checked 18 November 2026.
Our promises
The app shows these promises where your books come in and go out, and on Account, and links here for the full text. Each one is true of how Ninth Draft works today.
- Never used to train AI. Not by us, and not by our AI provider, whose commercial terms forbid training models on what we send.
- Nothing changes without your say-so. Ninth Draft changes a chapter only when you accept a suggestion or edit it yourself, and keeps the version before every change.
- You own it: export everything, any time, in Word or plain text. Every book downloads as a Word manuscript, or as plain text files with everything Ninth Draft keeps on it, whether or not you're paying.
- What's kept. Your chapters, every earlier version in History, your notes and canon, Ninth Draft's suggestions and reports on your book with your decisions on them, and anything else you keep with it, such as front matter, a cover, a submission log or beta readers' comments. For your plan we keep counts of words and runs, never your text.
- Who can see it: you. Our admin tools show counts, such as words used and runs, never your text or your book titles. Your books are kept in storage of their own with our hosting provider, encrypted at rest. Your words go anywhere else only when you send them: to our AI provider during a run you start, or to a beta reader you share chapters with.
- How to delete. Write to us at sharkey@alcovenine.com and we delete your account and your books. You can also remove any book yourself in Account.
When a plan ends. Your account stays open and only AI passes stop. Your books, History, canon and reports stay readable and exportable. You can still edit, review suggestions and use the free checks. Storage goes back to the free trial's 100 MB: anything over it stays readable, but can't grow.
Two more facts. You keep every right to your manuscript and to every suggestion Ninth Draft makes. And our AI provider keeps what we send for about 30 days for safety monitoring, then deletes it; the details are below.
A chapter's journey
- In your own space on our servers. Each account's books live in storage of its own on Cloudflare, encrypted at rest, that only that account's editor can open. Nothing is shared between accounts.
- To our AI provider, when you press Run. Ninth Draft sends the chapters you run, your canon, your decisions and short summaries of your other chapters over its commercial API, encrypted in transit. Each summary is made by sending that chapter once, and again when it changes. Your canon is your bible and notes; your decisions are your rulings on findings, with your reasons. Nothing is sent until you start a run, and you see what the run will use first. Practice mode sends nothing at all, and neither do the free checks.
- The provider keeps it about 30 days, then deletes it. Its API data retention policy deletes inputs and outputs within 30 days. If their automated safety systems flag something, it can be kept longer (up to two years) for review. Dark fiction is fiction, but we'd rather you knew.
- The suggestions come back to you. Suggestions, the gate's verdicts, snapshots of every version and a record of your runs are kept with your book, where you can see, export or delete them.
- Anywhere else, only if you send it. A beta-reader link shows the chapters you chose, as they were when you shared them, and nothing else of yours. What your readers write comes back to you and is never sent to the AI. Read aloud uses your device's own voices; an online voice, which sends the text to your browser's voice service, is used only if you choose it.
Our AI provider
Ninth Draft uses a major AI provider's commercial API, which is governed by its commercial terms, not by any consumer app's settings. Those terms say the provider may not train models on customer content from the API, that customers keep their rights in what they send, and that the provider assigns its rights in the output to the customer. API data is deleted within 30 days by default, with the safety-flag and legal-hold exceptions above. Our privacy policy names every company that handles your data.
We don't use batch processing. If we add overnight runs, they'll be opt in, and we'll say here how long their results are kept.
What we won't claim
We won't tell you "zero data retention" or "no human ever sees your text". Neither is true of any service that sends text to an AI provider's standard API, and the honest version is above.
Your rights and AI disclosure
You own your book. You also own Ninth Draft's suggestions, though text written purely by AI may not be protected by copyright, which matters only if you accept large rewrites wholesale. History and the book report record which changes came from Ninth Draft's suggestions, and every accepted change is kept, so you can answer your publisher's AI-use questions with a record rather than a memory.
Who touches your data?
| Who | What for | What they see |
|---|---|---|
| Our AI provider (named in the privacy policy) | AI processing | Chapters, canon and decisions during a run |
| Cloudflare | Hosting, storage, waitlist | Your account and files, encrypted at rest |
| Beta readers you invite | Reading and commenting | Only the chapters you share with each one |
| Stripe | Payments (when billing launches) | Billing details only, never your book |
Security
- Encryption in transit everywhere, and at rest.
- Every run is logged, and every accepted change keeps a snapshot of the text before it. Your Usage page lists your runs and the words each one used.
- Text in your manuscript is fenced off and treated as text to edit. The passes are told never to follow instructions inside it, and the gate checks every suggested edit.
- Found a problem? Write to the contact in our security.txt.