Clockdown Privacy Policy

1. 100% Local Event & Photo Storage

All user-authored content you create in Clockdown is stored strictly locally on your Android device using on-device storage (AsyncStorage and native Android SharedPreferences / internal app file storage):

• Event Data: Your countdown titles, widget text, target dates, times, categories, symbols, and reminder preferences never leave your device.
• Custom Photo Backgrounds: When you select a photo from your device gallery to use as a widget background, Clockdown requests local media read access solely to resize and save a copy of that image into the app's private internal storage directory (filesDir) so your home screen widget can render it. Your photos are never uploaded to any external server.
• No Accounts or Cloud Sync: Clockdown does not require user registration, logins, email addresses, or cloud accounts.

2. Shareable Countdown Cards & Data Exports (New in v1.1)

Clockdown allows you to share visual countdown cards and export your event history:

• On-Device Image Generation: When you tap "Share Countdown," the countdown card image is captured and rendered locally in your device's memory.
• User-Controlled Sharing: Clockdown uses Android's native system share sheet to let you send your countdown card or CSV backup to the app or contact of your choice. Rux Labs never receives, views, or stores a copy of your shared images or exported CSV files.

3. What We Never Collect

Our telemetry collector is strictly configured to never log, collect, or persist:

• ❌ IP addresses (logpush and request IP logging are explicitly disabled at the edge)
• ❌ User agents or device hardware fingerprints
• ❌ Countdown titles, widget text, dates, notes, or custom photos
• ❌ Names, email addresses, or account identifiers
• ❌ Persistent install IDs or cross-session tracking identifiers

4. Anonymous, Session-Scoped Telemetry

To help us diagnose crashes and understand basic app stability, Clockdown uses a lightweight, zero-PII telemetry pipeline backed by Cloudflare Workers and D1:

• Ephemeral Session IDs: Every time Clockdown launches from a cold start, a random sessionId is generated in memory only. It is never written to disk, never derived from any device identifier, and cannot be correlated across separate app launches.
• On-Device Sanitization: Before any error or crash report leaves your device, Clockdown automatically scrubs quoted strings, file paths, and numeric literals from error messages. Only coarse screen views (screen_view), anonymous feature actions (action), and sanitized error templates (error) with basic app-state metadata (such as app version and OS platform) are transmitted.

5. Third-Party Services (Ads & In-App Purchases)

To support the free tier and process optional Pro upgrades, Clockdown integrates two industry-standard SDKs:

• Google AdMob (react-native-google-mobile-ads): Displays banner and rewarded advertisements to free-tier users. Upgrading to Clockdown Pro permanently disables all advertisements. Google may use device advertising identifiers in accordance with the Google Privacy & Terms.
• RevenueCat & Google Play Billing (react-native-purchases): Manages and verifies the one-time Clockdown Pro unlock and purchase restorations. RevenueCat uses an anonymous app user identifier to validate your Pro entitlement with Google Play and never receives your billing credit card details. View RevenueCat's Privacy Policy.

6. Device Permissions

Clockdown only requests permissions required for features you actively use:

• Photos / Media Selection: Used via the system photo picker only when you choose a custom photo background for a widget.
• Notifications: Used only when you enable event reminders to schedule local alerts on your device.

7. Data Deletion & Control

Because all of your countdowns and widget photos are stored locally on your device, you have complete control over your data at all times:

• Deleting a widget inside Clockdown or removing it from your Android home screen automatically deletes its associated settings and local background photo file.
• Uninstalling Clockdown from your device permanently and immediately erases all locally stored events, widget configurations, and custom background images.

8. Contact Us

If you have any questions about this Privacy Policy or Clockdown's privacy practices, please contact Rux Labs via our Support page.