Legal
Privacy Policy
Last updated 11 September 2026.
1. What stays on your device
BookPublish.app does the real work in your browser. Your book projects — the title, author, cover artwork, layout settings and the manuscript you load into the Interior Formatter — are stored locally in your own browser's storage. They are not uploaded to us as you work, and we cannot see them.
This is why your books appear on one computer and not another unless you deliberately save them to your account.
2. What we do receive
| What | When, and why |
|---|---|
| Your email address | If you create an account. We use passwordless sign-in, so we email you a link
instead of storing a password. We have no password to lose.
If you buy something without signing in, or order Concierge, we create an account for the email address you pay with, so your license can always be found again. That never signs anyone in — signing in still takes a link sent to that inbox. |
| Your name and email from checkout | When you buy something. Stripe collects these and passes them to us so we can send your license key and answer support questions later. Your book's title goes to Stripe with the order, so it can appear on your receipt. |
| A saved book, in full | Only if you press "save to my account" on a book. Be aware this uploads the whole project, including the manuscript you loaded, so it can be restored on another computer. |
| ARC Delivery | If you use it: the names and email addresses of your reviewers, the watermarked copy for each, the book's title and author name, your reply-to address, and when each copy was first downloaded — so we can deliver them and show you who has them. |
| Concierge | If you order it: everything you send us to make the book — your manuscript, any cover art, and your answers about the book — plus the proofs we make, your approval, and your revision request. See section 5. |
| A launch reminder | If you asked us to tell you when something launches: your email address, for that one message. |
| Ordinary server logs | IP address and request information, kept briefly by our host and our network provider for security and troubleshooting. Some page addresses include a book's title — the checkout page, for example — so a title can appear in these logs. |
3. What we never see
Your card details. Payments run through Stripe, and card numbers go straight to them. They never touch our servers and we could not retrieve them if we wanted to.
4. Cookies and tracking
We use no advertising networks and no third-party trackers. There is nothing here following you around the internet.
Cookies. Our own pages set only one, and only if you use it: pressing "Was this helpful?" in the Help Center sets a session cookie, so one person cannot vote many times. On the payment page, Stripe's payment form sets its own cookies to help stop fraud; those are Stripe's, covered by Stripe's privacy policy.
We do count how the tools are used, because otherwise we cannot tell what to fix. It runs on our own server — no Google, no Facebook, nothing shared with anyone — and it records the shape of the work, never the work:
- which tool was opened, and which kind of file was exported;
- for a book being formatted: the trim size, interior style, page-fill level and genre you chose, the page count in steps of 10 pages, the word count in steps of 5,000 words, and simple counts such as the number of chapters or edits;
- when the checkout page was opened.
It never records your title, your name, your file name, or any of your writing, and it stores nothing tied to your account.
Each visit is given a random number so we can tell "one person did five things" from "five people did one thing each". It is kept in your browser's tab memory and is gone when you close the tab — it is not a cookie, and it cannot connect one visit to the next. To stop anyone flooding the counter, we also keep a scrambled form of your IP address for up to an hour. It is made with a secret key, so it cannot be turned back into the address, and it is stored apart from the counts.
Not being counted. If your browser sends Global Privacy Control or Do Not Track, we do not count you — those settings are honored, not ignored. Or use this switch, which works in any browser:
We do use your browser's local storage for things the site cannot work without: keeping you signed in, remembering which book you had open, and holding your license keys. That is functional storage, not tracking, and clearing it only signs you out and forgets your local books.
5. Concierge
Concierge is the one service where we work on your book ourselves, so we have to read it.
- Who reads it. We do, to set the book and write the blurb and cover. We use AI tools to help: Claude, from Anthropic, reads the manuscript and helps draft the copy, under an account setting that does not allow it to be used to train AI models. Your manuscript goes nowhere else.
- Cover art and Ideogram. Cover art we make for you is generated by Ideogram from descriptions we write. It never sees your manuscript. It does see your own artwork in exactly one case: in a Concierge order, if the art you sent is too small to print and you choose "upscale it for me". (The Cover Maker's own Upscale to 300 DPI button is a different thing entirely — it enlarges the picture inside your browser, with no AI and nothing uploaded.) Ideogram's privacy policy says it may use what it is sent — the descriptions, and images uploaded with them — to improve and develop its products and AI technology. Our generations are private to our account, so nobody else can see or reuse them. If you would rather your artwork was not sent there, upload a larger file or ask us to make the cover instead; both options are offered at the point where it matters.
- Where it goes. Nowhere else. Your manuscript is never published, and we use it only for your order.
- Order notices. When your order moves along, we email ourselves a note with your email address, the title and author, and any notes you gave us, so the work gets done.
- How long we keep it. See the table below: the kit and everything you sent are deleted 30 days after your first download of the kit.
6. Who else is involved
We share data only with the services needed to run the site, and only what they need:
- Stripe — payment processing. They receive your payment details and email, and the title of the book you are buying for; we receive back your name, email and what you bought.
- Cloudflare — email delivery for sign-in links, license keys, ARC copies and Concierge updates, and content delivery for the site itself.
- Hostinger — hosting. Your saved books and our database sit on their servers.
- Titan — our email inbox. If you write to us, your message is stored there.
- For Concierge orders only: Anthropic and Ideogram, as described in section 5, and Google, whose Gmail receives our order notices.
We do not sell, rent or trade personal information, and we do not share it for advertising.
7. How long we keep things
| Data | Kept for |
|---|---|
| Account and email address | Until you ask us to delete it |
| Purchase and license records | Kept as business records, as tax and accounting rules require |
| Books saved to your account | 60 days after you last save or open them, then deleted automatically |
| ARC files and recipient lists | 30 days, then deleted automatically |
| Concierge kit, and the manuscript and art you sent | 30 days after your first download of the kit — or 60 days after delivery if you never download it — then deleted automatically |
| Concierge project in your My Books | 90 days from delivery or your last edit, whichever is later |
| Concierge order record (email, amount, dates, title and author) | Kept as a business record |
| Usage counts | 12 months |
| Our log of emails sent (date, address, subject) | 30 days |
| Launch reminder list | Until you ask to be removed |
| Sign-in sessions | 60 days |
| Sign-in links | 15 minutes |
8. Security
The site is served over HTTPS. Saved books and our database are kept in folders the public web cannot reach — every request for them is refused — and ARC and Concierge files are stored outside the website's folders entirely. Sign-in tokens are stored hashed rather than in the clear. No system is perfect, but we do not collect what we do not need, which is the best protection there is.
9. Your choices
- Erase this device. "Erase everything on this device" in My Books removes every local book, key and session from the browser you are using.
- Delete a saved book from My Books at any time. To remove a Concierge book early, email us.
- Stop being counted — see the switch above.
- Delete your account and everything with it — email us and we will do it, and confirm when it is done.
- Get a copy of your data — ask and we will send it.
Depending on where you live you may have additional rights over your personal data, including access, correction and deletion. Email us and we will honor them regardless of where you are.
10. Children
BookPublish.app is a tool for people publishing books and is not directed at children. We do not knowingly collect information from anyone under 13.
11. Changes
If this policy changes, the date at the top changes with it. If a change materially affects what we collect, we will say so on the site.
12. Who is responsible, and how to reach us
BookPublish.app is a service of Belladrey LLC, an Ohio limited liability company in the United States. Belladrey LLC is responsible for the personal data described here.
Email [email protected] for anything on this page, including deletion requests — a real person reads it. See also our Terms of Sale.