Privacy Policy — Computer Detection for Tasker
Last Updated: 04-Nov-2026
This Privacy Policy describes how Kanetik ("we", "us", "our") handles information in Computer Detection for Tasker. The product has three parts, and this policy covers all of them:
- the Android app, a Tasker condition plugin;
- the Windows companion, from the Microsoft Store, and the Mac companion, which you install on your own computer;
- the relay, a small service we run that passes messages from a computer to the phones paired with it.
None of them displays advertisements, and none requires you to create an account or sign in.
In Plain Terms
- It is for your own computer. You install the companion on a computer you use and pair your phone with it by scanning a code the companion shows. Your Tasker profiles can then react to whether you are using that computer. Do not install it on a computer someone else uses without their knowledge. The companion always lists the phones it is shared with, by name.
- What the companion reads: how long since the keyboard or mouse was last used, whether the computer is locked, when it goes to sleep or shuts down, and the process name of the app in front, such as "outlook". It does not read window titles, document or file names, web addresses, keystrokes, or anything on the screen.
- What it sends is encrypted end to end. The companion encrypts each update on the computer. Only the phones that scanned the pairing code hold the key to read it. The relay passes the update on but cannot read it.
- What the relay can see is when a computer sends an update, and two unencrypted markers on each one. From those it can tell when something changed that the phone should hear about quickly, and when a computer goes to sleep, shuts down or stops reporting, but not which change it was. It cannot see which app is in front or how long the computer has been idle. See "What the Relay Stores and Sees" below.
- You can cut phones off at any time. Disconnect removes one phone from the computer's list until it scans the code again or taps Reconnect; Reset pairing on the computer locks every phone out until you pair again.
The Companion Apps (Windows and Mac)
What the companion reads on your computer
- Idle time: the time since the last keyboard or mouse input, as the operating system reports it, rounded to steps of minutes.
- Lock, sleep and shutdown: whether the screen is locked, and when the computer goes to sleep, shuts down or you sign out.
- The app in front: the process name of the foreground app, for example "outlook" or "chrome". Never the window title, so it does not see which document, email or web page is open.
The companion uses no administrator rights, input hooks, screen recording or accessibility access to do this.
What the companion sends
- Each update holds the items above and is encrypted on the computer before it is sent, padded to a fixed size so its length reveals nothing. It goes to the relay over HTTPS and from there to your paired phones.
- The companion also sends requests that keep the pairing working, such as a periodic check-in. Each is signed with a key that never leaves your computer.
- The companion sends no analytics and no crash reports, and contacts no server but the relay. The help and privacy links in it open in your web browser.
What the companion stores on your computer
- The pairing: its keys and the computer's display name. On Windows they are encrypted for your user account with Windows' data protection. On Mac they are kept in your login keychain, on that Mac only and not synchronised to iCloud.
- Settings: such as whether to start when you sign in.
The pairing code
The code the companion shows, as a QR code or as text, contains the pairing's ID, its key and the computer's display name. Anyone who sees it can read that computer's updates until you use Reset pairing, so the companion shows it only when you ask or are pairing, hides it again after two minutes, keeps it out of screenshots and screen sharing, and clears a copied code from the clipboard after a minute. The computer's name travels only inside this code; the relay never receives it.
What the Relay Stores and Sees
The relay runs on Google Firebase (Cloud Functions, Cloud Firestore and Firebase Cloud Messaging) in a project used only for this product.
What it stores, for each pairing
- a random pairing ID;
- the public half of the computer's signing key, and a key that paired phones use to sign their requests;
- for each paired phone, its Firebase Cloud Messaging token (the address used to deliver messages to that phone), which the relay can read; and its name, encrypted so the relay cannot read it;
- the most recent encrypted update, its sequence number, and when the computer was last heard from;
- a short one-way hash of each phone you disconnected on the computer, so it is not let back in unless it scans the code again or taps Reconnect;
- the previous public key after a Reset pairing, and timestamps and counters used to prevent replayed requests and abuse.
The relay holds no key that can read an update or sign one as your computer.
What it can see
- Timing: when each update and check-in arrives.
- Two unencrypted markers on each update. One marks updates that should reach the phone quickly: coming online, locking or unlocking, a change in idle time, or a new app that has stayed in front for a minute. The relay cannot tell which of these it was. The other marks the last update before sleep, shutdown, signing out or quitting the companion. So the relay can infer when something changed on a computer, and when it stopped reporting.
- IP addresses: like any web service, the relay receives the IP address of each computer and phone that contacts it, and Google Cloud records it in standard request logs. We use these logs only to operate the relay and protect it from abuse. They are kept for Google Cloud's default log retention period, currently 30 days.
Messages to your phone
The relay delivers updates to your phones through Firebase Cloud Messaging. A message that cannot be delivered expires after 28 days.
The Android App
What it stores on your phone
The following is stored on your phone and is not transmitted to us, except as described under "What it sends".
- Pairings: for each computer, its keys (encrypted under a key held in your phone's secure hardware), its name or the name you gave it, its latest state, and when that state began and when the computer was last in use.
- Recent apps: the names of apps the computer has reported in front, so you can pick them when you set up a condition.
- Condition configuration is stored by Tasker, as part of how plugins work, and is governed by Tasker's own privacy practices.
- A random install token that the app writes into each condition you save, so that only conditions saved through this app can read your computers' state.
- Settings: the offline alert and your analytics choice.
What it sends
- To the relay: your phone's Firebase Cloud Messaging token, which the relay can read because it needs it to deliver messages to your phone; and your phone's device name, encrypted so that only your paired computers and phones can read it. The computer shows that name in its list of phones.
- Analytics: we use Firebase Analytics. The app sends no events of its own about your computers, their names, their state or their apps. Firebase collects its standard usage and device information, as described in Google's privacy policy.
- Approximate location: Firebase Analytics derives a coarse, city-or-region-level location from the IP address your phone uses to reach Google's servers. The app requests no location permission and sends no location of its own. You can switch this off; see "Your Choices".
- Crash and diagnostic data: we use Firebase Crashlytics. A crash report includes the stack trace, device model, Android version, app version, and a short trail of recent log messages.
- Identifiers: Firebase generates installation-scoped identifiers so that events and crashes from one install can be counted together. They are reset if you clear app data or reinstall. The app does not collect an advertising ID; that permission is removed from it.
Scanning the pairing code
The app scans the code with Google Play services' code scanner. The app is not given camera access; the camera is used by Google Play services on your phone, and only the scanned text is handed to the app.
Tasker
When a condition is checked, the app answers satisfied, not satisfied or unknown, and gives Tasker the variables %pcname, %pcstate, %pcapp and %pcidle: the computer's name, its state, the app in front and its idle minutes. What Tasker does with them is governed by Tasker's own privacy policy.
How We Use Your Information
- To pass your computer's state to the phones you paired with it, and tell those phones when the computer goes silent
- To keep the relay running and protect it from abuse
- To respond to your support requests
- To identify and fix crashes and bugs, and understand how the Android app is used
We do not sell or share your personal information, and we do not use it 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. We share data only with the service providers below, and only as necessary to operate the product:
- Google Firebase (Cloud Functions, Cloud Firestore, Cloud Messaging, Analytics, Crashlytics) — Google Privacy Policy
- Google Play services (the code scanner, on your phone) — Google Privacy Policy
- Microsoft Store, which installs and updates the Windows companion and collects its own data about installs and updates — Microsoft Privacy Statement
- Legal requirements: we comply with valid legal requests and will provide information we are obligated to under law. Your computer's encrypted updates cannot be read by us, so we cannot provide their contents.
Data Backup
The Android app's pairing keys are excluded from Android's cloud backup and device-to-device transfer, so a backup cannot be used to read your computer's updates. The install token and settings are included in that backup, which is encrypted by Google and tied to your Google account, so your saved Tasker conditions stay valid on a restored or new phone once you scan each computer's code again. You can disable backup for this app in Android Settings.
Data Retention and Deletion
- On your phone and computer: kept until you forget a computer in the app, reset the pairing, clear the app's data or uninstall it, except as noted for the Mac below.
- On the relay: a pairing's record is kept while the pairing exists, and we do not currently delete inactive pairings automatically. Reset pairing on the computer removes every phone's token and name and the last update from the relay; what remains is the random pairing ID, the new keys and the previous public key, and timestamps and counters used to prevent replayed requests and abuse; none of these identifies you. Disconnecting a phone on the computer removes that phone's token and name, and keeps a short hash of it, so it is not let back in unless it scans the code again or taps Reconnect. Forgetting a computer in the Android app removes your phone's token and name from that pairing.
- Deleting the Mac companion leaves its pairing in your login keychain, under "com.kanetik.computer-detection". Use Reset pairing first, or delete that item in Keychain Access.
- Uninstalling the Windows companion deletes its keys from the computer but does not reset the pairing on the relay. Your phones will show the computer as offline. Use Reset pairing before uninstalling if you want them cut off straight away.
- Request logs are kept for Google Cloud's default retention period, currently 30 days.
- Analytics and crash data are kept according to Firebase's standard retention policies.
- Support request data is kept as long as needed to resolve your request and may be kept for reference.
To have a pairing's record deleted from the relay, or any other data we hold, contact us at privacy@kanetik.com.
Your Choices
- Analytics and crash reporting: in the Android app, open Settings and turn off "Share usage analytics". This stops Firebase Analytics and Crashlytics collection, including the IP-derived approximate location described above. It is on by default, and your choice is remembered across updates.
- Who can see your computer: the companion lists every phone it is shared with. Disconnect one, or use Reset pairing to lock all of them out.
- Notifications: you can turn the app's notifications off in Android Settings.
- Cloud backup: you can disable Android's cloud backup for this app in your device's backup settings.
Permissions
Android app
- Internet: to reach the relay and receive your computers' updates, and to send analytics and crash reports.
- Notifications: for the optional alert when a computer has not been seen for a while, and to tell you when saved conditions need to be set up again on this install.
Windows and Mac companions
- No special permissions; the Mac companion asks to show notifications. On Windows the companion runs as a normal app for your user account and can start when you sign in, which you can turn off in the app or in Windows Settings.
Security
- Your computer's updates are encrypted end to end with AES-256-GCM. The relay cannot read them.
- Every request the computer sends is signed with a key that never leaves it, so neither the relay nor anyone who sees the pairing code can send updates as your computer.
- All network communication uses HTTPS.
- The product requires no account and collects no credentials.
Children's Privacy
Computer Detection for Tasker 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:
- Performance of a contract (Art. 6(1)(b)) — to relay your computer's state to the phones you paired with it, which is the service you asked for.
- Legitimate interests (Art. 6(1)(f)) — to keep the relay running and secure, to fix crashes, and to understand how the Android app is used through analytics, which you can turn off in the app.
- Consent (Art. 6(1)(a)) — 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
Computer Detection for Tasker 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. 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 and messaging tokens, coarse IP-derived geography, IP addresses in request logs, the timing of your computer's updates, which reveals when its state changed and when it stopped reporting, and — only if you contact us — the email address and message you provide. The contents of your computer's updates are encrypted and cannot be read by us. 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:
- Privacy: privacy@kanetik.com
- Support: support@kanetik.com
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.