Kimda

Main navigation

Language

Theme

Try it

Kimda

Privacy Policy

Last updated: 27 October 2026

This is a machine translation. The Czech version is legally binding.

The Czech version of this policy is binding. Translations into other languages are for information only; in the event of any conflict, the Czech version prevails.

This document describes what data the Kimda app ("the app", "we") and the kimda.app website process, why and on what legal basis, who we share it with, how long we keep it and what rights you and your children have. The app is designed to be used by the whole family, including children — which is why we take particular care in protecting data.

1. Who is the data controller

The data controller is Mgr. Ivo Slávka, who operates the Kimda app as a sole proprietor registered in the Trade Licensing Register maintained by the Prague 8 Municipal District Office, Company ID 30070929, with registered office at Bergerova 1115/2, 182 00 Praha 8 – Kobylisy, Czech Republic. Contact email for privacy questions and for exercising your rights: privacy@kimda.app.

2. What data we process and why

Why we process data and on what legal basis:

You can object to processing based on legitimate interest (section 7). The phone number is necessary for registration and sign-in; without it, the app cannot be used. The profile photo is optional and a photo of a completed task is only needed for tasks where the parent requires it. We do not use automated decision-making or profiling with legal or similarly significant effects (Art. 22 GDPR); automatic security limits, which for example temporarily block further SMS code attempts, serve only to protect accounts and the service.

3. Task photos

Photos that a child (or a parent on their behalf) uploads for a task can be seen only by members of the same family (parents and children in the app). They are not public, and the app does not share them with any other app or social network. A task photo can only be taken with the in-app camera. The app and then the server again remove metadata (such as GPS location or camera details) from the photo before saving it. Photos are stored in non-public object storage (see section 4) and the server will only release them to a signed-in member of the same family. A parent can request their deletion at any time.

For each uploaded photo, the server calculates a technical fingerprint (a checksum and a simplified 64-bit image fingerprint). It only serves to let the app recognize when the same or an almost identical photo is used for a task again, and to ensure the photo belongs to the task for which the child just took it in the app. The photo cannot be displayed or reconstructed from the fingerprint, and it is deleted along with the photo. The record of the time challenge for the photo (who requested it in the app, for which task and when) is deleted by the server after 7 days. The parent sees a warning next to the photo when the photo does not have a valid app time check or is very similar to a previous photo, as an aid during approval; the check does not guarantee that the photo cannot be spoofed.

4. Who we share data with and transfers outside the EU

We only share data with providers who operate the app for us (processors), and only to the extent they need to do so. Processors may only use the data to provide their service for us and according to our instructions. Apple and Google act as independent controllers for store purchases.

Railway, Cloudflare, Twilio, Expo, RevenueCat, Sentry, Spaceship, Apple, Google and Meta (section 9) are companies based or backed in the USA, and may therefore process data outside the European Economic Area. For transfers outside the European Economic Area, we use a mechanism under Chapter V of the GDPR that applies to the specific recipient and processing - typically the recipient's certification under the EU-USA Data Privacy Framework (an adequacy decision by the European Commission, Art. 45 GDPR) or standard contractual clauses approved by the European Commission (Art. 46(2)(c) GDPR). We will provide you with information about the mechanism for a specific recipient and about where a copy of the relevant safeguards can be obtained upon request at privacy@kimda.app.

We do not sell data from the app, share it with advertisers or use it for targeted advertising. Measurement of advertising on the kimda.app website, with the visitor's consent, is described in section 9.

5. Parental consent and children's roles

Only an adult may set up the app (the "parent" role and a new family). An account with the "child" role is only ever created after joining with an invite code that only the parent knows - so a child can only take part with the knowledge and consent of the parent who shares the code. Furthermore, every connection of a child or another parent must be explicitly approved by a parent in the app; until approved, the new member can only see the family's name. The family invite code is valid for 48 hours, an unapproved request is automatically deleted after 72 hours, and a rejected or cancelled one immediately. By registering in the "parent" role, you confirm that you are of legal age and that you have the legal right to consent to the processing of your children's data in the app.

We process a child's data only to the extent necessary for the functioning of the family account set up and managed by the parent, i.e. for the performance of the contract with the parent (Art. 6(1)(b) GDPR). The parent, as the legal representative, decides on the child's participation: they share the invite code, explicitly approve the child's connection and can remove the child from the family or request the deletion of their account at any time. The child only acknowledges the policy during registration; consent to the processing of their data is given by the parent when they approve the child's connection in the app, and the server records the time, the parent and the policy version. For children approved with an older version of the app, the app will additionally request the missing consent from the parent. If the processing required consent and the child was not yet 15 years old (the age limit in the Czech Republic under Art. 8 GDPR and Section 7 of Act No. 110/2019 Coll., on personal data processing), the parent gives consent on behalf of the child. The child's rights under section 7 can be exercised by the parent on their behalf.

6. How long we keep data

We keep account and family data until a user requests deletion of the account or of the entire family. Mere inactivity in the app does not trigger automatic deletion. Users therefore do not have to open the app regularly in order not to lose the family history, and they can start the deletion at any time directly in the app or request it at privacy@kimda.app. We keep the history of changes to financial rules (section 2) for the entire duration of the family's existence, without a time or total numerical limit (a family may save changes to financial rules a maximum of 30 times per hour), because it serves as an immutable proof of who changed the rules and when, for example in a dispute between parents; it cannot be edited or deleted in the app. After the deletion of the entire family (section 7), the server deletes it during the next cleanup; the deletion of an individual member's account does not change it and only an internal identifier without a name remains with it.

The following periods apply to other specific records:

Production operational and security hosting logs may be kept for no more than 30 days. Technical error reports of the app and server are kept by Sentry for no more than 90 days so that we can trace and fix errors that only appear after the release of a new version of the app; any operational backups of Sentry expire no later than 90 days after their creation. Database backups are taken daily, encrypted even before transmission from the production environment and deleted 30 days after being taken, so previously deleted data will remain in them for no more than 30 days; they are not used to routinely restore a deleted account. If we had to restore the database from a backup, we would reapply deletions made after the backup was taken according to the log of deletions. The hosting, database and storage settings must technically enforce these periods, and the operator reviews them regularly.

If deletion of a record at an external subscription provider cannot be completed immediately, Kimda anonymizes the local personal data without further delay once the media have been removed. In order to safely retry the external request, it keeps only the internal random family identifier and the technical deletion status, not names or phone numbers. The server deletes the record of this external deletion task (internal family identifier, provider designation, number of attempts, times and the last error code, without names and phone numbers) 90 days after its completion; an unfinished task is kept until it is completed.

We retain the proof of consent to the immediate start of Premium (internal family and user identifiers, time of consent, chosen plan, start of the paid period, store transaction identifier, internal identifier of the purchase attempt and version of the displayed text) for the period necessary to prove this consent in a potential dispute, standardly 3 years from its granting. Upon expiration of the period, the proof is deleted in a controlled manner. The proof is not deleted together with the account or the family (section 7). We also store its copy (without the internal identifier of the purchase attempt) in the separate non-public Cloudflare R2 storage (section 4) so that the proof survives a loss of the database between backups; the storage deletes it itself after 1125 days from its storage.

7. Your rights

You have the right:

Send your request to privacy@kimda.app. To ensure we do not hand over or delete data to someone else, we will first verify that the request is made by the account owner (for example, by confirmation from the phone number associated with the account); never send us codes from sign-in SMS. The only exception is the code from the SMS marked “Kimda obnova účtu”, which support will request from you only in response to your own request for the return of a hijacked account, or to your own confirmation of such a request from another parent in your family (section 2); even then, tell it only to support, never to another family member. Support requests this code from you exclusively by e-mail from the address support@kimda.app with your request number, never by phone or through another family member. We handle requests for access or portability by exporting the family's data in JSON format (without sign-in tokens and their fingerprints and without fingerprints of original phone numbers from security records, which serve only to verify a request for the return of an account, and without the journal of phone and member status changes, which serves only to protect against taking over a number; the export includes records of direct payouts and manual repayments (section 2); for photos it contains their technical fingerprint according to section 3, we will provide the photos themselves separately upon request); we record each export (who prepared it, when and based on what request). Upon request, we will provide you with event data from the journal of phone and member status changes (type and time, without fingerprints). We will respond without undue delay, at the latest within one month; in more complex cases, we may extend the period by a further two months, of which we will inform you in good time. The rights of a child can be exercised by a parent as their legal representative.

8. Security

The app does not use passwords (sign-in only via a verified phone number). Access is protected by a short-lived sign-in token valid for 15 minutes and a refresh token, which the server stores only as a fingerprint; upon proven reuse of an already replaced refresh token, the server signs the account out on all devices, cancels its registrations for notifications, writes a security record and notifies other parents. In production, communication between the app and the server takes place over HTTPS. Photos are kept in non-public storage, and before releasing them the backend verifies the account and membership of the same family. Database backups are encrypted even before transmission and can only be decrypted with a private key stored outside the cloud; promo codes are in the database only as an HMAC fingerprint with a key outside the database, and we record promo code management. The server does not write phone numbers, tokens or request content into operational logs.

9. The kimda.app website and cookies

This section applies only to visitors of the kimda.app website, not to use of the app. The website runs on the Cloudflare network, which technically processes the IP address and browser data on each visit in order to deliver the page and protect it against attacks; Cloudflare keeps records for website error diagnostics for a maximum of 3 days. Depending on the browser language (and for the download link, also the device type), the website redirects you to the appropriate version of the page. The legal basis is our legitimate interest in a secure and functional website (Art. 6(1)(f) GDPR). The website remembers the selected theme only in your browser (localStorage). Your cookie decision is stored in localStorage and in a strictly necessary technical cookie kimda-consent-proof (valid for 180 days), which contains only the type of choice and the time of the decision, with no identifier of a person or account. Your browser technically sends it with every request to the website; the server does not evaluate it, it is used only by the script in your browser to verify that consent has not been withdrawn. This cookie does not require consent and is not used for measurement or advertising.

Only if you choose "Accept" in the banner on the website does the website load Meta Pixel from Meta Platforms Ireland Limited. It stores a cookie in your browser (e.g. _fbp, valid for up to 90 days) and sends Meta data about the visit: the page visited, IP address, browser data and the cookie identifier. We use it to measure the effectiveness of advertising on Facebook and Instagram. The legal basis is your consent (Art. 6(1)(a) GDPR and Section 89(3) of Act No. 127/2005 Coll., on electronic communications). We are jointly responsible with Meta for the collection and transmission of this data; its further processing, including any transfer to the USA under the EU-USA Data Privacy Framework, is carried out by Meta as an independent controller in accordance with its policy at facebook.com/privacy/policy. We never send data from the app, your account or your family to Meta.

Without consent, Meta Pixel is not loaded at all. You can withdraw your consent at any time via the "Cookie settings" link in the website footer; the website then deletes the Pixel cookies and no longer loads the Pixel.

If you join the tester group in Google Groups via the tester page, the group administrator will see the email of your Google account; we will use it only for testing the app and for access to its test version in Google Play. The test version for iPhone is distributed by Apple via TestFlight. Google and Apple process the data as independent controllers in accordance with their policies. The legal basis is your request to participate in testing (Art. 6(1)(b) GDPR). The email will remain in the group until you unsubscribe from it or until the testing ends.

10. Changes to this policy

We will inform you in the app and on the kimda.app website of any material change to this policy. The app recognizes which version of the policy you have agreed to: it will ask parents to confirm the new version (and where applicable for consent on behalf of children), and a child will acknowledge it. We will record the time and version of the confirmation.

11. Contact

Questions about personal data protection: privacy@kimda.app