Sharing an unpublished book takes trust. Whether you're writing a first draft or sending a finished manuscript to twenty beta readers, you want to know it's safe. There are practical ways to protect your manuscript at every stage. This guide explains, in plain language, how Author Beta helps protect your manuscript at each step, and what no tool can promise.

Layer 1: Encryption on your own computer
At the Writing Desk and in beta reads, your manuscript is encrypted in your browser before it's saved or sent. The keys that can open it are not held by us. That means:
- We can't read your manuscript
- Someone who gained access to our server couldn't read it either
- No AI service can read it through us
See The Writing Desk: a tour for more on how the desk stores your work.
Layer 2: No AI on your private work
We never use manuscripts, notes, feedback, reviews or anything you write here to train or feed AI. AI tools on Author Beta are optional. The AI Assistant only sees what you paste into it, and AI Artwork only sees the picture description you write and approve.
Layer 3: Readers' keys and agreements
When a reader joins your beta read, their browser receives a key to your book, handed over from your browser. Readers agree to keep the book confidential and not to use AI on it. Readers' keys expire when the round closes, unless you choose to let them keep access.
Layer 4: Watermarks and invisible marks
In the reader, every page shows the reader's name. Each reader's copy of your text also carries invisible marks. If a passage turns up somewhere it shouldn't, you can paste it into Trace a leaked passage in the round's control panel to see whose copy it came from. See leak tracing.
Layer 5: Copying, printing and saving turned off
The reader turns off copying, printing and saving, which removes the easiest ways to take text out of a beta read.
What no tool can prevent
Honesty matters here. No system can stop someone from photographing a screen or retyping text. Photos, screenshots and retyped text carry no invisible marks, though the reader's name in the page watermark may still show in a photo. That's why the strongest protection combines technology with choosing readers carefully. See how to find beta readers.
Protect your manuscript: good habits
- Share with readers who love your genre and have a track record
- Use private, link-only rounds for sensitive drafts
- Give readers a clear deadline so access doesn't linger
- Keep your own backups of your work
Copyright basics
In many countries, you own the copyright in your writing from the moment you create it. Registration is optional in some places and useful in others. In the US, the U.S. Copyright Office explains registration and your rights. We're not lawyers, and this isn't legal advice.
Tus datos
Accounts, payments and pages are stored on our servers and backed up nightly, encrypted. Manuscript text is never backed up by us, because we can't read it and deleted manuscripts must stay gone. Read our Privacy policy for full details.
To see the protections in action, follow how to run a beta read on Author Beta.
Questions to ask any writing or reading platform
Whatever tools you use, it's worth asking:
- Who can read my manuscript, including staff?
- Is my writing used to train AI?
- What happens to my files if I close my account?
- Can I export everything?
- How do readers access the book, and can they download it?
Clear, specific answers to these questions are a good sign that a service takes your work seriously.
Preguntas frecuentes
Can Author Beta staff read my book?
No. Your manuscript is encrypted on your computer with keys we don't hold, so we can't open it.
What happens if I lose access to my keys?
Keys are stored in your browser and protected with your password. Keep your password safe and your own backups; Help explains how to keep access across devices.
Can a beta reader copy my book?
Copying, printing and saving are turned off in the reader, and every copy carries the reader's name and hidden marks. No system can stop someone retyping or photographing a screen, so choose readers carefully.



Comentarios