Privacy Policy

Marytale · Last updated 4 August 2026

Marytale is an app of illustrated bedtime stories for children. It is listed in Apple’s Kids Category, and it is built so that a parent can hand the phone to a child without worrying about what happens next.

This policy describes exactly what the app does and does not do with data. It is short because the app collects very little.

What Marytale does not collect

Marytale never asks for and never collects:

• a name, an email address, a phone number or a postal address;
• a date of birth;
• photos, camera or microphone access, contacts, or location;
• the Apple advertising identifier (IDFA). The app contains no tracking permission prompt, because it does not track anyone.

There is no advertising inside Marytale of any kind — no banners, nothing that interrupts a story, and no advertising network in the app. Google Analytics for Firebase is switched off and is not built into the app.

We do advertise Marytale itself on other platforms, and one measurement service tells us whether those advertisements led to installs. It is named below. It runs in the build its maker publishes for children’s apps: the part that reads the advertising identifier is not compiled into Marytale at all, so it cannot read one.

There are no accounts. You do not sign in, and there is nothing to sign in with.

What Marytale does store

• A random identifier. The first time the app runs it generates a random identifier and keeps it in the device keychain. It is not derived from your device, your Apple Account, or anything about you, and it is not shared with anyone. Its only purpose is to keep your reading progress attached to your copy of the app.
• Reading progress, stored against that identifier: how many books and pages have been read, which days reading happened on, and the reading streak. This is what the profile screen shows you.
• Subscription status — whether an active subscription exists, so the app knows which stories to open.
• A push notification token, if you allow notifications. It identifies the device to Apple’s notification service so a message can reach it. Notifications are optional and can be turned off in iOS Settings at any time.
• The three answers given when the app first opens — an age range for the stories (1–2, 3–4, and so on up to 11+, never an exact age and never a date of birth), the themes you picked, and what brought you to the app. They are stored on their own, with no identifier of any kind beside them, so they cannot be linked to you, to your device or to your reading progress. We read them together rather than one by one: they tell us who the app is for and what to write next. The answers unlock nothing and restrict nothing — every story is open to everyone, whatever you choose.
• Settings and saved books, which stay on the device itself.

Corrections you send us

If you notice a mistake in a story — a wrong word, a clumsy translation — you can mark it and type what it should say. The entry sits behind a parental gate, so it is meant for an adult. Sending a correction is entirely optional; the app works exactly the same if you never do.

What reaches us is only what is needed to find and fix the place:

• the fragment you marked and the words you typed in its place;
• a little of the text on either side, so we can locate the fragment in the book;
• which book, which page and which language, and the version of the app.

Nothing else travels with it. There is no name, no email address, no contact field, and no identifier at all — not even the random identifier that carries your reading progress. A correction therefore cannot be linked to you or to your device, and it is not shown to any other reader; only we see it. This also means there is nobody for us to write back to, so a correction never receives a reply.

Because a correction carries no identifier, we have no way to find the ones that came from you, and so a single correction cannot be withdrawn or retrieved on request. A correction is kept while it waits to be read, and after it has been dealt with, so that a wrong edit can be undone; we clear them out once the queue no longer needs them. If a correction ever contains something personal — a child typing their own name into the box, for instance — we delete it on sight and it is never used for anything.

Who else is involved

• Apple handles every payment. We never see or receive card details. Apple also operates SKAdNetwork, a measurement system that tells us, in aggregate and without identifying anyone, whether an advertising campaign led to installs.
• Google Firebase stores the stories and illustrations and delivers push notifications. Firebase’s analytics product is disabled in this app.
• Adapty manages subscription status. It runs in its children’s mode: the advertising-identifier component is compiled out of the app entirely, and IP address collection is switched off in code.
• AppsFlyer tells us whether an advertisement we placed on another platform led to an install, and whether that person later started a free trial or subscribed. It runs in the strict build its maker publishes for children’s apps: the component that reads the advertising identifier is not in Marytale at all. What it receives is which step was reached — the end of the introduction, the first story read to the end, the moment a locked story is tapped — together with the device’s network address and an identifier that belongs to this app on this device only and cannot follow anyone into another app. It never receives a name, an age, an email, or anything a child types.

None of these companies receive a child’s name, age, email address, photograph or anything a child writes, because Marytale does not collect those. What they do receive is described above, item by item, so you can judge it yourself rather than take a promise.

Children

Marytale is made for children and follows Apple’s Kids Category rules. It contains no third-party advertising and no third-party analytics that transmit device or user identifiers. Purchases, settings and every link that leads outside the app sit behind a parental gate — a step a young child cannot complete on their own.

We do not knowingly collect personal information from children, in line with the US Children’s Online Privacy Protection Act (COPPA) and Article 8 of the EU General Data Protection Regulation. If you believe a child has somehow provided personal information to us, write to us and we will delete it.

How long data is kept, and how to delete it

Reading progress is kept while the app is in use. Deleting the app removes everything stored on the device, including the random identifier — after which the reading progress held on our side can no longer be linked to anyone or retrieved.

To have the stored reading progress erased outright, write to support@pixagen.io and we will delete it. You may also ask what is stored, ask for a copy, or object to its storage.

Changes

If this policy changes, the new version appears on this page with a new date at the top.

Contact

support@pixagen.io