What We Keep, and What We Don't: Your Child's Privacy
Before you type your child's name into anything, there is usually a small hesitation. That hesitation is wise. A child's name, age, and the little details that make them themselves are not data points to hand over lightly, and a parent who pauses is doing exactly the right thing.
So this is a plain-English account of how a personalized story can respect that instinct. No statutes, no fine print theater, just what gets collected, who it comes from, and why the details should always stay yours.
1. The parent is the customer, not the child
The most important idea in children's privacy is also the simplest: a young child is not the customer. You are. You hold the account, you make the decisions, and in privacy terms you are the person the company is responsible to.
This is not a technicality. It shapes everything downstream: where information comes from, who can change it, and who has the right to ask for it back. A product built this way treats you as the data subject, with the child kept out of that relationship entirely.
2. Data comes from you, never from the child
Good personalization is fed by a parent, not gathered from a child. There is no account a child logs into, no behavior of theirs being watched, no quiet collection happening in the background.
You provide a few details on purpose, knowingly, and that is the whole input. The child simply receives a story. Keeping the child out of the data relationship is one of the clearest signs a product was designed with their privacy in mind.
3. Less is the point: data minimization in plain words
Data minimization means collecting only what a product genuinely needs and nothing more. For a personalized story, that is a short list: a name, an age, a few interests, and some details about how the child should be represented in the art.
That is enough to make a story feel like theirs. It is not enough to build a profile, and that is deliberate. When a company asks for only the few things the story actually uses, the small size of the ask is itself a form of respect.
4. Appearance is art direction, not a photo on file
Making a child the illustrated hero of a story raises a fair worry: is their face being stored somewhere? The honest answer for a well-built product is no.
Appearance details are used as art direction for a stylized illustration, a description that guides a drawing, not a photograph kept on a server. There is a real difference between "draw a child with curly hair and a gap-toothed smile" and "store this child's photo," and a privacy-respecting product stays firmly on the former side.
5. No selling, no third-party sharing
A child's information should never be a product. That means it is not sold, and it is not passed to advertisers or outside companies to do their own things with.
This is one of the bright lines worth checking explicitly, because it is where a lot of trust is won or lost. If a company cannot tell you plainly that it does not sell or share children's data, that silence is the answer.
6. Memory means the story remembers, not that you are tracked
A story that grows with your child has to remember things: what happened last night, who the characters are, where the adventure is heading. That memory is what makes a serial feel alive.
It is worth being clear about what that memory is for. It exists to keep the story coherent and personal, not to track your child or accumulate insight about them. The story remembers. That is the beginning and the end of it.
7. You stay in control
Respecting privacy is not only about collecting little. It is about leaving you in charge of the little that exists. You should be able to see what is held, change it, pause the whole thing, or ask for it to be deleted, without a fight.
Control is the difference between information you handed over and information that was taken. The details should always feel like a loan you can call back, not a transfer you cannot undo. For the safety side of the same question, see [Is AI Content Safe for Kids?](/blog/is-ai-safe-for-kids).
With Chapterling, you are the account holder, the customer, and the person we are responsible to. We collect a small set of details from you, the parent: your child's name, age, a few interests, and how they should be represented in the illustrations. We never collect anything from the child, we never store a photo of them (appearance is used only as art direction for a stylized drawing), and we never sell or share children's data with third parties. The story remembers your child so it can grow with them, and the details stay yours: you can review, change, pause, or delete them whenever you like.
Start your child’s story →Frequently asked questions
It is, with a product built the right way: one that collects the name from you, uses it only to write the story, keeps no profile of your child, and lets you delete it on request. The thing to check is who the customer is and how little is kept.
A privacy-respecting one does not. Appearance should be used as art direction for a stylized illustration, a written description that guides a drawing, not a stored photograph. Chapterling never stores a photo of your child.
With a trustworthy product, yes, easily. Because you are the account holder, you should be able to review, change, pause, or delete what is held whenever you choose. That control is part of what "details stay yours" actually means.