Welcome! At Bedtime Stories, we keep things simple when it comes to your family's privacy. This policy explains exactly what we need to create magical, personalized bedtime stories for your child.
The simple truth: To personalize a story we use the details you enter for each child profile — a first name or nickname (with an optional phonetic spelling so the narrator says it correctly), the child's gender, the child's age in years, and an age range (3-4, 5-6, 7-8, or 9-12 years) for age-appropriate content. You decide what to enter, you can use a nickname instead of a real name, you can edit a profile at any time, and you can remove a profile as long as another one remains (see Children's Privacy).
Bedtime Stories is a sole proprietorship registered with the Dutch Chamber of Commerce. For the purposes of the EU General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR"), we are the data controller for personal data processed through the Service.
You can reach us about any data-protection matter — including access, correction, deletion, portability, restriction, or objection requests — at hello@bedtime-stories.fun. We respond to verified requests within 30 days. We are below the GDPR threshold for appointing a Data Protection Officer; the business owner handles all privacy queries directly.
For Your Account:
For Your Child Profiles & Stories:
Like any website, we automatically collect some technical information to keep things running smoothly:
Here's exactly what we do with your information:
AI Processing Note: Story text is generated using Anthropic Claude for creating personalized narratives. To personalize a story, the story details you enter in the creation wizard — including your child's first name, age range, and any custom instructions — are sent to Anthropic (story text) and Google (illustrations) solely to generate that story; we never send your email address, account details, or voice recordings to these providers. Story images are created through Google's Gemini image model using only story-related prompts. Text-to-speech conversion is handled by ElevenLabs for catalog voices and by Fish Audio (Hanabi AI Inc., United States) for custom voice cloning. We log AI requests through Helicone for observability and validate the inputs you provide before a story is generated. As part of that check, the story details you type and the illustration prompt are sent to TypeSafe (TypeSafe AI, Inc., United States), with the names attached to the story replaced by placeholders (see the section on international transfers). TypeSafe only answers whether they try to manipulate the AI or name a trademarked or copyrighted character, a brand or a real public figure, and does not train AI models on them; it never receives your email address, account details, or voice recordings. Our backend services running on Hetzner European servers coordinate these AI services and store the final content in Supabase. Every AI processor we use is named in this policy, along with the country it operates from.
Bot Protection: We use Cloudflare for DNS and Turnstile captcha protection to protect against automated abuse and ensure platform security. Turnstile processes technical information (IP address, browser signals, TLS fingerprint) to distinguish humans from bots. This data is processed by Cloudflare Inc. (US) under their privacy policy. Turnstile does not use traditional cookies and collects minimal data solely for security purposes.
Analytics & Cookies: We use PostHog (European data region) for analytics and product improvement. PostHog uses cookies and local storage to track user sessions, feature usage, and platform performance. With analytics on, each story you create also records the age range you picked for it, such as 5-6, and on the website playing a child's name preview during setup records the child's gender. In the app, analytics also carries your account ID, a device ID, device details such as model, system version and language, and the credit packages you buy with their price and currency. You can manage your cookie preferences and opt out of analytics tracking at any time. In the mobile app, analytics is off until you turn it on: the app asks you, and you can change your answer at any time in the Account tab, under Privacy. Your answer is stored on the device. When you sign out, or another account signs in, analytics is turned off and the app asks again. PostHog data is processed under their privacy policy and the GDPR. For more details, see our Cookie Policy.
Error Monitoring: We use Sentry to detect and fix technical issues. Sentry does not use cookies and we have disabled personal data collection.
Email Communications: Transactional emails (account confirmations, password resets, story-ready notifications) and the welcome series for new accounts are sent via Resend. Every marketing message includes a one-click unsubscribe link, and you can also turn marketing emails off in your account settings at any time.
Under GDPR Article 6 (and Article 9 for special-category data) we rely on the following lawful bases:
Accounts are for adults. Our Terms of Service say the Service is operated by adults for adults. A person under the age of majority may only use it through a parent or legal guardian who accepts the Terms on their behalf. There is no checkbox: the app and the website say that by continuing you agree to the Terms. There are no child accounts. The app can save child profiles for a guest before an account is created. If a guest is not used for 30 days and has bought nothing, we delete it with its child profiles and stories.
What we hold about a child. Only what a parent enters:
Analytics is opt-in. Analytics stays off until you say yes: on the website in the cookie settings, in the app when it asks you. You can change your answer at any time: on the website through the Cookie Settings link in the footer, in the app in the Account tab, under Privacy.
Deleting a child's data. You can remove a child profile as long as another one remains. When you remove a child profile, it no longer appears in your account, but we keep it until you delete your account. You can delete your account in your account settings, on the website or in the app. You can undo this for 30 days. After that, we delete the account with its child profiles, stories, voices and stored files (story audio, cover images, name clips and voice recordings), and ask our voice provider to delete your voice clones. Encrypted backups can keep a copy for up to about 7 months (see Data Retention).
Here's the simple truth: We use the names, gender, and ages from your child profiles, plus the choices you make in the story wizard, to create personalized stories.
You can optionally record your own voice to narrate bedtime stories. The voice clone is created by Fish Audio (Hanabi AI Inc.), a company based in the United States. Fish Audio's terms allow it to use the audio you submit to train its own AI models. Here is exactly how your voice data is handled:
We (Bedtime Stories) are the Data Controller for your voice data. Fish Audio is our processor: we send it your recording, it creates and hosts the voice clone, and we call it to narrate your stories. We do not hold a signed Data Processing Agreement with Fish Audio, and its terms let it use submitted content to train its models. That is why we ask for your explicit consent before you record, and why this section spells out what Fish Audio may do.
Voice data is biometric data under GDPR Article 9. We process it based on your explicit consent (GDPR Article 9(2)(a)), which you provide before recording by checking the consent box. Sending the recording to Fish Audio also takes it outside the EEA, and we rely on your explicit consent for that transfer too (Article 49(1)(a)). Fish Audio's own privacy policy states that it relies on standard data protection clauses adopted by the European Commission. You can withdraw consent at any time by deleting your voice from your dashboard or deleting your account.
Fish Audio's terms state that content submitted to its service may be used to develop, train, or enhance the AI models behind its products. The terms draw no distinction between free and paid accounts, and Fish Audio offers no opt-out. We tell you this before you record so the choice is yours. If you would rather your voice was not used this way, do not create a custom voice. The catalog voices need no recording from you and are not affected.
Your account, child profiles, stories, and media files are stored on European servers through Supabase's European data region, which covers our database, object storage, and authentication. Custom voice cloning is the one exception. Those recordings go to Fish Audio in the United States; everything else stays in the EEA.
We implement enterprise-grade security measures including encryption, access controls, and regular security audits. For detailed technical security information, please see our comprehensive Security Policy.
We work with trusted partners who maintain strict data protection standards:
Where a partner processes personal data outside the EEA, the safeguard we rely on is set out in the next section.
Most of your personal data stays in the European Economic Area (Supabase Frankfurt, Hetzner Germany, PostHog EU). Some processors are based outside the EEA, primarily in the United States:
Where personal data leaves the EEA, we rely on one or more of the following safeguards under Chapter V of the GDPR:
TypeSafe is an exception. While a story is being made we may ask a screening service, TypeSafe AI, Inc. in the United States, two questions: whether the text you typed tries to manipulate the AI, and whether the cover-image description names a trademarked or copyrighted character, a brand or a real public figure. The names attached to this story (its characters and the children in its goodnight line) are replaced by a placeholder such as CHARACTER_1 before that text leaves our servers. This is pseudonymisation, not anonymisation: we can still link the placeholder to the name on our side. Other names may remain in the text, including names you type into the story yourself, names saved in your account that are not part of this story, and unusual spellings of a name we do replace. TypeSafe never receives a date of birth or an account identifier. It does receive the rest of what you typed, and the scene description, which may say what a character looks like.
We hold no transfer document for TypeSafe, and its privacy policy names neither a Data Privacy Framework certification nor Standard Contractual Clauses, so none of the three safeguards above covers the text it receives. We record this as an open gap in our register of processing activities. No voice recording, email address or account ID is sent.
For custom voice cloning we rely on your explicit consent (Article 49(1)(a)), given through the consent box before you record. We have no separate agreement with Fish Audio; its own privacy policy states that it relies on standard data protection clauses adopted by the European Commission.
Ask us which safeguard applies to a specific processor and we will tell you, and send a copy of any transfer document we hold, at hello@bedtime-stories.fun.
We do not sell, rent, or trade your personal information. We may share limited data only in these circumstances:
You can delete your stories or entire account anytime directly from your account settings. When you delete data, it's removed from our live systems within 30 days (encrypted backups can keep a copy for up to about 7 months; see Data Retention). No need to contact us - you're in complete control!
To exercise any of these rights, email hello@bedtime-stories.fun. We may ask for proof of identity to prevent unauthorised disclosure. We respond within 30 days.
We may update this Privacy Policy to reflect changes in our practices, legal requirements, or service features. When we make material changes:
Have privacy questions or concerns? I'm here to help!
Email Me
hello@bedtime-stories.fun
Contact Form
Visit our contact pageRelated: Security Policy | Cookie Policy
This policy is effective as of the date listed above and applies to all users of Bedtime Stories.