KidPair privacy policy

Version of 3 November 2026

This policy describes what data the apps "KidPair: Parental Control" (net.kidpair.parent) and "KidPair — for the child" (net.kidpair.child), the KidPair server and the kidpair.net website with its parent cabinet process, why, how long it is kept and how to delete it. We have tried to write in plain words and only about what the apps really do.

1. Who is responsible for the data

The controller of personal data is the independent developer PairedApps (pairedapps.net). Questions about data and requests to access, correct or delete it: privacy@pairedapps.net.

2. In short

KidPair is open parental control: the child always sees that the app is installed, which rules apply and what the adults can see.
An adult installs and sets up both apps. The child app joins a family only after the child has read what the adults will see and agreed.
Data is stored on KidPair's own server. We show no ads, do not sell data or share it for advertising, and use no analytics, Firebase or Google Play services; the apps contain no third-party SDKs that collect data.
Every kind of data has a retention period (section 9). Location is kept for 30 days.
"Sound around" and calls are only transmitted live and are never recorded by us.
A family and all its data can be deleted in the app or via the website — see kidpair.net/delete-account.

3. Who KidPair is for

Both apps are intended for adults: parents, guardians and other adults they invite into the family. An adult creates the family. The adult installs "KidPair — for the child" on the child's phone or tablet, connects it with a code from the parent app, and grants the Android permissions on that phone themselves — ideally together with the child. The child uses the child app (SOS, calls and chat with the family, tasks) but does not create the family or set up supervision.

4. What data is processed

For each child the adults choose "Full control" or selected parts: rules and screen time, app statistics, location and places, calls and "Sound around", uninstall protection. If a part is not chosen, its data is not collected and the child's phone does not ask for its permissions.

4.1. About adults (parent app and web cabinet)

Name and role: what the child calls the adult ("Mum", "Dad", "Grandma") and a name, if entered.
E-mail address — if the adult linked one: for sign-in codes, bringing the family back on a new phone, and letters (section 4.6). Linking an e-mail is optional.
Sign-in and security data: family, account and session identifiers, a key created by the app on the phone, the phone's maker and model or the browser's name — to show you "Phones with access".
What adults set up: children's names, rules, schedules, limits, places on the map, tasks and rewards, the school timetable, chat messages and answers to the child's requests.
The parent app does not collect the adult phone's location, contacts, SMS, call log or files.

4.2. From the child's device

Location (precise and approximate, including while the app is closed): coordinates, accuracy, time and device. Used for the map, notices when the child arrives at or leaves places the family named, "Not there on time", the day's route and history, the "may run out on the way" battery warning, and SOS. Location history is on by default and kept for 30 days; an adult can switch it off — then only the latest position is kept. An adult can turn on "Precise location": while the child is on the way, positions arrive more often (every 10–15 seconds); no new kinds of data are collected.
Steps and motion. The motion sensor tells the app that the child started walking or riding, so the location is taken more often. With each location point the child's phone sends the number of steps since the previous point, so the trip history can tell "walking" from "by vehicle" or "by bike". Steps are kept with the location history and also as hourly totals — for the adults' "Steps" (today and by day); they are seen only by the family's adults, kept for 31 days and deleted with the child. The child sees their own "Steps today" on their screen. Without the steps permission the app works, just without steps.
Apps and screen time (through Android's "Usage access"): the list of apps that can be opened (name, package name, icon), minutes per day in each app, installation of new apps (for new-app approval), break and limit events. Limits are counted on the phone itself.
The accessibility service "KidPair: breaks and schedules". It receives from Android only the package name and window class name of the app that came to the front. With them the app: (1) shows the break screen over an app the family's rules close; (2) tells the adults which app is open right now — the server keeps only the latest value, no history; (3) if the adults turned on uninstall protection, returns to the Home screen from the settings pages through which KidPair could be disabled or uninstalled. The service does not read screen content, typed text, passwords, notifications or messages, does not tap anything in other apps (apart from going to the Home screen), does not change settings and does not record the screen. The dialer, emergency calling (112), the launcher, the keyboard and KidPair itself are never blocked.
Device administrator is used with an empty set of powers and only so the app cannot simply be uninstalled without an adult. It gives no access to passwords, locking, wiping, the camera or files. If the administrator right is removed, the adults are notified. An adult removes the protection by disconnecting the device from the family in the parent app.
Device state: battery and charging, connection, Android and app versions, which permissions are granted and whether protection works — to tell the adults honestly when something has stopped working.
Identifiers: a device key and ID created by the app itself, a notification channel ID, the maker and model. The advertising ID (AAID), IMEI, MAC address, serial numbers and the Wi-Fi network name are not collected.

4.3. Family messages, calls and "Sound around"

Family chat: message text, photos the child or an adult chose to send, and voice notes (recorded by the phone's own recorder app, up to 512 KB). Photos are taken with the phone's camera app; the apps have no camera permission, and only the photos that are sent leave the phone.
Calls inside KidPair between the child and adults go over the internet, encrypted (WebRTC), through our own relay server, and are not recorded on the server or on the child's phone. The child can answer or decline. Only a log is kept: who called whom, when, and for how long. An adult can record a call on their own phone — the child's call screen shows that it is being recorded.
"Sound around" is a live stream from the child's phone microphone that an adult starts from their own phone to make sure the child is all right. It is never covert: while the microphone is on, the child sees a notification "An adult is listening to the sound around" with a Stop button, and Android's microphone indicator. One listening session lasts at most 15 minutes; to keep listening, the adult has to tap "Continue" again. The sound is only streamed live, encrypted, and is never stored on our server or on the child's phone. Only a log is kept: who listened, when, and for how long. Only the adult can record the sound — on their own phone, in the "Music/KidPair" folder; that recording never reaches us. Other people may be near the child; use the feature only for the child's safety.
SOS: the time of the alert, which adult answered, the child's location (every 15 seconds for 30 minutes after the alert). After an SOS, the child's microphone turns on only when an adult has answered and starts listening — with the same notification.

4.4. Tasks, requests and the school timetable

Tasks and their Piri coins, "I did it" marks, the child's jar (coins, history, coins taken off by adults), gifts (title, price, a picture or an adult's photo), the child's goal, requests to get a gift and their handing over, the child's wishes, "I want a task", swaps of coins for time, "I'm OK", the child's requests for more time, to end a break or for a new app.
When the child's phone is closed as a whole — today's time is up, a schedule or a break is on — and since when.
Reading a timetable from a photo. When an adult chooses "Read from a photo", the picture (scaled down to 2400 pixels) is sent to our server, where a text-recognition program reads it. Neither the photo nor the recognised text is stored on the server or written to logs — the adult only gets the result, which they check and save as the timetable themselves.

4.5. The child's messages to the developers, and "I need help"

In the child app's "Help", the child can write to the developers about a problem in the app. Such a message (text, device, time) is not shown to the adults of the family; it is stored on the server and sent to the developers by e-mail. The "I need help" screen with 112 and helpline numbers sends nothing: the adults do not learn that it was opened.

4.6. Letters

An adult's linked e-mail receives sign-in and PIN-reset codes, letters about an SOS, about the child's phone being silent for a long time, about the battery, and weekly and monthly reports (which can be turned off). The KidPair server sends the letters itself, directly to the recipient's mail server, without third-party mail services. After that the letter is kept by your mail provider under its own rules.

Support. If you write to support from the parent app, in the "Support" window on the website or to the KidPair bot in Telegram (@kidpair_support_bot), the conversation is kept: your messages and the answers. From the app it is linked to your account and the family number ("KP-…"), so the developer knows which family it is about; from the website — to a random number your browser keeps, and the e-mail if you left one (the answer goes there); from Telegram — only the number of your chat with the bot, so the answer can come there (no name or username). You can attach a screenshot or a screen recording: screenshots are kept with the conversation (made smaller, without where they were taken), videos are not kept on the KidPair server — they go straight to the developer in Telegram. The developer receives and reads the messages in the Telegram messenger, so their text passes through Telegram. First an AI helper (GPT models by OpenAI or, when those are unavailable, Claude by Anthropic) answers from the KidPair help: it receives the conversation (text, screenshots and frames of videos), and its answers are marked "KidPair helper (AI)" — any of them can be reported. If the question is about something that happened in your family, the helper asks whether it may look at the family's data, and looks only after your "yes" (or after a "Support code" you sent yourself), in that conversation and for no more than a day: the children's devices and app versions, when they were online, battery, permissions, rules and limits, what was sent to the phones, screen time, tasks and coins, when location fixes and "Arrived/Left" came (with the place's name, no coordinates or addresses), and facts about the family chat: how many messages, when and from whom, whether they were delivered and seen, whether a photo or a recording is attached. The helper does not see the words of the messages, the photos, the recordings or any sound. This goes to that company only to answer and is not kept by KidPair; if the helper finds a fault in the app, it sends the developer a description of it. The conversation is kept for 180 days after the last message and is deleted with the account or the family. You may rate the answer with stars and add a comment, which is kept with the conversation. Please don't send passwords or the child's personal details to support unless needed.

4.7. What stays only on the phone

Recordings of "Sound around" and calls made by an adult — on the adult's phone.
The child's photo an adult chose for the child's card — in the app's storage on the adult's phone.
Cloud backup of app data is switched off in both apps.

4.8. The kidpair.net website

The website uses no cookies, ads or third-party visitor counters (Google, Yandex or others). The site counts its own public pages: how many times each page was opened a day, how many browsers opened the site today and how many for the first time, where visits came from (a search engine, a social network, a link tag or direct), how many times "Get it on Google Play" was tapped and a video started. Only these events are sent, with no cookie and no browser number; the server does not record the IP address with them but adds them straight into the day's totals and keeps them for 2 years. So as not to count one person twice, the browser remembers only the day it last opened the site and that it has been here before. The browser also keeps the chosen language, the colour theme and, if you signed in to the cabinet, the sign-in key (the browser remembers the sign-in for 30 days). Like any web server, ours receives the IP address and technical details of each request; we use them only to run and protect the server. To find faults, the server keeps for 14 days which requests of the child's phone it refused (kind of request, response code, time, no content), and for 30 days when the phone said it was closed as a whole (time up, a schedule, a break).

5. What KidPair does not collect

Contacts, SMS, the phone's call log, calendar, files, browsing history, screen content, typed text, notification texts, messages in other apps, health data, payment data, the advertising ID. There is no screen recording and no hidden audio recording. The child app's icon is never hidden, and the permanent notification "Parental control is working" shows that supervision is on.

6. Why, and on what legal basis

Data is used only to run KidPair for your family: to show the adults where the child is and how the device is used, to apply the family's rules, to deliver SOS alerts, calls, messages and notifications, to tell you when supervision has stopped working, and to sign in and protect the account. We do not use data for advertising, profiling, sale, or training third-party systems.

Adults' data — to provide the service the adult asked for by creating a family (performance of a contract).
The child's data — by the decision and with the consent of the parent or other legal guardian, given when creating the family and connecting the child's device; when connecting, the child sees what the adults will see and agrees. Consent can be withdrawn: switch parts of supervision off, disconnect the device or delete the family.
Security logs (sign-ins, adults' actions, call and listening logs) — a legitimate interest in protecting the family and accounts from misuse, and in letting the child see what the adults did.
In some cases — compliance with a legal obligation.

7. Who sees the data

The family's adults. Only the adults added to the family see the child's data. Each of their actions is recorded in a log the child can see ("Mum started a break").
The child sees on their own phone the rules, the "What adults can see" screen (every kind of data, why it is used and how long it is kept) and the adults' recent actions. This screen is always open, without a PIN.
The developer. Only the developer has access to the server, to run it and fix faults. We do not look at families' data except when needed to solve a problem you reported, or when the law requires it.
Overall statistics. To understand what is used and what to improve, the developer looks only at de-identified overall numbers across all families at once: how many families, children and devices there are, how many times a day each feature was used, how many families are on a trial or subscribed, which Android and app versions are in use, and in which countries and languages the app is used. For this the parent app tells the server only the country — from the mobile network, the SIM card or the phone's region; no city, address, IP address or GPS is used for it, and the country is kept while the account exists and goes only into overall numbers. The apps and the cabinet also report once a day how many times each screen was opened the day before (say, "Piggy bank — 3"): numbers only, with no times and nothing about whose phone it is; on the server they are added straight into the totals of all families. When an adult changes something (a task, a break, a place…), the server adds one to that action's count for the day — separately for the app and for the website cabinet, without who did it. These numbers contain no names, e-mail, messages, places, photos, sound or anything else about an individual family. The developer looks at or changes a particular family's subscription only by its number ("KP-…", shown under "Subscription") when the family itself contacts support; every such action is written to a log.
OpenStreetMap maps. The map in the parent app and in the cabinet loads map tiles from OpenStreetMap servers (tile.openstreetmap.org). OpenStreetMap receives your device's IP address and which part of the map you are viewing (which may show where the child is), but no family data. The OpenStreetMap Foundation's privacy policy applies. An address search when adding a place («Find») goes through our server to OpenStreetMap's search (nominatim.openstreetmap.org): only the words typed and the rough area of the map are sent, without your IP address or family data.
Telegram. The developer reads and answers support messages in Telegram: Telegram receives the text of the conversation, attached screenshots and videos and its number, but no other family data.
OpenAI. The AI support helper (GPT models) receives the support conversation (text, screenshots, frames of videos) and the KidPair help to write an answer, and with your consent in that conversation the details of your family needed to find out what happened (see "Support"). OpenAI processes them under its API terms, does not use them to train models, and may keep them for up to 30 days to check for abuse.
Anthropic. When OpenAI's models are unavailable, the same details go to the helper on the Claude model: it receives the support conversation (text, screenshots, frames of videos) and the KidPair help to write an answer, and with your consent in that conversation the details of your family needed to find out what happened (see "Support"). Anthropic processes them under its API terms and does not use them to train models.
RuStore. When a child asks to allow a new app, the parent app may itself load that app's short description from its public RuStore page. RuStore sees the adult's phone IP address and the app's name, as when opening the link, but no family data.
lava.top. If you pay for the subscription by card on the website, the payment is taken by the lava.top service. It receives the e-mail address for the receipt, the chosen plan and the language of the payment page; you enter your card details only on lava.top's page, and KidPair neither sees nor stores them. lava.top processes the payment under its own rules and tells our server the payment number, whether it went through and until when the subscription is paid.
Google Play processes app installation data under its own policy. It may show us anonymised install and crash statistics — a feature of Google Play, not of our apps.
Authorities — only on a lawful request that is binding on us.

We do not sell data and do not give it to advertisers, data brokers or other third parties.

8. Where the data is stored and how it is protected

All data is stored on the KidPair server operated by the developer (located in: the Netherlands). If you live in another country, your data is transferred there; we protect it the same way for every family. The apps talk to the server only over an encrypted connection (HTTPS/TLS); call and "Sound around" audio goes over WebRTC (DTLS-SRTP) through our own relay server, which stores nothing. Devices sign in with keys created on the phone itself, not with passwords; sensitive actions need a recent sign-in confirmation. No system is perfectly secure, but if a breach does affect your data, we will tell you and, where required, the supervisory authority.

9. How long data is kept

The server deletes expired data automatically, every hour.

The child's location (points) — 30 days; with history switched off — only the latest position of each device.
Arrivals at and departures from named places — 30 days.
SOS and other safety alerts — 1 year.
Chat messages — 30 days; photos and voice notes — 14 days.
Time in apps per day — 30 days; weekly and monthly totals (reports) — 1 year.
The app list and the current app — only the latest data, overwritten on every update.
New app installations — 90 days.
The "Sound around" log (who, when, how long) — 30 days. The sound itself is not kept.
The call log — 90 days. The calls themselves are not kept.
Device state and battery warnings — 30 days.
The log of adults' actions that the child sees — 12 months.
The technical copy of sent letters — 7 days.
Sign-in sessions — while valid, then another 30 days to protect against account takeover.
The service's overall numbers per day (nothing about individual families) and the log of the developer's subscription actions — 2 years. The family's support number — as long as the family exists.
Card payment on the website: lava.top's payment number, the plan, the amount, until when it is paid and the receipt e-mail (lava.top cancels the renewal by it) — as long as the family exists.
Timetable photos for recognition — not kept.
The child's messages to the developers about a problem in the app — no time limit, until the family is deleted (we delete the letter in the developers' mailbox on request).
Names, e-mail, rules, schedules, places, tasks and rewards, the child's requests, the school timetable, device identifiers — until the adults change or delete them, until the device is disconnected from the family (for device data), or until the family is deleted. E-mail — until it is unlinked.
Database backups — no longer than 30 days, on the same server, only for recovery after a failure.

10. Deleting your account and data

The adult who created the family deletes it in the parent app: "Family" → "Delete the family and all data". All adults are notified at once, and for 7 days any of them can cancel. Then the family, the children, the devices and all their data are deleted, together with the accounts of adults who do not belong to another family.
Any other adult deletes their own account with "Delete my account and leave the family". The family's and the child's data then stays with the family.
The family's creator who wants to leave but keep the family going first hands it over to another adult of the family: "Family" → "Hand the family over to another adult". That adult becomes the family's creator, and the former creator becomes an ordinary adult who can delete their own account as described above. The family's and the child's data is not deleted and stays with the family.
Without the app — in the web cabinet, "Account" section (kidpair.net/app/delete-account), or by e-mail to privacy@pairedapps.net.
To disconnect one child device, use "Devices" — data collection from it stops.

In detail — what is deleted, what remains and why — on the page "Deleting your account and data". Simply uninstalling an app from a phone does not delete data on the server.

11. Your rights

You can find out what data about you and your child is stored and get a copy of it ("Family" → "Download a copy of the data" — one file with everything the server keeps), correct it, delete it, restrict or stop its processing (switch parts of supervision or location history off, disconnect the device) and withdraw consent. If something cannot be done in the app, write to privacy@pairedapps.net — we will answer within 30 days. Before we hand over or delete data on the basis of a letter, we make sure that it comes from an adult of that family: deletion also destroys the record of what happened to the child's phone. You also have the right to complain to your country's data protection authority.

12. Children

KidPair processes data of children, including children under 13, but only because a parent or other legal guardian created the family, connected the child's device and chose what is used. Only an adult may create a family; if we learn that a child created a family without an adult, we delete it. Children's data is used only to run KidPair for their family and never for advertising or profiling; the child app contains no ads and no third-party SDKs.

A parent can at any time review the child's data (the data copy), stop its collection (switch features off or disconnect the device) and delete it (delete the family) — including under the US COPPA and the EU GDPR. The child always sees on their own phone what is collected and why. If the child wants their data deleted or changed, they can ask an adult, write to the developers from the child app's "Help" ("A problem in the app"), or write to privacy@pairedapps.net. We will consider such a request together with the family's adults, taking the child's age and interests into account.

13. Changes to this policy

If we change what data is collected or how long it is kept, we first update this page and the child's "What adults can see" screen, and we announce significant changes in the parent app. The version date is at the top.

14. Contact

PairedApps, pairedapps.net. E-mail for questions about data: privacy@pairedapps.net, support: support@pairedapps.net.