AndroMate — Privacy Policy

Device management & automation agent — package com.kam.andromate

Effective date: 2026-07-05 · Last updated: 2026-07-05

What AndroMate is. AndroMate is an enterprise Mobile Device Management (MDM) and automation agent. It is installed as a Device Policy Controller (Device Owner) on Android devices that are owned and/or explicitly managed by an operator (for example, an organization managing its own device fleet, test devices, or dedicated automation devices). AndroMate is not a consumer application and is not intended for covert monitoring of individuals. Management only occurs after clear disclosure and consent shown on the device.

Contents 1. Who we are 2. Scope & nature of the service 3. Data we access and why 4. Sensitive permissions explained 5. Accessibility Service disclosure 6. How we use data 7. Sharing & disclosure 8. Notice & consent 9. Data retention 10. Security 11. Your rights 12. Children 13. Changes to this policy 14. Contact

1. Who we are

This application is provided by AndroMate (“we”, “us”, “AndroMate”). This policy explains what information the AndroMate agent accesses on a managed device, why, how it is used, and the choices available. It applies to the Android application identified by the package name com.kam.andromate.

The party that deploys AndroMate onto a device (the “Operator”) is the controller of the data processed on that device. AndroMate acts on the Operator’s behalf to manage and automate the Operator’s own devices.

2. Scope & nature of the service

AndroMate is a legitimate device-management tool. It is provisioned as a Device Owner only on devices that:

are owned or lawfully controlled by the Operator, and
are enrolled through an explicit provisioning process (e.g. QR provisioning, ADB, or an enterprise enrollment channel), and
display a disclosure and consent screen the first time the agent runs.

AndroMate keeps a visible app icon and shows a persistent notification while it is active, so the device user is always aware that the device is managed.

3. Data we access and why

Depending on the automations configured by the Operator, AndroMate may access the following categories of data. We access only what is required to perform the management and automation tasks the Operator has configured.

Data	Why it is accessed
SMS messages (read, receive, send)	To run SMS-based automation and testing workflows (e.g. sending a message, reading a received code) defined by the Operator.
Approximate & precise location	To run location-based automation and to report the location of the managed device to the Operator.
Screen content & input (Accessibility, Screen capture)	To perform UI automation (tapping, reading on-screen elements) and remote screen streaming/control of the managed device.
Installed applications (package list)	To manage apps — check whether an app is installed, launch, install, update or remove apps on the managed device.
Device & network information (device ID, model, hardware, connectivity, phone state)	To identify the managed device, report its status, and route management commands to it.
Automation results & logs	To report the outcome of workflows back to the Operator’s server.

We do not collect data unrelated to device management, and we do not use collected data for advertising or profiling.

4. Sensitive permissions explained

Permission	Purpose
`SEND_SMS`, `READ_SMS`, `RECEIVE_SMS`	SMS automation/testing tasks configured by the Operator.
`ACCESS_FINE_LOCATION`, `ACCESS_COARSE_LOCATION`, `FOREGROUND_SERVICE_LOCATION`	Location automation and managed-device location reporting.
`BIND_ACCESSIBILITY_SERVICE`	UI automation (reading/acting on on-screen elements) — see section 5.
`FOREGROUND_SERVICE_MEDIA_PROJECTION`	Screen capture / remote screen streaming for management.
`REQUEST_INSTALL_PACKAGES`, `QUERY_ALL_PACKAGES`	Application management (install/update/remove, query installed apps).
`SYSTEM_ALERT_WINDOW`	Display management overlays where required by a workflow.
`RECEIVE_BOOT_COMPLETED`, `FOREGROUND_SERVICE`, `WAKE_LOCK`	Keep the management agent running reliably on the managed device.
Device Administration / Device Owner	Apply management policies (e.g. lock, silent app install, configuration) on the Operator’s devices.

5. Accessibility Service disclosure

AndroMate uses Android’s Accessibility Service solely to perform UI automation on the managed device — for example, reading on-screen content and simulating taps to execute the automation workflows configured by the Operator. The Accessibility Service is not used to collect data for advertising, and its use is disclosed to the user through the in-app consent screen before it is enabled.

6. How we use data

To execute the automation and management tasks configured by the Operator.
To report device status and workflow results to the Operator’s AndroMate server.
To maintain the reliability and security of the management agent.

We do not use the data for any purpose other than providing the management and automation service to the Operator.

Data processed by AndroMate is transmitted only to the Operator’s own AndroMate server that controls the device. We do not:

sell personal data;
share data with third-party advertisers or data brokers;
transmit data to any destination other than the Operator’s configured backend.

Operator-only access. Each automation workflow is cryptographically identified and scoped to the Operator that created it. As a result, only that Operator can execute or read their own tasks on their own devices. The AndroMate platform provider or administrator cannot execute tasks on, or read task data from, an Operator’s managed devices — this isolation is enforced by the signature attached to each workflow.

We may disclose data if required by law, or to protect the security and integrity of the service.

On first launch, AndroMate displays a disclosure and consent screen that lists the capabilities it uses (SMS, screen, location, application management, automation) and links to this policy. The agent proceeds only after the user acknowledges and consents. A persistent notification remains visible while the agent is active, and the app icon stays visible. Consent is stored with a timestamp.

9. Data retention

Operational data (workflow results, device status, logs) is retained by the Operator on their AndroMate server according to the Operator’s own retention practices. On the device, AndroMate stores only the data needed for its current operation and the record of consent. When the device is un-enrolled or the agent is removed, local management data is cleared.

10. Security

Communication between the agent and the Operator’s server uses encrypted transport (HTTPS/TLS). Locally stored sensitive values are protected using the platform’s standard mechanisms. Access to management functions requires the agent to be an authorized Device Owner on the Operator’s devices.

11. Your rights

Because AndroMate processes data on behalf of the Operator, requests to access, correct, or delete personal data should be directed to the Operator that manages the device. Where we act as controller, you may contact us using the details in section 14. Depending on your jurisdiction, you may have rights to access, rectify, erase, or restrict processing of your personal data.

12. Children

AndroMate is an enterprise device-management tool and is not directed to children. It is not intended to be installed on devices used by children as a consumer product.

13. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the “Last updated” date above, and, where appropriate, by re-displaying the in-app consent screen.

14. Contact

For any question about this policy or your data, contact:

Email: support@andromate.net
Entity: AndroMate