Privacy policy
Last updated October 6, 2026
Petite Tales is made and operated by Bitfuzed (PVT) LTD (“BitFuzed”, “we”). It’s an app for families with young children, so we’ve tried to collect as little as possible and to explain exactly what happens to it. This policy covers the app on iPhone, iPad and Android.
The short version. There are no ads and no analytics, and you don’t need an account: signing in is optional, for grown-ups who want their stories on a new phone. We never ask for, take or upload a photo of your child. Reading library stories sends nothing about your child anywhere. Making a personal story sends the choices you made about your child (first name, age, look, favourite things) to our server and to Google’s Gemini AI to write, paint and narrate it, and the finished story is kept in your family’s backup while you subscribe. You can delete everything, including your account, from the app.
Your family ID
You don’t need to sign up. When the app is first opened it creates a random family ID on your phone. It isn’t linked to your name, email or device by us. The app sends it with every request to our server, so the server can keep your family’s stories and allowances apart from everyone else’s. If you subscribe, the app attaches the family ID to the purchase in Google Play or the App Store, which is how your stories find their way back to you on a new phone.
Optional sign-in
In Settings, behind the grown-ups’ gate, you can sign in with Google, with an email address and password, or on iPhone and iPad with Apple. Signing in lets your family’s stories follow you to a new phone or tablet. It is handled by Firebase Authentication (Google LLC), which keeps a user ID, the email address of a Google or email account, and when the account was made and last used. Passwords are kept by Firebase in a form no one can read back, us included. We ask Apple for no name or email address.
We keep one small record in Cloud Firestore (Google LLC) linking that user ID to your family ID, and nothing else. We don’t send you email, apart from a password-reset link you ask for, and we never use your email address for marketing.
Signing out takes your family’s personal stories off that phone; they stay in your backup and come back when you sign in again. The phone gets a new family ID, and child profiles and portraits stay on it.
What stays on your phone
- Child profiles: first name or nickname, age, whether stories should say he, she or just the name, the look you chose (skin, hair, eyes, glasses, pyjamas), a cuddly companion and its name, and a few things your child loves.
- Painted portraits of each child, and your personal stories (text, pictures and narration).
- Library tales you’ve opened, kept in the phone’s cache so they replay offline.
- Settings such as story language, narrator, the owl’s name, reading progress, which weekly stories you’ve had, the family ID and a copy of your subscription status.
Your device’s own backup may also include some of this, so it returns when you restore a phone or tablet. On Android, if Android backup is turned on, it may include the app’s settings (with the family ID) and child profiles and portraits; that backup is run by Google under your Google account. On iPhone and iPad, an iCloud backup or a backup to a computer may include the app’s settings (with the family ID), child profiles, portraits and the personal stories saved on the device; that backup is run by Apple under your Apple Account, or kept on your computer. Downloaded library tales are left out of both.
Library stories
The library is the same for everyone. When you open a tale, the app downloads its text, pictures and narration from our server. Nothing about your child is sent to do this.
Personal stories and portraits
Personal stories are part of Petite Tales Plus. To make one, the app sends our server (a Cloudflare Worker) the following, together with your family ID:
- your child’s first name, age, and he, she or name-only;
- a sentence describing their look, built from your choices, such as “a 5-year-old child with warm medium skin, curly dark brown hair and brown eyes, dressed in soft lavender pyjamas”;
- the cuddly companion (and its name), and the things they love;
- the story idea (one of ours, or words you type), the optional lesson, the length, language, narrator voice and reading style;
- a random ID for the child’s profile, so stories can be grouped by child;
- for the cover picture, the painted portrait of your child, so the character looks the same in every book. The portrait is itself a painting made from your choices, never a photo.
Painting a portrait (which free families can also do a couple of times) sends just the first name and the look sentence.
Our server passes this story material to Google’s Gemini API (Google LLC), which writes the story, paints the pictures and records the narration. Your family ID, IP address and device details are not sent to Gemini. Google processes the material to produce the result and may keep it for a limited time under its Gemini API terms, for example to detect abuse.
The family backup
Every finished personal story is stored on our server in Cloudflare R2 storage, under your family ID: its title, text, the look description used for the pictures, language, narrator, your child’s first name and profile ID, the cover, the pictures and the narration. This is what lets a story come back after a reinstall or on a new phone. We don’t keep child profiles, ages, favourite things or portraits as records on the server; they only appear there as part of a story’s text or pictures.
Stories are deleted automatically 90 days after your Plus subscription ends. You can delete a single story, or everything, at any time (see below).
The server also keeps small records under your family ID: your subscription status and end date (from Google Play or the App Store), how many personal stories and portraits have been used this month, and your balance of extra stories. Monthly counts expire on their own after the month ends; subscription records expire a few days after the subscription does.
Purchases
Plus and extra stories are sold and billed by Google Play or, on iPhone and iPad, the App Store. We never see your card details, name or email address. Our server checks each purchase with the store it came from: with Google Play using the purchase token the app receives, or with the App Store’s signed transaction, and Apple tells the server when a subscription renews, lapses or is refunded. From this it learns the product, whether it’s active or in a free trial, when it ends, and the family ID attached to it. To stop a purchase being credited twice, a record that it was credited is kept for about 13 months. Plus belongs to the family ID, so every phone and tablet in your family has it, whichever store it was bought in; the server keeps which store that was.
Crash reports
Release versions of the app use Firebase Crashlytics (Google LLC) to report crashes and errors. A report contains technical details: what went wrong in the code, the device model, operating system version (iOS or Android), app version, a Crashlytics installation ID and the time. It never includes your child’s name or profile, your stories or your family ID. Firebase keeps crash reports according to its own retention policy. The app has no switch to turn this off; write to us if you’d like help.
Reporting a story
Stories, pictures and narration are made with AI, so every book has a Report this story button (behind the grown-ups check). A report sends our server which story it is, the page, the language, the reason you picked and anything you type, together with your family ID so we can find a personal story in your backup and review it. Reports are kept for up to 13 months to look into problems and improve our safety filters, and are deleted with everything else when you delete all your data.
What we don’t do
- No analytics: we don’t record which stories you read, for how long, or how you use the app.
- No ads, no advertising ID, and no tracking across other apps or websites.
- No photos, camera, microphone, contacts or location. The app doesn’t ask for any of them.
- No chat, social features or public profiles. Your child can’t contact anyone through the app.
- We don’t sell, rent or share your family’s information with anyone for marketing.
Children’s privacy
Petite Tales is meant to be set up by a parent or guardian and enjoyed with a child. Information about a child comes only from the grown-up who fills in the profile, and it is used only to make that child’s stories. Making a personal story, buying, Settings, reporting or deleting stories and links out of the app are behind a parent gate (tap three numbers written out in words).
We follow the US Children’s Online Privacy Protection Act (COPPA), the EU and UK GDPR rules for children’s data, and the rules of the store you got the app from (Google Play’s Families policy, or Apple’s App Store Review Guidelines). We don’t knowingly collect personal information directly from a child: the app has no chat and no way for a child to share anything publicly, and the optional sign-in is for grown-ups, behind the parent gate. The details that make a personal story are given by the parent or guardian, who asks for the story, and are used only for that. We don’t use them for advertising or profiling, and the app collects no advertising ID, location, contacts or hardware identifiers. If you believe a child has given us information without a parent’s permission, write to us and we’ll delete it.
As a parent or guardian you can:
- use Petite Tales without sharing anything about your child: the free library story and Read together send nothing about them;
- see what we hold: it’s all in the app, with profiles in Settings and personal stories in My Stories (the backup holds copies of those same stories);
- delete it: remove a child in Settings, delete any story, or delete everything with “Delete all our data”;
- stop further collection by not making personal stories or portraits, or by uninstalling the app.
Deleting your data
- One story: in My Stories, press and hold a story and delete it. It’s removed from the phone and from the backup.
- One child: in Settings, open the child and tap Remove. Their profile and portrait are removed from the phone; stories already made are kept until you delete them.
- Everything: Settings → “Delete all our data” deletes every personal story, portrait and child profile from the phone, and every story, extra-story balance, usage count and subscription record for your family on our server. The phone needs a connection; if the server can’t be reached, nothing is deleted and the app tells you.
- Your account: if you signed in, Settings → Your account → Delete account deletes all of the above, the record linking your account to your family, and the account itself. If you signed in with Apple, the app’s access to your Apple Account is revoked too. You may be asked to confirm it’s you first; if you back out, or the server can’t be reached, nothing is deleted.
A few records with no information about your child expire on their own: the link between a purchase and your family ID (a few days after the subscription ends), the record of credited purchases (about 13 months) and short-lived counters that limit repeated requests (two days). Cancelling Plus is done in the store it was bought in: on iPhone and iPad, Settings → your name → Subscriptions; on Android, Google Play → Payments & subscriptions. More ways, including if you’ve already uninstalled the app, are on the delete your data page.
Who processes data for us
- Cloudflare, Inc. runs our server and stores the library and family backups. Cloudflare handles your phone’s IP address to deliver each request; our code doesn’t store it.
- Google LLC: the Gemini API (writing, painting and narrating personal stories), Google Play (purchases on Android), Firebase Crashlytics (crash reports), and Firebase Authentication and Cloud Firestore (the optional sign-in).
- Apple Inc.: the App Store (purchases on iPhone and iPad) and Sign in with Apple, if you choose it.
These providers may process data in countries other than yours, under their own safeguards for international transfers.
Keeping your backup safe
All traffic between the app and our server is encrypted (HTTPS). Your family ID works like a key: the server only returns stories to requests that carry it. It stays on your phone, in your device’s backup (Android backup or iCloud), in the store’s record of your purchase (Google Play or the App Store) and, if you sign in, in your account’s record, and we don’t publish or share it.
This website
This website has no cookies, analytics, ads or tracking scripts. It is served by Firebase Hosting (Google), which handles your IP address to deliver the pages.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete personal data, and to object to how it’s used. Write to us and we’ll help. Unless you signed in, we can’t look a family up by name or email, so the quickest way to delete everything is from the app itself.
Changes
If this policy changes, we’ll update the date above and, for significant changes, say so in the app.
Contact
Bitfuzed (PVT) LTD · contact@bitfuzed.com
