Privacy Policy — Geofence Detection
Last Updated: 15-Aug-2026
This Privacy Policy describes how Kanetik ("we", "us", "our") handles information in Geofence Detection, a Tasker condition plugin for Android. We value your privacy and are committed to transparency about our data practices.
Geofence Detection is a paid app, purchased once on Google Play. It does not display advertisements, does not offer in-app purchases, does not process payments itself, and does not require you to create an account or sign in.
Location, in Plain Terms
Geofence Detection is a location app, so this is the first thing you should know:
- The places you set as geofences stay on your device. The coordinates, radius, and name of each geofence you create are stored in a local database on your phone and are never transmitted to us.
- We never receive your device's position. The app does not send your current or historical location anywhere. It does not build a location history.
- The monitoring itself is done by Google Play services on your device. The app hands your geofence definitions to Android's Geofencing API, which is part of Google Play services already installed on your phone, and that system tells the app when you cross a boundary. This is how geofencing works on Android; it is the only way to have the operating system watch a boundary efficiently in the background.
- Approximate location is still listed on our Data Safety form, and here is the honest reason. The app uses Firebase Analytics, and Firebase derives a coarse, city-or-region-level geography from the IP address your device uses to reach Google's servers — as it does for any app using Analytics. That is unrelated to the location permission and unrelated to your geofences, but it is location data, so we declare it rather than claim "location never leaves the device". You can switch this off; see "Your Choices" below.
Background Location
Geofence Detection requests the "Allow all the time" location permission (ACCESS_BACKGROUND_LOCATION). This is required, and here is exactly why: a Tasker profile built on a geofence has to fire whether or not you happen to be looking at your phone. Without background location, Android will not deliver boundary crossings while the app is closed, and the plugin refuses to register any geofence at all rather than pretend to work.
Background location is used for one purpose only: detecting when your device enters, leaves, or dwells inside a geofence you created. It is not used for advertising, profiling, analytics, or any other purpose, and the resulting position is not stored as a history or transmitted off the device.
What Information We Collect
Information You Provide
- Geofence definitions: The name, coordinates, radius, transition type, and dwell time you set for each geofence. Stored locally; see below.
- Support requests: If you contact us for support — by email at support@kanetik.com, or through a support link in the app — you provide your email address and a message so we can respond. To help us troubleshoot, a support message may include basic device and app information such as the device model, Android version, and app version. Anything else you include is up to you; we ask only for what is needed to reproduce the problem, and we do not need your geofence coordinates.
Information Collected Automatically
- Analytics: We use Firebase Analytics to understand which conditions people actually configure and whether background monitoring is working. The events we send are deliberately limited to fixed categories and ranges — for example, that an "enter" condition was configured, and that its radius fell in a range such as 100–500 m. Coordinates and geofence names are never sent, and the radius is reported as a range rather than an exact figure precisely because an exact radius helps narrow down a place. Firebase Analytics also collects standard device and usage information as described in Google's privacy policy.
- Approximate location: As described above, Firebase Analytics derives coarse IP-based geography. We collect no location ourselves.
- Crash and diagnostic data: We use Firebase Crashlytics to identify crashes and errors. A crash report includes the stack trace, device model, Android version, app version, and a short trail of recent warning-level log messages. These messages are filtered so that they carry no coordinates and no geofence names.
- Identifiers: Firebase Analytics and Crashlytics generate their own installation-scoped identifiers (an Analytics app instance ID, a Firebase installation ID, and a Crashlytics installation UUID) so that events and crashes from the same install can be counted together. These are reset if you clear app data or reinstall. Geofence Detection does not collect an advertising ID — the advertising-ID permission is explicitly removed from the app.
- Permission state: We record whether the background location permission is granted or denied, as a property attached to the above analytics. A denied background permission means geofencing is doing nothing at all, and we would otherwise read that as a bug. It records only "granted" or "denied".
Information Stored Locally on Your Device
The following data is stored only on your device and is not transmitted to us or to any third party:
- Geofences: For each geofence, the name you typed, its latitude and longitude, its radius, the transition it watches (enter, exit, or dwell), its dwell time, whether your device is currently inside it, and when it was created and last updated.
- Condition configuration: The settings you choose for each Tasker condition. Tasker also stores a copy of this configuration in its own profile data as part of how plugins work; that copy is governed by Tasker's own privacy practices.
- Analytics preference: Whether you have turned off usage data and crash reporting.
Google Maps
The configuration screen shows a Google Map so you can pick a geofence location visually. Displaying that map requires the Google Maps SDK to fetch map imagery from Google, and those requests necessarily tell Google which part of the map is being displayed. This happens only while you have the configuration screen open, and it is Google acting as the map provider — the coordinates you save are not sent to us. Google's handling of these requests is described in Google's privacy policy.
How We Use Your Information
We use the information described above to:
- Detect geofence entry, exit, and dwell events so Tasker conditions can be evaluated
- Respond to your support requests
- Identify and fix crashes and bugs
- Understand which conditions are used and whether background monitoring is being established successfully
Geofence Detection does not display advertisements, does not sell or share your personal information, and does not use your data for advertising, profiling, or to train any artificial intelligence or machine learning model.
Data Sharing
We do not sell, rent, or trade your personal information to third parties. We share data only with the service providers listed below, and only as necessary to operate the app:
- Firebase (Analytics, Crashlytics) — Google Privacy Policy
- Google Play services (Geofencing API, on your device) and Google Maps SDK (map imagery in the configuration screen) — Google Privacy Policy
- Legal requirements: We comply with valid legal requests from law enforcement authorities and will provide information we are obligated to under law.
Third-Party Automation
Geofence Detection is a plugin for Tasker. Tasker asks the plugin whether a condition is currently satisfied, and the plugin answers satisfied, not satisfied, or unknown. Coordinates are not passed to Tasker as part of that answer. Your Tasker configuration and any data Tasker itself collects are governed by Tasker's own privacy policy.
Data Backup
The app's local data, including your saved geofence coordinates, is included in Android's standard cloud backup and device-to-device transfer, which is encrypted by Google and tied to your Google account. This means your geofences can be restored to a new device rather than re-entered by hand. If you would rather your geofence locations never leave the device at all, you can disable backup for this app in Android Settings.
Data Retention and Deletion
- Local data (geofences, condition configuration, preferences) is retained on your device until you delete the geofence, uninstall the app, or clear app data.
- Support request data is retained as long as necessary to resolve your request and may be kept for reference.
- Analytics and crash data is retained according to Firebase's standard retention policies.
You can delete all locally stored data at any time by clearing the app's data in Android Settings or by uninstalling the app; this also unregisters your geofences from Google Play services. To request deletion of any data we may hold externally, such as support request history, contact us at privacy@kanetik.com.
Your Choices
- Analytics and crash reporting: Open Geofence Detection from your app launcher and turn off "Share anonymous usage data". This disables both Firebase Analytics and Crashlytics collection, including the IP-derived approximate location described above. It is on by default and your choice is remembered across app updates.
- Permissions: You can revoke location access at any time through Android Settings. Revoking background location stops geofence monitoring entirely.
- Cloud backup: You can disable Android's cloud backup for this app from your device's backup settings, which keeps your geofence coordinates off Google's backup servers.
Permissions
- Precise and approximate location: Required to register geofences and detect boundary crossings.
- Background location ("Allow all the time"): Required for geofences to fire while the app is closed, which is the entire point of a Tasker geofence profile. See "Background Location" above.
- Receive boot completed: Re-registers your geofences after the device restarts, so your Tasker profiles keep working.
- Internet: Added by the Firebase and Google Maps SDKs, and used only to send analytics and crash reports and to load map imagery in the configuration screen.
Security
- All network communication uses HTTPS
- The app does not require or collect any account credentials
- Geofence coordinates and names are stored only on your device, and are filtered out of crash reports before they are sent
Children's Privacy
Geofence Detection is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us at privacy@kanetik.com and we will delete it promptly.
Data Breach Notification
In the unlikely event of a data breach that affects your personal information, we will notify affected users as promptly as practicable and take steps to mitigate any harm.
Your Rights
You have the right to:
- Access the personal information we hold about you
- Correct any inaccurate information
- Delete your personal data (see Data Retention and Deletion above)
- Request a copy of your data in a portable format
To exercise any of these rights, contact us at privacy@kanetik.com. We will respond within the timeframe required by applicable law, and we will not discriminate against you for exercising any of these rights.
Legal Bases for Processing (EEA & UK)
If you are in the European Economic Area or the United Kingdom, we rely on the following legal bases under the GDPR and UK GDPR:
- Legitimate interests (Art. 6(1)(f)) — to provide, maintain, secure, and diagnose the app's core geofence detection functionality, to fix crashes, and to understand usage through analytics, which you can disable in the app.
- Consent (Art. 6(1)(a)) — where you grant location and background-location permission, which you can withdraw at any time in Android Settings; and where you contact us for support and provide your email address and message.
- Legal obligation (Art. 6(1)(c)) — to comply with valid legal requests.
In addition to the rights listed above, EEA and UK users have the right to restrict or object to processing, the right to data portability, and the right to lodge a complaint with a supervisory authority — your national data-protection authority in the EEA, or the UK Information Commissioner's Office (ICO) in the United Kingdom.
U.S. State Privacy Rights
Geofence Detection serves no advertising and collects no advertising identifier, so we do not "sell" or "share" personal information as those terms are defined by the California CCPA/CPRA or by other U.S. state privacy laws. Note in particular that your precise geolocation — sensitive personal information under the CPRA and several other state laws — is never collected by us; it stays on your device. If you are a resident of California, Virginia, Colorado, Connecticut, Utah, Oregon, Texas, Montana, Delaware, Iowa, Indiana, Kentucky, Maryland, Minnesota, Nebraska, New Hampshire, New Jersey, Rhode Island, Tennessee, Florida, or another state with a comprehensive consumer-privacy law, you may confirm whether we process your personal data and may access, correct, delete, or obtain a portable copy of it. The categories we collect are device and diagnostic data (crash reports and analytics), installation-scoped identifiers, coarse IP-derived geography, and — only if you contact us — the email address and message you provide. To exercise these rights, or to appeal a decision if we decline a request, contact privacy@kanetik.com.
Data Controller and Privacy Contact
Kanetik is the data controller responsible for the personal information described in this policy. We have not appointed a statutory Data Protection Officer; privacy@kanetik.com is the designated point of contact for all data-protection inquiries and requests.
Contact Us
If you have questions about this Privacy Policy or believe your privacy has been affected, contact us at:
Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on our website. We encourage you to review this policy periodically.