CountDays

Privacy Policy

Effective 23 August 2026 · Last updated 23 August 2026

CountDays counts the days until, and since, the things that matter to you. Those things are private, and the app is built so they stay that way.

Your countdowns live on your device. Nothing is uploaded unless you sign in for sync, export a backup yourself, or turn on analytics — and all three are off until you choose them.

Who we are

CountDays is published by Zenski. You can reach us at support@countdays.app about anything in this policy, including a request to access or delete your data.

What the app stores, and where

Everything below is written to a database on your phone. The app does not require an account, and it works completely offline.

DataWhere it livesDoes it leave the device?
Event titles, notes, dates, times and time zones On your device Only if you sign in for sync, or export a backup yourself
Categories, tags and collections On your device Same as above
Photos you set as event backgrounds The app's own storage area on your device Never. Photos are not synced, not included in a backup, and not sent anywhere
Reminder schedules On your device, and with your operating system No
Home-screen and Lock Screen widget setup On your device No
App settings On your device Some settings sync if you sign in; others are marked device-only and never travel
Your CountDays+ purchase On your device, and with Apple or Google Handled entirely by the App Store or Google Play. We never see your payment details

The only four things that can send data

1. Cloud sync — off unless you sign in

If you sign in with Apple or Google, the app copies your event definitions to Google Firestore so another device can rebuild them: title, date, time zone, type, emoji, colour and similar fields.

2. Analytics — off by default

Analytics are disabled until you switch them on in Settings → Privacy. When on, the app records the names of actions — "an event was created", "the paywall was opened" — and short categorical values such as which plan was chosen or which widget design was picked.

A filter in the app drops any value that could carry your content, so an event title, a person's name, a note or a specific date cannot reach analytics even by mistake. Provided by Google Analytics for Firebase.

3. Crash reports — opt-in

If enabled, crashes send a stack trace and a redacted trail of recent actions to Firebase Crashlytics so we can fix the fault. Nothing you typed is included.

4. Support email — only when you write to us

If you contact support from inside the app and leave the "include details" switch on, your message is accompanied by the app version, your platform, OS version and language. Never a countdown.

What we never collect

Permissions the app may ask for

PermissionWhyIf you decline
Notifications To deliver the reminders you set Everything works; reminders simply do not fire
Photos / camera Only when you choose a photo background Everything else works; the photo stays on your device either way
Calendar Only if you ask to import events from your calendar Everything works; nothing is imported

Onboarding asks for none of these. Each is requested at the moment you first use the feature that needs it, and never before.

Children

CountDays is not directed at children under 13, and we do not knowingly collect personal data from them. As the app collects almost nothing by design, a child using it locally sends us nothing at all.

Keeping and deleting data

ThingWhat happens
An event you delete Waits in Recently Deleted for 30 days by default — adjustable in Settings — then is permanently removed from your device
The cloud copy of a deleted event Removed on the next sync
Your account Delete it from Settings → Account. The cloud copy goes with it; your device keeps its own data
Everything, at once Uninstalling removes all local data. If you have synced, delete your account first

Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to or restrict its processing. In practice the app gives you most of this directly:

Where we process data with your consent — analytics, crash reporting, sync — you can withdraw it at any time by turning the feature off or signing out.

Where data is processed

If you use sync, your data is stored by Google Firebase in the asia-south1 region. Firebase acts as our processor; their terms are at firebase.google.com/support/privacy. Transfers out of your own region are covered by Google's Standard Contractual Clauses.

Security

Cloud data is protected by server-side rules that scope every document to your account and deny everything else by default. Sign-in with Apple is nonce-bound to prevent token replay. The app stores no password and no long-lived token of its own.

No system is perfect. Local device data is protected by your device's own encryption and passcode, so keeping those enabled matters.

Changes to this policy

If we change anything material we will update the date at the top and, where the change affects how your data is used, tell you in the app before it takes effect.