FAMILYKITE / DOCUMENTATION
Privacy policy
Who we are
FamilyKite ("the app") is a parental control and activity time app published by Mahmut Berat İmdat, an individual developer who publishes under the name mbisoft ("we", "us"). mbisoft is a publishing name, not a company. Mahmut Berat İmdat is the data controller for the personal data described in this policy.
Contact: support@mbisoft.com
Postal address: Cumhuriyet Neighborhood, Arda Street, 150/3, No. 31, Nilüfer, Bursa 16210, Türkiye
Telephone: +905384384092
Website: https://mbisoft.com/products/familykite/
This policy explains what personal data the app collects, why, who processes it for us, how long we keep it, and what you can do about it. It is written to be read by parents. Where we say "you", we mean the parent who holds the account.
Who the app is for
• The account is opened by a parent or legal guardian who is at least 18 years old.
• The parent creates the child profiles and decides whether a child’s phone is connected.
• Children use only the child screens the parent set up for them. A child cannot open an account on their own.
• The app is only for parents supervising their own children. It must not be used to monitor another adult, or a child you have no parental responsibility for.
What we collect
• Parent account: name, email address, preferred language, and a password. The password is handled by our authentication provider; we never see or store it in plain text. On your own phone, sign-in is kept in the operating system’s secure storage. Face ID or fingerprint unlock happens entirely on the device; we never receive biometric data.
• Child profiles: the display name and username the parent creates, and an avatar picked from the app’s built-in set or, on iPhone, a photo the parent chooses. The photo is cropped to a small square on the phone and only the family can see it.
• Activity time: an activity with a countdown the child watches, such as teeth-brushing or homework. We keep each activity time’s title and length, a photo only if the parent picks one to show on it, and a history of when activity times were added, when they were started and when they ran out.
• Child support profile (optional): a parent may choose to fill in a support profile for a child under Tools. It can hold birth date and gender; language level, sleep and toilet routines; calming methods, sensitivities and triggers, and phrases that work; and family rules. All of these fields are optional. They are visible only to that parent and are used only to show the parent their own notes. The profile is not a health record and has no health field. Please do not enter health information in it.
• From a connected child Android phone: the list of apps that can be opened from the home screen (name, package name and icon), how long each app was used that day, the phone’s name and time zone, a random installation code, a security key that proves requests really come from that phone, which protection settings are on or off, and the extra-time requests the child sends, the short note they add, and the parent’s answer.
• From a connected child iPhone (Apple Screen Time): on iPhone, apps are chosen on the child’s phone with Apple’s own picker, and app usage is measured by Apple’s Screen Time frameworks. The choice stays on the device as Apple’s private tokens. We do not receive which apps are in it or how long they were used. What reaches our servers: the name the parent types for each group of apps and a random reference for that group; the rules the parent set on those groups and the phone’s confirmation that it applied them; the phone’s name, a random installation code, and a security key that proves requests really come from that phone; and whether Screen Time permission and monitoring are on.
• "Lend my phone" (parent’s iPhone): it runs only on the parent’s own iPhone. The apps chosen for it stay on that phone as Apple’s private tokens and are never sent to us.
• Notifications: a notification token, so the app can deliver notifications, and a short record of whether each notification was delivered.
• Subscriptions: if you buy Premium, we receive your subscription status (active, expired, renewed) from Apple or Google through our subscription provider. We never receive your card or payment details.
• Usage statistics and crash reports (parents on iPhone): what screens a parent opens and which features they use — for example, that an activity time was started, never its title — and technical crash reports. These are linked to a random installation identifier and, once you are signed in, the parent account’s ID. The sign-in screens are measured without an account ID. Nothing is recorded while a child is signed in. You can turn this off under Account → Privacy and data.
• Consent records: who agreed, to what, when, and under which version of this policy, so that consent can be shown later; that you confirmed, when you opened the account, that you are 18 or older and the parent or legal guardian of the children you add, and which versions of the terms and of this policy you accepted; and that a message confirming your consent was sent to your email address, and when.
What we never collect
• We never read or collect messages, typed text, screen content, contacts, location, browsing history or audio.
• We never collect photos or files other than the activity time or avatar photo a parent picks.
• The app contains no advertising and uses no advertising identifiers.
• We never sell personal data and never share it for advertising.
• Usage statistics never contain names, app lists, activity time titles, messages, or anything a child does.
Phone permissions and how they are asked
Before each permission, the app explains why it is needed and what it uses. You can choose “Not now”; declining turns off only the feature that needs that permission.
• Usage access (Android): measures how long each app is used, so the parent’s daily limits work.
• App blocking — Accessibility (Android): notices which app has just opened, so the break screen can appear over a paused app. It sees only the app’s name at that moment — never what is on the screen or what is typed.
• Notifications and background running (Android): keeps a permanent notification visible while protection is on, and keeps rules working while the phone sleeps.
• Screen Time (iPhone): lets the parent choose apps to limit, using Apple’s own Family Controls.
• Camera / photos: the camera only when a parent takes an activity time photo; the photo library only when a parent picks an activity time or avatar photo.
• Face ID / fingerprint: only to unlock the parent side on that phone.
While a child’s phone is connected, a notification on it always says that protection is on, and the child can see their parent’s rules in the app.
How we use data, and on what legal basis
We use data only to run the service: applying the parent’s rules; showing app time to the parent and the child; running activity times; delivering notifications and account emails; keeping the connection between phones secure; and managing accounts and subscriptions.
• Parent account, activity times, subscription: performance of the service you signed up for (KVKK Art. 5(2)(c); GDPR Art. 6(1)(b)).
• Data from a connected child phone: the explicit consent the parent gives in the app, as the person with parental responsibility, before a phone is connected (KVKK Art. 5(1); GDPR Arts. 6(1)(a) and 8).
• Child support profile: the parent’s explicit consent, given by choosing to enter it (KVKK Art. 5(1); GDPR Art. 6(1)(a)). You can delete it at any time.
• Usage statistics and crash reports: our legitimate interest in keeping the app working and improving it (KVKK Art. 5(2)(f); GDPR Art. 6(1)(f)). You can turn them off at any time.
• Consent records: our legal obligation to be able to show consent (KVKK Art. 5(2)(ç); GDPR Art. 6(1)(c)).
Who processes data for us
• Supabase: stores the data, handles sign-in, and runs our server functions.
• Resend: sends account emails, such as verification and password-reset codes, and the message that confirms your consent.
• Expo Push Service and Google Firebase Cloud Messaging: deliver notifications.
• Google Firebase (Analytics, Crashlytics): receives usage statistics and crash reports from the iPhone app.
• RevenueCat: manages Premium subscription status. It is identified only by a random account ID, never by name.
• Apple App Store and Google Play: distribute the app and handle payments under their own privacy policies.
These providers process data only to provide these services to us. Some of them process data outside Türkiye and the EU. Where that happens, the transfer relies on the safeguards required by KVKK Article 9 and GDPR Chapter V, such as standard contractual clauses. We do not share personal data with anyone else, except where the law requires it.
How long we keep it
• Installed-app list and daily app time from a connected phone: deleted 35 days after the phone last reported them, and at once when the phone is disconnected.
• Protection status reports (for example, a permission being turned off): 90 days.
• Notification delivery records: 30 days.
• One-time device security checks: 1 day.
• Extra-time requests, their notes and answers: 90 days.
• Daily time-sharing records: 90 days.
• Activity time history (when an activity time was added, started and ran out, with its title and length): 90 days.
• A disconnected phone's remaining settings: 30 days.
• Usage statistics (Google Firebase): up to 14 months. Crash reports: 90 days.
• Account, child profiles, support profiles, rules, photos and consent records: until the account is closed, plus 30 days so it can be reopened on request; then deleted.
Your choices and rights
• Phone permissions: turn any of them off in the phone’s settings. The parent is told that protection is incomplete.
• Usage statistics and crash reports: turn them off under Account → Privacy and data.
• Child’s phone: disconnect it from the parent’s device card. Its app list and app time are deleted at once.
• Support profile: edit or clear it at any time.
• Child account: delete it under Account → Children.
• Whole family account: close it under Account → Privacy and data → Close my account. Sign-in stops at once for the parent and every child. The data is kept for 30 days so the account can be reopened on request, then deleted.
• Without the app: write to support@mbisoft.com from your parent account’s email address to ask for the account to be closed and its data deleted.
Under KVKK Article 11 and the GDPR, you can ask to access, correct, delete or export your data, to restrict its processing, or to object to it. Where processing relies on your consent, you can withdraw it at any time: disconnect the child’s phone, clear the support profile, or write to us. Withdrawal does not affect what was processed before it.
Write to support@mbisoft.com. We answer within 30 days. You can complain to the Personal Data Protection Authority of Türkiye (KVKK) or to the data protection authority where you live.
Children
FamilyKite is used by children, but it is controlled by their parent. We collect data about a child only when the parent creates the child’s profile, when the parent chooses to enter a support profile, and when the parent connects the child’s phone after giving consent.
A child cannot change what is collected, and cannot open an account. If you believe we hold data about a child without a parent’s consent, write to support@mbisoft.com and we will delete it.
Parents in the United States
FamilyKite’s child screens are used by children under 13, so the Children’s Online Privacy Protection Act (COPPA) applies. This section says, for a parent in the United States, what the rule asks us to say. It adds nothing to what is collected.
Operator: Mahmut Berat İmdat, publishing as mbisoft
Postal address: Cumhuriyet Neighborhood, Arda Street, 150/3, No. 31, Nilüfer, Bursa 16210, Türkiye
Telephone: +905384384092
Email: support@mbisoft.com
What we collect from a child:
• The username and password a child signs in with. The parent creates both; the password is handled by our authentication provider.
• From a connected Android phone: the app list, each app’s daily time, and which protection settings are on.
• From a connected iPhone: whether Screen Time permission and monitoring are on. The names of app groups are typed by the parent.
• Extra-time requests, and the short note a child may add to one.
• The child’s answers to the notices and permission questions on their phone.
• Device identifiers: a random installation code, a security key, and, on Android, a notification token.
A child’s profile name, avatar and support profile come from the parent, not from the child. A child cannot make any information public and cannot contact anyone through the app.
What the device identifiers are for: the installation code and the security key prove that a request really comes from the phone the parent connected, so nobody else can read or change a family’s rules. The notification token delivers the notifications the app sends about rules and requests. They are never used to advertise, to build a profile of a child, or to contact a child about anything else.
Who receives it: a child's information is stored by Supabase, our hosting and sign-in provider. On a connected Android phone, the notification token and the notifications themselves pass through Expo Push Service and Google Firebase Cloud Messaging so that they can be delivered. Google Firebase Analytics and Crashlytics receive nothing while a child is signed in. These providers act only on our instructions and only so that the app works. We do not sell a child's information, do not share it for advertising, and do not disclose it to anyone else, so no separate consent to disclosure is asked.
How a parent consents: nothing is collected from a child’s phone until the parent, signed in to the parent account, agrees in the app. We then send a message to the parent account’s email address that confirms the consent and says how to take it back.
Your rights as a parent:
• Review: the app shows you what a child’s phone has sent. You can also ask us for a copy.
• Delete: disconnect the phone, delete the child’s account, or close the family account. You can also ask us to delete it.
• Refuse further collection: disconnect the phone at any time. The child can keep using activity time without it.
Write to support@mbisoft.com from the parent account’s email address, so that we know the request comes from the parent. We never ask a child for more information than the feature in front of them needs.
How long we keep a child's information
We keep a child's information only as long as the purpose below needs it, then delete it. We do not keep it indefinitely.
- Child's username, password and profile: to let the child sign in to the screens the parent set up. Deleted when the parent deletes the child's account, or 30 days after the family account is closed (the 30 days let the parent reopen it on request).
- App list and daily app time from a connected Android phone: to show the parent the child's app time and apply the daily limits. Deleted 35 days after the phone last reported them, and at once when the phone is disconnected.
- Protection settings reported by the phone (on Android which protections are on; on iPhone whether Screen Time permission and monitoring are on): to tell the parent when protection is incomplete. Deleted after 90 days.
- Extra-time requests and the note a child adds: so the parent can answer them. Deleted after 90 days.
- The child's answers to the notices and permission questions on their phone: to show what the child was told. Kept with the family account and deleted 30 days after it is closed.
- Device identifiers (installation code, security key, notification token): to prove a request comes from the connected phone and to deliver notifications. Deleted 30 days after the phone is disconnected.
Security
• All traffic is encrypted in transit.
• Each family can reach only its own data; this is enforced in the database itself.
• Photos are kept in private storage.
• Rule changes sent to a child’s phone are signed, and the phone rejects any change it cannot verify.
• Access to our admin tools is limited to the publisher and the people the publisher authorises.
Changes to this policy
When this policy changes, the version above changes. When a change affects what is collected, the app asks for agreement again before continuing.