Privacy · Updated October 6, 2026

Privacy policy

Anomal Labs LLC operates the ItinerarMe website and mobile trip planner. Contact us at team@itinerarme.com. We collect the information needed to run your account and the planning features you choose; external travel merchants handle their own bookings and payment information.

Information we handle

Account data includes your email address, account identifier, sign-in and consent records. If you choose Google or Apple sign-in when offered, we receive the identity information needed to authenticate you, such as your provider identifier, email address (including an Apple relay address) and any name shared by the provider. We do not receive your Google or Apple password. Trip data can include departure and destination, dates, traveler counts and child ages supplied by an adult, preferences, budget, accommodation options, itinerary items, edits, notes, self-reported booking marks and costs you enter. We also process support messages, subscription entitlement and transaction identifiers (not your card number), request/security logs and optional approximate location if you grant permission for a nearby-airport suggestion. Avoid placing passports, payment cards, medical details or reservation references in free-text notes.

How and why we use it

We use account and trip data to provide your requested planning, save and restore trips, authenticate you, honor subscription allowances, answer support requests, protect the service and comply with legal duties. Where applicable under European privacy law, those uses rely on performance of the service contract, our legitimate interests in security and support, or a legal obligation. Optional device location requires your permission. Your device uses that location to find a nearby departure airport; the selected airport is saved with your trip, while the device coordinates stay on your device. Personalized AI planning is optional: turn it off before creating a trip if you do not want planning details sent for that purpose.

AI, places and travel partners

When personalization is on, our server sends OpenRouter and its selected model your trip destination, origin airport, dates, party counts and child ages, flight and stay needs, budget and selected preferences, plus fixed itinerary dates and times. Optional details can include must-see/must-avoid places, daily hours, preferred cuisines, transport/access preferences, and a booked hotel location and destination-local flight times. Dietary or allergy needs are only sent when you explicitly enable their use for restaurant suggestions; turn that option off to remove them. Avoid medical details. Suggestions cannot establish dietary suitability or allergen safety; confirm requirements with the venue. We do not include your account email, traveler names, payment details, booking references or private notes in that planning request. The model may generate incomplete or inaccurate suggestions. Place discovery may use Foursquare or public sources. On a deliberate partner handoff, the partner and merchant may receive the relevant route or destination, dates, party details and search preferences; their own privacy and cookie policies then apply. Images may load from external photo sources when displayed. When you choose a map link, the map service receives the place or route in that link and applies its own privacy policy. We do not send child ages or personal identifiers in affiliate tracking sub-IDs.

Service providers and international processing

Cloudflare hosts the website; Supabase provides account and saved-trip services; OpenRouter and selected model providers support optional planning; RevenueCat, Stripe for web subscriptions, and the applicable app store for mobile subscriptions may handle payment and digital subscription status where enabled. Card details are entered with the payment provider; ItinerarMe receives purchase and entitlement information rather than full card numbers. Duffel may receive route, travel dates, passenger ages and cabin preferences to search flights; ItinerarMe does not place flight orders with Duffel. Viator receives the destination and date range for tour discovery; it does not receive your account email or saved-trip identity. Public place names may be sent to Wikimedia to look up photos or approximate place coordinates; those server lookups exclude account identifiers, travel dates and traveler preferences. Search, map, photo and approved travel partners receive the information needed for the feature you use. These providers may process information outside your country, including in the United States. We review applicable contractual and transfer safeguards as part of release readiness. A merchant's booking and payment records are controlled by that merchant.

Hotel photos

Where a hotel photo is supplied by Google Maps, our server sends the hotel name and city to Google. It does not send account identifiers, travel dates, traveler preferences or your device location. Loading the photo shares your network address with its image provider. Google photo URLs, author information and images remain in the current view; they are not stored with your trip, cached by ItinerarMe, sent to the planning model or included in exports. Credits and source links identify these photos. Other images use their displayed source and attribution. Google Maps photo services are subject to Google’s Privacy Policy.

App updates and subscription records

The mobile apps use Expo’s update service to check for compatible improvements. Those requests include the app and operating-system versions, update identifiers and a random identifier for that app installation. It is generated on your device, is not an advertising or hardware identifier, and normally changes after the app is removed or its data is cleared. The update library can also send a limited description of a previous startup or update failure. Expo uses these requests to deliver updates and report their adoption and failures; its privacy policy explains its processing. This is separate from ItinerarMe’s technical search metrics described below. RevenueCat receives your account identifier and purchase history to verify paid access, prevent purchase fraud and provide subscription reporting, as described in its privacy policy. We do not use these identifiers or reports for advertising or cross-app behavioral tracking.

Sign in with Apple connections

Where automatic Apple connection removal is supported, we keep an encrypted Apple refresh credential on the server to check that connection and revoke it when you delete your account. It is used only for account access and removal, never for itinerary planning, analytics or advertising. Pending deletion credentials are removed after cleanup, or after at most seven days if Apple cannot be reached; the deletion receipt then explains manual removal. We retain only hashed notification replay records for 90 days. Older sign-in connections may require the manual steps on our deletion page.

Downloaded mobile trips

Mobile builds with downloaded-trip support can keep an encrypted, account-specific copy of up to 20 saved trips within a 50 MB device-storage budget. Downloads contain permitted itinerary details and edits you explicitly save on the device; they exclude Google Maps photos and other provider content that cannot be stored offline. The app shows when the copy was last updated. Device edits wait for account verification and a version check before syncing; conflicting edits stay available for review. Signing out or deleting an account removes local access and starts cleanup of that account's downloads. A disconnected device cannot receive a remote deletion request until it reconnects. Protect access to your device and review its downloaded trips before sharing it.

Content reports

If you report planning content, we keep the selected text and your reviewed explanation in a private support queue until account deletion. Your reports are included in your account export; internal review notes are not. Avoid personal or booking details. Independently verified public-source safety restrictions may remain after deletion without a link to your account.

Sharing and local reminders

Trip sharing grants online read-only access to the verified email you invite until expiry or revocation. Preview shared labels first; costs, child ages, booking references, private notes and photos stay private. Viewers cannot edit or download the shared view. You can revoke access, but screenshots cannot be retracted. Invitation permissions are included in account exports and removed with the trip/account. Optional app activity reminders stay on the device; secure choices contain hashed identifiers, and notification text is generic. Signing out removes those choices and scheduled reminders. There is no remote marketing push or live-flight monitoring.

Storage, retention and protection

Guest drafts may remain in browser or device storage until cleared there. When you export from the mobile app, a temporary file stays in the app’s private cache so your chosen sharing app can read it. Files at least 24 hours old are removed the next time you open an itinerary or export; the operating system may clear them sooner. Copies saved or sent to other apps remain under your control. Essential browser storage keeps you signed in across tabs in the same browser until you sign out, your session expires or you clear browser data; mobile credentials use device secure storage. One-time sign-in verification and private deletion receipts remain tab-scoped on the website. Account and saved-trip records remain while your account is active or until removed through a verified request. Technical search outcomes, missing-result counts, retry runs, latency and reported planning usage/cost help us improve reliability. That history does not contain prompts, travel preferences, destinations or contact information; individual records are aggregated and removed after 90 days. Expired provider-response caches are cleared daily while usage counters remain. Private account-deletion receipts are retained for 90 days to track cleanup and prevent account restoration; unfinished cleanup stays queued until resolved. Backup copies expire under our hosting provider's retention schedule, and we replay deletion records before reopening a restored system. Required financial records and independent bookings remain with their providers. Security logs and provider records follow their own retention schedules. We use access controls and encrypted transport, but no online service can guarantee absolute security. See Cookies and device storage and Security.

Your choices and rights

You may edit trips, disable optional AI planning, decline location permission, clear local data in Account, and request access, correction, a portable copy or deletion of account data. Depending on where you live, you may also object to or restrict processing and complain to your local data-protection authority. California residents may ask about applicable access, deletion, correction and opt-out rights; we do not intentionally sell personal information or use cross-context behavioral advertising in the current service. We do not discriminate for exercising applicable privacy rights. Contact team@itinerarme.com; we will verify account control before releasing or deleting data. See account-deletion instructions. Account deletion does not cancel an external travel booking.

Children and changes

Accounts are for adults. An adult may enter a child's age to plan age-appropriate travel; children should not create accounts or submit personal details. We will update the date on this page when practices change materially and request fresh consent where required.