Clockdown Privacy Policy
Effective Date: September 22, 2026
This Privacy Policy applies specifically to the Clockdown mobile application ("Clockdown") developed by Rux Labs. Clockdown is designed with a "Zero-PII" (Personally Identifiable Information) architecture. We do not require account creation, and we do not store your personal event data on our servers. This policy supplements the general Rux Labs Privacy Policy.
1. Data Stored Locally on Your Device
All user-authored content generated within Clockdown is stored exclusively on your local device. This includes:
- Event names and widget text
- Event dates and times
- Custom photo backgrounds uploaded to the app
- Categories and reminder configurations
Because this data is stored locally via AsyncStorage and native SharedPreferences, Rux Labs cannot access, read, or share your event data. Uninstalling the application will permanently delete this data from your device.
2. Data We Collect (Anonymous, Session-Scoped Telemetry)
To improve app performance and understand usage trends, Clockdown collects anonymous, session-scoped telemetry only. There is no persistent user identifier and no user-authored content ever leaves the device.
- What We Never Collect: We strictly do not collect IP addresses, user agents, device fingerprints, Advertising IDs, email addresses, or account identifiers. Furthermore, we never collect countdown titles, dates, notes, photos, or any other user-authored input.
- Ephemeral Session ID: Clockdown does not use on-device install identifiers or rotating hashes. Telemetry is grouped using a random sessionId generated in memory the moment the app launches. It is never written to disk, is regenerated on every cold start, and cannot be correlated across app launches.
- On-Device Sanitization: Free-text fields are scrubbed before they ever leave your device. Error logs are stripped of quoted strings, absolute file paths, and numeric literals. Metadata only accepts scalar device and app-state fields (e.g., OS version, screen orientation).
- Event Types: We track coarse analytics securely stored in our D1 database, including screen views, UX actions (e.g.,
paywall_vieworwidget_config_save), and sanitized error logs.
3. Third-Party Services and Data Collection
Clockdown utilizes secure third-party SDKs to provide monetization and advertising features. These services may collect and process certain data as outlined below:
- Google AdMob (Advertising): For users on the Free tier, Clockdown displays banner and rewarded advertisements. AdMob may collect your device's Advertising ID and app interaction data to serve contextual or targeted ads. Google Privacy Policy
- RevenueCat (In-App Purchases): Clockdown uses RevenueCat to manage the "Pro Lifetime" upgrade. RevenueCat collects purchase history and transaction receipts to validate your Pro status. RevenueCat does not receive your payment details (e.g., credit card numbers), which are processed securely by Google Play. RevenueCat Privacy Policy
4. Data Retention and Deletion
- Local Data: You can delete your local event data at any time by deleting the widgets, using the in-app reset tools, or uninstalling the app.
- Telemetry Data: Anonymous telemetry events are processed in batches. Because we only collect session-scoped data without PII or stable identifiers, we cannot process individual data deletion requests for telemetry.
- Purchase Data: Managed directly through your Google Play account.
5. Children's Privacy
Clockdown does not knowingly collect personal information from children under the age of 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.
6. International Privacy Rights (GDPR, CCPA, etc.)
Because Clockdown is designed with a Zero-PII architecture and does not collect or store Personally Identifiable Information or persistent identifiers, standard privacy rights regarding data access, portability, or deletion (the "right to be forgotten") cannot be fulfilled—we simply do not hold any data that can be linked back to your identity. Our collection of anonymous, session-scoped telemetry is performed strictly under the legal basis of "legitimate interest" to ensure app stability and improve performance.
7. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes to our practices or for other operational, legal, or regulatory reasons. The "Effective Date" at the top of this policy indicates when it was last revised. Your continued use of Clockdown following any updates signifies your acceptance of the revised policy.
8. Contact
For support or privacy inquiries regarding Clockdown, please contact us: