Updated October 29, 2026
This policy describes the Android application Smart Auto Clicker Pro, package com.best101blogger.smartautoclicker.
Smart Auto Clicker Pro uses Android AccessibilityService only after a prominent in-app disclosure and your explicit action in Android Settings. The service performs taps, long presses, waits, and swipes that you configure. It does not request accessibility window content, inspect the accessibility node tree, read screen text, capture passwords, or independently decide what to click. Automation is scoped to the target app you select and stops on protected system/security windows, target-app changes, device lock, permission loss, cancellation, or configured limits.
Overlay permission is used to show visible Pause/Resume/Stop controls while automation runs. The app will not start automation without this permission. You can revoke it in Android Settings.
Gesture plans, target coordinates, timing settings, preferences, and locally saved profiles are stored in private app storage. Automatic Android backup is disabled. Clearing app storage or uninstalling removes local data. Debug builds may keep a bounded local diagnostic event log and sanitized stack information; debug diagnostics do not record screen contents, typed text, passwords, or target coordinates and are shared only when a tester explicitly invokes Android sharing.
The modern Studio can create or sign in to an optional account through the app's Cloudflare Worker and Supabase Auth. If you choose cloud features, the service processes your email address, user ID, authentication/session information, profile names, gesture-plan configuration that you choose to sync, preferences, and entitlement status. Passwords are sent over HTTPS to the authentication service for verification and are not stored in the app's profile database or diagnostic log. Session tokens are encrypted with Android Keystore before local storage.
A legacy owner/testing account screen can also use Appwrite Cloud for owner authentication and server-managed owner/premium labels. This path is not required for ordinary local automation.
Premium purchases use Google Play Billing. The app queries Google Play for localized product/offer information and purchase state. When restoring or completing a purchase, the app sends the product ID, purchase type, and Google Play purchase token over HTTPS to the Smart Auto Clicker Pro backend for server-side verification with the Google Play Developer API. Raw purchase tokens are not written to the billing event database; the server stores a cryptographic hash and verification metadata for audit/fraud-prevention purposes. Pending purchases do not unlock Premium until Google Play confirms payment.
The Free experience uses Google AdMob banner advertising. Google may process advertising/device identifiers, network/device information, approximate location signals, and ad interactions according to Google's services and configuration. Smart Auto Clicker Pro integrates Google's User Messaging Platform (UMP) and checks consent eligibility before requesting ads. Premium users do not receive the app's free-tier banners. Debug builds use Google's official test ad identifiers.
A signed-in user can choose Settings → Delete Cloud Account in the app. A browser deletion option is also available at Delete Account. Deletion removes the Supabase account and associated cloud profiles, cloud preferences, and entitlement record through database cascade rules. Local profiles remain on the device until app data is cleared or the app is uninstalled. Google Play purchase records remain with Google and are governed by Google Play; deleting the app account does not itself cancel an active Play subscription.
Local data remains until you clear app data or uninstall. Cloud data remains until account deletion, except minimal billing-verification event records may retain hashed purchase-token references and non-secret verification metadata for security/audit needs. Network traffic uses HTTPS. Cloud database access is protected by row-level security, and entitlement/billing writes are server-controlled.
Depending on the features you use, data may be processed by Google Play/AdMob/UMP, Cloudflare, Supabase, and the legacy Appwrite owner-authentication service. Their respective privacy terms apply to their processing.
See the Support page for troubleshooting, privacy resources, and account deletion. A public developer support/privacy email must be added to this page and the Google Play listing before production publication; no email address is invented or embedded by this project.