Legal
Privacy policy
Easymatic has no server. There is no account to create, nothing is collected about you, and no data is sent anywhere except to destinations you configured yourself.
Last updated 30 August 2026.
The short version
- There is no sign-up, no login and no user account.
- There is no analytics SDK, no crash reporting, no advertising and no advertising identifier. None at all, not an optional one.
- The developer operates no server and receives no data from the app. Ever.
- Your macros, your run history and your credentials stay on the device. Credentials are encrypted with a key held in the device's hardware keystore, which cannot be exported.
- Data leaves your phone only when a macro you built tells it to, and only to an address you entered.
Where data can go
Easymatic is an automation app, so sending data somewhere is a thing you can build. Every destination below is one you set up. None of them belongs to the developer, and nothing is sent to any of them until a macro of yours runs a node that does so.
- An AI provider you choose
- Anthropic, OpenAI, Google, OpenRouter, or any OpenAI-compatible server you run yourself. Receives the prompt a macro sends, and — depending on the node — a photo or screenshot, or a recording from the microphone. Your API key is sent to authenticate the request.
- Your Home Assistant
- Receives the service calls your macros make, and sends back the entity states they read. Authenticated with a token issued by your own instance.
- Your MQTT broker
- Receives whatever your macros publish, and delivers the topics they subscribe to.
- Your mail server
- IMAP and SMTP, for the mail trigger and the mail action. Message bodies and your mailbox credentials go to the server you named and nowhere else.
- Your Philips Hue bridge
- On your local network only. Never leaves the LAN.
- Any address an HTTP node points at
- The Make HTTP Request and Open URL nodes send exactly what you configured them to send, to exactly the address you typed.
- Google Maps and Google Play services
- The map in the place editor loads tiles from Google. Geofences are registered with Play services location, which is how they keep working while the app is closed. Google's own privacy policy governs both.
- Google ML Kit
- Translation and language detection run on the device. The models they use are downloaded from Google the first time they are needed.
- Google cloud backup
- Android's automatic backup is enabled, so your macros are included in your device backup if you have that turned on. Stored credentials are sealed with a key that cannot leave the device, so they are unreadable anywhere else.
The permissions that need explaining
Easymatic asks for a lot, because an automation app can only react to what it is allowed to see. Every one of these is optional, every one is requested when you first build a macro that needs it, and the app tells you what it is for before Android asks.
- Accessibility service
- Optional, and off until you turn it on. Android exposes three things nowhere else, and they are the only reasons this service exists: starting a macro from a hardware key, starting one from a swipe across the fingerprint reader, and the screenshot action. It does not read window content. Easymatic is not built for users with disabilities and does not declare itself an accessibility tool.
- Notification access
- Optional, and off until you turn it on. It lets a macro react to notifications other apps post — the message and notification triggers, replying to a chat, and knowing a call is ringing. Sender and text are matched against the filters you configured, in memory, on the device.
- Location, including in the background
- Used by the geofence trigger and the location value. Background access is what lets "when I get home" fire while the app is closed; without it a geofence macro simply never runs. Your position is compared against the places you saved and is not sent anywhere unless a macro you built sends it.
- SMS
- Incoming messages are matched against your SMS trigger nodes. Outgoing messages are sent only by an action you placed on a canvas. Easymatic does not read your message history — it holds no permission that could.
- Contacts, calendar, photos, camera, microphone
- Each is requested only when a node that needs it runs, and used only for that node. A contact is resolved to dial or message it; a calendar is read or written by the calendar nodes; a photo is read by the image nodes; the camera and microphone are used by the nodes that capture from them.
- Device administrator
- Optional, and requested for one policy only: being told that a screen unlock failed, which is what the failed-login trigger fires on. It grants no other administrative power. While it is enabled Android will not let the app be uninstalled, so turn it off first if you want to remove Easymatic.
Other apps on your phone
Two features cross the boundary to another app, and both are gated by you. Aplugin is a separate app that contributes its own nodes; it can only be reached after you enable it in Settings, and it receives only the values the node you placed hands it. The process API lets another app start one of your macros; every calling app has to be approved by you the first time it asks, and you can withdraw that at any time.
Children
Easymatic is not directed at children and is not designed for use by them.
Changes to this policy
If the app gains a new destination or a new sensitive permission, this page changes in the same release. The date at the top is when it last did.
Contact
Questions, or a correction to this page:open an issue on the project's GitHub, where the whole app is open source under the MIT licence.