Bedtime stories, read in your voice.

Tuck & Tales takes short bedtime stories written in advance, and renders them into audio narrated in a parent's own recorded voice.

Each story has named places for your child's name, their pet, a companion and a setting — the same story, told to your child.

It is built to help a child fall asleep, so there is nothing in it that tries to keep anyone awake: no recommendations, no autoplay, no streaks, no badges, nothing to share.

Not yet — sign-ups are not open. Tuck & Tales is still being built, and there is no account to create today. We would rather run a landing page that says that than a sign-up form that leads nowhere.

No price has been set either, so this page does not name one.

How it works

You record once, in the app

You read a short passage aloud in your browser — including a line giving spoken permission for your voice to narrate stories to your child. There is no file upload, so a voice can only ever be enrolled by the person it belongs to, while they are present.
The recording is locked before it leaves your device

Your browser encrypts the recording under a key only our rendering hardware holds. What reaches our servers is ciphertext we cannot open, and the client that does the encrypting ships as source you can read.
Stories are rendered on hardware we own

Rendering happens on studio hardware we run ourselves rather than a shared cloud voice service. That machine accepts no incoming connection from the internet — it reaches out to ask for work, and nothing else.
Nothing is generated while your child is listening

Every story is rendered ahead of time, never at the moment of playback. Bedtime does not wait on a queue, and it does not depend on us being fast.

The part that actually matters

This is the same wording as the privacy one-pager, not a summary of it. Every sentence maps to a mechanism in the code and, in most cases, a test that proves it.

Your child is never recorded

There is no feature, screen, or setting anywhere in Tuck & Tales that records your child's voice — and no server endpoint exists that would accept it even if one tried. Your child does not sign in and does not have an account; the only information we hold about them is a first name and a small profile you create.

There is no way to upload a recording of someone else

You cannot upload an audio file to create a voice — recording only happens live, in the app, while you are present. That means Tuck & Tales cannot be used to recreate the voice of someone who is absent, unable to consent, or who has passed away. We built it this way on purpose, not as a workaround.

We cannot read your enrollment recording — including while it's waiting

Your recording is encrypted in your own browser, before it ever leaves your device, under a key only our rendering hardware holds. Because that hardware is not always turned on, your recording sometimes waits before it is processed — and even then, we cannot open it. This is true by construction, not by policy: our client is shipped as source code, so it can be checked, not just taken on faith.

What we keep, and for how long

We keep a compact voice profile — not your original recording — used only to render your child's stories. Because part of that profile can currently be used to reconstruct audio close to your original recording, we treat and protect it exactly like a voice recording: encrypted, accessible only for rendering, deleted the moment you ask.

Today that means the same retention and deletion rules as your original recording, and protection from Cloudflare's own automatic storage encryption. It does not yet mean the same browser-side encryption your original recording gets before it ever reaches us — closing that gap is real, named, ongoing work, not a claim we are making today.

Deletion is one tap, and it's real

Deleting a voice, a child's profile, or your whole account starts a tracked job with a real, permanent, recorded outcome — not a flag that just hides something on a screen. Most of the time it finishes right away. If our rendering hardware happens to be offline at that moment, deletion finishes as soon as it is back online, and we tell you plainly that it is in progress rather than pretending it is already done. Closing your account fully purges everything within 30 days.

No third-party trackers near your child's story

The screen where your child listens to a story loads no third-party analytics, advertising, or tracking code of any kind. Any usage data we collect about how the product is used is collected directly, by us — never handed to an ad network or analytics vendor.

Read the whole privacy one-pager — it is short.

Who writes the stories

Honestly: not a children's author, not yet. The stories published today were drafted with AI and edited by the Tuck & Tales content team, and they are credited exactly that way in the library.

They exist to prove the pipeline end to end, not to be the finished library. We would rather say that plainly than let a landing page imply a byline that does not exist.

The plan is to engage a children's author as editor over drafted material, because the library is the part of this that lasts — voice technology is becoming a commodity, and good bedtime stories are not.

You install it to your home screen

Tuck & Tales runs in your browser, and adding it to your home screen is a real step in setting it up rather than an optional extra. It is worth knowing that before you start.

On an iPhone it is what makes stories stay downloaded: Safari clears a plain tab's stored data after roughly a week of not being opened, which would quietly empty your library over a holiday.

It is also the only way iOS will let us tell you a story is ready, instead of asking you to keep checking back.

What is working today, and what is not

Tuck & Tales is being built in the open, and this page is written to be true on the day you read it rather than on the day it launches.

Working

Recording your voice in the browser, with spoken consent captured in the same recording
Client-side encryption of that recording, verified across both stacks
Stories as versioned, validated content with named personalisation slots
Rendering on our own hardware, which leases work outward and is never dialled into
Deletion as a tracked job with a permanent record, including the render host's copy
Honest waiting times, phrased against bedtime rather than as a queue position

Still being built

The production narration and mastering pipeline
The parent review screen, where you approve a story before your child hears it
Offline downloads and the player itself
Notifying you when a story is ready
Accounts, billing, and opening sign-ups

Things we are deliberately not building

A microphone that listens in a child's room, or any recording of your child at all
A chatbot your child talks to, or stories invented on the fly while they listen
Streaks, badges, rewards, or anything else designed to bring a child back
Messages written by a machine and presented as if you had said them