Country Days Count
Privacy policy
Last updated 10 November 2026 Version 2.1
The short version. The record of where you have been — countries, dates, trips, the limits you set — is stored on your phone, not on a server of ours. There is no account. Your phone's own backups include it, which is how it survives a change of phone.
Some things do leave the phone. Positions go to your phone's own geocoding service to be turned into a country name. Purchases go through Apple or Google, and RevenueCat confirms them. Usage statistics and crash reports go to Google Firebase and, on iPhone, an install may be matched to an Apple Search Ads campaign, unless you turn off Share usage data in Settings. None of these carries your travel history. Sections 4 to 7 set out each flow.
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. On your phone the app is named Country Days Tracker; in the App Store and Google Play it is listed as Country Days Count. This policy replaces the one previously published on Google Sites.
02What stays on your device
The following is written to the app's private storage on your phone. It is not sent to the developer, and there is no account to sync it to.
- The countries you were in and on which calendar days: for each day, a country code and name. On iPhone these come from location checks that can also run in the background; on Android, from checks made while the app is open or its tracking notification is showing.
- Your calendar and trip history, including days you add or remove by hand.
- The stay limits you set up — the rule type, the country or area, the allowance, the period, the start date, the alert threshold and any note you add.
- App settings: language, notification and tracking preferences, your Share usage data choice, the countries you picked recently, and the result of the install attribution in section 7.
- Files you export as CSV, Excel or PDF (a Pro feature). They are written to the app's temporary storage, which is not backed up; a copy you share from there is yours.
Positions
Since version 1.1.10 a recorded day keeps no coordinates. The first time the updated app starts, it erases the coordinates earlier versions stored with each day. Two kinds of position record remain, each only for as long as it is needed:
- The last position checked. On Android, the last one the tracking stream accepted; on iPhone, the last one the background tracker saw. It is used only to tell whether the phone has moved since, and each new check replaces it.
- Positions waiting for a country. A position recorded without a connection is kept until the geocoding service in section 4 can name its country, and is then deleted. If the lookup has failed for 14 days and at least 10 times, the app names the country from the coarse outlines built into the app, on the phone, or drops the position; either way the stored position is deleted.
Backups
Your phone's own backups include the app's data: iCloud Backup or a computer backup on iPhone, and Google's backup or a device-to-device transfer on Android. That is deliberate — it is how your history survives a change of phone. It also means those backups hold your countries and days, your stay limits and settings, the last position checked, and any positions still waiting for a country. Apple and Google keep these backups in your account under their own terms; the developer cannot see or reach them.
A backup made before you updated to version 1.1.10 can still hold the coordinates earlier versions stored, until a newer backup replaces it.
Deleting it
Under Settings → Delete Data for Date Range you can erase recorded days over any range you choose, or all of them with Delete All Travel History. Deleting everything also removes positions still waiting for a country, the last-position record, exported files, the list of recently picked countries, and any copy of a damaged data file: if the app ever finds one of its files damaged, it keeps at most two copies of it in its cache, which backups do not include, and recovers what it can. Stay limits are kept; delete them one by one in the Stay Limit Manager. Uninstalling the app removes all of its data from the phone, but not from backups you have already made — delete those in your iCloud or Google account, or on your computer.
03What leaves your device
These flows send something off the phone. Each has its own section below.
- Positions sent to your phone's own geocoding service, to be turned into a country name.
- Purchases, handled by Apple or Google, with Pro confirmed by RevenueCat.
- Usage statistics sent to Firebase Analytics and crash reports sent to Firebase Crashlytics, unless you turn them off.
- On iPhone only, an install attribution token exchanged with Apple, by the app and by RevenueCat, unless you turn it off with the same switch.
Separately, your phone's own backups copy the app's data to your iCloud or Google account, or to your computer, as section 2 describes. None of these flows carries your countries and days.
04Turning a position into a country
To know which country a position is in, the app asks your phone's built-in geocoding service — Apple's on iPhone, and on Android the one the phone provides, which on most phones is Google's. 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 code and name are kept, with the date. The coordinates are not kept in your history (section 2), 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. On iPhone, Always lets the app count days in the background; with While Using the App a day is counted only when you open it. On Android the app has location access only while it is in use, which includes while its tracking notification is showing; it never has background location access. Withdraw the permission and the app stops adding new days; the days already recorded stay, and you can still add days by hand.
05Purchases
Pro is sold as a yearly or weekly subscription, or as a one-time lifetime purchase. 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 you have Pro, the app uses RevenueCat, Inc. RevenueCat receives a random app user identifier created on the phone, the purchase receipts issued by the store, technical details such as the app version and platform, and, on iPhone, the identifier for vendor (IDFV) — an identifier Apple gives each developer's apps on a device, which is not the advertising identifier. On iPhone, while Share usage data is on, it also receives the install attribution in section 7. It returns whether Pro is active. None of this is used to show you ads.
06Crash reports and usage analytics
The app uses two Google Firebase services. Both are on unless you turn them off with the switch described at the end of this section.
Firebase Crashlytics
Crashlytics sends a report when the app crashes, and also when the app records an error it recovered from. A report contains the stack trace, the app version, the operating system version, the device model and technical state such as free memory, a random installation identifier, and the app's own warning and error messages from that session — a short log of what it was doing. It exists so that problems can be found and fixed.
Those messages never contain coordinates, and none of them names a country or a day from your history.
Firebase Analytics
Usage events record what is used in the app, not where you are:
- which screens are opened, and the steps of the first-run setup — including the goal you pick there (for example "Schengen 90/180" or "tax residency"), how many concerns and limits you chose, and whether you allowed location and notifications;
- the upgrade screen being shown, closed, or used to buy or restore, with the plan's product identifier;
- a Pro feature being opened, with whether you already have Pro, and being used;
- once a day, the location permission level, whether background refresh is available, and how many days ago the last background check was;
- a stay-limit alert being shown, with the type of rule (rolling, fixed or per visit) and nothing else;
- events Firebase records by itself, such as the first open, sessions, app updates and store purchases.
With them go a random app-instance identifier, the app version, basic device information such as the operating system, and at most a coarse location derived by Google from the connection's IP address. Since 10 November 2026 granular location and device data collection is switched off in Google Analytics for every region, so no city-level location is collected.
Your recorded countries, dates, day counts and stay limits are not sent. Since version 1.1.10 no event carries a country code or a day count from your history.
The developer also exports these events to Google BigQuery, stored in Google's EU region, to analyse them. Each day's events are one table there, and since 10 November 2026 each table is deleted automatically about 14 months after its day.
The switch. Settings → Share usage data is on by default. While it is on, the app sends the usage statistics and crash reports described above. On iPhone it also uses Apple Search Ads attribution (section 7): an Apple AdServices token is exchanged with Apple to learn which Apple Search Ads campaign, ad group and keyword, if any, led to the install, and that answer is stored with Firebase Analytics and RevenueCat.
When you turn it off, usage statistics and crash reports stop at once, crash reports not yet sent are deleted, and the analytics identifier on the phone is reset, together with the analytics data held there. On iPhone, the app's own Apple Search Ads lookup stops at once, and RevenueCat's collection of the AdServices token stops from the next time the app starts. Purchases and restores keep working. What was already sent, attribution included, is not withdrawn: it stays until it expires (section 12) or is deleted on request (section 13).
While the switch is on, Settings shows your Analytics ID under it. Tap it to copy it, and include it in a deletion request. Turning the switch off resets the ID, so copy it first.
07Install attribution on iPhone
On iPhone, while Share usage data is on, 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 for the install. The app sends it to Apple's attribution service, and RevenueCat's software in the app sends it to RevenueCat, which asks Apple the same question. Apple answers with the campaign, ad group and keyword identifiers, the App Store country or region the ad ran in, and the kind of conversion — or says the install was organic. The answer is stored on the phone and attached to the RevenueCat record for the install and to Firebase Analytics, so that advertising spend can be assessed.
With the switch off, the app makes no attribution request of its own, and RevenueCat stops collecting the token from the next time the app starts; section 6 sets out what changes when.
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. The app asks again on later launches until Apple answers or a small number of attempts runs out, and then never again. There is no equivalent on Android.
08Notifications
Alerts — that you are approaching a limit, or have passed one — are scheduled and shown by your device itself. They are not push messages and no server is involved; the only trace that leaves the phone is the analytics event in section 6. On Android the app also shows a notification while it is tracking your country. Notification permission can be granted or withdrawn in your device settings.
09What the app never does
- No ads, no advertising network SDK and no ad targeting. Firebase Analytics runs on Google's measurement library; the app includes it without advertising-identifier support, so the IDFA is never read on iPhone, and on Android the advertising-ID permission is removed and ad-ID collection is switched off.
- 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, and no sync 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 ("Always") on iPhone, 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 Pro, so that the paid features you bought are available.
- Legitimate interests — crash reporting, usage analytics and install attribution, so that the app can be kept working, improved and sustained. You may object at any time: Share usage data in Settings stops analytics, crash reports and install attribution (section 6), and section 13 covers the rest.
11Processors and transfers
- Apple Inc. — App Store purchases, geocoding on iPhone, Search Ads attribution.
- Google LLC — Google Play purchases, geocoding on most Android phones, Firebase Analytics, Firebase Crashlytics, BigQuery for the analytics export, Firebase Hosting for this website.
- RevenueCat, Inc. — purchase confirmation and install attribution.
Backups in your iCloud or Google account are a service Apple or Google provides to you, under your own agreement with them.
These providers process data in the United States and elsewhere outside the European Economic Area; the BigQuery copy of the analytics events is stored in the EU. 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. Copies in your phone's backups last as long as those backups do.
- Last position checked — until the next check replaces it, or until you delete all travel history.
- Copies of a damaged data file — at most two, until you delete all travel history or the system clears the app's cache.
- Positions waiting for a country — until the country is found, or at most until the app gives up on them as section 2 describes.
- Subscription records — kept by RevenueCat and by the stores for the life of the purchase 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 Google Analytics for up to 14 months; in the BigQuery export, each day's table is deleted about 14 months after its day.
- 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 phone, exercise those rights directly: the app shows every day it holds in History and on the calendar, lets you add and remove days, and deletes any date range or everything (section 2). Export as CSV, Excel or PDF is part of Pro.
To stop analytics, crash reports and install attribution, turn off Settings → Share usage data (section 6 sets out what stops when). Doing so also resets the analytics identifier, so what the phone sends afterwards is not connected to what it sent before.
To have analytics, crash or subscription data deleted, or to see it, write to favamvv@gmail.com. The developer holds no name or email address to look you up by, so include the Analytics ID that Settings shows under Share usage data (tap it to copy it; copy it before turning the switch off, which resets it). Also say which phone and operating system version you use, roughly when you installed the app, and the app version shown at the foot of Settings; for a purchase, include the order number from the store's receipt, which lets the purchase and its RevenueCat record be found. Analytics and crash data can be deleted only when it can be matched to your installation with reasonable confidence. Where it cannot, the developer has no way to find it, and it expires as section 12 sets out. 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. Copies in your backups are protected by Apple's or Google's backup security.
- All communication with the services named above uses TLS.
- Release builds are compiled with symbol obfuscation.
- The developer keeps no database of anyone's travel history, so there is none 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 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