Privacy Policy
- We collect only what the features need: screen-time figures, app names, location (when location sharing is on), battery level and phone model from the child's phone, and the names and rules you enter on the parent's phone.
- We never collect messages, calls, contacts, photos, files, passwords or keystrokes, camera, microphone, screen content or browsing history.
- The app is always visible on the child's phone, shows a permanent notification and lets the child see what is shared.
- No ads. We do not sell data. We share data only with Google, which hosts the service for us.
- Location points are deleted after 30 days. You can delete your whole family account in the app at any time.
1. Who we are
Parental Control App is developed and published by Anar Məmmədli, an independent developer publishing as Malikoglu (malikoglu.az). In this policy, “we” and “us” mean the developer. We are responsible for the personal data processed through the app (the “controller” under data protection laws such as the EU and UK GDPR).
Contact for any privacy question: [email protected].
2. How the app works
The same app is installed on two kinds of phones. At first launch you choose a role:
- Parent mode, on the phone of a parent or legal guardian. The parent adds a child, sets rules and sees the child's screen time, location and requests.
- Child mode, on the child's phone. It is connected to the family with a 6-digit pairing code created in the parent's app (valid for 10 minutes). Before anything is shared, the child's phone shows a “What is shared” screen. The app stays visible, shows a permanent notification (“Parental Control is on”) and lets the child open “See what your parent can see” at any time.
Accounts. When the app is opened for the first time, it creates an anonymous account with Firebase Authentication. No email address or phone number is needed. A parent may link a Google account so they can sign in again on a new phone; in that case we receive the name and email address of that Google account. A second parent can join the family with an invite code and gets their own account.
3. Data we collect
From the parent's phone
| Data | Details | Purpose |
|---|---|---|
| Account ID | A random user ID created by Firebase Authentication. | Sign-in; keeping each family's data separate. |
| Google account (optional) | Name and email address, only if you link a Google account. | Signing in again on another phone; support. |
| Display name | The parent name shown in the family, for example “Parent: Anar” on the child's phone. | Showing who manages the phone. |
| Children | Each child's name or nickname, age group (6–8, 9–12, 13–15, 16–17) and chosen avatar. | Showing and managing each child. |
| Rules | Daily and weekend limits, bedtime, school hours, pause, per-app limits, blocked and always-allowed apps, extra time given. | Applying the rules on the child's phone. |
| Places | Places you save, such as Home and School: name, position on the map and radius. | Arrival and departure alerts. |
| Family codes | Pairing codes and invite codes for a second parent. | Connecting a child's phone or a second parent. |
| Subscription status | Which plan is active and its renewal state, as reported by Google Play. We never receive your payment card details. | Unlocking Premium features. |
From the child's phone
| Data | Details | Purpose |
|---|---|---|
| Account ID | A random, anonymous user ID created by Firebase Authentication. No name, email or phone number. | Linking the phone to the family securely. |
| Phone model | For example “Pixel 7”. | Telling devices apart. |
| App usage | Minutes spent in each app per day, with app names and package names, and daily totals. Counted on the phone with Android's usage access. We do not see what happens inside apps. | Limits, “Time left today”, charts, top apps and the weekly report. |
| Installed apps | The list of apps that can be opened from the home screen (names and package names). | Letting the parent choose app limits, blocked and always-allowed apps. |
| Location | Location points (coordinates, accuracy and time), only when location sharing is on. They are collected when the parent refreshes the map, to build today's route and to detect arrival at or departure from saved places, including when the app is closed or not in use. | The parent's map, route and place alerts. |
| Battery and status | Battery level, last seen time and whether the four permissions are granted. | Showing whether protection works. |
| Requests | “More time” requests: minutes asked for and, if chosen, the app. | Letting the parent approve or decline. |
| Events | Short notes such as “limit reached”, “arrived at Home” or “usage access was turned off”. | Notifying the parent. |
From both phones
- Notification tokens. Firebase Cloud Messaging tokens, so that we can deliver notifications, for example a “more time” request to the parent.
- Technical connection data. When the app connects to Firebase, Google processes technical data such as the IP address to deliver the service. We do not store IP addresses in our database.
- Data kept only on the phone. The role, language and a copy of the current rules are stored locally on the phone so that rules work offline. Android backup is turned off for the app.
The app contains no advertising or analytics SDKs and does not use the Android advertising ID.
4. Data we never collect
- Messages, calls, call logs and contacts
- Photos, videos and files
- Passwords or anything typed on the keyboard
- Camera, microphone or the content of the screen
- Browsing history and notifications from other apps
- What happens inside other apps (we only count time)
The app does not request access to the camera, microphone, contacts, SMS, call logs, photos or files, and does not use accessibility services, device administrator rights or notification access.
5. How we use data
- To provide the features: applying rules on the child's phone, showing screen time, location and requests to the parent, and sending notifications.
- To manage accounts, the family and subscriptions.
- To answer support requests.
- To keep the service secure, for example to prevent misuse of pairing codes.
- To meet legal obligations.
We do not use data for advertising, profiling or selling, and we do not use it to train AI models. Rules are applied automatically on the child's phone exactly as the parent sets them (for example, the “Time is up” screen); there is no other automated decision-making.
6. Legal bases
Where the EU or UK GDPR or similar laws apply, we rely on these legal bases:
- Parent's data — performance of a contract (GDPR Art. 6(1)(b)): we need it to provide the app and the subscription you asked for.
- Child's data — consent of the parent or legal guardian (Art. 6(1)(a)), given when the parent pairs the child's phone with a code from the parent's account and the “What is shared” screen is shown on the child's phone. We also rely on the legitimate interest of the parent in the child's safety and wellbeing (Art. 6(1)(f)). We balance it by collecting only the data listed above, informing the child on their own phone and never collecting content.
- Location — consent, through Android's location permission on the child's phone and the location-sharing setting in the parent's app. It can be withdrawn at any time by turning location sharing off or removing the permission (the parent is notified).
- Security and abuse prevention — legitimate interests (Art. 6(1)(f)).
- Legal obligations (Art. 6(1)(c)), for example answering lawful requests from authorities.
Withdrawing consent does not affect processing that happened before.
7. Children's data
The app is made for parents and legal guardians. The child mode exists so that a parent can apply family rules openly, with the child's knowledge.
- Parental consent. Child mode can only be connected with a pairing code created in a parent's account. Entering that code on the child's phone is the step by which the parent authorises collection; the child sees the “What is shared” screen at the same moment.
- Data minimisation. From the child's phone we collect only the data in section 3. We do not ask the child for an email address, phone number or any other contact details. The child cannot publish content; the only thing a child can send is a “more time” request.
- No ads, no profiling. Child data is never used for advertising or marketing. Subscriptions can only be bought in parent mode.
- Transparency for the child. The app keeps its icon and a permanent notification, and the child can open “See what your parent can see” at any time.
- Parent's control. A parent can review the child's data in the app, unlink the child's phone, delete the whole family account in the app, or ask us by email to delete a child's data. Uninstalling the app from the child's phone stops collection immediately.
- United States (COPPA). We collect information from a child's phone only after a parent sets it up with a code from their own account. Parents can review their child's information, have it deleted and refuse further collection at any time, as described above. We do not require a child to provide more information than the features need.
- If we learn that a child's phone was connected without the authority of a parent or legal guardian, we will delete the related data.
Older children and teenagers can also contact us directly at [email protected] with questions about their data.
8. Who we share data with
- Your family. Parents in the family, including a second parent you invite, see the children's data. The child's phone shows the parent's display name and the rules.
- Google, as our service provider (processor). Firebase Authentication, Cloud Firestore and Firebase Cloud Messaging host and deliver the service, Google processes this data on our behalf under the Firebase and Google Cloud data processing terms.
- Map tiles. The map on the parent's phone is drawn with MapLibre using map tiles from OpenFreeMap (map data © OpenStreetMap contributors). To load the tiles, the parent's phone connects to OpenFreeMap's servers, which see the phone's IP address and the map area being viewed — never the child's location points or any account data.
- Google Play processes subscription payments as an independent controller under the Google Privacy Policy.
- Authorities, only if the law requires it or to protect the safety of a person.
- If the app is ever transferred to another developer, this policy continues to apply to your data and we will tell you beforehand.
We do not sell or rent personal data and do not share it with advertisers or data brokers.
9. Where data is stored
The family database (Cloud Firestore) is stored in Google Cloud's European multi-region eur3 (Belgium and the Netherlands). Firebase Authentication and Firebase Cloud Messaging are global Google services and may process data in the United States and other countries. For transfers outside the EEA and the UK, Google relies on safeguards such as the European Commission's Standard Contractual Clauses.
10. How long we keep data
| Data | Kept for |
|---|---|
| Location points | 30 days, then deleted automatically. |
| App usage figures | Today's figures and a rolling history of recent days (currently the last 14 days) for charts and the weekly report. Older days are overwritten. |
| Installed apps, battery, phone model, last seen | Replaced with each update; deleted with the child's profile or the family account. |
| Requests and events | As long as the family account exists. |
| Pairing codes | Usable for 10 minutes and only once. |
| Account, family, children, rules, places | Until you delete the family account. |
| Support emails | As long as needed to help you, and no longer than 12 months after the conversation ends. |
When data is deleted, it is removed from the live database right away. Copies may remain in Google's internal backup and replication systems for a limited period until they are overwritten.
11. Deleting data
- In the app: in parent mode, open Account → Delete account. This deletes the family, all children's profiles and their data (app usage, app lists, location history, requests, events), rules, places and your account.
- Unlink a device: the parent can unlink a child's phone; it then stops sending data to the family.
- Uninstall on the child's phone: collection stops immediately.
- By email: write to [email protected] or use the form on the Delete account page. We complete requests within 30 days.
12. Security
- All data is encrypted in transit (TLS) and encrypted at rest by Google Cloud.
- Database security rules allow access only to members of the family. A child's phone can write only its own status and requests and cannot change the rules.
- Pairing codes expire after 10 minutes and work only once.
- We do not store passwords; sign-in is handled by Firebase Authentication and Google.
No system is perfectly secure. If a data breach affects you, we will inform you and the authorities as the law requires.
13. Your rights
Depending on where you live, you have the right to access your data, correct it, delete it, receive a copy (portability), restrict or object to processing, and withdraw consent. You can also complain to the data protection authority in your country.
To use these rights, email [email protected]. We answer within 30 days and may ask you to confirm that you own the account. A parent or legal guardian exercises these rights for a child's data.
California and other US states: we do not sell personal information and do not share it for cross-context behavioural advertising.
14. Permissions on the phones
| Permission | Phone | Why |
|---|---|---|
| Usage access | Child | To count the time spent in apps. |
| Location, including background location | Child | The child's phone collects location data to enable the live map, today's route and arrival/departure alerts for places, even when the app is closed or not in use. |
| Display over other apps | Child | To show the “Time is up” screen when a limit is reached. |
| Notifications | Both | Time reminders and the permanent status notification on the child's phone; requests and alerts on the parent's phone. |
| Foreground service, start at boot | Child | To keep the rules working, with a visible notification, also after the phone restarts. |
| Internet | Both | To sync rules and status with the family. |
Each child-phone permission is explained on screen before Android asks for it. If a permission is turned off later, the parent is notified.
15. Changes to this policy
If we change this policy, we will update the date at the top. If the changes are significant, we will tell you in the app or in the Google Play listing before they take effect.
16. Contact
Anar Məmmədli (Malikoglu), independent developer
Email: [email protected]
Website: malikoglu.az