1. What we collect
Your account
- Your email address. You have to verify it before the service will generate anything.
- Your full name and your date of birth. Asked when you sign up (or once, before your next book, if your account is older). We use them for one thing: to know you are old enough for an account where you are — 18 or older, or 13 or older in the United States — and to keep accounts for people under 18 on the free plan, with the readers they may pick limited to under-18 books. Both are your own statement; we do not check ID. Your name never goes on a book, and your settings show the date only as “on file”. We also keep the two-letter country your connection came from when you gave the date, because that decided the minimum age.
- If you are too young for an account, we keep nothing about you: no account, no email, no date of birth, no log line. A small cookie in that browser (sw_age_block, 30 days) stops a second try with a different date.
- Your pen name — or names. You are asked for one when you register, and you can hold several, with one marked as the default. Each book chooses which one it publishes under. The pen name is what goes on the title page, and on a public book's card in the showcase.
- Not a copyright registration identity. The full name above is your own statement for the age check, never printed. If you later register a copyright you will be asked for what that needs then.
Your book, and everything that goes into it
- The premise and every intake answer — including the dedication, the epigraph, the scenes you already picture, the things to avoid, and the comparison titles you name.
- The book itself — the story bible, every chapter, the cover art and the exported files.
- The authorship record. Every human decision is logged as it happens: each sentence you rewrite, each outline or reference sheet you approve, each cover prompt you edit, each mid-draft question you answer. This is what your edit share is calculated from.
Payment
Payments are handled by Stripe. Card numbers never reach us.What we store on our side is a Stripe customer id, the email Stripe has for that customer, a subscription or price lookup key, and invoice ids. A billing address is collected only if tax requires it.
Signing in with Google, and your Google account data
Sign in with Google is not switched on yet. Today you sign in with your email address (and, if you add one, a passkey). This part says what will happen when Google sign-in is offered, so that it is written down before it exists.
- What we ask Google for. Only the basic sign-in information: your email address, whether Google has verified it, your name and your profile picture, and an account identifier Google issues for our app. We do not ask for access to your Gmail, Google Drive, Google Docs, contacts, calendar, or anything else in your Google account.
- Why. To create your Shadow Writer AI account and to sign you in to it. Your email address becomes your account email — the same one used for sign-in links, receipts, and notices about your books. Your Google name is not used as your pen name; you choose that yourself.
- Where it is kept. With your account, in our account database (see section 3), protected in the same way as the rest of your account (section 7). It is deleted when you erase your account (section 5).
- We do not sell it. Google account data is not sold, not used for advertising, not used to train or evaluate AI models, and not shared with anyone except the service providers who run the sign-in and the database for us.
- You can disconnect. You can remove Shadow Writer AI’s access at any time from your Google Account’sthird-party connections page. That stops Google sign-in; to delete the account itself, erase it from your account page.
Shadow Writer AI’s use and transfer of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements. The Terms of Service cover the rest of how the service may be used.
2. Your prompts are an unpublished manuscript
A premise, an outline and a draft are the most sensitive thing a writer owns. We treat them as confidential: your premise, your story bible and your outline are never shown to other users, never published, and never used as examples. The finished book is private too, until you choose to share it — section 4 says exactly what sharing means: once we have reviewed it, its cover can appear in the showcase, and signed-in members can read it.
We do not train or evaluate models on your premises, story bibles, or manuscripts.
Confidential on our side is only half the answer, because writing your book means sending your text to a model provider. Here is what that routing actually does:
- Free-tier books are drafted by the free-tier writing model, reached through our model-routing provider. Every free-tier model call is sent with collection and training refused — the setting that denies provider logging and training on that traffic. On the free tier every stage — planning, drafting and the continuity check — runs on that one model.
- Paid-tier books are planned to draft on the paid-tier writing model, bought directly from its model provider rather than through the routing provider.
- Your text is sent repeatedly. The story bible is rebuilt byte-for-byte as the leading part of every chapter request, so material from your intake is transmitted on each of 35 or more calls per book, not once.
We cannot promise that a provider never logs a request on their side. We can say what we send, and that we do not opt in to collection.
3. Who else sees your data
These are the kinds of company involved in running the service, named by the job each one does. Each entry says what that company actually receives. Data-processing agreements and standard contractual clauses with them are not claimed as signed. They will be in place before any EU paid traffic.
- Model routing — free tier
- Routes the free tier's drafting to the free-tier writing model. Receives your story bible and chapter instructions — which means your premise and intake answers — on every chapter call, and returns the generated prose. Every call is sent with collection and training refused.
- Writing model — paid tier
- Planned to draft paid-tier books, bought directly from the model provider. Receives the same material as above for those books.
- Cover and illustration service
- Generates cover art, and the pictures in a picture book or comic. Receives the cover or picture brief — a description built from your story bible, plus any prompt text you edit yourself — and any character picture you upload (section 9). It does not receive your chapters.
- Database host
- The account database. Holds your account, your pen names, your books and chapters, your authorship record, and your credit balance. This is the one that holds everything.
- Website host
- Serves the website. As the host it necessarily sees request metadata, including IP addresses. The bot challenge on signup and login is this host’s.
- Product analytics
- When enabled, records page views of public pages and signed-in pages. Cookieless: it keeps what it needs in memory for the visit and sets no cookie. It does not receive premises, outlines, chapter prose, or story bibles. When analytics is on, our server also records a few account milestones (account created, book started, book finished or stopped), linked only to your account ID, never to your email, name or book text. Accounts of readers under 18 are never counted.
- Payment processor — Stripe
- Takes payment for credits and subscriptions. Receives your card details directly; we do not. We keep the identifiers listed in section 1.
- Transactional email
- Sends transactional email — verification, and the message telling you your book has finished. Receives your email address and the contents of those messages.
- Error monitoring
- Receives error reports from the website and the book engine so a failed run can be found. Reports are stripped of long strings; we do not send premises, outlines, chapter prose or story bibles there.
Cover-art and title screening is done in-process, by us. There is no separate moderation vendor at MVP, so no extra processor sees your titles for that job.
4. The gallery, and what is public
The showcase shows book covers, and signed-in members can open a public book that we have reviewed and read it. It exists as social proof, not as a marketing channel. The text of a book is never public to the open web: reading it needs an account, and the premise behind it is never shown to anyone.
- A finished book is private by default — on every plan, free and paid alike. Nobody but you can read it until you choose to share it.
- You can make any of your books public, on any plan, at any time, from the book's Edit page — and private again. Public means, once we have reviewed it, the cover can appear in the showcase with the pen name on the book, and signed-in members can read the book. It is not public to the open web.
- A book that is private stays private. Changing the default did not change the setting of any book that already existed.
- Covers and titles are reviewed before they appear in the showcase, not just the premise behind them. That review is in-house, and a book whose cover or title changes afterwards leaves the showcase until it is reviewed again.
5. Private is not the same as deleted
Both exist, and they do different things. This distinction is deliberate, because a service that offers only the first is quietly refusing the second.
- Private hides a book from the showcase and from other members. It stays in your library, and we still hold it.
- Deleted means gone from the app. You delete a book yourself, one at a time, from the foot of its Edit page: its chapters, cover and authorship record go with it, and so does the working copy the writing service kept while it wrote the book.
You can erase your account yourself fromyour account page. When you do:
- Your books are not deleted. Each keeps the setting it had: a public book stays public, under no pen name, and a private book stays private — readable by nobody, because nobody can sign in to that account again. If you want a book gone, delete it before you erase the account.
- Account data — pen names, authorship events, passkeys, the profile, premise screenings and any unfinished interview — is removed from the product. Pictures you uploaded of a character, trained looks and print files are removed from private storage.
- A pen name already drawn into a cover image stays in that image; we cannot take it out of the pixels.
- The credit ledger is kept. It is append-only.
- The login identity is tombstoned (stripped, not replayed as a person).
- Files you have already downloaded stay on your device. Nothing we do reaches your hard drive.
- Host backups follow the residual windows of the database host and, when object storage is in use, of the file backups at the host. Those windows are the host’s, not a number we invent here.
We delete what we hold. We cannot delete a model provider’s inference logs.
How long we keep things
- An open account — while it is open.
- The identity tombstone and the credit ledger — seven years after erasure.
- The authorship record — while the account is open, and no longer. Erasing the account deletes it, even though the books themselves stay; it is not part of the seven-year residual. Deleting a book deletes that book's record. Ask for an export before you erase. We do not warrant it for a copyright office.
- Books left in place after erasure — for as long as the service runs, with the setting they had. Delete a book first if you do not want it kept.
- Refused requests — we keep a private safety record of refused requests. The link to your account is removed when you delete your account. Old records are deleted by hand, usually within about a year.
- Free-book check — to stop the free book being claimed twice, we keep a one-way scrambled code made from your email, device and network, for as long as the service runs, and we keep it when you erase your account. It does not contain your address, but we can tell whether an address used to sign up again matches it.
- Application logs and error-monitoring reports — about 90 days.
6. Cookies and analytics
There is no fat consent banner, because we do not set marketing trackers. If that changes, the banner comes back and this section will name the new cookie.
__Host-sw_session — the login session. HttpOnly, Secure, SameSite=Lax, host-only (it cannot span the public site and the app). About 30 days; the tokens inside it rotate sooner.__Host-sw_device (sw_device) — account security: a random id for this browser, so a sign-in from a device your account has not used before asks you to approve it by email first. We keep only a one-way hash of it. HttpOnly, about 365 days, first-party. Not used for analytics. The day anything reads it for analytics it reclassifies, and the security exemption is lost.__Host-sw_checkpoint — short-lived (ten minutes) security cookie set only while a new-device sign-in waits for your approval, so the waiting page can finish it.__Host-sw_flash and__Host-sw_pending_email — short-lived functional cookies (two minutes and ten minutes) so a form can finish without putting your email or an error in the address bar.__Host-sw_cover_job — short-lived (one day) functional cookie set when you ask for a cover, so the cover page can tell you what became of it if you leave while it is being drawn. It holds that job's id and your book's id and nothing else, and is deleted once the outcome is known.__Host-sw_return — short-lived (ten minutes) functional cookie set only when you sign up or log in from a showcase book, so the link in your email brings you back to that book. It holds the book's address and nothing else, and is deleted when used.
Product analytics, when enabled, is cookieless and keeps its state in memory for the visit. It sets no cookie. The bot challenge on signup and login is the website host’s; it is not a cookie we set.
One thing that is not a cookie but still leaves this site: every page loads its fonts from Google Fonts. Your browser makes a request to Google on each page view and discloses your IP address to Google in doing so. There is a recorded decision to self-host the book's interior font; the website's own fonts still load from Google.
7. How we protect it
The measures that are decided, rather than aspirational:
- Provider API keys are server-side only. Your browser never holds one.
- Rate limits run per account and per IP address, which means IP addresses are processed for abuse prevention.
- Everything you type is treated as untrusted. Text you supply is marked off explicitly and handed to the model as material for a book, never as instructions to follow — because your premise is repeated inside every chapter request, so anything smuggled into it would persist across the whole book rather than affecting one call.
No system is perfectly secure.
8. Your rights over your data
Soft launch is United States first. We do not take paid traffic from the EU, the UK or Canada until processor agreements, a chosen establishment, and a request process for those laws exist. That is why this page does not claim GDPR or CCPA readiness.
In practice you can read your books, make any of them private, delete any of them, erase your account, and — on a paid plan — download PDF and EPUB files of the book. Beyond that:
- A copy of what we hold. Paid export already gives you the book files. A “download my data” zip — premise, story bible, chapters, authorship record — is available on requestat hello@shadowwriter-ai.com. Self-serve comes later.
- Erasure. Self-serve fromyour account page, as in section 5.
If we have a personal-data breach, we will email affected users without undue delay. Where GDPR later applies, we will also notify the lead authority within 72 hours of becoming aware, when that law requires it. The operator of Zedara LLC owns that response until it is delegated. Write tohello@shadowwriter-ai.com.
9. Children and teens
You must be 18 or older to create an account — or13 or older in the United States. The service can write a children’s book as output. It does not offer accounts to children under 13, and it is not directed at them.
Teens aged 13 to 17 (United States only) are on the free plan: no purchases of any kind, no advertising, no analytics tracking, and nothing they write is used to train or improve any model. Their books can only be for readers under 18.
If we learn that someone under 13 has an account, a person reviews it and, within 30 days, deletes the account and its data, books included, and refunds anything paid to the person who paid it. Parents and guardians: if you believe your child under 13 has an account, or you want to see or delete what a teen in your care has given us, write tohello@shadowwriter-ai.comwith the account’s email address. We answer within 30 days.
Pictures you upload of a character. For a picture book or a comic you may upload up to four photos or drawings of a character, so its reference sheet is drawn to look like them. A photo may show you, an adult who has agreed to be drawn in your book, or your own child or a child in your legal care — and only their parent or legal guardian may upload a child’s picture. You confirm this for every picture, and we keep that confirmation with the book. We remove the file’s hidden data (location, camera, and similar) when it arrives, keep the picture in private storage that no public link reaches, and use it only to draw that book’s sheets and to train that book’s own look — never another book, and never a shared model. The pictures, and the training sets that contain them, are deleted when the book is finished, when you remove them, or when you erase your account. The illustration service that draws the sheet (section 3) receives the picture to do so.
10. Contacting us, and changes to this policy
The operator is Zedara LLC. Privacy and legal notices go tohello@shadowwriter-ai.com. Copyright complaints go todmca@shadowwriter-ai.com— that address is on the terms; it is not a second privacy inbox. A registered street address is not published yet. Until it is, notices go by email. There is no separate data-protection officer or EU representative while launch stays US-first.
If we make a material change, we will email the address on the account at least 30 days before it takes effect. Continued use after that date is acceptance.
Last updated 13 October 2026. Working defaults; not counsel sign-off.