Privacy

Our privacy promise

First names only

We store a first name, an age, a few things they like, and an optional note. There is no field for a surname, a birthday, a school or an address — not hidden, not optional. It does not exist.

No photos, ever

There is nowhere to upload a picture of your child, because we never want one.

The account is yours

Children have no logins. Only you can see your family’s stories, and nothing is shared with other families or made public.

Delete in one tap

Any story can be deleted from the story itself. Deleting your account removes your children’s details and every story we store with it.

No tracking of your children

No advertising trackers and no third-party analytics that profile children. We count page views and nothing else.

If we can't make a story

If we turn a topic down, or a story fails partway through, it does not use one of your three stories for the day. The words that were turned down are kept for at most 24 hours, only to improve our safety checks, and then deleted.

What we store about a child

Exactly five things, and there is no database column for anything else:

• First name — so the story can be about them by name. Optional: leave it blank and we'll choose a name for the stories instead.
• Age — a whole number, to pitch the vocabulary and how much peril the story is allowed. Not a birthday.
• Up to ten likes — short tags such as “football”, “dinosaurs”.
• An optional note — up to 300 characters, whatever you think helps.
• An optional reading level — younger, typical or older than their age.

Please keep the note about the story, not about the child's life: it is the one free-text field, and we would rather it never held anything you would mind us having.

What we store about you

Your email address, so you can sign in — there is no password to lose. A family name and a timezone, both of which you choose. If you add one, your Kindle’s Send-to-Kindle address, used only to email you a story you ask for. And the stories we made for you, with what each one cost us to generate.

Who can see it

You. Every page and every API route that touches a child's details requires your session, and the database enforces the same rule a second time with row-level security, so one family's rows are not reachable from another family's account even if the application has a bug.

Your children and AI

We know many parents think carefully about AI, and especially about sharing anything about their children with it. We do too. So here is plainly how a story is made, and what leaves LastTen.org when it is.

Our stories are written by AI models. When you ask for one, we send a short request to the outside AI services that run those models: one that compares models on quality and cost, and the company whose model writes the story. So the model that writes a story can change over time. The request holds only what the story needs to feel like it was written for your child:

• the first name you gave each child, so they can be the hero;
• their age, so the words and the adventure suit them;
• their likes, any note you added, and their reading level;
• the topic you typed.

That is all. We collect as little about your children as we can, to protect who they are: there is no surname, birthday, school, photo or address to send, because we never ask for them. Your email address is never sent.

The service that compares models keeps a copy of each request and the story it wrote. Its published terms say it does not use them to train models for anyone else, and we can ask it to delete them. We never use your stories or your children's details to train any model ourselves.

Analytics

None of the usual kind. No Google Analytics, no advertising pixels, no session recording, no third-party script that could follow a child around the web. We count page views in aggregate and nothing else.

Deleting everything

Settings → Delete account. It is immediate and it is a real delete, not a flag: your children's profiles, your series, your story bibles and every story go in one transaction, and your sign-in is removed with them. There is no restore, so we ask you to type the word first.

We keep one thing: the accounting rows that record what each generation cost, with the family reference stripped to null. They carry no name, no topic and no story text — just a model, a token count and a price — and we need them to know what the service costs to run.

The copies that service keeps of past requests are separate from your account, so deleting your account does not remove them. We can ask the service to delete them.