Back to itinerary

Itinerary privacy

Privacy Policy

Last updated: May 4, 2026

This itinerary-specific privacy notice explains how trip planning data, map details, saved itineraries, public links, and support requests are handled inside the itinerary extension.

1. Information the itinerary builder uses

The itinerary builder stores the trip names, stop titles, descriptions, schedule fields, stop types, place names, Google Place IDs when available, and map coordinates that you add to your itinerary.

If you sign in, account identifiers such as your Firebase user ID and email are used to sync saved itineraries, enforce cloud and public publishing limits, and support account recovery or support requests.

2. Local saves and cloud sync

Guest or local itinerary work may be stored on your device so the builder can preserve drafts and reopen your current workspace.

When you save while signed in, itinerary data can be stored in Firebase-backed cloud storage so it can sync across devices and remain associated with your account.

3. Maps, places, and external services

Map and place lookup features may rely on Google Maps or related Google services. Searches, map tiles, coordinates, and place lookups may be processed by Google under its own service terms and privacy policy.

Opening directions, map search links, or public links can take you to third-party services or websites, which may apply their own privacy practices.

4. Publishing and sharing

Itineraries are private by default. If you publish an itinerary, the published snapshot becomes accessible to anyone with the public link until you update or unpublish it.

A public itinerary can include trip names, stop details, place names, coordinates, schedules, descriptions, and any other information you chose to publish. Avoid publishing private addresses, sensitive travel plans, or personal details you do not want viewers to see.

5. Analytics, billing, and support

We may use Firebase Analytics and operational logs to understand high-level product usage, diagnose failures, and improve onboarding, saving, publishing, and subscription flows.

If you use paid features, payment and subscription processing is handled through Lemon Squeezy. We do not directly store full payment card details.

When you submit the contact form, your message, selected category, email when provided, page URL, user agent, and basic account context may be stored so we can respond and track support work.

6. Your controls

You can edit or delete saved itineraries from the app, clear local browser or app storage to remove local drafts, and unpublish public itineraries you no longer want shared.

For privacy questions or account/data requests, contact pramoddhhalo@gmail.com.

Need help with an itinerary?

Send a bug report, feature request, or general question. You can also email pramoddhhalo@gmail.com.