Writing tools fic authors actually trust

Fic writers increasingly draft in tools that promise not to train AI on their work. Ellipsus is a popular choice for collaborative drafting, Fileverse's ddocs.new for encrypted ownership, and plain local files remain undefeated. Here's the full picture, including why "just use Google Docs" stopped being the automatic answer.

Why fic writers care where they draft

Three reasons, all practical. Privacy: a draft shared with a beta reader may contain unfinished, personal, or adult material the writer never intends to make public under their real name, and fandom has always kept fan identities and legal identities separate. Ownership: after watching platforms delete a decade of work (see the community history), fandom's rule is to control your own copy. AI training: since large platforms began updating terms of service to allow training AI on user content, writers have looked hard at who can read, and learn from, their drafts. Fanfiction was scraped into AI training datasets without consent, and the community hasn't forgotten it.

Ellipsus: collaborative drafting with a no-AI pledge

Ellipsus is a free, browser-based writing tool built for drafting and collaboration, and it has found an audience in fandom largely because of its stated policy: no generative AI features, and no training on your words. In practice it works like a simpler Google Docs. You can share a draft with your beta, leave comments, and track versions, and it exports in AO3-friendly formats.

Two caveats worth knowing before you move your drafts in. Ellipsus is not open source, and it is not end-to-end encrypted. That means your drafts are readable on the company's servers, and there is no way to independently verify what happens to your data. The no-AI promise is a policy, not a technical guarantee, so you are trusting the company to keep its word.

Fileverse ddocs.new: encrypted, self-owned docs

Fileverse's ddocs.new takes the ownership idea further. It is an open-source, end-to-end-encrypted document editor where files belong to you rather than living on a company's server on the company's terms. Because drafts are encrypted and self-owned, no company can read them, train AI on them, or delete them out from under you. It is quickly becoming the app of reference for writers who want to avoid having accounts closed down and data suddenly lost, or used by anyone else. The trade-off is a slightly more technical setup than a mainstream editor, but for writers who felt burned by platform TOS changes, "encrypted and mine" is exactly the point.

Local files: the undefeated classic

LibreOffice Writer (free), Word, or any plain-text editor, saved to your own machine and backed up. Zero terms of service, zero scraping, works on a train. The weakness is collaboration, since you'll be emailing drafts to your beta, but many long-time writers draft locally and only paste into a shared tool for the beta pass.

Scrivener, Google Docs, Notion: with eyes open

Scrivener (paid, local-first) is beloved for organizing longfic: chapters, scene cards, and research live in one binder. Google Docs remains the most common beta-reading tool in fandom because everyone has it, and its comment system is genuinely good. Just know your drafts live on Google's servers under Google's terms, and decide if you're comfortable. Notion works well as a fandom wiki for your own WIP (timelines, character notes), less well as a prose editor. Whatever you choose, keep a backup copy of every fic somewhere you control. That is the one rule every fandom generation has learned the hard way.

A simple workflow that works

• Draft locally or in Ellipsus, whichever keeps you writing.
• Beta in a shared doc with comments (Ellipsus or, if your beta prefers it, Google Docs).
• Format for AO3. Its rich-text editor handles pasted text well, and HTML is there if you want control.
• Back up the final version locally. AO3 also lets you download your own works as EPUB/PDF. Do it.