Endless StorytimeAll posts

Built Like It's My Own Kid's Data (Because It Is)

By Fatima Abdulah · March 28, 2026 · 4 min read

Before Endless Storytime, I spent eight years building systems that protect sensitive data: personal information, regulatory documents, financial data, the kind of information that belongs to real people. When I built this, I brought every lesson with me. My own kid's data lives on these servers, so I built our privacy architecture the exact way I'd want it built for her.

We use AI to personalize unique stories for your child each night. No tracking, no ads, no data selling. Here is exactly what we do to ensure their information stays locked down.

Our Three Promises

How It Works

Your side

“Layla”

Parent types their child’s name

Protected

“Alex”

Third-party services only see a placeholder

Your side

“Layla”

Your child hears their real name

Encrypted

a7×f2…9×e1

Encrypted at rest in our database

This happens automatically, every time, for every story. The services that write and personalize your child's story only ever see a placeholder.

The Voice Narration Exception

There is one place your child's first name is shared: the audio narration. For the voice engine to say your child's name out loud, the text-to-speech service needs to see the text.

We hold ourselves to a higher standard than what the law requires. Under COPPA, a first name alone (without an age, location, or photo) is not classified as personally identifiable information. But we are actively developing local narration to eliminate even this external touchpoint.


I built this for my own kid. She's not a test case. Her data gets the same protections yours does. If you have a question about how we handle your child's information, you have my direct line.

Most children's apps collect device IDs, location, and behavioral data. We collect a first name and an age range. Try a free bedtime story.