PastRouteBook legal center
Overview
PastRouteBook is a personal travel-history tracker. It lets users save trips, transportation segments, stays, cruise ports, ferry ports, attractions, statistics, badges, map routes, and related travel memories.
The app is built to work across the website and iPhone app. To do that, PastRouteBook stores account data in Firebase and may keep a local copy in the browser or on the phone so maps, trips, and stats load faster.
Privacy Policy
This Privacy Policy explains what PastRouteBook collects, how it is used, where it is stored, and the choices users have.
Information users provide
- Account information, including display name, email address, sign-in provider, Firebase user ID, and account security settings.
- Profile and onboarding information, including place born, date of birth, places lived, current city, language, time format, distance units, and app preferences.
- Trip information, including trip names, dates, notes, flights, aircraft, registrations, airlines, airports, trains, stations, cruises, ships, cruise ports, ferries, ferry ports, cars, buses, cities, hotels, hostels, attractions, route stops, and ports of call.
- Generated travel summaries, such as trip summaries, map route indexes, map snapshots, dashboard summaries, statistics indexes, achievements, and country drill-down points.
- Payment or access information if paid unlocks, promo codes, subscriptions, ads, or pro features are used. PastRouteBook should store entitlement status, not full payment card details.
- Feedback, compliments, complaints, recommendations, missing-place reports, bug reports, performance reports, and optional contact information submitted through feedback tools.
Information collected automatically
- Authentication and session information needed to keep users signed in.
- Basic technical information created by Firebase, hosting, browser storage, iPhone storage, and security services to run, secure, sync, and improve the app.
- Local browser storage and iPhone local storage may keep cached trips, profile settings, summaries, map route data, and app settings for faster loading and offline fallback.
- Map providers and routing helpers may receive map tile requests, map view information, route endpoints, or route queries needed to display maps and draw routes.
How information is used
- To create and protect user accounts.
- To save, sync, display, edit, export, and delete each user's travel history across website and iPhone app.
- To calculate statistics, badges, maps, and personal travel summaries.
- To generate faster-loading dashboard, stats, country, route, and trip summaries from saved trip records.
- To troubleshoot bugs, improve features, and respond to feedback.
- To manage paid feature access, promo codes, ads, or subscription status if those features are enabled.
- To maintain security and prevent misuse.
How information is stored
PastRouteBook uses Firebase services, including Firebase Authentication and Cloud Firestore. User records are intended to be stored under the logged-in user's Firebase user ID. The website may also use browser local storage, and the iPhone app may use local device storage, to keep the app responsive and available between cloud syncs.
Current core travel data includes full trip records plus derived records such as trip summaries, dashboard summaries, statistics indexes, map snapshots, and map route indexes. Those derived records are used to avoid loading every full trip on every page.
If photo upload or cloud photo storage is enabled in the future, photos may be stored in Firebase Storage or another storage provider. Downloaded map images generated from trip maps are created for the user and are not intended to be uploaded automatically.
Sharing
PastRouteBook is designed for personal travel tracking. User trip data is not intended to be sold. Data may be processed by service providers used to operate the app, such as Firebase/Google Cloud, Apple services used by the iPhone app, map providers, payment providers, email providers, and hosting providers. Data may also be disclosed if required by law or needed to protect the app, users, or the public.
Users should not enter private information about other people unless they have permission to do so.
Your Data
Users should be able to access, correct, export, or delete their personal travel data. Account and trip data is intended to be stored under the user's Firebase user ID. Clearing browser storage or deleting the app may remove local fallback copies, but it may not delete cloud records.
- Trip data belongs to the logged-in user account that created it.
- Users can use profile backup tools to export their data where available.
- Users should only upload or enter photos, notes, and information they have the right to use.
- Location and travel history can be sensitive. Users should avoid adding information they do not want stored.
- Deleting a trip should delete the full trip and update related summaries, stats indexes, map indexes, and cached browser or device copies.
- Because local storage is used for speed, a user may need to refresh, sync, or clear local app/browser data if a device shows stale information.
Photos and Map Images
If PastRouteBook allows photo uploads, users are responsible for the photos they upload. Photos may contain personal information such as faces, locations, travel dates, documents, or other visible details.
- Do not upload photos that violate another person's rights.
- Do not upload illegal, harmful, or private content without permission.
- Photo storage may count toward Firebase Storage usage and billing limits.
- Trip map image downloads are generated from map content. Users are responsible for how they share exported images.
Terms of Use
By using PastRouteBook, users agree to use the app responsibly and understand that it is currently an alpha testing product.
Permitted use
- Use PastRouteBook to record personal travel history and related memories.
- Enter accurate information where possible, while understanding that public data lists may contain errors or omissions.
- Report missing, inaccurate, or broken data through the feedback tools.
- Keep account login information secure and use only accounts the user owns or is authorized to use.
Not permitted
- Do not attempt 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.
- Do not use the app to track someone else without their consent.
Prototype disclaimer
PastRouteBook is provided as-is during development. Features, maps, sea routes, road routes, statistics, badges, data lists, translations, sync behavior, paid unlocks, and app behavior may change. The app may contain bugs or incomplete data.
Data Deletion and Account Deletion
Users may request deletion of their account data, saved trips, feedback, and uploaded photos. Where self-service deletion is available, it should delete the user's Firebase account records, trips, summaries, settings, and local cached records on that device.
- Browser-only data can be cleared by clearing the website's browser storage.
- Cloud data stored in Firebase must be deleted from Firebase/Firestore/Storage or through an account deletion flow.
- Some backup, payment, log, fraud prevention, or security records may remain for a limited period where permitted or required.
- Deleting the app from a phone does not automatically delete Firebase cloud data.
Contact
For privacy questions, data access, corrections, export requests, deletion requests, or complaints, contact:
Privacy contact: Add your privacy contact email before launch
Logged-in users can also use the feedback form for recommendations, missing data, corrections, compliments, and complaints.