Legal

AntiTap Privacy Policy

zeroemdashes (Bojan Gasparovic) · Effective 2026-10-02

AntiTap stores its settings, your picked apps and your lock count on your device. zeroemdashes has no access to any of that data.

AntiTap uses Firebase Analytics to record usage events, such as when a lock starts and ends and how it was unlocked. These events never contain what is on your screen, what you type, or anything about the person holding the phone. AntiTap never sends the names of the apps on your phone or of the apps you pick for Tight Lock.

Section 1

Who we are

zeroemdashes is an independent software publisher operated by Bojan Gasparovic. This privacy policy applies to AntiTap: Toddler Touch Lock for Android (package com.zeroemdashes.antitap).

Section 2

What data AntiTap collects

2a. Data stored locally on your device

The data the app needs to work stays on your device. zeroemdashes has no access to it.

What is stored	Where	Why
Your settings (active lock mode, how to lock and unlock, what is blocked while locked, Snark's position on the screen)	On-device DataStore	So the app remembers your choices
Whether Tight Lock shows Snark in all apps or in your own list, and the apps on that list	On-device DataStore	So Snark appears where you chose
How many locks you have used, whether you bought the full app, and an early-user mark	On-device DataStore	So the app knows which features you have

None of this information is uploaded to any server, except the counts and labels described in Section 2b. Uninstalling the app removes all of it.

2b. Analytics events sent to Firebase

AntiTap sends usage events to Firebase Analytics (Google LLC).

Every event is a count, a duration or a fixed category label. No event ever includes what is on your screen, text you type, photos, audio, video, your contacts, your location, or any information about the person holding the phone.

The events fall into five groups:

Setup. Which lock mode screens are opened, which permissions are requested and granted, and which mode is turned on.
Locking. When a lock starts and ends, what started it (for example the Snark button or a shake), how it was unlocked, how long it lasted, how many taps and button presses it blocked, and whether a call was on.
Lock reliability. Whether a lock was broken (for example the locked app left the screen), whether Android stopped the lock, and a once-daily check that the lock mode still works on your phone.
Purchases. When the upgrade screen is shown, when a purchase is started, and whether it completed or failed, with any failure reason recorded as a category label.
Settings. Which setting was changed, and its new value.

AntiTap also sets a small number of user properties, which Firebase attaches to later events so that usage can be grouped by state. These record, for example, the active lock mode, whether each mode is ready, the number of picked apps, whether the phone has a fingerprint or face unlock, and the app version. Each is a count or a fixed category label.

This section describes the categories of data collected rather than naming every individual event. The specific events may change from one release to the next, but they will remain within the categories and limits described here. If that ever ceases to be true, this policy will be updated and the effective date changed, as described in Section 9.

In addition to these custom events, Firebase Analytics automatically collects certain data from every app that uses its SDK: a Firebase Installation ID (a pseudonymous per-device identifier that can be reset), device model, operating system version, device language, country (derived from IP address by Google), app version, and session-level events such as first open and session duration.

Advertising ID collection is disabled. The google_analytics_adid_collection_enabled key in AndroidManifest.xml is set to false, which prevents the Firebase SDK from reading the Google Advertising ID (GAID) on Android. The GAID is not collected.

Section 3

Permissions

Display over other apps (Light Lock). AntiTap uses it to show the Snark button and the lock layer on top of the app your toddler is using. It reads nothing from the app underneath.

Accessibility (Tight Lock, optional). Android describes this permission as full control of your phone. AntiTap uses it only to cover the whole screen, to block the back, Home, Recents and volume buttons, to close the notification shade, and to see which app is in front so it can show Snark where you chose and bring the locked app back. The service is set up so it cannot read screen content (canRetrieveWindowContent is false). It does not record keys or text. Before Android's accessibility settings open, AntiTap shows its own explanation and asks you to continue.

Installed apps. To build the list of apps you can pick for Tight Lock, AntiTap asks Android which apps are installed, using a declared list of app types rather than access to every app. The list never leaves your device.

Notifications. Light Lock shows a notification with a Lock button while it is ready. AntiTap also uses notifications to tell you if a lock mode stopped working.

Fingerprint and face unlock. When you hold the padlock to unlock, AntiTap asks Android to show its own fingerprint or face prompt. AntiTap receives only a yes or no. Your fingerprint and face data stay inside Android and are never available to AntiTap.

Motion sensor and call state. AntiTap reads the motion sensor only while Snark is showing, to detect the shake that locks the screen. It reads the phone's audio mode to tell whether a call is on. It never reads who is calling, never records audio, and needs no microphone or phone permission for this.

Start at boot. AntiTap starts its lock mode again after the phone restarts. A restart always ends any lock that was on.

You can revoke any of these permissions at any time in Android Settings. The lock mode that needs it stops working; the rest of the app is unaffected.

Section 4

Third-party services

AntiTap uses two third-party services, both from Google.

Service	Operator	Data received	Purpose
Firebase Analytics	Google LLC	Firebase Installation ID, device model, OS version, language, country, app version, session data, the custom events and user properties described in Section 2b	Usage analytics, lock reliability and purchase measurement
Google Play Billing	Google LLC	Handled by Google Play when you buy the full app. zeroemdashes receives a purchase confirmation, never your payment details.	Processing the one-time purchase

Firebase Analytics is governed by Google's privacy policy and the Firebase Data Processing and Security Terms. Google processes this data as a data processor on zeroemdashes's behalf, not as an independent data controller. Purchases are governed by the Google Play terms of service and Google's privacy policy.

The app also uses the following open-source libraries, all of which run entirely on your device and transmit no data:

DataStore(Google/AndroidX)local settings storage
WorkManager(Google/AndroidX)the once-daily check
Biometric(Google/AndroidX)fingerprint and face prompt
Hilt(Google)dependency injection framework
Jetpack Compose(Google/AndroidX)user interface

Section 5

Children's privacy

AntiTap is made for parents, and only an adult sets it up and unlocks it. While a lock is on, a child may tap the screen, but AntiTap only counts the blocked taps and button presses. It records nothing else about the child: no images, no audio, no touch positions, no names and no ages.

AntiTap is not directed at children under 13 and we do not knowingly collect personal information from children. If you have a concern, contact support@zeroemdashes.com.

Section 6

Data retention

Data stored on your device stays until you change it in the app or uninstall the app. Uninstalling removes all data the app stored on your device.

Google retains Firebase Analytics event data according to the retention settings configured for the Firebase project (the default is two months for user-level data and fourteen months for aggregate reporting). zeroemdashes does not independently control Google's server-side retention beyond those project-level settings. Existing event data already transmitted to Firebase cannot be individually deleted by zeroemdashes, but you may contact support@zeroemdashes.com to initiate a deletion inquiry.

Section 7

Your rights

For locally stored data, your rights of access, rectification, erasure, and portability are satisfied directly: you can view and change everything from within the app, and uninstalling removes it. For Firebase Analytics data, your rights extend to data held by Google under the Firebase Data Processing and Security Terms. Contact support@zeroemdashes.com and zeroemdashes will coordinate with Google where required.

European Union (GDPR) Processing of locally stored data is carried out on the basis of contract (Article 6(1)(b)), to provide the screen lock you have requested. Processing of Firebase Analytics data is carried out on the basis of legitimate interest (Article 6(1)(f)): confirming that the lock holds on your phone, and measuring how users set up the app and progress through the purchase screen, restricted to counts, durations and category labels. You have the right to object to processing based on legitimate interest by contacting support@zeroemdashes.com. Your full GDPR rights include access, rectification, erasure, restriction of processing, data portability, and the right to object; to exercise any of these, email support@zeroemdashes.com. Firebase Analytics event data is processed by Google LLC, a US-based company, under Standard Contractual Clauses incorporated into the Firebase Data Processing and Security Terms.

California (CCPA) AntiTap does not sell or share personal information for cross-context behavioral advertising, so there is no "Do Not Sell or Share My Personal Information" link. Google LLC processes Firebase Analytics data on zeroemdashes's behalf under a Data Processing Agreement that restricts Google to providing the Firebase Analytics service; under California law this makes Google a service provider, not a third party. The Google Advertising ID is not collected. The categories of personal information collected are identifiers (Firebase Installation ID), internet or network activity (the events and user properties described in Section 2b), and coarse geolocation (country level, derived from IP address). You have the right to know what is collected, to request deletion, and to non-discrimination for exercising these rights. Contact support@zeroemdashes.com.

Section 8

Google Play Store data safety

The data safety section in the Google Play Store for AntiTap reflects what is stated in this policy:

Data collectedApp interactions (the events and user properties in Section 2b), app diagnostics, and device or other IDs (Firebase Installation ID). The Google Advertising ID is not collected.
Data sharedNone. Google processes Firebase Analytics data as a service provider, not shared with other third parties for their own purposes.
Encrypted in transitYes. Firebase Analytics transmits data over HTTPS/TLS.
Data deletionLocally stored data is removed by uninstalling. Firebase Analytics event data is retained by Google per the project's retention settings and cannot be individually deleted by zeroemdashes.
Security practicesNo user account is required. zeroemdashes has no server-side storage of its own. AntiTap reads no screen content.

Section 9

Changes to this policy

This version is effective 2026-10-02. It replaces the first version (2026-10-01): AntiTap no longer offers to share the names of your picked apps, so no app names are ever sent.

If this policy changes in a meaningful way in the future (for example, if additional data collection is added), the effective date at the top of this document will be updated. The updated policy is published at the address linked from the Play Store listing before the change takes effect.

Section 10

Contact

Questions about this policy?

support@zeroemdashes.com

There is no automated system on the other end. You will get a reply from Bojan.