Privacy Policy

Privacy Policy for Dayzo

Dayzo - Countdown & Event Tracker is built as a local-only app. This policy explains what the app stores, what it does not collect, and how you remain in control of the event information saved on your device.

Last Updated: June 23, 2026

Introduction

Dayzo - Countdown & Event Tracker helps you create countdowns for dates that matter to you, such as birthdays, trips, product launches, school deadlines, personal milestones, and other events. This Privacy Policy describes how Dayzo handles information in a direct and transparent way.

Dayzo is intentionally local-first. The app does not require an account, does not connect to a Dayzo backend, and does not use Firebase, login services, analytics, advertising networks, notifications, cloud sync, or remote databases. The privacy design is simple: the information you enter stays on the device where you enter it.

Information We Store

Dayzo stores the event titles and event dates that you choose to create in the app. It also stores your dark mode preference so Dayzo can reopen with the same visual setting you selected. These values are used only to provide the countdown and event-tracking features inside the app.

Event titles are created by you. If you include personal details in an event title, that wording remains local to your device. Dayzo does not collect, inspect, sell, rent, or transmit those titles to a Dayzo-controlled server.

Local Device Storage

Dayzo saves events and settings using local device storage through SharedPreferences. This storage allows the app to restore your countdown list after you close and reopen Dayzo. It is not a cloud account, online database, or remote backup service.

Your locally stored Dayzo data remains on the device unless you delete events, uninstall the app, clear app data, reset the device, or transfer device data using operating-system tools outside of Dayzo. If you use device-level backup or migration features, those tools may handle app data according to the policies of your device platform, not according to a Dayzo backend.

No Account Required

Dayzo does not require a username, password, email address, phone number, profile, or social login. You can use the app without registering or identifying yourself to Dayzo.

Because there is no account system, Dayzo cannot recover deleted events, restore events from a server, merge data between devices, or verify ownership of local data after it is removed from your device.

No Personal Data Collection

Dayzo does not intentionally collect personal data from users. The app does not ask for your name, email address, phone number, mailing address, precise location, contacts, photos, calendar access, camera access, microphone access, or other personal identifiers.

The app's core inputs are event title and event date. You decide what to write in those fields. Dayzo uses those values locally to display cards, calculate countdowns, and sort events by the nearest upcoming date.

No Analytics

Dayzo does not include analytics SDKs, product analytics, session tracking, behavioral tracking, or event measurement tools. The app does not track which screens you view, which buttons you tap, how often you open the app, or how long you use it.

Dayzo also does not collect device identifiers, advertising identifiers, retention metrics, funnels, cohorts, or similar analytics data. There is no analytics service configured for Dayzo to send this information to.

No Advertising Networks

Dayzo does not show advertisements and does not include advertising network SDKs. It does not request ad identifiers, create advertising profiles, serve targeted ads, or share event information for advertising purposes.

The app experience is not funded by using your countdowns, event titles, device behavior, or local settings for ad targeting.

No Third-Party Sharing

Dayzo does not sell, rent, disclose, or share your event information with third parties. The app has no Dayzo backend service that receives your event titles, dates, or theme preferences.

App stores, operating systems, and device manufacturers may separately process download, purchase, crash, diagnostic, or platform-level information under their own policies. That platform activity is separate from Dayzo's in-app handling of local event data.

Data Security

Dayzo reduces privacy risk by avoiding unnecessary network services and keeping app data local. Your device and operating system provide the primary security controls for local app storage, such as screen lock, app sandboxing, device encryption, and platform security updates where available.

You are responsible for protecting access to your device. If another person can unlock or access your device, that person may be able to view the events stored in Dayzo.

Children's Privacy

Dayzo is a general productivity app and is not directed specifically to children. The app does not knowingly collect personal information from children or any other users.

Because Dayzo does not use accounts, analytics, advertising networks, notifications, a backend, or third-party data sharing, it does not knowingly transmit children's personal information to Dayzo-controlled services.

User Control of Data

You control the event titles and dates you add to Dayzo. You can create events, edit event details, delete individual events, and use the immediate undo option after a confirmed deletion if you change your mind.

You also control the app appearance by turning dark mode on or off in Settings. Dayzo stores that preference locally so the selected mode persists across app launches.

Data Deletion

You can delete an event from the main Dayzo event list. Dayzo asks for confirmation before removing the event from local storage and then offers an undo action immediately after deletion.

You may also remove Dayzo data through your device settings by clearing app data or uninstalling the app. These actions may remove all locally stored Dayzo events and preferences. Because Dayzo has no server account, there is no additional server-side profile to delete.

Changes to Policy

This Privacy Policy may be updated to reflect app improvements, legal requirements, platform requirements, or clearer explanations of how Dayzo works. The current version should always describe Dayzo's data practices accurately.

If Dayzo ever introduces a feature that materially changes how user data is handled, the policy should be updated before or alongside that release so users can review the change.

Contact Information

If you have questions about this Privacy Policy or Dayzo's local-only data practices, contact the Dayzo team through the support or developer contact listed on the app store page or project website.

Please do not send sensitive event details unless they are necessary for your support request. Dayzo does not need your private countdown titles to explain this policy or respond to general privacy questions.