Version 2026-11-17
Privacy Policy
Who we are
Hami and Hami Kids ("Hami") are operated by ANALİZ35 MÜHENDİSLİK MİMARLIK LTD. ŞTİ. ("Analiz35", "we"), a limited liability company registered in Türkiye, which is the data controller.
- Trade name: ANALİZ35 MÜHENDİSLİK MİMARLIK LTD. ŞTİ.
- MERSİS no: 0068092817100013
- Registered office: Bahriye Üçok Mah. 1843/3 Sok. No: 4E, Karşıyaka / İzmir, Türkiye
- Email: [email protected]
Requests about your personal data can be made through the channels described under "How to apply" below. This policy explains in detail what we collect and why. The short Privacy Notice gives the same information in the form required by Turkish law (KVKK) and the GDPR, and the Child Data Consent Text covers the optional child features.
Data we collect
- Account: email address; name only if you enter it or it is provided by Apple or Google sign-in; language.
- Identifiers: user id and a device installation id. The kids app sends one app-scoped install id so that a reinstalled phone replaces its old record. It is not an advertising id.
- Device information: model, OS and app version, permissions, battery and the list of installed apps, to show protection status and apply rules.
- Child profiles: the name a parent gives a child, the child's birth year and, optionally, gender, used to tell children apart and to pick age-appropriate defaults.
- Child location and app usage: only after a parent gives explicit consent for that child, and only while it is on.
- Safe zones: the places a parent defines (name, centre point and radius).
- Map tiles: the parent app's map is drawn from tiles fetched from a map tile provider, which receives the requested map area and the device's IP address. It does not receive the child's identity.
- Place names for trips: for a stop that is not a named safe zone, the parent app sends the child's location, rounded to the centre of a cell about 100 m wide, to Apple (iPhone) or Google (Android) to look up the neighbourhood name. Hami does not receive or store these lookups.
- Web protection: the parent's website rules and the daily count of blocked lookups. On Android, the child's phone sends its website lookups to Cloudflare's resolver to be filtered, only while Web protection is on; Hami does not receive the lookups themselves. With the Visited sites history on, the phone regularly sends Hami the domain names it looked up (see the next item); if Web protection is off, those lookups go to the phone's usual resolver, not to Cloudflare. See the Child Data Consent Text.
- Activity history (Android only, Hami Pro): if you switch on Visited sites for the child (a separate switch that works with or without Web protection), the names of the websites the child's phone looked up (domain names only, such as example.com; never full addresses or page content), per day, with the hours of the day they were used and whether they were blocked; and, if you switch on YouTube history for the child, the title and channel of the videos watched in the YouTube app and the searches typed there, with the time. Nothing from before you turned a history on is collected. Each entry is deleted after 30 days. On iPhone none of this exists: Apple does not let apps see it.
- SOS: when the child presses SOS, the alert carries the phone's position at that moment.
- Purchases: subscription status via RevenueCat and the app stores. We never see card numbers.
- Product interaction (first-party analytics; opt-out in Settings) and crash diagnostics of the parent app (Sentry, no personal identifiers, IP address not stored). The kids app sends crash diagnostics only (error type, stack trace, app version, phone model and OS version; no name, no account, no child or family data, no location, no apps or websites, no IP address) and has no analytics SDK. The crash reporter adds a random technical identifier of its own, which is not linked to an account, child or family.
- Country derived from the IP address (Cloudflare).
- Legal records: which version of the Terms you accepted and when, which Privacy Notice version you were shown, and each consent you gave or withdrew, with its text version and date.
What we never collect
Hami never reads the content of messages, emails or chats, never records or listens to calls, never accesses the phone's call log or contacts, and never accesses your child's photos, camera, microphone or passwords. It never stores full web addresses or page content: the visited-sites history holds domain names only. There are no advertising SDKs, no advertising identifiers and no cross-app tracking. We do not sell data.
Why, and on which legal basis
- Running the service you signed up for (account, sign-in, notifications, rules, subscriptions): performance of the contract (KVKK art. 5/2-c, GDPR art. 6(1)(b)).
- Connecting the child's phone, applying your rules and showing protection status (device information, rules, child profile): our legitimate interest in providing the service you asked for, with the child's rights weighed (KVKK art. 5/2-f, GDPR art. 6(1)(f)).
- Child location, app usage and web protection, including the activity histories (visited sites, YouTube): explicit consent of the parent as the child's legal representative (KVKK art. 5/1, GDPR art. 6(1)(a)). Optional; off until consented; withdrawable at any time. The visited-sites history needs the web protection consent but has its own switch and works with or without Web protection on; the YouTube history belongs to the app usage consent and additionally needs a switch per child.
- SOS location: protection of the child's life or physical integrity (KVKK art. 5/2-b, GDPR art. 6(1)(d)).
- Security, analytics, crash diagnostics, country: legitimate interest (KVKK art. 5/2-f, GDPR art. 6(1)(f)). You can turn analytics off in Settings.
- Tax and commerce records of purchases: legal obligation (KVKK art. 5/2-ç, GDPR art. 6(1)(c)).
- Marketing notifications: your consent, given by a toggle that is off by default (KVKK art. 5/1, GDPR art. 6(1)(a)).
Providing your email address is necessary to create an account. Everything else about your child's location and usage is optional.
Children's data
The Hami Kids app is installed on a child's phone by a parent. It is transparent: it has a visible icon and a persistent notification, it shows the child a screen called "What my parent can see" and a short notice about their information, and the child knows it is there. Child data is linked to the parent's family account, is shown only to the parents in that family, is used only to apply their rules, and is never used for advertising. Only parents can create accounts; children do not sign up.
Parents give consent for location, app usage and web protection per child in the app, as the child's legal representative. Nothing from these categories is collected before consent. The activity histories work the same way: nothing from before you turned a history on is collected, the child sees in Hami Kids which histories are on, and Hami Kids explains them to the child before it asks for the related phone permission. A parent can at any time review the child's data in the app, withdraw a consent, ask us to delete the child's data, and refuse further collection. We do not disclose children's data to third parties for their own purposes. If we ever wanted to, we would ask for a separate consent first. We do not require a child to disclose more information than is reasonably necessary for the features the parent turned on.
Processors and transfers abroad
Our servers are in Türkiye. The following companies work as processors, only on our instructions and only with the data named next to each:
- Google LLC, USA: Firebase Cloud Messaging and Remote Config (push tokens, notification content, install id).
- Functional Software, Inc. (Sentry), USA, data stored in the EU: crash reports of the parent and kids apps, no personal identifiers.
- RevenueCat, Inc., USA: subscriptions (app user id, store receipts, status).
- Cloudflare, Inc., USA: network protection and hosting connection (IP address, request metadata).
Email. Transactional email (verification, password reset, deletion confirmation, export notice) is sent through our mail server hosted in Türkiye. The mails contain only your address, your language and a one-time link; no names and no child data. No email data is transferred abroad for this, and no email-sending software runs in the apps.
Safeguards for transfers abroad. We have concluded a data-processing agreement with each of these four processors. The agreements bind the processor to process the data only on our instructions and for the purposes in this text, to confidentiality and security duties, to rules on sub-processors and to assisting with data-subject rights; for data under the GDPR they contain the art. 28 terms and the processor's EU transfer mechanism (the EU standard contractual clauses or an adequacy decision). Only the minimum data named next to each processor leaves Türkiye; the child's location, usage and activity histories are stored only on our servers in Türkiye and no processor receives them. You can ask for a copy of the agreements at [email protected].
Other recipients under their own terms. The following requests are made directly from the phone, not from Hami's servers; these recipients are not our processors, they process what they receive under their own terms of use and privacy policies as independent controllers, and Hami does not receive the requests:
- Apple Inc. and Google LLC (USA): the App Store and Google Play (purchases, subscription receipts), Sign in with Apple or Google, the push delivery services (APNs, FCM) and the place-name lookups the parent app makes for trip stops (coordinates rounded to about 100 m; the child's identity is not sent).
- OpenStreetMap Foundation (UK): the tiles of the map in the parent app (requested map area and the parent phone's IP address). A commercial provider may be used in a later version and will be named here.
- Cloudflare, Inc. (USA), public DNS resolver: on Android only while Web protection is on, the child phone's website lookups and IP address are subject to Cloudflare's own privacy policy (the network protection and hosting connection Cloudflare runs for us is covered by the processor agreement above). With only Visited sites on, the lookups go to the phone's usual resolver and Cloudflare does not receive them.
We do not share data with anyone else unless the law requires it.
Retention and deletion
Data is kept while the account is active. You can delete your account in the app or at /account/delete. When the last parent of a family deletes their account, the family data, including all child data, is deleted. A minimal unlink record (random device id and a verifier) may be kept until the offline child device acknowledges deletion, at most 12 months. Turning an activity history off stops collection and the phone deletes its local copy; withdrawing the related consent deletes the stored entries at once. The periods are:
| Data | Retention period | Basis |
|---|---|---|
| Account data (email, name, password hash, language, sessions) | While the account exists; deleted when you delete the account | Performance of the contract; KVKK art. 7, GDPR arts. 5(1)(e) and 17 |
| Child profile, device and rule state | Until you delete the child or the family; device state is deleted when the device is unpaired | Providing the service; KVKK art. 7 |
| Location points | 8 days; deleted within 30 days after the consent is withdrawn, at once on request | Parent's explicit consent; KVKK art. 7, GDPR art. 17(1)(b) |
| App-usage and screen-time reports | 90 days; deleted within 30 days after the consent is withdrawn, at once on request | Parent's explicit consent; KVKK art. 7, GDPR art. 17(1)(b) |
| Activity history (visited sites, YouTube) | Each entry 30 days after the event; at once when the related consent is withdrawn | Parent's explicit consent; storage limited to the purpose (KVKK art. 4/2-d) |
| Web protection blocked-lookup counts | While the consent is active + 30 days | Parent's explicit consent |
| Alerts, including SOS and safe-zone alerts | 90 days | Protection of life and physical integrity; providing the service |
| Product interaction (raw events) | 90 days; then anonymous aggregates only | Legitimate interest |
| Crash data (parent and kids apps, Sentry) | 90 days | Legitimate interest |
| Consent and acceptance records (random user id, scope, text version, dates) | Account life + 3 years after deletion, reduced to a minimum | Proof of lawful processing; KVKK arts. 5/2-ç and 5/2-f, GDPR art. 7(1) |
| Marketing notification preference and its consent record | Stops when you turn it off; the consent record 3 years after it ends | Law 6563 and the Regulation on Commercial Communication art. 13 |
| Your requests about your data and our answers | 3 years | Duty to answer and prove it (KVKK art. 13) |
| Support emails ([email protected]) | 2 years after the last contact | Performance of the contract and support |
| Export files | Deleted after 24 hours | Fulfilling the right of access and portability |
| Device unlink record (random device id and verifier) | Until the offline device acknowledges deletion, at most 12 months | Legitimate interest |
| Subscription, invoice and accounting records | 10 years (Turkish Commercial Code art. 82); tax documents at least 5 years (Tax Procedure Law art. 253) | Legal obligation; KVKK art. 5/2-ç, GDPR art. 6(1)(c) |
Backups are encrypted, kept in Türkiye, follow the same periods and age out after at most 30 days. Data whose period has ended is deleted or anonymised.
Security
Data travels encrypted (HTTPS). Passwords are stored as hashes. Access to the servers is limited to authorised persons at Analiz35 and protected by keys. We keep a written information-security program and review it at least once a year.
Your rights
You can access, correct, export and delete your data, object to processing based on legitimate interest, restrict processing, and withdraw a consent at any time without affecting earlier processing. Parents exercise these rights for their children. Data export is requested in the app, and the file is downloaded in the app once it is ready; it includes the activity history still stored. You may complain to the Turkish Personal Data Protection Board or to the data protection authority of your country. See "How to apply" below for the channels and deadlines.
How to apply
To exercise your rights under KVKK art. 11 and the GDPR, apply to us through one of these channels (Turkish Communiqué on the Procedures and Principles of Application to the Data Controller):
- Email: [email protected], from the email address registered in your Hami account.
- Post: Analiz35, Bahriye Üçok Mah. 1843/3 Sok. No: 4E, Karşıyaka / İzmir, Türkiye, in writing and signed (registered mail or through a notary).
- KEP (Turkish registered e-mail): our KEP address will be published here once it is available and will also accept applications.
Your application must contain: your name and surname; your signature if it is on paper; for Turkish citizens the T.C. identity number, otherwise your nationality and passport number or identity number if you have one; your residential or business address for notifications; your email address and phone number, if any, for contact; and what you request. Attach any information or documents about the request. If you live outside Türkiye, enough information to identify you is sufficient; we ask for more only if we have reasonable doubts about your identity. For applications sent from the email address registered in your account, that is usually enough to confirm who you are.
For your child: applications about a child's data are made by a parent or guardian with parental responsibility, on the child's behalf. Say that the request concerns a child linked to your account. Children may also write to [email protected] themselves, in a way suited to their age.
We answer as soon as possible and at the latest within 30 days, in writing or electronically (for requests under the GDPR the period is one month, which we may extend by up to two months for complex requests, telling you why). Applying is free of charge; only if the answer itself causes a cost may we charge the fee set in the tariff of the Turkish Personal Data Protection Board. If we refuse a request, we give the reasons in writing. If you find our answer insufficient or receive none in time, you may complain to the Turkish Personal Data Protection Board within 30 days of learning our answer and in any case within 60 days of your application (KVKK art. 14); a complaint to the Board requires that you applied to us first. If you live outside Türkiye, you may also contact your country's data protection authority.
You do not need an application to delete your account, export your data or withdraw a consent: do these directly in the Hami app (Settings > Privacy); account deletion is also available at /account/delete.
Changes
We publish a new version date when this policy changes materially and tell you in the app. The Privacy Notice and this policy never require your approval; the Terms of Use require acceptance when they change materially, and the Child Data Consent Text requires a new consent when it changes materially.
Website category lists
Hami's website categories on Android use the UT1 blacklist by Université Toulouse Capitole (https://dsi.ut-capitole.fr/blacklists/), licensed under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). Hami reformats the lists (normalised, de-duplicated, compressed) and shares the result under the same licence. Hami stores the daily count of blocked lookups and, when the Visited sites history is on (Hami Pro), the domain names the phone looked up, for 30 days, as described above. It never stores full web addresses or page content.