PastRouteBook Privacy Policy
Overview
PastRouteBook is operated by Paul Ardan. This notice explains how PastRouteBook handles information in its iPhone app and website, and in an Android app where available. PastRouteBook is a personal travel-history tracker for trips, routes, stays, ports, attractions, statistics, maps, and travel memories. Some features and providers differ by platform; platform-specific details below apply only when that feature is used.
The in-app notice summarizes this policy and links here. You can review and edit your information in the app, export a backup where that feature is available, or contact us about your privacy rights.
Information We Collect
- Account details such as display name, email address, sign-in provider, Firebase user ID, Apple or Google sign-in identifiers where used, and account security settings.
- Profile and onboarding details such as place born, birthday, places lived, current city, language, time format, distance units, and app preferences.
- Trip details and user content such as names, dates, notes, routes, airports, airlines, aircraft, stations, ships, ports, stays, attractions, and places. On iPhone, newly selected cover, timeline, and segment photos are linked from your Photos library rather than copied into new trip records. On Android, selected photos remain with the device's media provider and portable backups do not include their image bytes. Older trip records may still contain embedded cover-photo data.
- Generated summaries such as trip summaries, dashboard summaries, statistics indexes, achievements, map snapshots, route indexes, and country drill-down points.
- Purchase, entitlement, subscription, restore, no-ads, and product status details needed to unlock paid features and remove ads for eligible users.
- Advertising and consent data may include privacy choices, approximate location inferred from an IP address, device or advertising identifiers when permitted, ad interactions, and technical diagnostics processed by Google AdMob, Meta App Events, and their partners. Meta App Events is limited to the standard app-activation signal used for eligible install attribution: on iPhone after advertising consent permits requests and Apple tracking permission is authorized, and on Android only after an adult separately opts in.
- When first-party measurement is enabled for an app version, Firebase Analytics may process app sessions, session duration, controlled screen views and aggregate engagement time by page, app interactions, broad count and duration buckets, feature and export use, purchase and paywall outcomes, general device information, and Firebase measurement identifiers. Firebase Crashlytics may process crash traces, app and operating-system versions, device model and state, Firebase or Crashlytics installation identifiers, and sanitized error categories.
- Website technical data may include browser and device information, IP address, sign-in state, and essential local storage used for account access, preferences, and cached travel data. Public pages also request fonts from Google.
- Feedback, bug reports, missing-place reports, compliments, complaints, and optional contact details submitted through feedback tools.
How Information Is Used
- To create and protect user accounts.
- To save, sync, display, edit, export, and delete travel history in the iPhone app, Android app, website, and on the user's signed-in devices where available.
- To calculate maps, stats, badges, country lists, trip timelines, and personal travel summaries.
- To speed up loading by using saved summaries instead of reading every full trip on every screen.
- To validate subscriptions and purchases, restore access, show ads where allowed, and hide ads for eligible paid users.
- To troubleshoot bugs, improve features, manage account access, and respond to feedback.
- When enabled, to measure whether existing app workflows are completed, understand aggregate feature adoption, and diagnose crashes and recoverable technical failures.
Where Data Is Stored
- PastRouteBook uses Firebase Authentication and Cloud Firestore for account, profile, settings, entitlement, and eligible travel-data records associated with a signed-in user ID.
- The iPhone and Android apps and signed-in website may also keep local device or browser copies so trips, maps, stats, and settings load faster. Automatic app travel-data cloud backup and cross-device sync are included with eligible Monthly and Yearly Pro access. Android system backup may also include local app data, depending on device settings.
- Local device or browser data can become stale if another device changes the account before the app or website syncs again.
- In the current iPhone app, original photos selected for a trip cover, timeline, note, or segment remain in the iPhone Photos library. Photo-library references are kept on that device and are removed before a trip is sent to Firestore or packaged for trip sharing. Older trip records may retain cover-photo data embedded by earlier versions. Generated map images and videos remain on the device unless you share or export them.
Sharing and Service Providers
- PastRouteBook does not sell your saved trip history. If you choose to export or share a trip, image, or video, you choose where it goes and the recipient may retain a copy.
- Providers used to operate the service may process relevant data, including Google Firebase/Cloud, Firebase Analytics and Firebase Crashlytics where enabled, Google sign-in, Apple sign-in, Maps and StoreKit on iPhone, Google Play services on Android where available, Google AdMob and its disclosed ad partners for ads, Meta App Events for separately authorized install attribution, website hosting and fonts, and email services for support.
- Apple Maps on iPhone, and Google Maps or MapLibre/OpenFreeMap on Android where available, plus routing or place-search providers, may receive map, search, route-endpoint, or route-query information needed for the feature you use. PastRouteBook also uses some place data stored and searched on the device.
- Data may be disclosed if required by law or needed to protect the app, users, or the public.
Ads and Purchases
- PastRouteBook may show ads in free or unpaid areas of the app.
- Ads may be provided by Google AdMob or related advertising services. Google may process coarse location inferred from an IP address, device and advertising identifiers, advertising data, ad and app interactions, and crash or performance diagnostics for ad delivery, measurement, fraud prevention, and analytics.
- Where required, Google User Messaging Platform asks for advertising privacy choices before PastRouteBook requests an ad. The app shows a Privacy Choices control when Google indicates that users must be able to revisit those choices. Declining consent may change which ads can be served; it does not necessarily remove all ads.
- After advertising consent permits requests and Apple tracking permission is authorized, the current iPhone app may send Meta App Events the standard app-activation signal used for eligible install attribution. Meta automatic and codeless event logging remains disabled, and PastRouteBook does not send feature activity, saved trip content, photos, profile fields, or saved travel locations to Meta through this integration.
- On Android, Meta install attribution is off by default and has a separate in-app choice available only to adult users. If allowed, PastRouteBook sends Meta only the app-install/app-activation signal and permitted device or advertising identifiers used to measure whether a Meta ad led to the install. Automatic, codeless, purchase, screen, and custom-feature event logging remains disabled. Declining leaves the Meta SDK inactive.
- When iOS tracking permission applies, PastRouteBook asks before allowing an advertising identifier to be used for tracking across other companies' apps or websites. Declining tracking does not prevent limited or non-personalized ads.
- In-app purchases and subscriptions in the iPhone app are handled through Apple StoreKit. PastRouteBook stores purchase and entitlement status so paid access can be restored and ads can be removed for eligible users.
- In-app purchases and subscriptions in the Android app are handled through Google Play Billing. Google Play provides active purchase information so paid access can be granted, restored, expired, cancelled, refunded, or revoked as appropriate.
- The website may read synced entitlement status for signed-in accounts. Web checkout is not connected unless a purchase flow is clearly shown on the website.
- Users can manage Apple subscriptions from their Apple ID subscription settings.
- Android users can manage subscriptions and purchases through their Google Play account.
- When Monthly Pro, Yearly Pro, or another eligible no-ads entitlement is active, PastRouteBook hides in-app ads.
Age and Family Privacy
- The Android app asks the user to choose a neutral age group before advertising or optional measurement can begin. The selected age group is stored on that device and can be corrected in Profile > Legal & Privacy.
- Android users under 13 do not receive in-app ads, Firebase Analytics or Crashlytics collection, or Meta install attribution.
- Android users aged 13–17 may receive only restricted, general-audience advertising treatment. They do not receive optional Firebase Analytics or Crashlytics collection or Meta install attribution.
- Adult Android users can make separate choices for advertising privacy, optional analytics and diagnostics, and Meta install attribution. Declining one choice does not silently enable another.
- The age-group choice is separate from the optional birthday in a travel profile. PastRouteBook does not use profile birthday to encourage a different privacy treatment.
Analytics and Diagnostics
- PastRouteBook's iPhone and Android analytics implementations use Google Firebase Analytics for aggregate product measurement and Firebase Crashlytics for reliability reporting. These services are separate from Google AdMob's advertising consent and from Apple's App Tracking Transparency permission.
- Custom analytics events use controlled categories and broad buckets. They do not include trip names, exact travel dates, cities, airports, ports, routes or coordinates, hotel names, notes, photo content or filenames, search text, booking references, email addresses, Firebase account IDs, Apple IDs, receipts, or StoreKit transaction IDs.
- Crash reports may include stack traces, app version, operating-system and device information, crash time, and installation or session identifiers used to group reports. PastRouteBook limits its own Crashlytics keys and non-fatal reports to sanitized feature labels and controlled error codes; it does not intentionally attach saved travel content.
- First-party Analytics and Crashlytics collection is off by default. On Android it is unavailable to users under 18; adult Android users and eligible iPhone users receive a one-time Accept or Decline choice before optional collection begins. The choice can later be changed with Share Anonymous Analytics & Diagnostics in Profile > Legal & Privacy. Turning it off stops future collection, resets Analytics data stored on that device, and deletes unsent crash reports. Advertising consent or ATT status does not silently enable first-party product analytics.
- Meta install attribution is separate from first-party analytics. On Android it remains off unless an adult accepts the dedicated Allow Meta Install Attribution choice, which can later be changed in Profile > Legal & Privacy.
- Google Analytics event-level and user-level retention is controlled in the linked Analytics property and can be set to 2 or 14 months for a standard property. Firebase states that Crashlytics keeps crash traces and associated installation identifiers for 90 days before beginning removal from live and backup systems. Aggregated reports may persist without identifying an individual app installation.
Purposes and Legal Bases
Where the GDPR or similar law applies, we rely on the following bases for our own processing:
- Contract: account access, saving and displaying your travel history, requested cloud sync, exports, paid features, and purchase restoration.
- Legitimate interests: keeping the service secure and reliable, preventing abuse, diagnosing faults, responding to support requests, and using minimized aggregate product measurement where permitted. These interests are balanced against your rights, and you may object where the law gives you that right.
- Consent: personalized advertising, optional advertising identifiers or device storage, first-party analytics or crash collection, and Meta install attribution where consent is the applicable basis. Advertising, first-party measurement, and Android Meta attribution choices are handled separately. Withdrawing consent does not affect earlier lawful processing.
- Legal obligation: records or disclosures required by applicable tax, accounting, consumer-protection, or other law.
An account identifier and sign-in details are needed for signed-in and cloud features. Trip details and photos are optional, but the related feature cannot work without the information you choose to provide. Third-party ad partners may identify their own purposes and legal bases in the consent message.
Retention and International Transfers
- Account and eligible cloud travel records are generally kept while your account exists and removed through the account-deletion process, subject to limited backups, security needs, and legal retention requirements. Local copies remain until cleared by the app, device, browser, or user. Deleting the app alone does not delete cloud records.
- Support messages are kept as long as reasonably needed to resolve the request and meet any applicable legal or security obligations. Purchase, ad, and consent records held by Apple, Google, or other providers follow those providers' retention practices.
- When enabled, standard Google Analytics user-level and event-level retention is configured in the linked property for 2 or 14 months. Firebase Crashlytics reports and associated installation identifiers are generally kept by Firebase for 90 days before removal begins. PastRouteBook may retain aggregate reports that no longer identify an app installation.
- Our providers may process information outside your country, including outside the EEA, UK, or Switzerland. Applicable transfer protections depend on the provider and destination; contact us for details about safeguards relevant to your data.
User Choices
- Users can correct travel records and profile information inside the app or website where editing tools are available.
- Users can export backups where backup tools are available.
- Deleting a trip removes it from your active travel history; related maps, summaries, and cached indexes are updated through the app's normal sync process.
- The Profile > Delete Account screen starts the account deletion flow for the signed-in account and its cloud data where deletion tools are available.
- Deleting the app from a phone does not automatically delete Firebase cloud data.
- PastRouteBook asks once whether the user accepts or declines Share Anonymous Analytics & Diagnostics. It remains off unless accepted and can be enabled or disabled later in the iPhone or Android app under Profile > Legal & Privacy. Disabling it stops new collection, resets Analytics data stored on that device, and deletes unsent crash reports. It does not change advertising choices and cannot remove reports that were already aggregated. Contact support to exercise applicable access, objection, or deletion rights.
- Eligible adult Android users can accept, decline, or later change Allow Meta Install Attribution under Profile > Legal & Privacy. It is off by default and unavailable to users under 18.
Privacy Rights
Depending on where you live and the applicable law, you may request access to your information, correction, deletion, restriction of processing, or a portable copy. You may also object to processing based on legitimate interests and withdraw consent for processing based on consent. Contact support@pastroutebook.com to make a request. We may need to verify that the account is yours before acting.
If you are in the EEA, UK, or Switzerland, you may also complain to your local data-protection authority. PastRouteBook's personal maps and statistics are automated calculations from trips you enter; we do not use them to make solely automated decisions with legal or similarly significant effects about you.
Account Deletion
Signed-in users can permanently delete their account from Profile > Delete Account in the iPhone or Android app. Users who cannot access the app can also submit a deletion request from the public PastRouteBook account-deletion page.
- Deletion removes the Firebase Authentication account and PastRouteBook cloud records for the profile, trips, segments, settings, summaries, and feedback associated with that Firebase user ID.
- Local app data is cleared when the account is removed or the app is uninstalled.
- Deleting a PastRouteBook account does not cancel an Apple or Google Play subscription. Users who do not want a subscription to renew must manage or cancel it separately in their Apple or Google Play account settings.
- Google Play, Apple, advertising, fraud-prevention, tax, or transaction records controlled by those providers may be retained under their own legal and security obligations.
- Aggregated or de-identified crash and diagnostic records may remain when they can no longer reasonably identify the user.
Terms of Use
- Use PastRouteBook to record personal travel history and memories.
- Do not try to access another user's account or data.
- Do not upload malicious files, unlawful content, or content that infringes another person's rights.
- Do not rely on PastRouteBook for navigation, safety, visa, immigration, legal, tax, or financial decisions.
- Routes, stats, and map summaries are informational and may be approximate.
Contact
For privacy questions, data access, corrections, export requests, deletion requests, complaints, feedback, or support, contact:
Operator: Paul Ardan
Privacy contact: support@pastroutebook.com