Auto Clicker – Privacy Policy

Auto Clicker Privacy Policy

Last Updated: 2026-05-08

Auto Clicker (the “App”) is an app that provides automatic clicking and automatic scrolling features. This Policy explains, with reference to personal information-related laws and regulations applicable in the Republic of Korea and Google Play policies, the matters directly handled by the App operator and the information that third-party SDKs may process.

The App does not provide user registration and does not separately request information used to identify users, such as name, email address, or phone number. However, users may directly enter names for saved data, and device-level identifiers generated by the App or server, as well as reward verification information, may be processed to provide App features, serve advertisements, improve App quality, verify storage slots based on rewarded advertisements, and prevent misuse or abuse.

Where external providers such as Google, Microsoft, and Cloudflare process information in accordance with their own policies, each provider’s privacy policy and settings tools also apply. Inquiries and requests related to personal information directly processed by the App operator will be reviewed based on this Policy and the relevant laws and regulations of the Republic of Korea.

1. Information Directly Processed by the App Operator

1) Accessibility Service and Automation Settings

- Items processed: Coordinates designated by the user on the screen, automatic tap and swipe settings, and setting values required to run automation

- Purpose of processing: To provide the App’s core feature of performing taps and swipes at locations directly designated by the user

- Method of processing: The information is stored on the user’s device. The App does not read or collect sensitive personal information such as screen text, passwords, payment information, or message contents through the Accessibility Service.

2) Local Storage Information

- Items processed: Automation settings, saved configuration data, names of saved data, language and App settings, advertising/analytics consent status, number of rewarded slots and related cache data, server credential information such as deviceId and deviceToken, App policy cache, and settings files that the user directly chooses to import or export

- Purpose of processing: To maintain App settings, maintain storage slot status, manage consent status, cache App policies, and back up and restore settings selected by the user

- Method of processing: The information is stored in AsyncStorage, SecureStore, device storage, or a document location selected by the user.

3) Developer-Operated Server Communication Information

- Items processed: Platform, package name, policy lookup scope, hashed values of deviceId and deviceToken, rewardRequestId, adUnitId, placement, reward processing status, reward quantity, request time, expiration time, update time, reward grant time, failure reason, daily reward count, and general access information such as IP address, User-Agent, and request time

- Purpose of processing: To check the minimum supported version and whether a mandatory update is required, check whether rewarded advertisements are allowed, verify the results of rewarded advertisement viewing, process storage slot rewards, prevent duplicate rewards and misuse or abuse, and maintain service stability

- Method of processing: The information is processed on a backend operated by the developer based on Cloudflare Workers + D1. The deviceToken itself is not stored on the server and may be stored as a hashed value. This information is not used as a member account or real-name-based identification system.

2. Third-Party Advertising and Analytics Tools

The App includes the following third-party SDKs to serve advertisements and improve App quality. These SDKs may process relevant data for advertising, analytics, security, prevention of fraudulent use, and service improvement, even where such information is not directly collected by the App operator.

1) Google Mobile Ads / Google AdMob

- Purpose: To serve advertisements, measure advertising performance, prevent fraudulent advertising activity, and comply with advertising-related policies

- Information that may be processed: Advertising ID, IP address, approximate location, device information, App interactions, operating system information, and information related to ad requests

- Timing and method of processing: During ad requests, ad display, and advertising performance measurement, information may be transmitted through the SDK to Google’s global infrastructure.

- Choice method: Advertising privacy options may be provided in regions where Google requires them, such as the EEA, the United Kingdom, Switzerland, or certain U.S. states subject to relevant regulations. If such options are enabled, users may change them, and users may also change settings through Android advertising settings.

- Reference policy: https://policies.google.com/technologies/ads

2) Firebase Analytics

- Purpose: To analyze usage statistics, analyze screen views, and improve App quality

- Information that may be processed: App usage information, screen views, event information, basic device information, app diagnostic information, automatic events, and similar data

- Timing and method of processing: During App execution, SDK initialization, and use of analytics features to which the user has consented, information may be transmitted through the SDK to Google’s or Firebase’s global infrastructure.

- Consent settings: The App checks the consent status and then applies the consent or collection settings for Firebase Analytics. Custom analytics events and screen view records defined by the App operator are used only when the user has allowed analytics consent in the App settings.

- Note: The Firebase Analytics SDK may process basic App usage information, device information, automatic events, and similar data during App execution and SDK initialization.

- Choice method: Users may allow or withdraw analytics consent in the App settings.

- Reference policy: https://firebase.google.com/support/privacy

3) Microsoft Clarity

- Purpose: To analyze user behavior, improve usability, and improve App quality

- Information that may be processed: App usage information, screen usage flows, user interactions, device and session-related information, and similar data

- Timing and method of processing: If the SDK is initialized after the user has allowed analytics consent, information may be transmitted to Microsoft’s global infrastructure.

- Consent settings: The App activates Microsoft Clarity only when the user has allowed analytics consent in the App settings. If the user withdraws consent, the App calls the function to stop subsequent collection.

- Choice method: Users may allow or withdraw analytics consent in the App settings.

- Reference policy: https://www.microsoft.com/privacy/privacystatement

The retention period, deletion method, and detailed processing locations for information already processed by external providers are governed by each provider’s policies and settings tools. Please contact the relevant external provider.

3. Purpose of Use by Permission

1) Accessibility Service

This is used to provide automation features that perform taps and swipes at coordinates designated by the user. This permission is used only to perform actions at locations directly selected by the user.

2) Display Over Other Apps (System Alert Window)

This is used to display the overlay toolbar and crosshair over other apps so that the user can place coordinates and control the automation status.

3) Foreground Service and Notification-Related Permissions

These are used to maintain the overlay toolbar and crosshair and to allow the user to directly control start, pause, and stop operations while being aware of the automation status. Notifications are used to display the current control status to the user.

4) Network Access

This is used for ad requests, operation of third-party SDKs, App policy lookups, verification of storage slots based on rewarded advertisements, and confirmation of reward processing status.

5) Advertising ID Permission

This is used to serve Google AdMob advertisements, measure advertising performance, comply with advertising-related policies, and prevent fraudulent advertising activity.

4. Cross-Border Processing and Transfer

The App operator’s own server is operated based on Cloudflare Workers + D1 and may process device-level identifiers and reward verification information necessary for service operation. In addition, overseas providers such as Google, Microsoft, and Cloudflare may process relevant data on global infrastructure, including servers located outside Korea such as in the United States, in the course of providing advertising, analytics, and infrastructure services. The following describes the main processing timing and methods to the extent known by the App operator, while specific processing locations, retention periods, and deletion methods are governed by each provider’s policies.

1) Google Mobile Ads / AdMob

- Information that may be processed: Advertising-related data such as IP address, advertising ID, App interactions, device information, and approximate location

- Timing and method of processing: During ad requests, ad display, and advertising performance measurement, information may be transmitted through the SDK to Google’s global infrastructure.

- Purpose: To serve advertisements, measure advertising performance, and prevent fraudulent use

- Choice method: If advertising privacy options are enabled in the App, users may change them, and users may also use Google advertising settings and Android advertising settings.

2) Firebase Analytics

- Information that may be processed: Usage statistics data such as App usage information, screen views, event information, and device information

- Timing and method of processing: During App execution, SDK initialization, and use of analytics features to which the user has consented, information may be transmitted through the SDK to Google/Firebase’s global infrastructure.

- Purpose: To analyze usage statistics and improve App quality

- Choice method: Users may withdraw analytics consent in the App settings.

3) Microsoft Clarity

- Information that may be processed: App usage information, user behavior data, and device and session-related information

- Timing and method of processing: If Microsoft Clarity is initialized after the user has allowed analytics consent, information may be transmitted through the SDK to Microsoft’s global infrastructure.

- Purpose: To analyze usability and improve App quality

- Choice method: Users may withdraw analytics consent in the App settings.

4) Cloudflare Workers + D1

- Information that may be processed: Platform, package name, policy lookup scope, deviceId, hashed value of deviceToken, rewardRequestId, adUnitId, placement, reward processing status and related metadata, and general access information

- Timing and method of processing: When the App connects to the developer-operated server or when a Google AdMob SSV callback is delivered to the server, information may be processed through the network on Cloudflare infrastructure.

- Purpose: To look up App policies, verify rewarded advertisements, process storage slot rewards, and maintain security and network stability

- Choice method: Because this processing is necessary for essential service operation, refusal may restrict the use of some features, such as App policy lookup, rewarded advertisement verification, and server-based storage slot processing.

- Related policy: https://www.cloudflare.com/privacypolicy/

5. Retention Period and Deletion

The App operator retains relevant information for the period necessary to provide App features and operate the service, and deletes information that is no longer necessary or processes it in a form that makes it difficult to identify individuals. The retention period and deletion method for data processed by external providers are governed by each provider’s privacy policy. Please contact the relevant external provider.

- Accessibility Service and automation settings: Stored on the device until the user deletes the settings or deletes the App.

- Names of saved data and saved configuration data: Stored on the device until the user deletes the relevant data or deletes the App.

- Advertising and analytics consent status: Stored on the device until the user changes consent or deletes the App.

- App policy cache: Stored on the device until App policy renewal, cache expiration, App deletion, or storage cleanup.

- Server credential information such as deviceId and deviceToken: Stored on the device until App deletion, server credential information reset, token invalidation, or processing of a deletion request.

- Device-level identifiers and reward verification information on the developer-operated server: As a general rule, retained for up to one year from the last access date or last reward processing date for reward verification, prevention of duplicate rewards, prevention of misuse or abuse, and dispute response, and then deleted or de-identified.

- Settings files exported by the user: Stored in the location selected by the user and must be deleted directly by the user.

Most local data may be deleted by deleting the App or using the storage deletion function in Android App Info. However, files separately exported by the user are not automatically deleted by the App and must be deleted directly by the user from the storage location.

6. User Choices and Requests

Users can directly manage most local data and permissions through settings in the App, Android settings, and App deletion. If a user wishes to request access, deletion, or suspension of processing regarding server records directly processed by the App operator, please contact the inquiry contact. Requests will be reviewed to the extent necessary under this Policy and the relevant laws and regulations of the Republic of Korea. For advertising and analytics data processed by external providers, please contact each provider. Such data is governed by each provider’s policies and settings tools.

Items that can be managed within the App are as follows:

- Allowing or withdrawing consent for Firebase Analytics / Microsoft Clarity analytics

- Checking or changing advertising privacy options, if such options are enabled

Items that can be managed in the operating system or external provider settings are as follows:

- Disabling Accessibility Service permission

- Changing the Display Over Other Apps permission

- Managing foreground service notifications

- Resetting or deleting the Android Advertising ID and changing settings related to personalized advertising

- Deleting local App data by deleting the App or using the storage deletion function in Android App Info

Because the App does not operate user accounts, minimum necessary information such as deviceId, rewardRequestId, and inquiry details may be requested when a user requests deletion of server information. Requests concerning data held by external providers are governed by each provider’s privacy policy and settings tools. Please contact the relevant external provider.

7. Children and Minors

The App’s Google Play content rating may be displayed as suitable for ages 3 and above, but the App is not a service designed primarily for specific children. In addition, the App does not separately request information used to identify users, such as name, email address, or phone number. Advertisement display follows Google Mobile Ads policies, and guardians may restrict receipt of personalized advertisements through device OS settings or the Google advertising settings page.

8. Automated Decision-Making Using Personal Information

The App does not perform automated decision-making using personal information that produces legal effects concerning users or significantly affects them. Depending on the results of App policy lookups, the minimum supported version, whether a mandatory update is required, and whether rewarded advertisements are allowed may be displayed. However, this is a feature for applying App operation policies and is not used to evaluate an individual’s tendencies or rights.

9. Security Measures

The App operator applies the following measures to ensure the security of personal information.

- In the operating environment, communication with the developer-operated server is performed over HTTPS.

- The deviceToken used for server authentication is not stored on the server in its original form and may be stored as a hashed value.

- Server credential information on the device is stored using secure storage such as SecureStore.

- Only the minimum information necessary to provide App features is processed.

- The Accessibility Service is used only for coordinate-based actions designated by the user and does not directly collect sensitive personal information.

- Access permissions to servers and databases are restricted to the scope necessary for service operation.

- Advertising and analytics collection by external SDKs is managed to operate in consideration of consent status and each service’s policies.

10. Policy Changes and Contact Information

- If the service contents or relevant laws and regulations change, this Policy will be updated and the revision date will be indicated.

- Personal information protection officer and complaint handling contact: App operator

- Email: denver.gl.goo@gmail.com

- When making an inquiry, please avoid exposing personal information and provide only the information necessary for the inquiry.

This Policy is effective as of 2026-05-08.