PastRouteBook Privacy Policy

Overview

This web notice and the in-app notice are the privacy policy for PastRouteBook on iPhone, Android, and the website where available. PastRouteBook is a personal travel-history tracker for trips, routes, stays, cruise ports, ferry ports, attractions, statistics, badges, map routes, and travel memories.

Users can review how data is handled, export a backup where tools are available, contact support, or use account deletion tools where available to delete the account and cloud data.

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 such as trip names, dates, notes, flights, airlines, aircraft, registrations, airports, trains, stations, cruises, ships, ports, ferries, cars, buses, cities, hotels, hostels, attractions, route stops, and ports of call.
• 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 data may include consent choices, coarse location inferred from an IP address, device and advertising identifiers, ad and app interactions, and crash or performance diagnostics processed by Google AdMob.
• 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.

Where Data Is Stored

• PastRouteBook uses Firebase Authentication and Cloud Firestore. User cloud records are intended to live under the logged-in Firebase user ID.
• The iPhone app, Android app, and website may also keep local device or browser copies so maps, stats, settings, and trips can load faster between cloud syncs.
• Local device or browser data can become stale if another device changes the account before the app or website syncs again.
• If cloud photo storage is added later, uploaded photos may be stored in Firebase Storage or another storage provider. Map image downloads are generated for the user and are not uploaded automatically.

Sharing and Service Providers

• PastRouteBook is designed for personal travel tracking. User trip data is not intended to be sold.
• Data may be processed by providers used to operate the app and website, including Firebase/Google Cloud, Google sign-in services, Apple services used by the iPhone app and Sign in with Apple, Google Play services used by the Android app, map providers, email providers, advertising providers, purchase providers, and cloud infrastructure providers.
• Map providers and routing helpers may receive map tile requests, route endpoints, or route queries needed to display maps and draw routes.
• 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. A Privacy Choices control is available in the app whenever Google requires users to be able to revisit those choices.
• 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 a yearly no-ads subscription or other no-ads entitlement is active, PastRouteBook should hide in-app ads.

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 should remove the full trip and update related summaries, map indexes, stats indexes, and local caches.
• 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.

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.
• 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:

Privacy contact: support@pastroutebook.com