Cochain Books — Privacy Policy
Version privacy-2026-10-r3 · Supersedes privacy-2026-10-r2 (17 October 2026)
Cochain LLC, doing business as Cochain Books ("Cochain Books", "we", "us"), is the controller of the personal information described here.
Cochain LLC d/b/a Cochain Books 5826 New Territory Blvd PMB 3027, Sugar Land, TX 77479 info@cochainbooks.com
1. What this policy covers
We run three things, and they treat your child's information very differently. This is the most important thing on this page, so it comes first.
The Free Library is a collection of illustrated books, with narration, that anyone can read on our website for free. It needs no account and no sign-in, and it asks you for nothing. The books in it belong to Cochain Books. It is published in US English, and we are adding other editions, beginning with UK English.
The story tool is a web application where an adult creates a personalised story for a child, with AI-assisted writing and optional narration. It asks for a first name and an age, and nothing more. There is no field for a surname. Nothing a child gives us here is published anywhere.
The publishing service turns a child's story into a real book, sold on Amazon and — for some packages — in bookshops through IngramSpark. Publishing a book means putting an author's name on it. So this service collects the child's full name, a photograph and a short biography, and publishes them: on the cover, on the title page, on the About the Author page, and in the retail listing.
That is not a side effect. It is the thing you are buying — a child becoming a published author under their own name. But it is permanent and public, which is why we ask for it separately, in writing, and why you choose how your child is named.
Where something applies to only one of the three, we say so.
This policy covers privacy only — what we collect, why, who it reaches, and how long we keep it. Our Terms of Service cover everything else: what the service does and does not promise, who is responsible for what, and how disputes are handled.
2. Who our account holders are
Accounts are for adults aged 18 or over. An adult holds the account, creates the story, and decides what happens to it — usually the child's parent or guardian, sometimes a relative or friend making a story as a gift. You confirm that you are 18 or over when you create your account. Separately, before a story is created we ask for the same confirmation about the child, whoever you are (section 3.2). A child may read and listen to a finished story, and anyone may read the Free Library, but children do not hold accounts, do not sign in, and cannot create or share anything themselves.
We do not knowingly permit anyone under 18 to create an account. If you believe a person under 18 has created one, contact us and we will delete it.
3. What we collect
3.1 When you create an account (story tool)
Our sign-in form asks for your email address and nothing else. There is no name, telephone, address or date-of-birth field.
If you sign in with Google, Google returns more than that, and we want to be straightforward about it. Google's standard sign-in response includes:
- your name, as it appears on your Google account
- a link to your Google profile photograph
- a stable Google account identifier
- your email address and whether Google has verified it
- if your account belongs to a Google Workspace organisation, that organisation's domain
We do not ask for these, we do not display them, and we do not use them. Our authentication provider stores them as part of the sign-in record. If you would rather we did not hold them, sign in with the emailed code instead of with Google.
We also hold a few settings on your account: the role you selected, your monthly story allowance where we have changed it from the standard one, and whether narration has been given to you at no charge.
3.2 When you create a story (story tool)
- Your child's first name. We do not ask for a surname, and there is no field for one.
- Your child's age, and an age band — 3-5, 6-8, 9-11, 12-14 — which we suggest from the age and you can change.
- What you would like the story to be about — free text you write.
- A story title.
- Which of our characters you have chosen, or details of a custom character you create, including custom character briefs.
That is the whole of what we ask you for to create your story. We do not ask for a date of birth, a surname, a school, an address, a telephone number, or a photograph of your child. (Section 3.6 describes the separate record we keep of what your account has done — it holds nothing about your child.)
The title you type, and your child's exact age, never reach the AI providers listed in section 4. We store your title and show it to you. The tool also writes a title of its own while it builds the story, and that one is sent to those providers. It is the title you see if you leave the title field blank. Of your child's age, only the band is sent.
You give this to us deliberately. Before a story is created you are asked to tick a box confirming that — if the first name and age you give belong to a real child — you are that child's parent or legal guardian, or you have their parent or guardian's permission, and that you consent to our using them for this purpose. That consent is separate from your acceptance of our Terms of Service — accepting the terms is not, on its own, consent to give us a child's information.
3.3 When you buy a publishing package
- Your full name, email address and telephone number
- Your child's name choice — full legal name, first name only, or a pen name. See below
- Your child's age, their pronouns, and a general physical description
- Your child's story
- A photograph of your child, a short biography, and their stated age, for the "About the Author" page
- Publisher marketing features, including a QR code or web link to Cochain Books' official social media channels, website or reader community, shown on the author page
- Where your order includes the likeness add-on: reference photographs — see section 6.2
How your child is named is your choice, and you make it as a standalone election. The Parental Consent & Publicity Release asks you to select one of three formats, which we then use on the cover, the title page, the copyright line and the retail listing:
- Full name — authorises publishing your child's legal surname, permanently
- First name only
- A pen name
The author photograph, biography and age are published, not kept private. They appear inside every copy of the book. Section 6.1 explains what publication means, how it differs from a private reference photograph, and why published material cannot be recalled once distributed.
3.4 Payment information
Payments are handled by Stripe, on Stripe's own pages. We never see or store a card number. For a subscription, we keep Stripe's reference for your customer record and subscription, a token of our own that identifies you to Stripe and means nothing on its own, your subscription status, whether it is set to end at the close of the current period, the date your current period ends, and when the status last changed. We keep the billing ZIP code you give us at sign-up and the state it falls in. For each invoice we keep the tax rate applied and the tax charged, together with the identifiers Stripe gives the invoice, each line on it and any credit note; the amounts; the billing country; how we determined the state; and the dates of the period each line covers. We also keep the events Stripe sends us about your subscription, and a record of any case where what Stripe told us and what we held disagreed, so that we can reconcile the two.
When you buy a publishing package, we keep what we need to work out and record Texas sales tax — among them the billing ZIP code you enter at checkout, the ZIP code of your card's billing address as Stripe returns it, the state each one falls in, the tax rate applied and the tax charged.
3.5 Story submissions are text
We accept stories as typed text, and for the publishing service also as a PDF or Word document. We do not accept audio recordings, voice notes, or photographs and scans of handwritten pages. (The May 2026 policy said we accepted voice and handwritten submissions. That was inaccurate and has been corrected.)
3.6 Records of what your account has used
Separately from your stories, we keep a short record each time your account creates a story or asks for narration — what happened, when, which account did it, and ordinary details of the request itself: which story it concerned, which option was chosen, how much text was involved, and whether it succeeded. Nothing about your child.
These records contain no child's name, no age, and no story text. They exist for three ordinary reasons: to count your monthly allowance, to work out what the service costs us to run, and to notice a pattern of use that looks automated rather than human.
They are deleted with your account. Unlike the records in section 8, there is no reason to keep them once you are gone.
4. What leaves our systems, and to whom
We use a small number of service providers, and we have chosen established companies rather than small ones. The third-party systems that process your or your child's data are listed here, together with a link to each provider's own privacy policy, where they publish one.
| Provider | What it does | What reaches it | Their privacy policy |
|---|---|---|---|
| Supabase | Database, sign-in, file storage | Everything described in section 3, and the reaction totals described in section 5. Supabase also keeps its own records of the requests that reach it, which include network addresses — those of visitors to our marketing site's home page among them, since that page reads the shelves from it | supabase.com/privacy |
| Vercel | Runs the story tool, the Free Library reader, and the shelf display on our marketing site's home page | Ordinary web request data, including IP address and the page addresses requested — from visitors to cochainbooks.com as well, because that page loads our program from here | vercel.com/legal/privacy-policy |
| Anthropic | Generates story text | Your child's first name, their age band, and your story premise | anthropic.com/legal/privacy |
| OpenAI | Safety screening only | The text you write, and the story text we generate — which contains your child's first name. See below | openai.com/policies/privacy-policy |
| ElevenLabs | Generates narration audio | For a story you create: the story text, which contains your child's first name. For a Free Library book: our own text, which contains no child's name. Our narration voices are designed from written descriptions, not copied from any person | elevenlabs.io/privacy-policy |
| Stripe | Payments | Your email, card and billing details — held by Stripe, not by us | stripe.com/privacy |
| Sign-in, if you choose it; and the spam protection on our marketing site's forms | See section 3.1 for sign-in. For the spam protection: every page of cochainbooks.com contacts Google as it loads, so Google receives your network address, your browser's details and the page you are on, together with whatever its check measures about how the page is used | policies.google.com/privacy | |
| Squarespace | Runs cochainbooks.com | Website analytics for the marketing site | squarespace.com/privacy |
| Amazon KDP | Publishing and distribution | Book metadata, including the author name you choose | amazon.com/privacy |
| IngramSpark | Publishing and distribution | Book metadata, including the author name you choose | ingramspark.com/privacy-policy |
| Adobe Sign | Electronic signature for publishing agreements and consent forms | The signed documents — the Author's name, the About the Author page proof, which contains the Author's photograph and biography, and your contact details | adobe.com/privacy/policy.html |
| Illustrators and editors | Publishing service | Your child's story, their pronouns and physical description, and reference photographs where applicable — under confidentiality agreement | — |
What we can promise, and what we cannot. We have never taken money for your information or your child's, and we do not intend to, and we do not use it to target advertising at anyone. We disclose it to the service providers above, who need it to run the service, and to no one else, except where the law requires it. The rest we can only promise for our own conduct. The providers above receive data in order to do their jobs, and each of them handles it under its own privacy policy, which governs what they retain and what they do with it. We do not control those policies, and we ask you to read the ones that matter to you.
A note on the AI providers. Your child's first name and age band are sent to Anthropic each time a story or a page is written, and the story text is sent to ElevenLabs when narration is generated. This is how the product works — it cannot write a story about your child without knowing their name.
A note on ElevenLabs. ElevenLabs turns the text we send it into the narration audio you hear. Under its terms we grant it a licence over both what we send and what it returns — a licence that is perpetual, worldwide and able to be passed on, and that permits ElevenLabs to use that material to run and to improve its own services, not only to make our audio. We would rather set that out than describe it as narration and leave it there. ElevenLabs offers an opt-out from the use of personal information for training, in the Data use menu of our account, and it takes effect only from the day it is switched on. We took it on 17 October 2026, and nothing a customer wrote was caught by the delay. No story made in the story tool had been narrated for anyone outside Cochain Books by that date; everything we had sent ElevenLabs until then was our own Free Library text and our own testing. The licence in the sentence above is a separate thing, and opting out does not touch it — it applies to what we send from now on as much as to what we sent before. For a Free Library book the text we send is our own and contains no child's name. For a story you create, it contains your child's first name, as the table above says.
Safety screening, and why your child's first name passes through it. Every page we generate is screened by OpenAI's moderation service before you see it. Because the page text is a story about your child, it contains their first name, and so their first name reaches that screening service — typically fifteen to twenty-five times over a full story, plus once for the outline.
We could strip the name out before screening. We have chosen not to, for two reasons.
The screen is a child-safety control, and we would rather it examined exactly the words you will read than a modified copy of them.
And the footprint is small. Here it matters which part of that is ours and which is not.
What we control, and have done: we have turned off every data-sharing option OpenAI offers us — model feedback, evaluation and fine-tuning data, and the sharing of inputs and outputs — and we do not switch on per-call logging, so nothing we send is retained at our request. We declined the free usage credits OpenAI offers in exchange for sharing.
What we do not control: OpenAI documents its moderation endpoint as retaining no content, and states that data sent to its API is not used to train its models by default. That is OpenAI's published position, not a setting of ours, and like every provider in the table above, what they do with what reaches them is governed by their policy rather than by us.
5. Cookies and tracking
The story tool and the Free Library reader set no analytics or advertising cookie, and load no third-party script. There is no Meta Pixel, no Google Analytics, no Tag Manager, and no session-recording or product-analytics tool anywhere in either of them — and no script of any other kind from anyone else either, down to the typefaces, which we serve ourselves rather than fetching them from another company. We checked this in October 2026: the public pages in a browser with a fresh profile, and every page in the code, including the pages you see only when you are signed in. Not against our own documentation — against the thing itself.
The story tool keeps your sign-in session in your browser — it is what keeps you signed in, and our sign-in library may split it across more than one cookie, depending on its size. If you sign in with Google, one more cookie is set for the moments the sign-in takes, and then it goes. The tool also holds, for the visit and until you close the tab, which role you selected and the selections you have made for a story while you are deciding what to publish.
The Free Library reader sets no cookie of its own. It remembers things in your browser's local storage, and only ever after you have done something: which books you reacted to, that you turned the music off, that you have seen the full-screen hint, and which language edition you chose. If you are signed in to the story tool, your sign-in cookie is refreshed on the reader's pages as well, because the reader sits at the same web address.
Some of that leaves your browser, and this is exactly what leaves. When you like or dislike a book, we send which book it was and which button you pressed, and we add one to a running total. What we store is the book, the button and the total, and nothing else — we keep no record of who pressed it: no address, no account, not even the time. When you choose a language edition, your choice travels with the pages you open so that we serve you the right one; we do not count it and we do not keep it.
What our hosting and database providers see is a separate matter, and we would rather say so. Like any website, ours runs on providers that keep their own records of the requests reaching them, and those records include network addresses and the pages asked for. Those are their logs, kept under their own policies, not ours. Section 4 names them.
One cookie is offered to your browser that is not ours, and your browser may refuse it. Parts of the site talk directly to our database provider — our home page reads the shelves from it, the Free Library fetches a book's pictures, the sign-in page fetches its settings — and the network in front of that provider offers a short-lived cookie of its own, at the time of writing one named `__cf_bm`, so that it can tell automated traffic from people. It is offered on that provider's own address rather than ours, it would last about half an hour, and scripts cannot read it. When we tested this in Chrome, the browser rejected it every time, because of the address it is scoped to. We have not tested every browser, so we tell you it is offered rather than promise it is never kept. We do not set it, we cannot read it, and nothing we hold is linked to it.
You can block or delete cookies, and clear local storage, in your browser's settings. If you block the sign-in cookie, you will not be able to stay signed in to the story tool. Clearing the reader's local storage loses nothing but the preferences above.
Our marketing site, cochainbooks.com, is built on Squarespace and does use ordinary website analytics. Its home page shows what is on our shelves, and to do that it loads a small program of ours and reads the public details and cover pictures of the books from the same database the story tool and the Free Library use. Nothing about you or your child travels that way — what it reads is the published description of a book, the same thing any visitor sees. But your browser does contact our own address and our database provider's while that page loads, so those two providers see the request, as section 4 describes.
One more thing happens on that site, before you click anything. Every page of it loads Google's spam-protection check, which Squarespace provides, so that our contact forms are not filled in by machines. It runs as the page loads rather than waiting for the cookie banner, because it is there to protect the site rather than to learn about you — and while it runs, Google receives your network address, your browser's details and the page you are on. It stores nothing in your browser: we looked, and it leaves no cookie and nothing in local storage, neither on our address nor on Google's. Google also states that what this check collects is not used for personalised advertising. That is Google's published position rather than a setting of ours, as with the other providers in section 4.
That site asks before it uses analytics, and you can change your answer. Until you answer, the only things kept in your browser are the ones the page needs in order to work. If you accept, Squarespace's analytics cookies are set; if you decline everything — which is one click — nothing is added but the record of what you chose. A "Cookie Preferences" link at the foot of every page reopens that choice, so turning analytics off later is as easy as turning it on.
6. Photographs — two kinds, treated differently
We may hold two entirely different kinds of photograph, and it matters which is which.
6.1 The author photograph and biography — published, and permanent
Every book we publish includes an "About the Author" page carrying a photograph of the child, a short biography, their stated age, their elected name format, and links or QR codes pointing to Cochain Books' official online platforms. These elements are published. They appear inside every copy sold, in print and in digital editions.
Publication is permanent. Once a book is printed and sold we cannot recall it from copies already in readers' hands. On request, or on revocation of publicity, we will remove the photograph, biography and name from future printings, and from digital editions where the retailer permits. Digital editions, metadata and retail search listings may remain searchable online indefinitely, across third-party platforms outside our control.
We ask for this explicitly and in writing, in the Parental Consent & Publicity Release, and you approve the exact layout proof — Schedule A — showing the final photograph, the biography text, the name as it will appear and the publisher links, before we publish anything.
It must show your child alone. If any other person appears in the photograph, you must warrant that you hold full legal authority and written consent to publish that person's image.
Retention. Published author photographs, biographies and approved names are kept for as long as the book remains in publication, because they form part of the published work. The 90-day timetable in section 6.2 does not apply to them.
6.2 Reference photographs — private, and deleted
Where your package includes a character drawn to resemble your child, we ask for reference photographs. These are never published. Here is exactly what happens to them.
A human illustrator uses the photograph as a visual reference. They separate your child from the background by hand, convert that outline into a line drawing, and then redraw and restyle it by hand until it matches our illustration style. What appears in the book is an illustration in our house style — not your child's photograph, and not a machine-generated likeness of it.
Your child's photograph is never submitted to any artificial-intelligence or generative image service, never used to train any model, and never processed by the generative AI features built into illustration software. Our illustrators are contractually prohibited from all of these, are given a written list of the specific features they must not use, and must confirm in writing on delivery that they have complied.
Reference photographs are shared only with the illustrator working on your book, under a confidentiality agreement. The illustrator must permanently delete them within 5 business days of final delivery, and we delete our own copies within 90 days of book completion.
The story tool does not accept photographs at all. There is no upload path, of either kind.
7. How long we keep things
We hold two different kinds of information, and they are treated differently.
7.1 Working data — deleted when you ask
This is what the service actively uses. If you ask us to delete it, we do.
| What | How long |
|---|---|
| Your account | Until you ask us to delete it |
| Your stories, generated text, narration audio and generated illustrations | Until you ask us to delete them |
| Reference photographs | 90 days after book completion, and 5 business days at the illustrator |
| Records of what your account has used (section 3.6) | 12 months, then deleted — and deleted with your account if that is sooner |
| Database backups | 7 days |
7.2 Records we keep to protect ourselves — not deleted on request
These are kept because we may need them to meet a legal obligation or to defend a claim. They are held separately from the working data above and are not used to run the service.
| What | How long |
|---|---|
| Financial and tax records we hold ourselves, including the sales tax details for each order and for each subscription invoice — among them the billing ZIP code entered, the ZIP code of the card's billing address where we hold it, the state each one falls in, the tax rate applied and the tax charged | Seven years from the end of the tax year they fall in. US and Texas tax law require less than that, and the periods vary with the record; we keep one longer period rather than judging each record separately |
| The same kind of records held by Stripe, our payment processor — your email address, billing name, postal code, receipt history and tax invoices | For as long as Stripe's own tax, accounting, anti-fraud and audit obligations require. Stripe decides that period; we do not set it |
| The Order — the checkout confirmation and fee record that forms part of the publishing agreement, including gift orders | 7 years from issuance |
| The record that you accepted our terms | See section 8 |
| Signed publishing agreements and project emails | The 3-year term of the agreement, and then as needed for any live dispute |
| Signed Parental Consent & Publicity Release forms, and the Schedule A proof attached to each | For as long as the book is distributed, and then for as long as a claim could be brought |
| Manuscripts and print-ready files for published books | Currently retained, so the book can be reprinted — see below |
| Records of automated safety and moderation blocks | See the paragraph below |
We retain records of automated safety and moderation blocks (including submitted prompts and timestamps) for up to 90 days for filter optimization. Records involving severe violations, potential harm to minors, or illegal conduct are preserved in isolated storage for at least 12 months to satisfy mandatory federal reporting and legal compliance obligations. These security and compliance records are exempt from user deletion requests.
On published books. Once a book is published and listed for sale, we currently retain the manuscript and print-ready files so that it can be reprinted and so that we can meet our obligations to the retailers who list it. We deliberately do not describe this as permanent. If you ask us to remove a published book, tell us and we will discuss what is possible — some of it is in the retailers' hands, not ours.
8. Your rights, and how to use them
You may ask us to:
- tell you what we hold about you and your child, and give it to you in a readable form
- correct anything wrong
- delete your account and the working data in section 7.1
- withdraw consent to marketing or publicity, at any time
- delete reference photographs immediately, without waiting for the 90 days
Email info@cochainbooks.com. We aim to respond within 10 business days, and in every case within 45 days — unless your request is complicated, or you have made several at once, in which case we may take up to 45 days more. If we need that extra time we will tell you inside the first 45 days, and tell you why. We do not charge for this, and we will not treat you differently for asking.
How we check that a request is really yours.
When you are signed in, deleting a story in the story tool takes effect at once. What follows is about requests you send us by email.
If the request comes from the email address on your account, we act on it. For an emailed request to delete your account or your stories, we first reply to confirm we have it, tell you the date we will act, and give you 7 days to tell us to stop. We act on that date whether or not you reply. Everything else — telling you what we hold, correcting something, withdrawing consent — we do promptly, with no waiting period. The same goes for reference photographs: we destroy those as soon as you ask, without a waiting period, as set out above.
If the request comes from any other address, we write to the address on the account and ask you to confirm from there, and we wait for that reply before acting. If no reply comes, we will write to you within 45 days to tell you that we are not able to act on the request, why, and how to appeal. A request is never left to go quiet.
We will not ask you for identity documents, and we will never ask you for a password — there is none to ask for, because you sign in with a code we email you or with Google. If we cannot tell that a request belongs to a particular account, we will say so and tell you what would let us act.
If you are a Texas resident, the Texas Data Privacy and Security Act gives consumers rights of this kind. We honour them for everyone, wherever you live, rather than sorting our customers by state.
If we say no, you can appeal. If we refuse a request, in whole or in part, we will tell you in writing why we refused it, within 45 days, and we will tell you how to appeal.
To appeal, reply to that email, or write to info@cochainbooks.com with "Appeal" in the subject line. It costs nothing. We will answer an appeal in writing within 60 days of receiving it, and we will give you our reasons.
If we turn down your appeal, we will tell you how to complain to the Texas Attorney General, and we will give you the address of the Attorney General's complaint form in that same reply. Appeals are open to everyone, wherever you live, on the same basis as the rights above.
Three things we want to be honest about.
Deletion is done by us, not by a button. There is currently no delete-my-account control in the story tool. When you ask, we delete your account, your stories, the generated text, and the narration audio and illustration files held in our storage. Deleted data remains recoverable from our database backups for up to 7 days afterwards, and is then gone.
Two classes of record survive deletion.
The first is proof that you agreed to something.
Whenever you accept one of our documents, confirm that you are 18 or over, or give consent to use a child's first name and age, we record what you agreed to, which version of the wording, and when — and we keep that version's exact text, unchanged, so what you agreed to can be shown word for word. That is recorded together with the IP address and browser it came from. Your email address is not part of that record. When your account is deleted we keep the record, but we change it first: the IP address and the browser are erased, and we add a one-way code worked out from the email address on your account.
They are kept because they are our only evidence that the thing was agreed, at the time it was agreed. A record that disappears when an account is deleted cannot prove anything, which defeats the purpose of keeping it.
What survives is the fact of the agreement. These records contain no child's name, no age, and no story. What they still hold about you is the one-way code made from your email address. It cannot be turned back into your email address — but if you ever ask us to show what you agreed to, we can work out the same code from an address you give us and match it to the record. That is the only thing it is for.
The second is a record of something our safety filters blocked, and only where it was severe.
Most blocks are ordinary — a word the filter did not like, something off-topic. Those records are kept for up to 90 days to improve the filter, and they are deleted with your account.
A small number are not ordinary. Where a block involves a severe violation, potential harm to a minor, or conduct that may be illegal, we are required by federal law to preserve the record — the text itself, the time, and the account and network details — for at least twelve months, and to report some of it. Those records are moved to separate, restricted storage, and a deletion request does not reach them.
We would rather say this plainly than bury it. Unlike the agreement records above, a preserved safety record can contain the text that was blocked, which may include a child's first name. Only one person here can read them, and only for that legal purpose.
Nothing else survives deletion.
Removing a published book is a separate question from deleting your data. Deleting your account removes your data from our systems. It does not automatically withdraw a book that is already listed for sale by Amazon or a bookshop, because those listings are not ours to control. See section 7.2.
9. Security
Access to stories is enforced by the database itself, not only by the application: your account can read your own stories and no one else's. Generated audio and images are held in private storage and served through links that expire.
Access to customer stories is restricted to authorised personnel who require it for support, troubleshooting and publishing setup, through the database administration tools. We do not read stories otherwise.
10. Children's information
In the story tool and the publishing service, a child never deals with us. You do. The account holder is an adult — the child's parent or legal guardian, or someone acting with their permission — and every piece of information we hold about a child in those two services was given to us by that adult. The Free Library is different, and the paragraph below says how.
The Free Library is the one place a child may be here on their own, and it is built so that nothing follows them. It needs no account and no sign-in, it asks for no name and no age, and there is nothing to type into. A child can read and listen without telling us who they are, and we would not know if one did. A few things are remembered in the browser on the device — which books were liked, the music turned off, the hint dismissed, the language chosen — and those stay on the device. A short-lived security cookie is also offered by the service our books are stored with, rather than by us — section 5 says what it is and what happened when we tested it. When a book is liked or disliked we add one to that book's running total, and we keep nothing about who pressed it. The language chosen travels with each page so that we serve the right edition, and we neither count it nor keep it. We do not profile readers and we do not advertise to them, and nothing we keep would let us recognise the same reader twice.
What we collect depends entirely on which of our services you are using.
The Free Library: nothing. No account, no name, no age, nothing to fill in.
The story tool: a first name and an age. Nothing else. There is no field for a surname, and nothing is published anywhere.
The publishing service: what it takes to publish a book. Your child's story, their stated age, a general physical description, a photograph and a short biography for the About the Author page, publisher links shown on that page, the author name format you elect, and — for custom-likeness packages only — reference photographs.
We never ask for a child's date of birth, home address, school, personal telephone number, or personal email address, for any of them.
One honest qualification. The box where you describe what the story should be about is free text, and we cannot stop you typing something into it that we did not ask for. Please do not put a surname, a school, an address, or anything else identifying into that box — we do not want it, and it would end up in the story. If you have already done so, email us and we will remove it.
On surnames and legal names, plainly. The story tool holds no surname and has nowhere to put one. The publishing service does hold a legal surname, and publishes it permanently — but only where you expressly elect "full name" on the Parental Consent & Publicity Release. A published book carries its author's name, and that is what the publishing package delivers. If you would rather your child's surname were not published, elect first name only or a pen name, and we will use that election everywhere the book appears: the cover, the title page, the copyright line, and the retail listings on Amazon and IngramSpark.
We treat everyone under 18 the same way. We do not operate one set of rules for children under 13 and another for teenagers. The stricter treatment applies to all of them.
Consent is asked for explicitly. Before you can create a story in the tool, you must tick a required box confirming that — if the first name and age you give belong to a real child — you are that child's parent or legal guardian, or you have their parent or guardian's permission, and that you consent to our using them. If the name you give is made up rather than a real child's, nothing in that box applies to you. For the publishing service, consent and final approval are given by signing the Parental Consent & Publicity Release with the About the Author page proof attached — and that must be signed by the child's parent or legal guardian. Someone else may pay for the package as a gift, but only a parent or guardian can give us permission to publish a child's name, biography and photograph, and nothing goes to print or to a retailer until they have.
On whether a first name is identifying. A first name and an age, on their own, would not usually identify a particular child. We are not going to lean on that, because your account — your name, your email, your payment record — sits alongside it, and a child's information that is linked to an identified parent may well be identifying in practice. We therefore handle a child's first name and age as personal information about that child, and ask for consent accordingly.
We do not use a child's information to advertise to anyone, and we do not build a profile of a child. In the story tool it is used to write and narrate that child's story and nothing else. In the publishing service it is used to make, distribute and promote their book, as you have authorised in writing.
If you believe we hold information about a child that you did not provide and did not consent to, contact us at info@cochainbooks.com and we will delete it.
11. Changes to this policy
We will post any new version on this page with a new version number and effective date, and keep the superseded version available on request. Please check this page from time to time, and before making any decision that depends on it. Continuing to use the service after a new version is posted means you accept it.
This version supersedes `privacy-2026-10-r2`, which superseded `privacy-2026-10`, which superseded `privacy-2026-09-r4`, which superseded `privacy-2026-09-r3`, which superseded `privacy-2026-09-r2`, which superseded `privacy-2026-09`, which superseded the policy of May 2026. Below is everything that has changed since May 2026, so that the list is complete whichever version you read last.
14 September 2026 (`privacy-2026-09`). Stories are accepted as typed text, and for the publishing service also as a PDF or Word document, but not as audio, voice notes or photographed handwriting; the story tool, its providers and its data flows are described for the first time; Google, Anthropic, OpenAI, ElevenLabs, Vercel, Supabase and Stripe are named and linked; the reference-photo section describes the actual illustration process; retention is separated into working data and records kept for legal purposes; and deletion, the surviving acceptance record and the treatment of children's information are described honestly.
16 September 2026 (`privacy-2026-09-r2`). Section 3.2 sets out what we ask you for to create your story, including the age band, and says that your child's exact age never reaches the AI providers named in section 4.
19 September 2026 (`privacy-2026-09-r3`). Section 8 now says how we check that a request is really yours, and gives you 7 days to stop an emailed request to delete your account or your stories. It also gives you an appeal if we refuse a request, and says how to take the matter further if we turn that appeal down. It says that a complicated request, or several at once, may take up to 45 days longer, and that we will tell you inside the first 45 days if that happens. Section 7.2 now describes the payment and transaction records our payment processor holds, and says plainly which financial records are ours and which are theirs. Section 3.2 now separates the title you type, which no AI provider sees, from the title the tool writes for itself, which they do. Section 4 corrects what is sent to Anthropic — your child's age band, not their exact age — and notes that not every provider publishes a privacy policy of its own. Section 8 now says that we keep each version's exact wording, so what you agreed to can be shown word for word, and describes what happens to that record when your account is deleted: we erase the IP address and the browser, and add a one-way code made from the email address on your account, so that we can still show you what you agreed to if you ask.
21 September 2026 (`privacy-2026-09-r4`). Section 7.2 now lists the Order — the checkout confirmation and fee record that forms part of your publishing agreement, including an order placed as a gift — and says that we keep it for 7 years from the day it is issued.
1 October 2026 (`privacy-2026-10`). Section 3.4 separates what we keep for a subscription from what we keep when you buy a publishing package, which includes the details we need to work out and record Texas sales tax: the billing ZIP code you enter, your card's billing ZIP code, the state each falls in, the tax rate and the tax charged. Section 7.2 lists those details among the financial and tax records we keep. Section 3.3 ties reference photographs to the likeness add-on rather than to named packages, and no longer lists a delivery address, because we do not ship anything: print editions are published on Amazon, where copies are bought.
17 October 2026 (`privacy-2026-10-r2`). The Free Library is described for the first time, in section 1 as the third of the three things we run, and in section 10 as the one place a child may be here on their own. Section 5 is rewritten. It now covers the story tool, the Free Library reader and the marketing site; it no longer counts what is stored in your browser; it names the cookie the story tool sets while you sign in with Google and the selections it holds while you decide what to publish; and it says exactly what leaves your browser when you like a book or choose a language edition, and what does not. It records that our hosting and database providers keep their own records of the requests reaching them, which include network addresses, and it describes a cookie that reaches your browser from outside — a short-lived bot-protection cookie offered by the network in front of our database provider, which both the Free Library and the sign-in page talk to, and which is not ours and which we cannot read. And it says when we last checked all of this, and how: in October 2026, against the public pages in a browser and against every page in the code, rather than against our own documentation. Section 4 adds the Free Library to what Vercel runs, adds the reaction totals and Supabase's own request records to the Supabase row, says what text reaches ElevenLabs for a Free Library book as against a story you create, and sets out the licence ElevenLabs takes over what we send it and what it returns — which is wider than making our audio, and which no earlier version of this policy described. It also records that we opted out of ElevenLabs' use of customer material to improve its models on 17 October 2026, and that no story written in the story tool had been narrated for anyone outside Cochain Books before that date. Section 2 now says that you confirm you are 18 or over when you create your account, which is separate from the confirmation you give about a child before a story is created. Section 3.1 lists the settings we hold on your account. Section 3.4 describes what we keep for a subscription accurately and in full, and no longer says we keep "only" Stripe's reference, which was not true. Section 7.2 states the real basis for the seven-year retention period — a single period we have chosen, longer than US or Texas tax law requires — rather than attributing it to a legal requirement. Section 8 no longer implies that you have a password; you do not. And in sections 3.4 and 7.2 a colon that made a list look exhaustive has been replaced, so that those lists read as examples, which is what they are.
This version (`privacy-2026-10-r3`). Our home page at cochainbooks.com now shows what is on our shelves, and section 5 says how: it loads a small program of ours and reads the public details and cover pictures of the books from the same database the story tool and the Free Library use. The sentence that said the marketing site never receives anything from the story tool or the reader is gone, because it is no longer true. What matters more is that your browser now contacts two of our providers while that page loads, so section 4's entries for Vercel and Supabase say that they see requests from visitors to the marketing site as well — people who have no account with us and may never want one. Nothing about you or your child travels that way; what the page reads is the published description of a book. Section 5 also describes the outside cookie more carefully than before: it is offered rather than set, our home page is one of the pages that prompts it, and when we tested it in Chrome the browser rejected it every time because of the address it is scoped to — which we report as a test result rather than as a promise about every browser. Section 10's mention of that cookie is corrected to match: it said the cookie was set, and it is offered. This version also names Google's spam-protection check on our marketing site, which loads on every page of cochainbooks.com before you click anything, and says what Google receives while it does. Section 5's opening sentence is narrowed to match. It used to say that nothing we run sets an analytics or advertising cookie and that none of it loads a third-party script; that was broader than we could support, because our marketing site does load that check. The story tool and the Free Library reader load nothing of the kind, which is what we can say and what section 5 now says. Our telephone number has also been removed from this policy, from the contact details at the top and from section 12. Email reaches us.
12. Contact
Cochain LLC d/b/a Cochain Books 5826 New Territory Blvd PMB 3027, Sugar Land, TX 77479 info@cochainbooks.com