Privacy Policy

Last updated: May 2, 2026

TimerAutoClicker (the "App") respects user privacy and is committed to protecting personal information. This policy explains how data is handled within the App.

1. Data Collected Directly by the Developer

The developer does not directly collect personal information such as user names, addresses, or phone numbers. The App does not require account registration, and the developer does not own or operate any backend server.

App settings (overlay position, tap-start counter, onboarding completion flag, Pro status flag, etc.) are stored locally on your device via Android SharedPreferences and are never transmitted to the developer or any external party.

2. Scope of AccessibilityService Usage

The App uses Android's AccessibilityService to dispatch synthetic taps at arbitrary screen coordinates on your behalf. This is the sole purpose for which the service is used. The App does not use AccessibilityService for any of the following:

• Reading the contents of other apps' screens (text, input fields, displayed information, etc.)
• Recording keystrokes or passwords
• Capturing or transmitting screenshots
• Reading clipboard contents

No information obtained via AccessibilityService is transmitted over the network. The service's onAccessibilityEvent handler is implemented as a no-op and does not process any event data.

3. Data Collection by Third-Party Services

The App uses the following third-party services, which may collect data as described below.

Google AdMob (Advertising)

Google AdMob is used to display full-screen ads (interstitial and rewarded) to free-tier users. AdMob may collect the following data for ad delivery purposes:

• Advertising ID (controllable from your device's Google settings)
• IP address (used to estimate approximate location)
• Ad display and interaction data

For details, see Google's Privacy Policy.

Google Play Billing (In-App Purchases)

Google Play Billing Library is used to process Pro subscription purchases. Purchase data is processed and managed by Google. The developer only receives the subscription status flag and the productId, and never has access to payment details such as credit card numbers.

For details, see Google's Privacy Policy.

Firebase Analytics (App Analytics)

Firebase Analytics (GA4) is used to understand how the App is used and to inform improvements. Firebase Analytics may collect the following data:

• App interaction data (screen transitions, tap session start/end, paywall view and subscribe click, permission grant results, ad load and display results, service start and stop, NTP fallback occurrences, and similar events)
• Device information (model, OS version, app version)
• Approximate location (estimated to country level from IP address)
• User properties such as Pro subscription status, theme preference, and notification permission status

This data is anonymized and does not include personally identifying information such as your name or contact details. The App does not transmit absolute tap coordinates, the literal target time text you enter, or the contents of other apps that AccessibilityService could technically observe.

For details, see Firebase Privacy and Security.

Firebase Crashlytics (Crash Reporting)

Firebase Crashlytics is used to improve App stability. When the App crashes, the following data is automatically transmitted:

• Crash logs (stack traces, exception information)
• Device information (model, OS version, memory state)
• App state (version, last screen viewed, Pro subscription status, and similar custom keys)

This data is used solely to identify and fix the cause of crashes and does not include information that directly identifies the user.

For details, see Firebase Privacy and Security.

NTP Time Synchronization

To compute precise dispatch times for synthetic taps in time-target mode, the App synchronizes time with NTP servers (ntp.nict.jp and time.cloudflare.com). This communication only exchanges time information and contains no personally identifying data.

4. Purpose of Data Use

Data Type	Purpose	Collector
Ad-related data	Delivering relevant ads	Google AdMob
Purchase data	Subscription management and restoration	Google
App interaction data	Feature improvement and usage analysis	Firebase Analytics
Crash data	Improving App stability	Firebase Crashlytics
Settings	Preserving user preferences	On-device only

5. Consent Model and Distribution Region

The App is distributed on Google Play only in Japan, North America, and Asia. The EU, UK, and EEA regions are excluded from distribution. Because GDPR / UK GDPR consent gateways (CMPs) are not mandated in the distributed regions, Firebase Analytics and Crashlytics are operated as always-on on the device side.

The use of the Advertising ID (AD_ID) can be controlled by the user through the device's Google Play services settings (Ads → Reset / Delete advertising ID). If the user opts out, AdMob will not deliver personalized ads.

If distribution to the EU is enabled in the future, consent collection via the Google User Messaging Platform will be implemented, and Firebase Analytics collection will be disabled until consent is obtained.

6. Data Retention

Firebase Analytics data is retained for the Firebase Console default period of 14 months. The developer has not configured an extended retention policy. Crashlytics data follows Firebase's default retention policy.

7. Sharing with Third Parties

The developer does not sell or otherwise provide users' personal data to third parties. Data collection by third-party services (Google AdMob, Firebase, Google Play Billing) is governed by each service's own privacy policy.

8. Children's Privacy

The App is not directed at children under 13. The developer does not knowingly collect personal information from children under 13.

9. Opt-Out

• Advertising ID: Reset or delete the advertising ID from Android Settings → Google → Ads.
• Firebase Analytics / Crashlytics: Uninstalling the App stops further collection.

10. Changes to This Policy

This policy may be updated from time to time. Any material changes will be communicated on this page.

11. Contact

For questions regarding this policy, please contact: