← Fablebee

Privacy notice

What we collect, why, and for how long. Written for parents.

Who we are

Fablebee is operated by InferShift AI Solutions Limited, previously called CogniForce Ltd (company number 16315093, registered office 6 Croft Down Road, Solihull, England, B92 9BD), which is the data controller for the personal data described here. You can reach us at help@fablebee.com.

Whose data this is about

This notice covers two people: you, the account holder, and your child, whose name and age range you give us so that stories can be written for them.

Your child is a data subject in their own right. Because their information comes to us from you rather than from them, this notice sets out what we do with it, and you exercise their rights on their behalf. At the end there is a short version in words you can read to them.

What we collect

From you: your email address, your password (stored only as a secure hash), and records of your payments if you subscribe.

About your child: a first name or nickname, and an age range such as 3 to 5. We do not ask for and do not want a date of birth, a photograph, an address, a school name or any contact details for your child.

What you type: the theme you choose and any details you add about the story you would like.

Evidence of what you agreed to: when you tick the boxes at sign-up or at checkout we record the date and time, your IP address and your browser’s description, because that is what makes the record evidence. We keep that record even if you later delete your account — showing what you agreed to and when is its whole purpose. Ask us and we will remove the IP address and browser description from it, leaving the fact and the date.

Technical records: basic security and error logs. Our web server keeps a short access log — IP address, page requested and browser description — which is overwritten after seven days. We do not use product analytics inside the app, and we never record your screen or your session.

If you pay: your name, your billing address, the last four digits of your card and your payment history, copied into our database from our payments provider so that we can answer questions about your plan. We never see or store your card number.

Records of the service working: which stories were made and how long they took, the safety scores each story was given before it reached you (scores only — never the checker’s words), what each account has cost us to run, and a reference number for each request we sent to the AI provider.

Whether you have to give it to us

You have to give us an email address to have an account — without it we cannot sign you in or send you your story.

To make a story for a child we need two things: something to call them, and an age range so the story is written at the right level. It does not have to be their real name — a nickname works just as well, and the story is written the same way.

Everything else — the theme, and any details you add — is your choice, and a story can be made without them.

Why we can use it

Making and narrating your stories, running your account and taking payment — to perform our contract with you.

Your child’s first name or nickname and age range — your child is not party to our contract, so we rely on our legitimate interests: making a story personal to the child it is for, which is the thing you asked us to do, using the least information that can achieve it. You can object at any time by emailing help@fablebee.com, or by removing the child from your account on the children page.

Checking every story against safety rules before it reaches you — our legitimate interests in not sending a child unsafe content.

Stopping the free trial being taken twice, and keeping a lid on what each account costs us to run — our legitimate interests in keeping the service viable.

Security and error logs — our legitimate interests in keeping the service working and your account safe.

Consent records and payment records — our legal obligations, and where the law does not require them, our legitimate interests in being able to evidence what you agreed to.

Who else sees it

We use a small number of processors to run the service: a database, sign-in and file-storage provider hosting in the United Kingdom, which also sends our sign-up and password-reset emails; a cloud provider in the United Kingdom that hosts our servers and that also runs the AI model that writes your story and separately checks it against our safety rules; and a speech provider that turns the text into audio. That speech provider uses two other companies to hold its own operational logs.

We require the speech provider to run that conversion on machines in the European Economic Area. The story text is encrypted before it leaves our servers and is decrypted only inside the process that produces the audio.

That provider holds the encrypted request for up to about half an hour while the audio is made, and holds the finished audio for up to thirty minutes after it is produced. It keeps operational logs for ninety days. Those logs contain no story text and no child’s name.

If you pay us, our payments provider handles the payment and your card details. We never see or store your card number. They send your receipt, and your statement shows their name rather than ours.

A full copy of the billing records our payments provider holds about you — including your name, email address, billing address, a phone number if you gave one, the last four digits and expiry date of your card, and every invoice, payment and refund — is synced into our own database so that we can answer questions about your plan. That copy also contains the equivalent records for another service operated on the same payments account, and our records are likewise present in theirs. Neither service uses the other’s records for anything. If you delete your account we delete your payment profile at the provider, which is what removes it at source, and we remove our copy at the same time.

We do not sell your data, and we do not share it for advertising.

Where your data goes

Everything we store ourselves is held in the United Kingdom — your account, your child’s details, your stories and every recording, in London. That includes the AI model that writes your story.

Two things leave. The step that turns the written story into speech runs at a company based in the United States, and we require that conversion to happen on machines inside the European Economic Area, which UK law treats as offering the same protection. The story text is sealed with strong encryption before it leaves our servers. That provider’s own operational logs, and the companies it uses to hold them, are not limited to the European Economic Area.

And if you pay us, our payment provider handles the payment and holds your billing details on its own systems, which are outside the United Kingdom. Your child’s name and your stories are never sent to the payment provider.

Email help@fablebee.com if you would like to know more.

Decisions made by computer

Two things happen automatically. Your story is written by an AI model, and once it is written — before it is turned into audio — the same model is asked to score it against safety rules for young children. If it does not pass, the story is not made and no person reads it. Your story credit is returned.

Nothing else about your account is decided automatically: we do not profile you or your child, we do not score you, and nothing we do produces a legal effect or anything similarly significant for either of you.

If a story of yours is ever blocked and you think that was wrong, email help@fablebee.com and a person will look at it.

Private by default

Nobody outside your household can see your stories. There is no public gallery, no sharing between families, and no way to send a story to another account — that is a deliberate design choice, not a feature we have not built yet.

Everything in Fablebee is already set to the most private option and there is nothing to switch off. There is no profile of your child. Children do not sign in and never have accounts. We do not run age checks, because doing so would mean collecting more about your child, not less.

Cookies and things stored in your browser

We set no advertising cookies and no analytics cookies, and there are no third-party scripts on the site at all.

Three things are stored in your own browser so that the app works. Your sign-in session, which keeps you signed in until you sign out. A note of which documents you agreed to when you signed up, held only until it reaches us and then removed. And an unfinished story you are part-way through making, which stays in that one browser tab for up to 24 hours and includes anything you have typed about your child. All three sit on your device, and clearing your browser data removes them.

If you connect Yoto, a fourth thing joins them: the key that lets your browser talk to your own Yoto account, along with a short note of a send that is part-way through, so it can carry on where it left off. Both are stored in your browser and only there — they are never sent to us. Disconnecting Yoto from your account page, signing out, or clearing your browser data removes them.

Keeping it safe

Your recordings are held in private storage that is not reachable from the open internet, and every request for one is checked against your account first. Your password is never stored, only an irreversible scramble of it. The story text is sealed with strong encryption before it leaves our servers for the step that turns it into speech.

If something ever goes wrong that puts your or your child’s data at risk, we will tell the Information Commissioner’s Office within 72 hours and, where it is likely to affect you, tell you too.

How long we keep it

Your stories are kept for as long as you have an account. If your subscription ends we keep your library — only playback stops.

The written script and the details you typed are deleted from our systems once the recording is finished. After that, the audio is the only copy of the story we hold. If a story fails part-way through, the script and what you typed are removed when you delete your account.

If you delete your account, your data and recordings are removed straight away. Your audio files are in no database backup at all, so they are gone at once. Copies inside our routine database backups are overwritten within seven days, and are not used for anything in the meantime.

Deletion clears the files from our delivery network within about a minute. A copy already sitting in your own browser’s cache expires within an hour, and we sweep both of our stores again about an hour later to make sure nothing was missed.

If you sent stories to Yoto, the copies in your own Yoto account are not ours to delete: unless you tick the box asking your browser to remove the playlists when you delete your account, they stay there under Yoto’s own rules — and even that removal cannot reach Yoto’s copy of the audio itself.

We keep your account for as long as you have one. We do not delete accounts for inactivity at present. If we ever start to, we will tell you before anything is deleted and give you a way to stop it.

One thing survives deletion and is not a legal record: a one-way scrambled version of your email address, kept so that deleting an account and signing up again does not hand out a second free trial. It cannot be turned back into your address, and it holds nothing about your child.

Records we must keep for legal reasons, such as consent and payment records, are kept for at least six years — that is how long someone has to bring a claim about a contract, and these records are the evidence. None of them contains your child’s name.

One limit we should be straight about

The AI provider that writes the story, and that also runs the safety check on it, does not publish a way to delete an individual past request. What we sent — your child’s first name and age range, the theme you chose and anything you typed — stays in that provider’s systems under their own retention, which they do not publish.

We keep a reference number for every request so that we can raise it with them, and we send them nothing about your account, your email address or your payments.

If you send a story to Yoto

If your family has a Yoto player, you can send stories from your library to your own Yoto account, and from there put them on one of your own Make Your Own cards. This happens in your browser, using your own Yoto sign-in, and only when you press send. The story goes straight from your library to Yoto — we never see or hold your Yoto password, and the key your browser uses to talk to Yoto stays on your device, never on our servers.

When you send a story, Yoto keeps its own copy of the audio in your Yoto account, and from that moment Yoto’s own terms and privacy notice apply to it. Deleting a story here, or your whole Fablebee account, does not remove that copy — the playlists stay in your own Yoto library and a linked card keeps playing. When deleting your account you can instead tick a box asking your browser to remove the playlists Fablebee made from your Yoto library; even then, Yoto’s copy of the audio itself may remain within Yoto’s own systems. You can also remove the playlists from your own Yoto account yourself at any time. Yoto has said it may remove Make Your Own content that nobody has listened to for over three years.

What we keep ourselves is small: a note of which stories you sent and which card they belong to, so that we can update the same card later and show you what is on it. That note is deleted with your account.

Emails we send

We email you about your account: confirming your email address, resetting your password, and your receipts, which come from our payment provider.

We do not send marketing email. If we ever want to, we will ask you first and you will be able to stop it in one click.

Your rights

You can ask us for a copy of the data we hold about you and your child; ask us to correct anything that is wrong; ask us to delete it; ask us to pause what we do with it while we look into a query; object to anything we do on the basis of our legitimate interests, including anything we do with your child’s name and age range; and ask us to send you your data in a portable form.

You can delete your account yourself at any time from the account page, and you can remove a child at any time from the children page.

These rights belong to your child as much as to you, and while they are young you exercise them for them. If your child is old enough to ask us themselves, they can — write to help@fablebee.com and we will deal with them directly, and we will tell you unless there is a reason not to.

Email help@fablebee.com and we will respond within one month. We will tell you if we need longer.

You can complain to the Information Commissioner’s Office at ico.org.uk.

Changes to this notice

If we change how we handle your data we will publish a new version of this notice at this address and change the date at the foot of the page.

We keep a record of which exact version you agreed to when you signed up, and that record does not change when the notice does — you can ask us at any time which version that was.

The short version, to read to your child

If your child asks what we know about them, this is the answer in words you can read out.

A grown-up in your family asked us to make stories for you. To do that we keep your first name, or a nickname, roughly how old you are, and whatever the grown-up tells us the story should be about.

We do not keep your photo, where you live, or where you go to school.

Nobody else can see your stories. They are only for you and your family.

A computer writes your stories and a computer voice reads them out.

If you want your name taken away, ask a grown-up in your family. They can do it, and then it is gone.

Version 1.1 · In force from 17 August 2026