Privacy Policy

Effective date: October 18, 2026

This policy explains how the Android app AutoGest handles your information.

The short version

The app works fully offline. It does not request the Internet permission, so it cannot send anything to us or to anyone else.
We have no servers, no accounts, no advertising and no analytics SDKs.
The Accessibility service only reads the screen and acts while a script you started, scheduled or set to run on a notification is running, while you record actions, or while you pick a point or an element or crop an image on screen. Screen content is processed on your device; only what you save into a script is kept, and it is never sent to us.
When you record typing, every key tap is saved — including in password fields. Anyone who has that script can tell what you typed, so do not share it (see section 1).
Notification access (only if you use the “Wait & detect notification” action or “Run on notification”) reads notifications from the apps you choose, only while a script with that action is running or a trigger is on. Notifications are read on your device and never sent anywhere (see section 2).
Everything you create (scripts, images, schedules, triggers, run history) is kept in the app’s private storage on your phone and is removed when you uninstall the app.
Only install AutoGest from Google Play. “Mod” or “cracked” copies on other websites are not made by us and can misuse Accessibility access to steal your data (see section 9).

1. Accessibility service (AccessibilityService API)

AutoGest lets you build or record automation scripts: sequences of taps, swipes, text input and other actions that the app replays for you. To do this it uses Android’s Accessibility service. You must turn the service on yourself in the system Settings, after reading an in-app disclosure that explains what it does. When it is on, the app:

Reads the content shown on screen — text, content descriptions and positions of elements in the app in front of you — to find text for a “Click text” step or a “text” condition, and to know where the on-screen keyboard is. While you record typing, it reads the text field you are typing into to recognize what you typed; while a “Type characters” step runs, it reads that field again to check the typing came out right.
Reads the layout of the screen for a “Click node” step (Android 11 and newer). When you capture the screen to pick an element, the app reads the tree of elements of the app in front of you so you can choose one; the picked element’s text, description, view ID, class, position in the screen layout (XPath), bounds and app package are saved into the script. While the step runs, the app reads that app’s elements again to find the same one, then taps it.
Takes screenshots (Android 11 and newer) only when you pick a color on screen, freeze the screen to pick a point or an element or crop a template image, or when a script has an image or color step or condition, to compare the screen with the image or color you chose. Screenshots are held in memory only while matching or while you pick on the frozen screen, then discarded; they are never saved to storage. The only part kept is an area you crop yourself as a template image.
Performs actions on your behalf — tap, long press, swipe, scroll, type text, tap keys on the on-screen keyboard, press Back, Home, Recent apps and open the apps you picked — exactly as your script’s steps say.
Records your touches when you use the recorder, or when you record keys for a “Type characters” step, so they can become script steps. Nothing is added to a script until you review and accept it.
Checks whether a new notification is an incoming call, only while a script is running and only if “Stop on incoming call” is on (it is on by default), so the script can stop and leave the phone to you. It looks only at which app posted the notification, its category (for example “call”) and its layout style — never at the caller, the text or anything else in the notification. It also checks whether the phone is ringing. Nothing about calls is stored.

Typing and password fields

When you record real touches and type on the on-screen keyboard, the app saves each key tap: where on the keyboard you tapped, the timing between taps, the size and position of the keyboard and the package name of your keyboard app. It also saves the text it recognized, so you can check it.

In a password field the app does not save the characters, but it still saves every key tap. Replaying those taps types the same password, and anyone who has the script can work out what you typed from them. The review screen and the step card warn you when this happens. Do not record passwords you would not want someone else to have, and do not share or export a script that contains them.

The service does not read the screen, take screenshots or act at any other time: not when no script is running, you are not recording and you are not picking on screen. We do not use the Accessibility service to collect personal or sensitive data, to change your settings behind your back, or for advertising, and we never receive anything it reads. You can turn it off at any time in Settings > Accessibility.

2. Notification access (NotificationListenerService)

This access is only needed for two Pro features:

the “Wait & detect notification” action, which waits for a notification that contains the words you chose (such as “new order”) or for a balance alert from your bank, then reads aloud the part you chose — for example as a payment speaker in your shop;
“Run on notification”, which starts one of your scripts when a notification you chose arrives.

The app only asks for it when you pick a notification for one of these features, after a separate in-app disclosure, and you turn it on yourself in Settings > Notification access. If you do not use them, you do not need it. When it is on:

Reading notifications from the apps you choose. Android passes every notification to an app with this access, but AutoGest only reads the text (title and body) of notifications from the apps you picked (such as a shop app, your bank or the Messages app), and only while a script with that action is running, while a “Run on notification” trigger is on, or while you pick a sample. Notifications from other apps, or that arrive at any other time, are ignored immediately. When the script stops and every trigger is off, the app stops listening.
Picking a sample. While you pick a sample, the notifications currently on your phone are listed so you can choose one and tap the words to look for or the amount; you can also type the words yourself. The script or trigger stores only the app name, the words you picked or typed, words to ignore, the labels in front of the part to read (such as “PS:”, “SD:”, “ND:”) and, for SMS, the sender (such as your bank’s name) — never account numbers, amounts, balances, the names of people who sent you money or the text of the notification.
Reading aloud. The part you chose — the amount (and the balance and note, if you turn them on), or the title, the text or a piece you picked — is spoken by the text-to-speech engine installed on your phone (Google, Samsung…), on the device.
Running a script. When a notification matches a trigger, the app starts the script you chose for it, at most once within the “Don’t run again for” time and only within the hours you set. If the script cannot start, the trigger shows when and why it was missed.

Notifications are read and matched on your device. The text of a notification is never written to logs and nothing is sent anywhere. You can turn this access off at any time in Settings > Notification access.

3. Information stored on your device

The following is saved only in the app’s private storage on your phone. We never receive a copy.

Data	What it contains	Why
Scripts	Script names, steps, screen coordinates, text you want pasted or searched for, the apps you picked to open, and text you typed while recording	To replay your automation
Picked elements	For “Click node” steps: the text, description, view ID, class, position in the screen layout (XPath), bounds and app package of the element you picked (see section 1)	To find and tap the same element again
Recorded key taps	For “Type characters” steps: each key tap’s position on the keyboard and timing, the keyboard’s size and position, your keyboard app’s package name, and the recognized text (left empty for password fields — see section 1)	To tap the same keys again, and to check the result
Template images	A downscaled copy of images you pick with the system photo picker, or an area you crop from the screen yourself (kept at full resolution)	To find that image on screen
Colors	The color of the single pixel you pick for a color step or condition	To wait for that color
Run history	The last 200 runs: script name, start and end time, how the run ended (including runs a trigger missed)	So you can see what ran and whether it succeeded
Schedules	Script, time of day and days of the week you chose	To start scripts at the time you set
Notification samples	For the “Wait & detect notification” action and “Run on notification”: the package and name of each app you chose, the words you picked or typed, words to ignore, the labels in front of the part to read, for SMS the sender, and your reading options (no text of any notification — see section 2)	To recognise later notifications in the same format
Triggers	For “Run on notification”: the script to run, its notification samples, the “Don’t run again for” time, the hours it is active, and when and why it last missed a run	To start the script when a matching notification arrives, and to tell you when it could not
Settings and consent	Your preferences, and the version and time you agreed to the Accessibility disclosure and the notification access disclosure	To remember your choices and show the disclosure again if it changes
AutoGest Pro	Whether the Google Play account on the phone owns Pro, and when Google Play last confirmed it	So scripts that use Pro features keep running when Google Play cannot be reached for a while

4. Permissions and how they are used

Accessibility service Described in section 1.

Notification access Described in section 2. Only needed if you use the “Wait & detect notification” action or “Run on notification”.

Display over other apps Shows the floating control bubble, the run progress banner and the recorder / coordinate picker overlays on top of other apps.

Notifications Shows a notification with Pause and Stop buttons while a script runs, and a “missed schedule” or “missed trigger” notice when a scheduled run or a run on notification could not start.

Alarms & reminders (exact alarms) Starts scheduled scripts on time. Without it the app uses a less precise alarm.

Run at startup Re-arms your schedules after the phone restarts, the app is updated or the time zone changes.

List of launchable apps Shows the apps installed on your phone that have a launcher icon so you can pick one for an “Open app” step or as the recording target. This list is not stored or sent anywhere.

Phone apps When a script starts, finds which apps on your phone show the incoming-call screen (your default Phone app and system call apps), so a call notification from them can be recognized (section 1). Only their package names are used, and they are not stored.

Storage (Android 9 and older only) Saves an exported script file to the Downloads folder when you ask for it. Newer Android versions need no storage permission for this.

For scheduled runs and runs on notification the app may turn the screen on and dismiss a lock screen that has no security (swipe). It never bypasses a PIN, pattern, password or biometric lock; in that case the run is skipped and you get a notification instead.

5. What we do not collect

The app does not collect, transmit, sell or share any personal data. It has no Internet permission, no user accounts, no advertising, no analytics or crash-reporting SDKs, and does not access your location, contacts, camera or microphone. It does not request permission to read SMS or the call log; the notification features only read notifications from the apps you choose, as described in section 2. It does not request the phone state permission: stopping on an incoming call works only from the notification check described in section 1, and never learns who is calling.

6. Sharing a script

A script leaves your phone only when you choose to export or share it. The exported .autoscript file contains the script’s steps — including recorded key taps and text you typed while recording — and any template images it uses. Check a script before you share it, and never share one that contains a password or other private text. You pick where it goes (Downloads folder, a messaging app, email…), and that destination’s own privacy policy applies. Importing a file someone sent you only reads that file. A “Wait & detect notification” action only carries the app name, the words and labels of the sample and, for SMS, the sender, never the text of a notification. A “Click node” step carries the attributes of the element you picked (section 1).

7. Google Play

The app is distributed through Google Play. Depending on your device settings, Google may collect crash and performance reports (Android vitals) and share aggregated statistics with us through the Play Console.

AutoGest Pro is sold as an in-app purchase through Google Play Billing. Payment is handled entirely by Google Play; we never see your payment details. The app only receives from Google Play a signed record of whether your account owns Pro, checks it on your device and keeps the result there (section 3). Pro belongs to your Google account, so reinstalling from Google Play or moving to a new phone with the same account restores it for free.

Google’s processing is covered by Google’s Privacy Policy.

8. Retention and deletion

Data stays on your phone until you delete it. You can delete scripts, schedules and history inside the app, clear everything with Settings > Apps > AutoGest > Storage > Clear data, or uninstall the app. Because we hold no copy of your data, there is nothing for us to delete on our side.

9. Security

Your data is kept in the app’s private storage, which Android isolates from other apps. The app has no network access, so it cannot leak your data over the Internet.

Only install AutoGest from Google Play. We do not publish the app anywhere else. Copies offered on other websites as “mod”, “cracked” or “Pro unlocked” are not made by us and are not covered by this policy. Because such a copy asks for the same Accessibility access, a malicious one can read everything on your screen — including messages, passwords and banking codes — tap and type on your behalf, and send that data away. If you installed AutoGest from anywhere other than Google Play, turn off its Accessibility service, uninstall it and install it again from Google Play.

10. Children

The app is not directed at children under 13 and does not knowingly collect information from anyone, including children.

11. Changes to this policy

We may update this policy when the app changes. The effective date above will change with each update. If the Accessibility service or notification access starts reading new kinds of data, the app will show the matching disclosure again and ask for your consent before continuing.

12. Contact

Questions or requests about this policy: automatedgestures@gmail.com