Privacy Policy
Lunabee writes illustrated bedtime stories from an idea you type, and reads them aloud. A parent or guardian holds the account; children read and listen inside child profiles that the parent creates and controls. This policy explains, in plain language, what we collect, where it goes, and the choices you have.
1. Information we collect about a parent
- Email address and the display name you choose.
- A securely hashed password (we never store the password itself).
- If you sign in with Google or Apple: the email, name and subject identifier those providers return (scopes: openid, email, profile).
- Sign-in tokens, kept for 7 days on a rolling basis.
- Your app language, theme and story defaults.
- Parental consent decisions and the parental PIN (stored hashed).
2. Information we collect about a child
The only information tied to a child profile is what you, the parent, enter or what the profile creates:
- First name, age band and an avatar colour.
- The stories created in the profile: the idea and structured choices (age band, language, category), the generated text, cover and scene images, and narration audio.
- Reading progress and downloaded-for-offline choices.
We deliberately do not collect a child's surname, date of birth, email, phone number, location, photos, contacts, microphone audio, or any advertising identifier, and we run no behavioural analytics on child profiles.
3. Generative AI: what is sent where
To write, illustrate and narrate a story we send only what each step needs:
- Story text — the idea and structured choices go to a large-language-model provider (OpenAI or Anthropic, through our routing layer) to write the story.
- Images — a generated image prompt (never the child's name or details) goes to an image-generation provider (OpenAI, or SiliconFlow for adult-band stories only).
- Narration — the approved story text goes to a text-to-speech provider (Google or ElevenLabs, with OpenAI as fallback).
These providers act as processors on our behalf under data-processing agreements, and the content is processed to return a result, not to train their models. For child profiles the request is made on the parent's behalf — nothing that identifies the child is passed to a provider — and images and narration run only if you switched them on in parental consent (see section 6). Voice cloning of children is never offered or performed.
4. AI moderation
Every story is screened before your child sees it. Text is checked by safety models that run on our own servers (Detoxify, and a policy layer tuned to the age band; LlamaGuard where enabled), with a final pass over the whole story before it is released. Every generated image is screened on our servers before it is shown; an image that does not pass is not displayed. Moderation results are kept with the story so we can audit them.
5. How we use this information
We use it only to run the service:
- To create, illustrate, narrate and store your stories, and to show them in your library across your devices.
- To enforce our safety policies and to respond to reports you make about content.
- To manage your account, child profiles and parental consent.
We do not use your or your child's data for advertising, we do not run third-party advertising or tracking SDKs, we do not profile children, and we do not sell data to anyone.
6. Children's privacy (COPPA)
The parent is the contracting party; a child does not transact. Child profiles for ages 4–17 are created only by a signed-in parent. Before a child profile can create stories, the parent confirms consent by email (the COPPA "email-plus" method) and chooses what the app may do for that child: use external AI providers, generate images, and produce narrated audio. Images and narration are off by default for children until you turn them on; you can change or revoke consent at any time. Story ideas for children's age bands are kept to the guided flow.
7. Storage and security
Story text, images and audio are stored in our database and object storage; connections use TLS; passwords and PINs are stored hashed. Access to production data is limited to operating the service.
8. How long we keep data
- Account details: kept while the account exists.
- Stories, images and audio: kept until you delete the story, then purged within 30 days.
- Sign-in tokens: 7 days, rolling.
- Content reports and generation audit records: 12 months, for moderation and safety audits.
- Deleted accounts: deactivated immediately; permanently purged after 30 days, keeping only an anonymised audit trail.
9. Your export and deletion rights
You can ask us at any time for a copy of everything stored for your account, or for its deletion. Deletion removes your account, child profiles, consents and preferences; it runs after the 30-day purge window described above. Email privacy@simplerlife.cc from the address on the account. Families in the EU have the full set of GDPR rights, with consent and contract as the lawful basis and no profiling or targeted advertising of children.
10. Changes to this policy
If we make a material change, we will email registered parents before it takes effect and update the date at the top of this page.
11. Contact
For privacy questions email privacy@simplerlife.cc. For general support, email support@simplerlife.cc.