Privacy Policy for Dayle

1. Scope, Application Identity & Contact

This Privacy Policy applies to the Dayle mobile application for Android (Application ID: com.rabpaulo.dayle) and this public website hosting the privacy notice. Dayle is developed and published by rabpaulodev.

We are committed to full transparency and compliance with Google Play Developer Policies, the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and applicable privacy laws worldwide.

If you have any questions, comments, or requests regarding this Privacy Policy or your data, please contact the developer directly:

• Developer / Publisher: rabpaulodev
• Application ID: com.rabpaulo.dayle
• Designated Privacy Contact: dayle.support@gmail.com

This policy does not apply to third-party operating systems, services, or platforms (such as the Google Play Store, Android OS, or third-party email providers) which govern your data under their own respective privacy policies.

2. Privacy Philosophy & Architecture

Dayle was designed from the ground up as a local-first, distraction-free tracker. Unlike cloud-dependent productivity software:

• There is no account creation, social login, or password required.
• We operate no central servers, databases, or user telemetry collectors.
• Your personal dates, milestones, memories, and habits remain strictly under your control on your physical Android hardware.

3. Information Handled Locally on Your Device

Dayle processes only the essential data needed to deliver its countdown, goal tracking, and reminder features. This information is stored exclusively on your device:

A. Countdown Events & Goals Data

• Event Titles & Labels: The custom names and labels you enter for your countdowns, milestones, and goals (such as birthdays, anniversaries, exams, project deadlines).
• Dates & Times: Target completion dates, optional start dates, exact target hours and minutes.
• Recurrence Rules: Preset recurrence cycles (daily, weekly, monthly, yearly) and custom recurrence intervals (every 2 to 999 days, weeks, months, or years).
• Reminders Configuration: Preferred notification delivery hours and reminder offsets (day-of, 1 day prior, or 7 days prior).
• Goal Completion Status: Timestamps indicating when a goal was completed or archived.

B. Preferences & Aesthetic Settings

• Visual Theme Palettes: Your selected color palette ID (Classic monochrome or one of 9 handcrafted color palettes).
• Notification Toggles: Your local notification toggle preference.
• Storage Schema Version: Internal technical version numbers used solely to ensure safe on-device database schema migrations.

C. Android Home Screen Widget Snapshots

To display real-time countdown progress and Year Progress on your home screen without draining battery, Dayle creates a private, aggregated snapshot stored locally in Android's private SharedPreferences (dayle_widget_data). This snapshot contains calculated day counts, recurrence flags, and theme colors. It never leaves the device.

D. Android Cloud Backup Is Disabled

Dayle explicitly specifies android:allowBackup="false" in its manifest configuration. This guarantees that your local database and settings are never automatically uploaded to unencrypted or unmonitored Google Drive cloud backups without your explicit knowledge.

4. How Information Is Used

All data processed by Dayle is used solely to perform the core app functions requested by you:

• To calculate and render real-time countdown days, hours, minutes, and elapsed percentages.
• To evaluate calendar recurrence cycles with deterministic date math (including leap-year clamping and month-end boundary handling).
• To schedule local device alarms for upcoming milestones and goals.
• To render dynamic Glance widgets on your Android home screen.
• To personalize your visual experience using your preferred WCAG AA compliant color palette.

Dayle never uses your data for profiling, targeted advertising, behavioral surveillance, or automated decision-making.

5. Zero Sharing, No Sale & No Advertising

We do not sell, rent, lease, or commercialize your data.

• No Advertisements: Dayle contains no banner ads, interstitial ads, native ads, or rewarded ads. We do not integrate any ad network SDKs (such as Google AdMob, Unity Ads, AppLovin, or ironSource).
• No Advertising Identifiers: Dayle does not request, read, or track Android's Advertising ID (AAID).
• No Analytics or Tracking SDKs: Dayle does not bundle third-party analytics trackers (such as Google Analytics for Firebase, Facebook App Events SDK, Mixpanel, Segment, or AppsFlyer).
• No Data Brokers: We do not disclose or transfer user records to data brokers, credit agencies, or marketing companies.

6. Device Permissions & System Capabilities

Dayle requests only the minimal permissions required for on-device operation. You may review or revoke these permissions at any time via Android Settings:

• Post Notifications (android.permission.POST_NOTIFICATIONS): Required on Android 13 (API level 33) and newer to deliver scheduled countdown and goal reminder alerts. If declined, the app will continue to function normally, but native notifications will be suppressed.
• Receive Boot Completed (android.permission.RECEIVE_BOOT_COMPLETED): Used exclusively by DayleReminderBootReceiver to automatically recalculate and re-arm your local reminder alarms after your device is rebooted, updated, or when the system timezone or clock changes.
• Inexact Alarms (AlarmManager.setAndAllowWhileIdle): Used to schedule energy-efficient, battery-friendly wake alarms for timely reminder delivery without requiring intrusive background processes or exact-alarm special access.
• In-App Billing (com.android.vending.BILLING): Used exclusively to facilitate the optional one-time Lifetime Premium purchase via the official Google Play In-app Billing service.

Explicitly Blocked Permissions: To ensure maximum privacy, Dayle's configuration explicitly blocks microphone recording (RECORD_AUDIO) and overlay windows (SYSTEM_ALERT_WINDOW). Dayle never requests access to your camera, device location, contacts, calendar, phone storage, or phone calls.

7. In-App Purchases, Billing & Third-Party Services

Dayle offers an optional non-consumable, one-time in-app purchase: Lifetime Premium (Product ID: dayle_premium_lifetime).

A. Payment Processing by Google Play

All financial transactions are conducted directly through Google Play In-app Billing. Dayle does not collect, receive, or store your credit card details, bank account credentials, or billing address. All financial data is managed by Google in accordance with the Google Play Terms of Service and Google's Privacy Policy.

B. Entitlement Verification via RevenueCat

To securely validate the lifetime purchase, unlock premium color palettes and custom recurrence intervals, and allow users to restore purchases across devices, Dayle uses RevenueCat (via the react-native-purchases SDK).

When you open the paywall or complete a purchase, RevenueCat processes the following pseudonymous, non-identifying technical data:

• Anonymous App User ID: A randomly generated pseudonymous identifier created by RevenueCat on the device (not linked to your personal identity or Google account name).
• Purchase Receipt & Token: The transaction receipt generated by Google Play confirming that dayle_premium_lifetime was purchased.
• Transaction Metadata: Date and time of purchase, currency, product ID, and entitlement status (premium).
• Device Technical Information: OS version, device model, and app version (used exclusively for fraud prevention, troubleshooting entitlement delivery, and debugging API errors).

What RevenueCat Never Receives: RevenueCat never has access to your countdown titles, goal names, target dates, reminder contents, or any personal notes.

For additional details regarding RevenueCat's data handling practices, please review the RevenueCat Privacy Policy.

8. User-Initiated Sharing

Dayle includes an optional feature allowing you to share a milestone celebration card or countdown card.

• This action is initiated strictly by you tapping the "Share" button.
• Dayle renders a temporary image card containing the event title and days count, then invokes the standard Android system share sheet.
• You choose the receiving application (such as a messaging app, email client, or cloud drive).
• Dayle does not transmit this image to any developer servers, and temporary cache files are discarded after sharing.

9. Data Retention, Control & Deletion Rights

Because Dayle operates without remote user accounts or cloud storage, you possess direct physical control over your data retention:

A. In-App Deletion

You can edit or permanently delete any countdown event or goal at any time from within the app. Deleting an item immediately removes it from local app storage, clears its widget snapshot representation, and cancels any scheduled notification alarms.

B. Complete Data Eradication

You can delete all application data, preferences, widget caches, and scheduled alarms at any time using standard Android system controls:

1. Open your device's Settings app.
2. Navigate to Apps, then select Dayle.
3. Select Storage & cache.
4. Tap Clear storage (or Clear data).

Similarly, uninstalling Dayle permanently deletes all internal database files, preferences, and snapshots from your device sandbox.

C. RevenueCat Purchase Record Deletion

If you purchased Lifetime Premium and wish to request the deletion of the anonymous purchase receipt record stored with RevenueCat, you can contact us at dayle.support@gmail.com with your Google Play order receipt number (formatted as GPA.xxxx-xxxx-xxxx-xxxxx). We will submit a deletion request to RevenueCat on your behalf within 30 days.

10. Data Security Practices

We implement rigorous technical safeguards to ensure your data remains protected:

• OS Sandbox Isolation: Dayle's database and preferences reside inside Android's private application sandbox, preventing unauthorized access by other installed applications.
• Encrypted Communications: Any network traffic initiated for purchase validation (between the app, Google Play, and RevenueCat) is strictly encrypted in transit using Transport Layer Security (TLS 1.2 / TLS 1.3 / HTTPS).
• No Server Vulnerabilities: Because Dayle has no centralized database or user authentication backend, your countdowns and personal milestones are not vulnerable to mass cloud data breaches or server-side exploits.

11. Children's Privacy (COPPA & GDPR-K)

Dayle is a general audience productivity utility. It is not directed at children under the age of 13 (or under 16 in the European Economic Area).

We do not knowingly collect, solicit, or maintain personal information from children. If a parent or guardian becomes aware that a child has provided us with personal information (for instance, by sending an email to our support address), please contact us at dayle.support@gmail.com, and we will promptly delete such communications.

12. Static Website Hosting & Technical Logs

This public privacy policy web page is a static HTML document designed for maximum transparency.

• This website does not set cookies, use tracking beacons, or load third-party advertising scripts.
• The infrastructure provider hosting this static site (such as GitHub Pages or Cloudflare Pages) may automatically log standard web server requests (including visitor IP addresses, browser user agent strings, and request timestamps) strictly for server diagnostics, abuse mitigation, and security purposes. These logs are processed pursuant to the hosting provider's respective privacy policy.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to accommodate new app features, updated platform requirements, or changes in legal regulations.

Whenever changes occur, the updated policy will be published directly to this URL, and the "Effective Date" at the top of the policy will be updated accordingly. Continued use of Dayle after the effective date of an updated policy constitutes acceptance of the modified terms.

14. Google Play Console Data Safety Reference Table

For complete transparency, the table below provides a full accounting of how each data category is handled by Dayle pursuant to Google Play Data Safety standards: