Privacy Notice

Adults manage family accounts

The planned Flairy app is designed for parents and caregivers to create and manage stories for shared reading with children. Child profiles are information managed by the adult account holder. Children do not have their own Flairy login or purchasing account.

Information you provide

The planned app would process your account email and authentication information. Family information would include child profile names, age bands, selected character presentations, languages, and optional reading and accessibility preferences. Story requests can include learning goals, real-life context, supporting characters and their names, ages and relationships, and optional photos you choose to provide.

Proposed processing also includes account, family, profile, story and photo identifiers; photo revision and permission records; generated stories and translations; subscription and entitlement information; story-library and reading-progress records; and technical information needed to operate and protect the service.

AI providers and optional photos

The proposed launch app would use OpenAI to create, translate and check story content; fal.ai to generate illustrations and character references; and ElevenLabs to generate scene narration. These services would receive relevant story content and the family information included in a story request.

For photo-based stories, the proposed processing would send selected photos to fal.ai to create character references. Generated images and story information would also be sent to OpenAI for quality and safety checks. Creating a translation would generate a new character reference from the original selected photos. Scene narration would be generated before the story becomes available, including before you press Listen. These transfers require the appropriate implemented permission before release.

Service providers

The proposed launch architecture uses Supabase for adult authentication and family records, Google Cloud for the API and workers, Cloudflare R2 for private media, Vercel for the website, and RevenueCat and Apple for subscription processing. The final notice must describe the services actually enabled for the release and their roles.

If you choose Apple or Google sign-in in the planned app, the selected provider and Supabase would process authentication information. Flairy would use the provider account identifier and sign-in authorization to authenticate your adult account. Apple may supply a private relay email instead of your personal email. Sign-in is separate from story generation.

The proposed Apple account-deletion flow would use stored Apple authorization to revoke the sign-in connection. Some deletions may also require you to remove that connection in your Apple Account settings; follow the app’s guidance. The final notice must confirm the enabled sign-in providers and how deletion works in the release.

Website and launch updates

If you join the website waitlist, your submitted contact details are intended for managing the waitlist and sending the launch or access updates you requested. You can request removal or withdrawal from those messages at contact@flairy.ai. The final notice must confirm the deployed form fields and how withdrawal is handled.

Your choices and requests

Contact contact@flairy.ai to ask about access, correction, deletion, or other rights that apply to your personal information. We may need to verify that a request comes from the authorized account holder before disclosing or changing family data. Deleting an app account and cancelling an Apple subscription are separate actions.

The planned app provides an account-deletion request in Settings, then Account. Removing family access and finishing private-data cleanup are separate stages, so a request being accepted does not mean all cleanup is complete. If the app cannot confirm completion, use contact@flairy.ai for help. Apple sign-in may also require removal in your Apple Account settings; deleting a Flairy account does not cancel an Apple subscription.