1. App and developer
This policy covers Auto Clicker for Android, developed by BeasonApps, package com.beasonsapp.autoclicker, and this policy website. Auto Clicker lets you configure and run taps, long presses, swipes, waits and optional button conditions. You do not need an account.
2. Information used on your device
- Your tasks: task names and IDs; action coordinates, areas, timing and repeat settings; your selected app name and package; and any button text or resource IDs you enter as conditions.
- Preferences: language and whether optional button recognition is enabled.
- Latest run report: task name and ID, start and finish times, completed actions and cycles, and the completion or stop reason.
These records are stored as local app data, including task JSON, in Android app-private storage. The target-app picker reads the names and package IDs of launchable apps on your device to let you choose a target; it does not upload that list. Basic execution diagnostics, such as timing, counts, action types and the target package, may be written to Android system logs. The app does not log the text it reads from accessibility nodes.
3. Accessibility service and your control
You choose whether to enable the Android accessibility service. It performs the system gestures you configure, provides the floating toolbar and bubble, and lets you pause, resume or stop a task. Ordinary coordinate tasks use foreground app package and window-event metadata to enforce an optional app restriction; they do not read the accessibility node tree.
Button recognition is off by default. After a separate in-app agreement, a condition task must specify a target app and button text or a resource ID. While that task is active in its target app, the service temporarily reads visible, enabled UI nodes and their text and resource IDs to find the condition, then clicks the matching control or a clickable ancestor. When both text and ID are supplied, both must match. Node text is processed in memory for this purpose, not saved as a screen history or sent to BeasonApps. The text or ID you enter as a condition remains part of your saved task.
Paused tasks and tasks waiting for another app do not scan nodes. Returning to the target app requires you to resume explicitly. You can stop with the floating controls, turn off button recognition in the app, or disable Auto Clicker in Android accessibility settings.
4. Screens, sensitive information and permissions
The app does not capture or record other apps’ screens, and uses no screenshot service, OCR or screen-upload feature. The glass navigation effect samples only a small strip of Auto Clicker’s own views in memory; it does not capture other apps or retain an image.
Auto Clicker does not request access to your contacts, photos, camera, microphone or location. No account credentials are required or uploaded. Avoid putting passwords or other sensitive information in task names, matching conditions or support messages. Android may expose personal text in a target app’s accessibility nodes, so use recognition only where you want the app to match a control.
6. Security
Local records use Android app-private storage and platform access controls. The app has Android backup disabled (allowBackup=false) and provides no cloud-sync feature. This website is served over HTTPS. These measures reduce exposure but cannot guarantee the security of a compromised device or information you choose to share with others.
7. Retention and deletion
- Saved tasks and preferences: stay on your device until you change or delete them, clear the app’s storage in Android settings, or uninstall the app.
- Latest run report: is replaced by the next finished or stopped run. Deleting a task does not separately erase its existing latest report; clearing app storage or uninstalling removes that app-held report.
- Live node data and navigation samples: are temporary in-memory data, not saved recordings. Android controls the lifetime of system diagnostic logs.
We do not maintain a server copy of your local tasks to delete or restore. Website request and security data follow Cloudflare’s retention practices. Support messages follow WhatsApp’s controls and the copies held by recipients; leaving the group, deleting a message or uninstalling Auto Clicker does not guarantee removal from every recipient. Ask a support administrator about information you voluntarily sent to BeasonApps; we will address requests concerning copies we control.
8. Your choices and privacy requests
You can edit or delete tasks in the task library, disable button recognition, and withdraw accessibility access in Android settings. To remove all app-held records, clear Auto Clicker’s storage or uninstall it. There is no Auto Clicker account to delete. For access, correction or deletion questions about support information you shared, use the contact channel below. Do not send your local task data just to request deletion; it is not stored on our servers.
9. Children
Auto Clicker is not directed to children aged 13 or younger. We do not ask users for their age or create child accounts. Local task data is not uploaded. If you believe a child has shared personal information in the support group, contact a group administrator so we can address copies under our control.
10. Changes and contact
We may update this policy when the app or our data practices change. The date at the top identifies the latest version.
For privacy questions or requests, contact BeasonApps through the WhatsApp support group. Begin with a brief request for a support administrator and avoid posting sensitive details in the group. Joining or using this external service is optional.