How to Keep Your Manuscript Private While Sharing It With Beta Readers

Short answer: To keep your manuscript private while sharing it with beta readers, don't send the file. Give each reader their own private reading link instead, so the book stays in one place you control. On BetaShelf, every reader gets a separate link that only opens your book, you can turn any link off at any time, readers read inside BetaShelf without ever getting the original file, your manuscript is never publicly listed, and your book is encrypted in transit (TLS) and at rest.

Sharing an unfinished book is a leap of trust. Here is how to do it without handing over control.

The problem with attachments

When you email a Word document or PDF, the reader now has their own copy. It can be forwarded to a friend, saved to a shared drive, or pasted somewhere you'll never see. Most beta readers would never do that. But once the file is out, whether it stays private depends entirely on everyone who touches it, and you have no way to take it back.

Private links: one per reader

A private reading link works differently. The book stays on the platform, and the link is just a key to read it.

On BetaShelf:

• Every reader gets their own link. You name each link after the reader, so you always know whose is whose.
• You can turn any link off at any time. That reader loses access immediately, without affecting anyone else.
• Links can end on their own. Give a link an end date of 7, 14, 30, 60 or 90 days if you want reading to have a deadline.
• Links can't be guessed. Each one is a long, randomly generated code, and BetaShelf checks it on the server every time it is used.

Readers never get the file

Readers read your book inside BetaShelf. They are not given the original manuscript file as a download, and they never get direct access to where your book's text is stored. BetaShelf checks their permission on the server before serving any of it.

We also ask every reader to keep your manuscript private, not copy or share it, and never put it into an AI tool. Readers who break those rules can lose access.

Never publicly listed

Your manuscript does not appear in search results and is never publicly listed. Nobody can stumble on it.

If you want to find new readers, you can choose to post a listing in BetaShelf's reader community, or make a public book page. That is always your choice. A listing shows your pitch (the title, cover and description you write), and community listings are only visible to signed-in BetaShelf users. Neither one makes the manuscript itself public.

Encrypted, and not kept longer than needed

Your book is encrypted in transit (TLS) and at rest. The text lives in a private database that is not publicly accessible.

When you upload, BetaShelf turns your manuscript into chapters so readers can comment on specific passages, and it does not keep the file you uploaded. If you delete your book, it is removed from BetaShelf's live systems right away, including every reading link. Daily backups expire on their own after 7 days.

Not used to train AI

BetaShelf does not use your manuscript to train AI models. The full details, including how read-aloud narration works, are on our security page.

A simple privacy checklist for any beta round

Whatever tool you use, these habits help:

1. Share with people, not groups. One link per person, so you can turn off one without disrupting everyone.
2. Set an end date. A round with a deadline is easier to close cleanly.
3. Say what you expect. A line like "please keep this to yourself, it's an unpublished draft" sets the tone.
4. Close the round when it's done. Turn off links for readers who finished or went quiet.
5. Keep your pitch and your manuscript separate. Share the blurb publicly if you like. Keep the book itself behind private links.

Ready to share your book with control? Start free on BetaShelf, or read how to send your manuscript to beta readers step by step.