Privacy policy

01Who is responsible

Country Days Count is made and operated by Borys Kuśmirek, an independent developer, acting as the data controller for the processing described here. Contact: favamvv@gmail.com.

This policy covers the Country Days Count mobile app for iOS and Android and this website. It replaces the policy previously published on Google Sites.

02What stays on your device

The following is written to local storage on your phone. It is not transmitted to the developer, and there is no account to sync it to.

• The country you were in on each date, built from periodic position checks, including checks that happen while the app is in the background.
• Your calendar and trip history, and any days you add, edit or delete by hand.
• The stay limits you configure — the rule type, the country or area, the allowance and the period.
• App settings: language, notification preferences and feature toggles.
• Files you export yourself as CSV, Excel or PDF, until you delete or share them.

You can erase recorded days from inside the app under Settings → Delete Data for Date Range, over any range you choose, including the whole history. Stay limits are deleted individually where you manage them. Uninstalling the app removes everything at once. Once it is gone there is no copy anywhere for us to restore.

03What leaves your device

Exactly four flows send anything off the phone. Each has its own section below. Nothing in any of them contains your travel history.

• Coordinates sent to the operating system's geocoder, to be turned into a country name.
• Purchase and subscription state, handled by Apple or Google and by RevenueCat.
• Crash reports and basic usage events, sent to Firebase.
• On iPhone only, an install attribution token exchanged with Apple.

04Turning a position into a country

To know which country a position is in, the app asks the operating system's own geocoding service — Apple's on iPhone, Google's on Android. That request contains the coordinates and is handled by Apple or Google under their own privacy policies, not ours. The developer never sees it.

Only the resulting country name and code are kept. The coordinates themselves are not stored as a history of your movements, and the app does not record streets, addresses or routes.

Location access is a permission you grant and can withdraw at any time in your device settings. Withdraw it and the app stops adding new days; the days already recorded stay, and you can still add them by hand.

05Subscriptions

Payment is handled entirely by Apple or Google. The developer never sees your card details, and receives no name, address or payment information.

To know whether your subscription is active, the app uses RevenueCat, Inc. RevenueCat receives a randomly generated app user identifier, the purchase receipt issued by the store, and technical details such as the app version and platform. It returns whether the subscription is valid. It is not used for advertising.

06Crash reports and usage analytics

The app uses two Google Firebase services.

Firebase Crashlytics

When the app crashes, Crashlytics sends a report containing the stack trace, the app version, the operating system version, the device model and a random installation identifier. It exists so that crashes can be found and fixed.

Firebase Analytics

Basic, aggregated usage events — which screens are opened, which features are used, whether onboarding was completed — together with a random installation identifier, coarse country-level region derived by Google from the IP address, and device and app version. This is used to understand which parts of the app work and which do not.

Your recorded countries, dates and stay limits are not sent to either service.

07Install attribution on iPhone

On iPhone, the app uses Apple's AdServices framework to find out whether an install came from an Apple Search Ads campaign. Apple issues an opaque token, the app exchanges it with Apple's attribution service, and Apple answers with the campaign, ad group and keyword — or says the install was organic. The campaign identifiers are then stored on the device and attached to the Firebase Analytics and RevenueCat records for that install so that advertising spend can be assessed.

This does not use the advertising identifier (IDFA), does not require an App Tracking Transparency prompt, and does not track you across other apps or websites. It happens once per install. There is no equivalent on Android.

08Notifications

Reminders — that you are approaching a limit, or have passed one — are scheduled and shown by your device itself. They are not push messages, no server is involved, and nothing about them leaves the phone. Notification permission can be granted or withdrawn in your device settings.

09What the app never does

• No advertising SDKs, no ad targeting, and no use of IDFA or the Android advertising ID for advertising.
• No cross-app or cross-site tracking.
• No sale or sharing of personal information, as those terms are used in California and other US state privacy laws.
• No behavioural profiling and no automated decision-making with legal effects.
• No account, no login, no upload of your travel history to us.

10Legal bases

Where the GDPR or UK GDPR applies, the processing above relies on the following bases.

• Consent — location access, including background location, and notification permission. Both are granted through your operating system and can be withdrawn there at any time.
• Performance of a contract — handling purchases and confirming subscription entitlement, so that the paid features you bought are available.
• Legitimate interests — crash reporting, basic usage analytics and install attribution, so that the app can be kept working, improved and sustained. You may object; see section 13.

11Processors and transfers

• Apple Inc. — App Store purchases, geocoding on iPhone, Search Ads attribution.
• Google LLC — Google Play purchases, geocoding on Android, Firebase Analytics, Firebase Crashlytics, Firebase Hosting for this website.
• RevenueCat, Inc. — subscription entitlement.

These providers process data in the United States and elsewhere outside the European Economic Area. Transfers rely on the safeguards those providers offer, including the European Commission's Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. All traffic is encrypted in transit.

12How long things are kept

• On-device records — until you delete them in the app or uninstall it. There is no other copy.
• Subscription records — kept by RevenueCat and by the stores for the life of the subscription and for the further period their own policies and accounting rules require.
• Crash reports — retained by Firebase Crashlytics for up to 90 days.
• Analytics events — retained by Firebase Analytics for up to 14 months.
• Attribution result — stored on the device for the life of the install, and inside the analytics and subscription records above for their own retention periods.

13Your rights

Depending on where you live, you may have the right to access your personal data, to have it corrected or erased, to restrict or object to processing, to receive it in a portable form, and to withdraw a consent you previously gave without affecting processing that already happened lawfully.

For anything held on your device, exercise those rights directly: the app lets you view and edit every record it holds, export the lot as CSV, Excel or PDF, and delete recorded days over any date range. Uninstalling the app erases all of it.

For anything held by a processor — a crash report, an analytics event, a subscription record — write to favamvv@gmail.com. Requests are answered within one month.

If you are in the EEA or the UK, you can also complain to your national data protection authority. If you are in Poland, that is the President of the Personal Data Protection Office (UODO).

14Children

The app is not directed to children and is not designed for use by anyone under 16. No age is collected, and no data is knowingly processed from a child. If you believe a child has used the app and something needs deleting, write to the address in section 18 and it will be handled.

15Security

• Records are held in the app's private storage area, protected by the operating system's sandbox and device encryption.
• Credentials the app needs are held in the iOS Keychain or the Android Keystore.
• All communication with the services named above uses TLS.
• Release builds are compiled with symbol obfuscation.
• The smallest safeguard is the strongest one here: your travel history is never transmitted to us, so there is no database of it to breach.

16This website

This site sets no cookies, runs no analytics, and loads nothing from a third party — the fonts and images are served from this domain, so visiting this page does not tell anyone else that you did.

It is served by Firebase Hosting, which as part of delivering it keeps standard request logs, including IP addresses, for its own security and operational purposes as described in Google's privacy policy.

17Changes to this policy

This policy will change when the app does. The effective date at the top always reflects the current version, and material changes will be announced in the app or in the store listing before they take effect.

18Contact

Borys Kuśmirek — developer of Country Days Count.
Privacy questions and requests: favamvv@gmail.com