Privacy Policy

Ticket Clock

1. Information We Collect

Ticket Clock is designed with privacy as a core principle and handles only the minimum information.

• Stored on your device only (never transmitted): Your settings — refresh interval, scheduled time, clock display options, saved links and sites — are stored in the app's local storage only.
• Anonymous community data (optional feature, sent to a server): When you use the community feature, a randomly generated install identifier (not linked to your account or device info), your nickname (auto-generated or chosen by you), chat messages, and the address (host) of the site you are watching are stored on Firebase servers. Site sharing can be turned off anytime via "Share presence" in settings.
• Server time measurement: To measure a site's server clock, the app sends standard network requests (HEAD) to the site you chose. These requests contain no personal information.
• Anonymous usage and diagnostics (sent to a server): Anonymous usage events and crash reports are sent to Firebase Analytics and Crashlytics to help us improve the app. See section 4 below for details.
• Screen content: The app does not read, store, or transmit the content of your browser screen.

2. Use of the Accessibility Service

This app uses the Android Accessibility Service for its core feature: automatically refreshing your browser when the on-sale time arrives.

• Detects which supported browser (Chrome, Samsung Internet, etc.) is in the foreground.
• Taps that browser's refresh button to reload the page.
• Displays the floating server-time clock over the browser.
• Does not read, collect, or transmit text, images, or any other content shown on the screen.
• You can revoke the accessibility permission at any time in system settings.

3. Permissions We Request

• Accessibility Service: Detect the foreground browser, tap its refresh button, and show the floating clock (core feature).
• Internet (INTERNET): Used for server time measurement, the community feature, and ads.
• Notifications (POST_NOTIFICATIONS) and foreground services: Used to show an ongoing notification while server time measurement or auto-refresh is running.

4. Third-Party Services

Ticket Clock uses the following third-party services.

• Google AdMob: Serves ads. AdMob may collect device identifiers (advertising ID) and usage data to provide relevant ads. See the Google Privacy Policy.
• Google Firebase (Firestore): Stores and syncs community chat messages and anonymous watching status. See Privacy and Security in Firebase.
• Firebase Analytics: Collects anonymous usage events to help us understand how the app is used (for example, starting or stopping auto-refresh, the refresh interval you chose, the browser you selected, and the address (host) of the site being measured). Full URLs are never collected — only the host. See the Google Privacy Policy.
• Firebase Crashlytics: Collects crash reports and diagnostic information to improve app stability. See the Google Privacy Policy.

5. How Information Is Used

Collected information is used solely to provide the app's features (showing server time, auto-refresh, community chat and status) and to analyze app usage and improve stability. It is never sold or shared.

6. Data Retention and Deletion

• Settings and saved links on your device are deleted when you uninstall the app.
• Community chat messages are automatically deleted from the server 7 days after they are sent.
• Watching status (the site you are viewing) keeps only the latest state and is deleted from the server when you turn off sharing or stop measuring.
• We recommend not entering personal information (real name, contact details) in nicknames or messages.

7. Children's Privacy

This app is not directed at children under 13 and does not knowingly collect personal information from children.

8. Changes to This Policy

This privacy policy may be updated as needed. Changes will be posted on this page.

9. Contact

For privacy inquiries: philleeran@gmail.com

Last updated: 2026-08-06