Plain-language disclosure
How writeMyBook handles your words.
This page describes the product behavior implemented in this deployment. It complements—but does not replace—the operator's formal privacy policy and terms.
What is stored
Your account identifier, email, display name, book brief, outline, chapters, cover settings, version history, and operational metadata are stored in the private application database. Generated export files are assembled when you download them; only export format, time, status, and file size are logged.
What reaches the writing model
When you request a plan, chapter, outline revision, or cover direction, the relevant book text, your instruction, and a one-way pseudonymous account token are sent through OpenRouter to the selected Gemini model. Generation logs keep a one-way prompt fingerprint and token counts—not a second copy of the prompt or response. Your saved manuscript remains in the application database.
Control and deletion
Every protected query is scoped to the signed-in user. “Delete writeMyBook data” removes live manuscripts, generation history, export logs, and the writeMyBook Stripe customer after password confirmation. If this deployment shares a Firebase identity project with another product, the shared login is intentionally retained. Database snapshots age out through the configured 14-backup rotation, so deleted records can remain in operator backups until rotation completes.