Privacy Policy for Kalimo

Last updated: 14 October 2026 · Version: 1.12 · Deutsche Fassung

Kalimo is an iPhone app that parents and other grown-ups use to create illustrated bedtime stories for their children and read them aloud. The text and pictures are made with artificial intelligence (AI). This policy covers the app and the website kalimostories.com.


The short version

  • Kalimo is made for grown-ups. A grown-ups' gate protects the settings. Children look at the books and tap the pictures; they don't enter any data themselves.
  • An account without a password, signing in is optional. The app creates an anonymous account the first time it starts. You can secure it with Apple, Google or an email address; then more phones can join, and nothing is lost on a new phone. We never need your phone number or address.
  • The AI never gets your children's names. The AI services only see placeholders such as "{{HERO_1}}"; your iPhone fills in the names. The names are kept in your family library on our server, so your books look the same on all your devices.
  • The AI does get your children's age, looks, favourite things and fears. That is how the stories and pictures are made. The providers are Google, Anthropic and OpenAI, reached through Vercel. Before the first story, the app asks for your explicit permission.
  • The photo is optional, and we never store it. Google Gemini looks at it once and suggests hair, skin and eye colour and a head covering from Kalimo's choices.
  • No ads, no tracking, no third-party analytics tools. Our own usage statistics, without names or content, are only sent if you agree. We don't sell data.
  • You can delete everything. In the grown-ups' area, "Delete account and all data" removes your data from the iPhone and from our server.

1. Who is responsible

Malte Schiebelmann
Salzmannweg 12
14469 Potsdam, Germany
Email: [email protected]

More details are in our legal notice (Impressum).

2. Who Kalimo is for

Kalimo is for parents and other adults with parental responsibility or care duties ("you"). The stories are for children aged about 3 to 10. Only grown-ups set up profiles, enter data, start stories and change settings, behind a grown-ups' gate (a sum or Face ID). Children only use the app to look at the books and be read to.

The data about your child comes from you (Art. 14 GDPR). Please only enter data about children you have parental responsibility for, or whose parents have agreed.

3. What we process and why

3.1 Your account, signing in and your phones

When the app first starts, it signs in to our server anonymously and gets a random account ID. The sign-in details are kept in your iPhone's keychain. The account keeps your books and profiles safe and the same on all your devices.

Securing the account (optional). In the grown-ups' area you can add a login. The account stays the same; no data is moved. An account can have several logins, for example one for each person who reads aloud.

  • With Apple (Sign in with Apple): Apple gives us an identifier and an email address, or, if you choose, an anonymous relay address from Apple.
  • With Google: you sign in on a Google page; we never see your password. We receive an identifier and your email address. The name and profile picture Google sends along are stored by the sign-in service; we don't use them.
  • With email: we send a link and a 6-digit code to your address. It lasts 15 minutes.

We keep the identifier, the email address and which logins your account has with the account. We use the email address only for signing in and, if you write to us, to reply; never for advertising.

Welcome back. Once your account is secured, the app leaves a small note in your own iCloud Keychain: the way you sign in (Apple, Google or email), that login's address (none for a hidden Apple address) and the date. A new iPhone with the same Apple ID then offers to sign in again with one tap; it shows the address only shortened ("anna.m•••"). The note holds no credentials and no account ID, stays with Apple in your keychain and never reaches us. It is deleted when you sign out on the iPhone or delete your account. If a new iPhone finds no note, the app asks Apple once on the first start whether this Apple ID signed in to Kalimo before; Apple only answers if so, and only after you confirm.

More phones. A secured account can take in more phones: one phone shows a code (as a QR code and to type in), the other scans it. We store the code only as a check value (a hash); it lasts 5 minutes and works once. We briefly count attempts to redeem a code, to prevent guessing. For each phone of the account we store its device ID, its model (for example "iPhone 13"), when it joined, when it was last seen, and its sign-in session, so you can remove it on its own in the grown-ups' area. The reading state notes which phone last opened a book (its model), so the other phones can show "Read on the iPhone 13 yesterday". If the new phone already had its own books or children, you can take them along into the shared account.

Inviting. If the other phone isn't nearby, you can send a link (for example by WhatsApp or text message). We store the link only as a check value (a hash); it lasts 7 days and works once, and you can take it back before then. Whoever opens it adds their name ("Grandma") and asks to join with it. We store the request with that name, the model of the asking phone and whether it wants to bring its own books, until you approve or decline it in the grown-ups' area. Only after your yes does the phone join the account; the name then appears next to it in the list of your phones. We briefly count attempts to redeem an invitation. Your phones get a notification when someone asks, and the asking phone gets one when you have said yes; neither contains a name.

  • Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR).

3.2 Your children's profiles and your family library

You can set up a profile for each child. It contains:

  • first name, age and gender or pronouns (he, she, neither)
  • language and how exciting the stories may be
  • looks (hair colour and style, skin tone, eye colour, glasses, freckles, clothes)
  • favourite things, and things that must not appear in stories ("fears")
  • siblings, friends, pets and cuddly toys, each with a name, kind, short description and pronouns

Your family library also holds:

  • characters you keep from a story
  • the books themselves: text and pictures
  • which names appear in which book
  • favourites and bookmarks (where you stopped reading, and which path you chose)

This data is kept on your iPhone and in your family library on our server (see section 5). It is linked to your account ID, and only you can access it.

  • Purpose: to write personal stories, and to keep your library safe and the same on all your devices.
  • Legal basis: the consent you give on your child's behalf (Art. 6(1)(a) GDPR), and performance of our contract with you (Art. 6(1)(b) GDPR).
  • Skin tone: it may indirectly suggest ethnic origin, so we only store and process it if you give it, and only with your explicit consent (Art. 9(2)(a) GDPR).
  • Without this data Kalimo cannot write personal stories. Most fields are optional.

Please don't enter health information. Under "fears", write things like "spiders" or "thunderstorms", not diagnoses or medical details. Please also don't write other people's names in free-text fields (ideas, wishes, feedback), such as "Grandma Helga": we can only replace the names you set up in the profiles.

3.3 Making stories with AI

When you start a story, our server puts together a request and replaces your children's and their companions' names with placeholders. The request contains:

  • the children's age, pronouns and looks
  • favourite things, things that must not appear, and the companions' descriptions
  • the topic or your own idea, mood, time of day, length and language
  • any characters you kept

AI models from these providers work on the request:

Task Model Provider
Writing the story, checking your own ideas are suitable for children, revising pages Gemini Google
Proofreading the story Claude Anthropic
Painting the pictures GPT Image OpenAI
Checking pictures for mistakes Gemini Google

All requests go through Vercel's AI Gateway, which passes them to the providers. We keep the finished text and pictures in your family library, and your iPhone fills in the names when it shows them.

Cut-outs for the magic. So that things in a picture can move when tapped, our server sends each finished picture to Runpod, which cuts it into layers on its servers in the EU. Runpod receives only the picture and where the things in it are, never a name or a text, and keeps the result for at most 30 minutes until our server has fetched it. Legal basis: performance of our contract (Art. 6(1)(b) GDPR).

  • Legal bases: your explicit consent, which the app asks for before the first story (Art. 6(1)(a) and Art. 9(2)(a) GDPR), and performance of our contract (Art. 6(1)(b) GDPR).
  • Withdrawing consent: you can withdraw it at any time in the grown-ups' area. No new stories are made after that; existing books stay readable until you delete them.

No training on your data. Vercel does not use the requests for training and does not keep them once answered. On top of that, we tell the gateway with every request to route it only to providers that do not use the data to train their models. How long the providers briefly keep requests, for example to detect misuse, depends on their terms.

Automated decisions: when you type your own story idea, an AI model checks it before the story is made. It turns down unsuitable topics, and you can then try another idea. This is not a decision with legal effect under Art. 22 GDPR.

AI-generated content: all stories, pictures and videos in Kalimo are made with AI.

3.4 A photo for your child's looks (optional)

When you set up a profile, you can take or choose a photo of your child (the "magic mirror") so that Kalimo can suggest their looks. This is what happens:

  1. The app makes the photo small (at most 1024 pixels) and removes metadata such as where it was taken.
  2. Our server sends the photo once, through Vercel, to Google Gemini. Gemini is only asked to name hair colour and style, skin tone, eye colour, glasses, freckles and a head covering from Kalimo's choices.
  3. You see the suggestions and can change them. Only what you accept is kept, as text (for example "blond").

We store the photo neither on our server nor in the app, and we write it into no logs. The request asks for it not to be kept and not to be used for training (see section 4). How long Google technically holds such a request depends on its terms. The photo is not used for facial recognition or identification, and it is not used to make the story's pictures.

  • Legal basis: your explicit consent (Art. 6(1)(a) and Art. 9(2)(a) GDPR). You give it by tapping "Snap!" or "Choose a photo" after the notice in the app.
  • Without a photo: you can simply pick the looks yourself ("I'll dress myself").

3.5 Camera, photos and Face ID

The app asks for camera access only for the photo in section 3.4. If you choose a photo from your library, you pick it in the iOS photo picker after the grown-ups' lock, and the app only sees the one photo you choose.

Microphone. On the "New story" screen you can say your own story idea instead of typing it. The app asks for the microphone and speech recognition only when you tap the microphone button for the first time, and listens only while it is on. Your iPhone turns what was said into text itself (Apple's on-device speech recognition); the sound never leaves the iPhone and is not stored. Before the text leaves the phone, the app replaces your children's and companions' names with placeholders. Our server then has the text tidied once, through Vercel, by Google Gemini (fillers and repetitions removed), and the app puts the names back. The tidied idea is handled like a typed idea (section 3.3); we store neither the spoken text nor the tidied idea for this step, and we write them into no logs. Legal basis: performance of our contract (Art. 6(1)(b) GDPR); you can always type instead.

If you wish, the app uses Face ID for the grown-ups' gate. iOS checks your face on your device; we receive no face data.

3.6 Notifications

If you allow notifications, Kalimo lets you know, for example, when the first pages of a book are ready. For this we store:

  • a random device ID and Apple's push token
  • language, time zone and app version
  • your notification settings

Apple delivers the notifications (Apple Push Notification service). They contain names only as placeholders; your iPhone fills in the names when the notification arrives.

  • Legal basis: performance of our contract (Art. 6(1)(b) GDPR) and § 25(2) no. 2 TDDDG.
  • Turning them off: at any time, in the app or in iOS Settings.
  • Promotional notifications: we only send them if you have agreed separately.

3.7 Reporting a page

The flag in a book lets you report a page that doesn't look right. We then store:

  • the reasons you chose and your comment (the app first replaces known names with placeholders)
  • language and app version
  • a copy of the page (text with placeholders, the picture's description, a reference to the picture)

We read reports ourselves, together with the records of that book's AI requests (section 3.9), and turn them into test cases so the mistake doesn't happen again. We also receive reports by email through the service Resend.

  • Legal basis: our legitimate interest in safe, child-appropriate and correct stories (Art. 6(1)(f) GDPR).

3.8 Feedback and ratings

After the first book, Kalimo asks how you like it. We store your answer, reasons and comment, together with language, app version, what prompted the question and how many books have been read. We store an email address only if you give one so that we can reply. We also receive feedback by email through Resend.

If you choose "Great", the app shows Apple's rating dialog. Apple, not us, processes what you enter there.

  • Legal bases: our legitimate interest in improving Kalimo (Art. 6(1)(f) GDPR). For the email address, your consent (Art. 6(1)(a) GDPR).

3.9 Records of AI requests, and costs

For each book we record the requests to the AI models and their answers: instructions, text, model, timing and errors. Pictures appear in the records only as a storage reference. The records contain no names (placeholders only), but they do contain the other details from section 3.3. For each request we also store the model, cost and duration, and for each account the costs per day, so that a daily limit applies.

  • Purpose: finding mistakes, improving the stories, and preventing misuse and unexpected costs.
  • Legal basis: our legitimate interest (Art. 6(1)(f) GDPR).

3.10 Technical logs

When the app or the website contacts our servers, our service providers process technically necessary access data: IP address, time, requested address, status code and technical details of the device. They do so to run and secure their services, and delete the data after a short time under their own terms.

  • Legal basis: our legitimate interest in secure, reliable operation (Art. 6(1)(f) GDPR).

Protection against misuse (App Attest and DeviceCheck). Every picture and text of a story costs us money. So that nobody can make books with scripts or many accounts, we use Apple's services to check that a request comes from the real Kalimo app on a real iPhone:

  • App Attest: the app makes a key once in your iPhone's security chip, and Apple confirms that it belongs to an unmodified Kalimo app. We store the public part of this key, a counter and Apple's confirmation (receipt) with your account. The app signs expensive requests with it (a story, the photo for the looks, redrawing or rewriting a page). Every few days Apple's confirmation tells us how many such keys this device made for Kalimo in the past 30 days; many of them suggest misuse, and the device then gets a smaller daily budget.
  • DeviceCheck: with the first book we give away, our server sets a mark for your iPhone at Apple. Apple keeps two yes/no values per device for us, which survive reinstalling the app. For this the app sends a device token from Apple once.
  • What Apple sees: the device, our app and the two yes/no values; no names, no stories, no content.
  • Results of the checks (valid, invalid and why, app version) are noted with no link to you, to see whether the checks work.
  • Legal basis: legitimate interest in protection against misuse and an affordable service (Art. 6(1)(f) GDPR) and Section 25(2) no. 2 TDDDG.

3.11 Storage on your iPhone

The app stores on your device:

  • your library, with its pictures
  • the sign-in details (in the keychain)
  • settings, such as the night filter or the grown-ups' gate
  • the names for notifications (in an area only Kalimo can reach)
  • a technical reading log without names or story text, which stays on the device
  • if you agreed to the usage statistics: your answer and events not yet sent (section 3.12)

This is strictly necessary for the service you asked for (§ 25(2) no. 2 TDDDG); the usage statistics rely on your consent (section 3.12).

If you share a book as a PDF, the PDF contains the names. You decide where it goes.

3.12 Usage statistics (optional)

If you agree, the app sends us usage events. They show us where Kalimo gets in the way: which setup steps are hard, how long a story takes, whether books are read to the end, which errors happen. Without your agreement, the app sends nothing. The app asks in the getting-to-know-you book, right below the consent to the AI services: the switch "Help improve Kalimo" is on there to begin with, and one tap turns it off. Confirming the page with the switch on means you agree. Families who haven't been asked yet are asked in the grown-ups' area.

  • Which events: opening the app, getting to know your child and setting up, the grown-ups' gate, story requests and how long they take, opening, turning and finishing books, tap surprises, reports, PDF export, the wardrobe, the rating question, notifications, deletions and errors. An event carries only numbers, yes/no values and fixed identifiers from the app (such as a book's or a topic's ID).
  • About your child, only: the age group (3–4, 5–6, 7–8 or 9–10 years), never the exact age, and how many children you have added.
  • Never included: names, story text, your own ideas, looks, favourite things, fears, pictures, photos, or the advertising identifier.
  • Also included: your anonymous account ID, the exact time of each event with your iPhone's time zone (such as "Europe/Berlin"), the country of your App Store account (such as "DEU"; no more precise location), app and iOS version, language, and the device class (such as "iPhone15"). Also a few of the iPhone's settings and states: whether notifications are allowed, the text size (in four steps), whether VoiceOver, Reduce Motion or Low Power Mode is on, whether storage is running low, when a story is requested the kind of connection (Wi-Fi, mobile, offline), and when a book is opened where the sound goes (speaker, headphones, Bluetooth, AirPlay, car).
  • Where: in our database at Supabase (section 4). We analyse it ourselves, also with the help of Claude (Anthropic), which only has read access to these statistics for this. The data goes to no analytics or advertising service.
  • How long: 13 months, then we delete it automatically. If you delete your account, it goes too. All that remains is a count with no link to you: the date, the number of your books, and the days since installing.
  • Withdrawal: any time in the grown-ups' area under "Data & privacy", switch "Help improve Kalimo". Once it is off, the app sends nothing more and discards events not yet sent.
  • Legal basis: your consent (Art. 6(1)(a) GDPR; for storing and reading on your iPhone, § 25(1) TDDDG).

3.13 No ads, no tracking

Kalimo has no ads and no third-party analytics, tracking or advertising SDKs, and it does not use the advertising identifier. The optional usage statistics in section 3.12 are our own and are not combined with data from other providers. We don't sell personal data or use it for advertising.

3.14 Purchases

Kalimo offers the subscriptions "Kalimo Plus" and "Kalimo Familie" and packs of more stories. Buying, paying and billing happen only through your Apple Account in the App Store; we never see payment details such as your card. Cancelling and refunds go through Apple.

So that a purchase counts for your family, on every phone of the account and after a new phone too, we use the service RevenueCat. The app reports purchases there with your account ID, a random number without a name. RevenueCat checks the receipt with Apple and receives the purchase data for this (product, time, term, renewal, the App Store's country and currency, the transaction's identifier) and technical details of the device (model, iOS and app version, language, IP address). RevenueCat tells our server which subscription is active; we store the subscription, product, end of term, whether it renews, payment problems and the packs bought. From this we work out how many new stories your family has made in the last 7 days and how many are still free. Without a purchase, RevenueCat only receives the account ID and the technical details when you open the subscription page.

If we give a family access for free (for example for testing), we note who got it, until when and why.

Inviting families: every family has its own link to recommend Kalimo. When another family comes to Kalimo through that link, we store that the account came through it (both account IDs, the time) and, for the check, its first own book, the phone it was made on (device ID, App Attest key) and whether this iPhone has had a free story before (Apple DeviceCheck). With this we check that it really is a new family on another iPhone, and give both families a story. The inviting family only sees numbers (how many families used the link), never who it was; the link itself says nothing about your children. The legal basis is performing the contract (Art. 6(1)(b) GDPR) and our legitimate interest in preventing abuse of the given stories (Art. 6(1)(f) GDPR).

The legal basis is performing the contract (Art. 6(1)(b) GDPR). RevenueCat receives no data about children.

3.15 Website

Cloudflare (Cloudflare Pages) hosts our website kalimostories.com. Visiting it only produces the technical logs in section 3.10. On the start page, a small program at Cloudflare checks your browser's language setting to show the page in German or English; it stores nothing. The website sets no cookies and uses no analytics or tracking services.

Cloudflare (Email Routing) forwards emails to [email protected] to our mailbox. We use your message and email address only to reply to you (Art. 6(1)(b) or (f) GDPR) and delete them once your request is settled.

4. Recipients and processors

We only share data with service providers that process it on our behalf under contracts according to Art. 28 GDPR, and with Apple to deliver notifications.

Recipient Purpose Data Location
Supabase, Inc. Server, database, storage, sign-in all data in section 3; the photo from 3.4 only passes through, without being stored servers in Ireland (Dublin), EU; company in the USA
Vercel Inc. AI Gateway (passing requests to the AI providers) requests and answers from 3.3, technical logs USA
Cloudflare, Inc. Website hosting, DNS, forwarding emails to [email protected] the website's technical logs, emails to us USA
Google (Gemini) Text, checking ideas and pictures, looks from the photo requests from 3.3, pictures, the photo from 3.4 (once), a spoken idea as text without names (3.5) USA
Anthropic PBC (Claude) Proofreading stories; help analysing the usage statistics story plan and chapter drafts (with placeholders); usage events from 3.12 USA
OpenAI (GPT Image) Pictures picture descriptions with looks, reference pictures USA
Runpod, Inc. Cutting the pictures into layers for the tap effects (section 3.3) the finished pictures and the position of the things in them servers in the EU; company in the USA
Apple Inc. / Apple Distribution International Ltd. Delivering notifications, rating dialog, App Store, signing in with Apple (only if you choose it), protection against misuse (App Attest, DeviceCheck) push token, notification text (with placeholders); when signing in, an identifier and an email address; Apple's confirmation of the app's key and the DeviceCheck device token Ireland / USA
Google LLC / Google Ireland Ltd. Signing in with Google (only if you choose it) identifier, email address, and possibly name and profile picture Ireland / USA
RevenueCat, Inc. Checking subscriptions and purchases and linking them to the account (section 3.14) account ID, purchase data and Apple's receipts, technical details of the device USA
Resend, Inc. Email for reports and feedback; sign-in emails with a link and a code; the warning before an unused account is deleted the report or feedback, and your email address if given; the sign-in address USA

We reach the AI providers through Vercel. Vercel engages them; we have no contract of our own with them.

We only disclose data to authorities where the law requires us to (Art. 6(1)(c) GDPR).

5. Transfers outside the EU

Some recipients are based in the USA or process data there. For the USA, the European Commission's adequacy decision (the EU-U.S. Data Privacy Framework) applies to recipients certified under it. Where a recipient is not certified, we use the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR). You can ask for a copy of the safeguards at [email protected].

6. How long we keep data

Data How long
Profiles, characters, books, bookmarks, account ID until you delete your account, or after 24 months in which Kalimo was opened on none of your phones. Before, we warn you twice, 30 and 7 days ahead: by email if the account has an address (a login with email, Apple or Google), otherwise by a notification if your phone allows them; opening Kalimo once keeps everything. An account we can't reach either way goes without a warning. An anonymous account an iPhone leaves behind, because it signs in to another account without taking it along, is deleted a few minutes later
Logins (identifier, email address) until you remove the login or delete your account
The list of your phones (device ID, model, times, session) until you remove the phone, sign out on it, or delete your account
Codes for more phones (only as a check value) and counted attempts one day
App Attest keys (public part, counter, Apple's confirmation) and which accounts used them until you delete your account
One-time challenges for App Attest (only as a check value) one day
Results of the checks (no link to you) 90 days
Invitations (only as a check value) and their requests (name, phone model) 30 days after the invitation runs out, or until you delete your account; afterwards the name stays only with the phone you took in
A single book or profile that you delete removed from your library and your devices straight away. We delete the book's request, pictures and records from the server within 48 hours. If you reported the book, this happens once we have dealt with the report
The photo from section 3.4 not stored by us; sent once to Google Gemini (section 3.4)
Records of AI requests 180 days; for reported books, as long as the report is kept
Cost records until you delete your account; for deleted books, without a link to the book
Invite link, which link an account came through and the check details, stories given until one of the two families deletes its account
Subscription, packs bought and access given for free (with us and with RevenueCat) until you delete your account; we then delete the customer at RevenueCat too. Please cancel a running subscription in the App Store first; Apple keeps its receipts by its own rules
Reports and feedback (including an email address) 12 months, or until you delete your account; a test case made from a report goes with it
Usage statistics (section 3.12) 13 months, or until you delete your account. After that only a count with no link to you remains (date, number of books, days since installing)
Push token and device details until you turn off notifications, delete the app (Apple then reports the token as invalid) or delete your account
Service providers' technical logs according to their periods (section 3.10)

Legal retention obligations remain unaffected.

Deleting your account: in the grown-ups' area, "Delete account and all data" immediately deletes, for every phone of the account:

  • your account with all its logins and the list of your phones; the other phones are signed out afterwards
  • all profiles, characters, books and pictures
  • the records, reports, feedback, usage events and device entries on our server
  • subscription and purchase data with us and with RevenueCat (cancel a running subscription in the App Store)
  • all data on that iPhone

7. Your rights

You have the right to:

  • access your stored data (Art. 15 GDPR)
  • rectification of incorrect data (Art. 16 GDPR). You can change most details directly in the app
  • erasure (Art. 17 GDPR), directly in the app (see section 6)
  • restriction of processing (Art. 18 GDPR)
  • data portability (Art. 20 GDPR)
  • withdraw consent with effect for the future (Art. 7(3) GDPR), in the grown-ups' area or by email
  • complain to a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is: the Brandenburg Commissioner for Data Protection and Access to Information (LDA), Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany, www.lda.brandenburg.de

Right to object (Art. 21 GDPR): where we process data on the basis of legitimate interests (sections 3.7 to 3.10), you can object at any time on grounds relating to your particular situation.

You can also exercise these rights on your child's behalf. Write to [email protected]. If your account is secured, the email address of your login is enough. If it is anonymous, please include the account ID shown in the grown-ups' area under "About Kalimo", so that we can find your data.

8. Security

Connections between the app, the website, our server and our service providers are encrypted (TLS). Your data can only be accessed with your account. Pictures are delivered through short-lived signed links that expire after one hour. Sign-in details are kept in your iPhone's keychain. Only we, as the operator, have access to the server.

9. For users in the USA (COPPA)

Kalimo is directed at parents. We do not collect data directly from children: grown-ups set up profiles behind the grown-ups' gate, and we ask for a parent's permission before the first story. Sections 3 and 4 say which data we process, why, and who receives it; section 6 says how long we keep it.

Parents can at any time:

  • review, change or delete their child's data, in the app or by email
  • refuse further collection by withdrawing their consent

We do not disclose the data to third parties other than the service providers that run the service (section 4). They process it only on our behalf, and the AI services do not use it for training (section 3.3).

Data retention policy for children's information

We collect children's personal information only for the purposes below and keep it only as long as that purpose needs it, never indefinitely. The data comes from a parent, never from the child.

Information Why we collect it Why we keep it When we delete it
The child's profile: first name, age, pronouns, language, how exciting stories may be, looks, favourite things, fears, and the people, pets and toys around the child (section 3.2) to write stories that fit the child and leave out what the child fears every new story needs it, and it keeps the library the same on all the family's phones when you delete the profile (straight away on your devices, on our server within 48 hours) or your account, or after 24 months without use (section 6)
Books: text with placeholders, pictures, which names appear in which book, bookmarks (section 3.2) to read the stories again, also offline they are the family's library when you delete the book (on our server within 48 hours; for a reported book, once we have dealt with the report) or your account, or after 24 months without use
The photo for the child's looks (section 3.4) to describe hair, skin and eye colour once not kept never stored: sent once to Google Gemini, which keeps it neither
Ideas you type or say for a story (section 3.3) to write the story you asked for as part of that book's request together with the book
Records of AI requests, with the profile details but no names (section 3.9) to find and fix mistakes in a story to look into a problem or a report after 180 days; for a reported book, as long as the report is kept (at most 12 months)
Reports of a page, with a copy of the page (section 3.7) to keep the stories safe and child-appropriate to fix the cause and test that it stays fixed after 12 months, or when you delete your account
Usage statistics, if you allow them (section 3.12) to see where Kalimo gets in the way to compare over a year after 13 months, or when you delete your account

You can delete any of this at any time in the app (section 6), or ask us to by writing to [email protected].

Information security

We keep a written information security program for children's information. It sets out who may access the data (only we, as the operator), how it is protected (encryption in transit, access only with the family's account, short-lived links to pictures, no names sent to AI services), which service providers process it and how we check them, and how data is deleted. We review it at least once a year and whenever Kalimo changes in a way that affects children's data.

10. Changes to this policy

We update this policy when Kalimo, our service providers or the law change. The current version always applies; the date at the top shows when it was last updated. You can find it in the grown-ups' area of the app and at https://kalimostories.com/en/privacy. If we want to use your data for new purposes, or anything else significant changes, we will tell you in the app beforehand. If a change needs your consent, we will ask you first.

This policy is available in German and English. If the two differ, the German version prevails.