Last updated: June 2026
Automator is an advanced, comprehensive macro engine and automation platform that allows users to build, execute, and manage fully customized workflow sequences on their Android devices. The app replaces dozens of single-purpose utility tools by integrating system gestures, hardware triggers, and cross-app workflows into a consolidated, zero-root automation ecosystem.
We enforce a strict offline-first architecture. We do not collect, store, upload, or share any personal data, usage metrics, or system information.
All configurations, automation scripts, logs, variables, and database records reside exclusively within the application’s secure local storage on your device.
No data ever leaves your device unless you explicitly configure an automation step to transmit a specific payload (e.g., via a custom HTTP request designed by you).
To provide cross-app automation and execution of user-defined workflows, the app requires access to several sensitive Android frameworks. Every permission is utilized strictly in real-time to execute your explicit instructions.
Automator utilizes the AccessibilityService API to programmatically interact with the device UI. This includes:
This framework operates solely when a macro is running and does not log keystrokes, monitor active background behavior outside of active macro rules, or capture credentials.
Automator complies with modern Android scoped-privacy standards. The app does not request or declare broad file system access permissions (such as MANAGE_EXTERNAL_STORAGE or READ_EXTERNAL_STORAGE). Instead, data access is strictly sandboxed and user-controlled:
.json or .zip macro packages) strictly through standard system intents (ACTION_OPEN_DOCUMENT_TREE, ACTION_OPEN_DOCUMENT). Persistent access is maintained entirely locally using secure, user-authorized URI permissions (takePersistableUriPermission).filesDir / getExternalFilesDir), meaning they are entirely inaccessible to other applications.Location data is processed strictly in real-time and entirely offline. The app accesses location in the background solely to evaluate user-configured geofencing triggers (e.g., executing a macro when entering or leaving a specified geographic area). We do not track, map, or retain historical location logs.
Automator contains modules for interacting with cellular features, which execute only if the device has physical telephony hardware:
SEND_SMS, READ_SMS, RECEIVE_SMS): Used strictly to trigger macros upon receiving a specific SMS message, or to programmatically send automated notifications based on your rules.CALL_PHONE, ANSWER_PHONE_CALLS, READ_PHONE_STATE): Used to detect incoming/outgoing call states to act as macro triggers, or to automate hands-free call handling within your workflows.READ_CONTACTS, WRITE_CONTACTS): Accessed only to look up contact names or manage records when executing user-configured communication macros.READ_CALENDAR, WRITE_CALENDAR): Used to check scheduled events as macro entry conditions or to automate the creation/modification of appointments.QUERY_ALL_PACKAGES) solely to populate user configuration menus, allowing you to select specific target apps for launching, automated context switching, or termination.REQUEST_INSTALL_PACKAGES, REQUEST_DELETE_PACKAGES), the app can bridge user-triggered automation steps to launch the native package installer or uninstaller dialogs, requiring manual verification by the user at runtime.The app monitors incoming system notifications purely to act as a trigger mechanism, allowing macros to fire automatically when specific text patterns or apps post a notification.
BIND_DEVICE_ADMIN): Used exclusively to invoke the system force-lock action when executing a screen-lock macro step.WRITE_SETTINGS): Used to automate basic system toggles (such as display behavior, brightness, or connectivity profiles) exactly as defined in your macro steps.The app accesses various hardware features purely to bridge them into automation workflows:
Automator does not include third-party analytics SDKs, advertising networks, or tracking frameworks. If you choose to utilize the optional Design-Time AI Assistant or Local Data Parsing features, text/visual prompts are sent directly to your designated API providers (such as OpenAI or Anthropic) via their official endpoints using API keys securely stored in your local encrypted storage. These interactions are user-initiated at design-time and are governed entirely by the privacy policies of those respective providers.
This application is designed for developer and power-user automation utilities; it is not directed at children under the age of 13, and we do not knowingly interact with or collect data from minors.
For technical queries regarding local permission enforcement or this policy, please reach out to us at: support.logicnexus@gmail.com