Privacy policy

This document was last updated on September 30, 2026

This policy («Policy») describes what the Aldiko mobile application («Application», «Service») does with data: what it keeps on the device, what it sends over the network, who receives it and why. It is a legally binding agreement between you («you», «your», the parent or legal guardian who installed the Application) and its developer («we», «us», «our»). By installing and using the Application you acknowledge that you have read and agree to this Policy.

It is written from how the Application actually works rather than from a template: where it collects something, the section below says what exactly, and where it collects nothing, it says that too.

Table of contents

• What stays on the device
• What leaves the device
• Purchases
• Privacy of children
• Use and processing of collected information
• Disclosure of information
• International transfer of information
• Retention of information
• What the Application does not do
• Social media features and links to other resources
• Information security
• Data breach
• How to stop the collection and request deletion
• Changes and amendments
• Acceptance of this policy
• Contacting us

What stays on the device

The Application saves the following into the device’s own storage:

• the chosen language;
• the child’s age band — «under three» or «older», which sets how hard the tasks are;
• the child’s name, if an adult entered one — the Application greets them by name;
• the adult’s answers to the questions asked at first launch: what they expect from the Application, how much of the language the child already knows, how many minutes a day are allowed;
• lessons finished, stars collected, words learned and the costume chosen;
• sound and music settings.

The name, the age, the adult’s answers, the words learned and the costume chosen do not leave the device. They are not sent to us, not copied into a cloud and not synchronised between devices. Delete the Application and they go with it, beyond recovery — by us as well.

One line of that list is half an exception, and we say so plainly: about a finished lesson the Application does report to us that it was finished and for how many stars. Without the name, without the age, without anything else — which lesson, and how many stars. Why that is needed, and what the whole message looks like, is in the next section.

What leaves the device

Three things, and each is named separately below.

New lessons, pictures and voice

Such a request carries only the content edition number and the Application version — that is, facts about the Application itself rather than about whoever is using it. It carries no installation number, no name, no age and no progress.

Steps on the way to payment

The Application counts where an adult leaves the road to a subscription, because there is otherwise no way to learn anything about it: launch, choice of language, the end of the introductory film, the offer being shown, the parental lock, the questions at first launch, the checkout screen, a purchase started, a purchase paid for and a purchase that failed, a lesson opened and a lesson finished. Fourteen steps, and deliberately not one more.

A message about a step has four fields: a random installation number, the time by the device’s own clock, the name of the step, and a few figures belonging to it — a lesson identifier and a star count, a plan name, the word «cancelled» or «failed». There is no name in these messages, no age, no device model and no chosen language: the Application does not put them there, and the server accepts nothing but those four fields.

The installation number is sixteen random bytes the Application invents for itself at first launch. It is tied to nothing — not to the subscription, not to the children’s profiles inside the Application — and neither a child nor a device can be identified from it. It lives until the Application is deleted: a reinstall is given a new number, and the two cannot be connected.

Crash reports

If the Application closes abnormally or runs into an error, a report about it goes to Firebase Crashlytics, a Google service. The report contains the error text and the place in the code, the device model and the operating system version, and the last fifty lines of the Application’s own technical log — the one it writes about itself (whether a lesson loaded, whether the store answered). The Application does not set a Crashlytics user identifier: a crash is attached to an installation, not to a child. Development builds send no reports at all.

Who receives it

The funnel steps are received by our own cloud function in our own project, which stores them in our own database and forwards them from there to Amplitude, the service in which we look at that funnel. Crash reports go to Firebase Crashlytics (Google). Those are the two recipients, and there are no others.

An important consequence of the arrangement we chose: there is not a single third-party analytics SDK on the device. The Application talks only to our server — neither Amplitude nor anyone else has code inside the Application or receives anything from the device.

Like any server on the internet, ours sees the IP address of an incoming connection and writes it into a technical log. We do not connect those records to any child and do not use them for anything other than diagnosing failures.

Purchases

A subscription is taken out through the App Store or Google Play. We never see a card number, a payer’s name or an address — that data stays with Apple and Google.

To know whether a subscription is active, the Application uses RevenueCat. It assigns the installation an anonymous identifier — a random string tied to no name, no email address and no account. By that identifier the service answers the Application one single question: is the subscription paid for or not.

About the purchase itself we learn exactly what is listed above: that it started, that it ended in payment or did not, and which plan was chosen. No payment details and no receipt are part of that.

Privacy of children

Aldiko is made for preschool children, and that decides everything else. The Application asks a child for no personal information whatsoever: it has no registration, no sign-in, no chat, no way to publish or send anything, and no correspondence with other people.

The child’s name, if an adult chooses to enter one, is the only field in the entire Application into which anything can be typed. It stays on the device. Entering it is not required: without a name the Application works in full.

The payment screen sits behind a parental lock — an arithmetic problem a preschooler will not solve.

Everything the Application reports about itself is addressed by the random installation number and contains no name, no age and nothing else by which a child could be identified. The Application does not collect the device advertising identifier at all, and it does not touch persistent identifiers such as a serial number, IMEI or MAC address in a single line of code.

We are the party that decides what is collected and why, and the collection is limited to what is described in this Policy. If you are a parent or legal guardian and you believe that more than that has reached us, write to us at the address at the bottom of this page and we will look into it and delete what should not be there.

Use and processing of collected information

We collect and use the information described above for these purposes and no others:

• Running and operating the Application — delivering lessons, pictures and voice to the device.
• Understanding where an adult leaves the road to a subscription, so that the road can be made shorter and clearer rather than louder.
• Finding and fixing failures — crashes and errors, with enough context to reproduce them.

We do not build advertising profiles, we do not sell data, and we do not use it to make decisions about any individual. The legal bases we rely on are our legitimate interest in operating and repairing the Application, and the performance of the agreement under which the Application and the subscription are provided to you. Where the law of your country requires consent for such collection, installing and using the Application after reading this Policy is how that consent is given, and deleting the Application is how it is withdrawn — see below.

Disclosure of information

We share information only with the service providers the Application cannot work without, and only with the part each of them needs:

• Amplitude — the fourteen funnel steps, forwarded from our server, addressed by the installation number.
• Google (Firebase Crashlytics, Google Cloud) — crash reports, and the hosting of our own functions and database.
• RevenueCat — the anonymous purchase identifier and the answer whether the subscription is active.
• Apple and Google — as the operators of the stores through which the subscription is sold; what they collect is governed by their own policies, not by ours.

These providers are not authorised to use the information for their own purposes, including their own marketing. We do not sell or rent data to anyone, and we share nothing with advertising networks. We may disclose information where the law requires it of us, and we will say so on this page unless we are forbidden to.

International transfer of information

Our functions and our database run in Google Cloud in the United States, and Amplitude processes the funnel steps on its own infrastructure. The data described in this Policy is therefore stored and processed outside Kazakhstan. Nothing in it identifies a child, which is what makes such a transfer acceptable to us; if the law that applies to you requires more than that, do not install the Application.

Retention of information

On the device. Everything in the first section lives until the Application is deleted or reset.

With us. The funnel steps sit in our database as rows addressed by the random installation number. We have not yet declared a fixed retention period for those rows; when we do, it will appear here.

Crash reports are kept by Crashlytics under Google’s rules, which also set the period.

What the Application does not do

• Advertising — none of any kind: no banners, no clips, no «watch this and get that».
• Advertising networks and trackers. The Application collects no advertising identifier, builds no profile, and passes nothing to anyone for advertising — ours or anybody else’s.
• Third-party analytics SDKs on the device. Not one. What the Application counts about itself it sends only to our server, which forwards it to Amplitude.
• Analytics inside the lesson itself. We do not know which pictures a child touched or how many times they were wrong: from a lesson only its opening and its end are counted.
• User accounts. No registration, no sign-in, no password — the Application can be used without telling us anything about yourself.
• Social features. No links out of the children’s part of the Application, no messaging, no friend lists.
• Access to the camera, microphone, contacts, location or photos. The Application does not request it.

Social media features and links to other resources

The Application contains no social media features — no share buttons, no embedded feeds, no widgets belonging to a social network.

It does contain a small number of links that lead out of it: this Policy, the terms of use, and the store’s own subscription management screen. All of them sit on the adult side of the parental lock. We are not responsible for the privacy practices of resources we do not own, and we encourage you to read their statements.

Information security

Everything the Application sends travels over an encrypted connection (HTTPS). The rows in our database are closed to reading and writing from outside our own server code. We maintain reasonable administrative, technical and physical safeguards against unauthorised access, use, modification and disclosure.

That said, no transmission over the internet can be guaranteed absolutely, and we do not claim otherwise: the security limitations of the internet are beyond our control, and the less we collect, the less any failure of ours can cost a child. That is the main safeguard in this document, and the reason it is written the way it is.

Data breach

If we learn that the Application’s security has been compromised, or that the data described here has reached unrelated third parties, we will investigate, take the measures the situation calls for, notify the authorities where the law requires it, and publish a notice on this page.

We have no email addresses of our users and cannot write to you personally — which is a consequence of collecting nothing that would let us. This page, and the Application itself, are how we will tell you.

How to stop the collection and request deletion

On the device. Delete the Application and everything it kept goes with it, including the random installation number. Inside the Application, in the settings behind the parental lock, there is also a separate reset: it wipes progress and leaves the Application installed.

How to stop the collection. There is no separate «do not send statistics» switch in the Application today, and we are not going to promise one here. The reliable way to stop the collection is to delete the Application: it stops at once, the installation number disappears from the device, and a new installation receives a different number connected to the old one by nothing.

A deletion request. Write to support@kopsoz.kz and tell us your installation number. The Application shows it to you: open the parent settings and find the Installation number row — pressing it copies the number, so you can paste it straight into the message. That number is the only thing by which the rows belonging to your installation can be found, and we hold no other information by which we could find you — which is the whole point of the arrangement. The steps, and the list of what is deleted and what is kept, are on their own page: delete your data.

Changes and amendments

If the Application starts doing something new with data, this page will be changed before such an update ships, and the date at the top will change with it. Your continued use of the Application after that constitutes your agreement to the revised Policy.

Acceptance of this policy

You acknowledge that you have read this Policy and agree to its terms. If you do not agree, do not install the Application, or delete it.

Contacting us

Questions about privacy go to support@kopsoz.kz. We answer in Russian, Kazakh and English.