1. Who we are
flytly is a personal travel atlas that lets you record countries and cities you have visited and save countries and cities you would like to visit. This policy explains how information is handled when you use the app.
The developer responsible for flytly is Christos Mountzouris (support@mountzou.dev) (“we”, “us” or “our”). For privacy questions or requests, contact support@mountzou.dev.
2. Accounts and information stored on your device and in Firebase
flytly stores the countries and cities you mark as visited, your Wishlist bookmarks, your map and city-display settings, your chosen appearance, and your last map position and zoom level. This information is used to display your travel collection, remember your preferences and restore your map view.
Access to flytly requires a Google or Apple account. We use Google’s Firebase Authentication to create and manage your flytly account. The account information includes your Firebase user identifier, your sign-in provider and provider account identifier, and your name and email address when supplied by that provider. If you choose Apple’s Hide My Email option, we receive the relay address Apple supplies. We use this information to authenticate you, display your account details and manage your account. Your Google or Apple password is not provided to flytly.
Firebase Authentication processes account information on Google’s infrastructure. Authentication tokens are used to establish and maintain your session, and the app retains sign-in credentials on your device so that you do not need to sign in every time. Firebase also processes technical information, including IP addresses and user-agent information, to operate authentication and help prevent abuse. Google and Apple process your sign-in interaction under their own privacy notices.
The Google Sign-In SDK included in flytly also declares data processing for app functionality and SDK analytics. Its privacy manifest covers name, email address, phone number and approximate location for app functionality; user identifiers and “Other Data Types” for both functionality and analytics; and device identifiers and “Other Usage Data” for analytics. Google declares these categories as linked to the user and not used for tracking. These are the SDK provider’s disclosure categories and do not mean that flytly asks you to enter all of this information. In particular, flytly does not request a phone number or offer phone-number sign-in.
Firebase Authentication also sends technical user-agent information, including device and operating-system details, the app bundle identifier and developer platform. Firebase describes this information as not linked to a user or device identifier. It is used to understand platform and version adoption and inform SDK development, and is disclosed as Other Diagnostic Data used for analytics. SDK analytics are distinct from your travel collection: flytly does not send your saved visits, Wishlist or city-search text as analytics events.
flytly lets you create a travel profile containing preference choices such as travel pace, nature, culture, food, crowds, mobility, weather and budget, together with optional must-have and must-avoid choices. These preference values are stored in Firebase Firestore under your flytly account so you can load and save your profile. Flytly uses them to personalise the destination-fit feature.
Starting with version 1.1.9, your saved visits and Wishlist are stored in Firebase Firestore, linked to your Flytly account, together with a local copy on your device. Saved place identifiers and their Visited, Wishlist or removed status, update timestamps, and limited installation-specific synchronisation metadata are used to back up and synchronise your collection. On the first signed-in launch after an update, existing records owned by that account are migrated automatically when a connection is available; records without a known account owner are not assigned or uploaded automatically. New additions, removals and collection changes are saved locally and synchronised with Firebase. Changes made without internet remain queued on that device and are sent when the connection returns. Cloud-saved places can be restored after reinstalling version 1.1.9 or later or signing in on another device with the same account. Unsent changes can be lost if the app's local data is deleted before they reach Firebase. Your travel-profile preferences remain a separate cloud record.
The Home Screen widget receives only visited-country and visited-continent totals and availability information through the app's shared storage. It does not receive account credentials or individual saved-place records. When you choose to share your travels, Flytly generates an image of your visited-country map and travel totals. The selected app or service receives that image under its own privacy terms; sharing is initiated by you. Sharing to Instagram Stories uses a temporary, device-local pasteboard item that expires after five minutes. Wishlist-only places are excluded from the shared travel card.
Country and city searches are matched against a catalog included with the app. flytly does not send the text you enter in these search fields to us or to an online search provider, and it does not keep a persistent search history.
3. Optional location and information we do not use
With your permission, flytly uses your device location while the app is in use to show the straight-line distance and current time difference between your location and a selected city. Location access is optional. You can continue recording visits and using your Wishlist without it, and change or revoke permission in iOS Settings. Places you mark as visited are entered by you; the app does not track your movements in the background or automatically record where you have been. Your location is processed on your device for distance calculations and sent to Apple through MapKit to resolve your time zone. Location and time-zone results may be held temporarily in memory to avoid repeated requests; flytly does not write your current location to persistent app storage, upload it to our servers, or attach it to your Firebase account. Apple processes requests under its own privacy policies. flytly does not request access to contacts, microphone or camera and does not read your photo library. When you choose Save Image for a travel card, iOS may ask for permission to add that image to Photos. Separately, Google Sign-In may use your IP address to estimate an approximate location for fraud prevention.
flytly does not include advertising or use advertising identifiers for cross-app tracking. We do not sell your personal information or share it for cross-app advertising. The authentication SDKs include the functionality and analytics processing described above, without tracking. Version 1.1.9 does not integrate the separate Google Analytics for Firebase or Firebase Crashlytics products. There are no subscriptions or in-app purchases in this version.
4. Service providers and external links
For details about Firebase’s handling of account information, cloud travel profiles and saved travel collections, security and retention, see Privacy and Security in Firebase.
flytly uses Apple’s MapKit framework to display and interact with the map, look up nearby points of interest around a selected city, and determine time zones. These requests may send the selected city’s coordinates and point-of-interest category, or your permitted location for time-zone lookup, to Apple. Nearby-place searches use the selected city’s location, not your device location. Results may be temporarily cached in memory. Although the app includes its own geographic catalog and map artwork, Apple’s framework communicates with Apple’s services for these lookups. Apple handles information associated with those services under its own privacy policies. Local storage of your travel records does not mean that all app functions operate offline.
Starting with version 1.2.0, flytly calculates your destination fit (shown as “Your Match”) on your device by comparing your saved preferences with city data included in the app. The selected city, preferences and match result stay on your device for this calculation. Your travel profile is still saved in Firebase Firestore as described in section 2.
In flytly versions up to and including 1.1.16, requesting a destination-fit analysis sends the selected destination name and a summary of your travel preferences to a Firebase backend. The backend checks your signed-in account and Firebase App Check, then sends the destination and preference summary to TypeSafe AI to generate the JEV analysis. The request to TypeSafe AI excludes your name, email address and Firebase user identifier. The backend uses your Firebase identifier to authorise requests and track usage. TypeSafe AI handles the submitted information under its privacy policy and applicable service and data-processing terms.
TypeSafe AI Privacy Policy: https://typesafe.ai/legal/privacy-policy
TypeSafe AI Data Processing Addendum: https://typesafe.ai/legal/data-processing
For requests from these earlier versions, flytly records request counts, success or failure, model and token-usage information in Firebase records linked to your Flytly account to manage quotas and operate the service. These usage records are not available for client reads. A separate project-level aggregate without your account identifier may be retained for quota and billing reconciliation.
Apple may also process App Store, device or diagnostic information and make certain analytics or crash reports available to developers, depending on Apple’s services and your sharing settings. Any such reports made available to us are used to understand reliability and improve the app, not for advertising. These Apple reports are separate from the authentication SDK analytics described above.
For more information, see Apple’s Privacy Policy and Apple Maps & Privacy.
If you open the Privacy Policy, a data-source credit or another external link, the destination website and your browser may process information such as your IP address and browser details under that provider’s policy. Opening a link does not cause flytly to attach your saved travel records.
5. Device backups and retention
Your Firebase account information is retained while your flytly account exists. You can request its deletion through Account → Delete my account. Firebase handles deletion and any remaining security logs or backup copies according to its retention practices; account deletion does not mean that all provider logs and backups disappear immediately. Google handles SDK analytics, diagnostics and associated technical records according to its applicable privacy and retention notices; deleting a flytly account does not guarantee immediate deletion of every provider-held technical record.
When your Flytly account is deleted, the cloud travel profile, cloud visits and Wishlist, their synchronisation records, and any account-linked usage records from the legacy destination analysis are removed by the account-deletion cleanup process, which retries transient failures. Project-level usage aggregates that do not identify an account may be retained for quota and billing reconciliation. Provider security logs, service logs and backups may remain according to the applicable provider retention practices.
Your saved visits and Wishlist remain in Firebase while your Flytly account exists. Removing a saved place updates its status; a minimal removal record may remain to prevent an older device from restoring the removed place. These synchronisation records are removed when the Flytly account is deleted. Signing out or deleting the app does not delete the cloud copy. Signing back into the same account restores cloud-saved places when a connection is available. Local copies and device-wide map or appearance preferences remain on a device until you remove the relevant local data. Depending on your device settings, the operating system may include app data in iCloud or computer backups. Those backups are managed by you and the backup provider and are separate from Flytly's Firebase synchronisation.
Deleting the app’s local data does not necessarily delete copies in existing backups. Offloading the app may preserve its data. You can manage backups through Apple’s device and backup settings.
6. Your choices and deletion
You can remove a city visit, unmark a country visit, or remove a Wishlist bookmark inside the app. Changes update the local copy and synchronise with Firebase when a connection is available. A country is automatically marked as visited when you add a visited city and cannot be unmarked while it still contains visited cities. Reset map settings restores map preferences; it does not erase your visits or Wishlist.
In Account, you can view your account details and sign-in method, log out, or choose Delete my account. Deletion requires confirmation and a fresh sign-in with the same provider account. The app deletes your Flytly account from Firebase Authentication, removes the cloud travel profile, cloud visits and Wishlist, their synchronisation records, and any account-linked usage records from the legacy destination analysis, and removes that account's visits and Wishlist from the device where you perform the deletion. For Apple sign-in, the deletion flow also revokes the Sign in with Apple authorization for Flytly. Project-level usage aggregates without your account identifier are not deleted because they are used for quota and billing reconciliation. If local cleanup fails, the app tells you to delete the app to clear the remaining local data.
Deleting your flytly account does not delete your Google or Apple account. You can manage Google’s connected-app permissions in your Google Account settings. Account deletion does not erase device-wide map or appearance preferences, local data belonging to other flytly accounts, copies on other devices, existing backups or support correspondence retained as described below.
Deleting or offloading the app does not delete your Firebase account. To delete that account, use Delete my account first, or contact us if you cannot access the app. To remove all locally stored flytly data on a device, use Delete App rather than Offload App, and manage backups separately. We cannot remotely delete or export records stored only on your device.
7. When you contact us
If you email us, we receive your email address, your message and any information or attachments you choose to include. We use that information to respond to your request, provide support and resolve issues. Please avoid sending sensitive information or travel details unless they are needed for your request.
Support correspondence may be handled by our email service provider. We retain it only for as long as reasonably needed to handle the inquiry and related follow-up, or to meet an applicable legal obligation. We do not use support messages for unsolicited marketing.
8. Privacy rights and security
Where applicable data-protection law applies, you may have rights to access, correct, delete or receive a copy of personal information we hold about you, and to restrict or object to certain processing. You may also complain to your local data-protection authority. Contact us using the privacy email above. These rights concern information we hold or process through our providers, including account information, your cloud travel profile, cloud visits and Wishlist and their synchronisation records, any account-linked usage records from the legacy destination analysis and support correspondence. Travel records stored only on your device are managed through the app and your device.
Where the GDPR applies, we process account information as necessary to provide the account-based service you request. We rely on our legitimate interests in protecting accounts, preventing abuse, providing support and maintaining a reliable app for related security and support processing, where those interests are not overridden by your rights. Information needed to meet a legal obligation is processed on that basis. Google/Firebase, Apple and our email provider may process information outside your country. TypeSafe AI may also do so for destination-fit requests from versions up to and including 1.1.16. Their privacy and data-processing notices explain the applicable processing locations, transfer mechanisms and safeguards.
flytly uses the operating system's app storage protections, Firebase Authentication for account access and Firestore access rules limiting saved cloud collections to their account owner. No device, online service or storage method can be guaranteed completely secure. Protecting access to your device, your Google or Apple account and your backups helps protect your information.
9. Children
flytly is a general-audience travel app and is not specifically directed at children under 13. It requires Google or Apple sign-in but does not request a date of birth. If you believe a child has provided personal information to us through an account or support message, contact us so that we can review and address it.
10. Changes to this policy
We may update this policy if flytly’s features or privacy practices change. The current policy will be available through the app’s Privacy Policy link. If a future feature requires additional information or permissions, we will provide the relevant notice and obtain consent where required before using that information.