Data We Process
Account identity comes from Firebase authentication. Saved trips, itinerary requests (processed with Google Gemini, see “AI Itinerary Generation”), preferences, reservations you choose to import, reminders, support requests, purchases and creator activity may be processed on Journvia’s servers. When you are signed in and a trip is saved, expense records and safety check-ins sync privately to your Journvia account so your own devices can reconcile the trip. These records are not shown to trip collaborators and are included in account export and deletion. A safety check-in stores its trip, label, due time and status; it does not collect live location. Encrypted document-vault files and some learned preferences remain on your device unless a feature clearly says otherwise.
Per-stop notes and links are saved with the itinerary and follow its sharing settings. Personal numeric budgets and places you explicitly record as visited stay encrypted on this device, separately for each account; they are not automatically shared or synced. Recorded visits do not collect live device location or infer visits from a planned trip. Settings provides an offline export and a separate removal control for these device travel records. Account JSON export also includes this device’s budgets and recorded visits when readable; account deletion does not remove records held only on your device.
AI Itinerary Generation
When you generate a trip, use “Surprise me”, or ask Journvia to regenerate a day or an activity, Journvia’s server sends the details needed for that request to Google’s Gemini API, which Google provides as our AI service provider. These details are the destination, travel dates and trip length, the type of travel party, the budget level and trip style you choose, and general preference hints your device has learned. Journvia does not send your name, email address, account identifier, payment details, document-vault files or your device location to Gemini. The preference hints are used for that request only and are not stored by Journvia.
Google processes these requests under its Gemini API terms and may keep them for a limited period to detect abuse and meet legal obligations. The itinerary that comes back is saved to your account like any other trip and follows the same export and deletion controls. AI-generated suggestions can be inaccurate or out of date, so check opening hours, prices, entry rules and safety advice with the provider before you rely on them. You can report an itinerary or stop from inside the app.
Safety Check-ins
Safety check-ins are private organisational records. Journvia does not use them to monitor your location, message a trusted contact, dispatch assistance or contact emergency services. If you need help or miss a planned check-in, use an agreed contact plan and contact the appropriate local service directly.
Shared Trip Photos and Receipts
If you add a photo to a shared trip, or attach a receipt image to a shared expense, Journvia uploads the image together with the caption you enter. You choose each image; Journvia does not scan or upload your photo library. Uploaded images are encrypted on Journvia’s servers and are visible only to people who are members of that trip. Remove anything you would not want fellow travellers to see, including faces of other people, documents or location details in the picture.
The person who uploaded an image, or the trip owner, can remove it at any time. Removing it makes it unavailable to all trip members immediately. Images are also deleted when the trip is deleted or when the uploader’s account deletion completes. Each image may be up to 5 MB and a trip can hold up to 200 shared attachments. Receipt text recognition, where offered, runs on your device; the image is uploaded only if you choose to attach it to a shared expense.
Why We Use It
We use data to authenticate you, generate and save trips, provide lifecycle tools, protect purchases, answer support requests, prevent abuse and maintain required financial records. We do not sell personal information.
App Analytics, Diagnostics and Configuration
The mobile app uses Firebase services provided by Google. Firebase Authentication processes account identifiers such as your email address and technical request information, including an IP address, to create and protect your sign-in. Firebase Analytics processes app interactions and app, device and installation identifiers so we can understand which Journvia features work and where users encounter problems. Firebase Crashlytics processes crash traces, relevant app state, diagnostics and device or installation identifiers so we can investigate reliability issues. Firebase Remote Config processes an installation identifier and technical request information to deliver safety switches and configuration. These services use encrypted transport and may derive a general country or region from a network address; Journvia does not request or store your precise device location for these purposes.
Advertising
On supported free mobile-app surfaces, Journvia uses the Google Mobile Ads SDK. After the applicable consent flow, the SDK may process and share with Google an IP address (which can indicate a general location), app interactions such as launches, taps and video views, diagnostic information, and device or account identifiers including the Android advertising ID or Apple advertising identifier where permitted. Google uses this information to provide advertising, measurement and fraud prevention. Where required, you can change advertising privacy choices from Journvia Settings. Reward credit is granted only after Google’s signed server-side verification; Journvia does not rely on the device alone to award it.
Purchases
Google Play or Apple processes payment details for in-app purchases. Journvia receives the selected product, purchase status and a store verification token or order reference so the server can verify the purchase, prevent duplicate grants, restore eligible purchases and maintain required transaction records. Journvia does not receive or store your payment-card number.
Weather Forecasts
When you open live trip weather, Journvia’s server sends one rounded itinerary-place coordinate - not your live device location, name, email or account identifier - to MET Norway. Forecasts are cached to reduce external requests and are displayed with source attribution and freshness information.
Google Maps Place Search
When an itinerary map is available, map images for the area you view are requested from the configured map provider. For OpenStreetMap maps, the OpenStreetMap Foundation receives your IP address, the tile area requested and ordinary browser information under its Privacy Policy. Journvia does not send your account details or itinerary text with tile requests. Viewed map images are cached on your device to reduce repeat requests. Journvia does not bulk-download tiles or provide offline map-area downloads from OpenStreetMap's public tile service. Opening external directions sends the selected stop coordinates or place search to the maps service you choose.
If you search for hotel locations or attractions in the app while this optional feature is enabled, Journvia sends the destination text and place category to Google Places through our server. We do not send your name, email, saved trip or precise device location to Google Places for this search. Google processes the request under its Privacy Policy. Place results are shown with Google Maps attribution and are not stored as a hotel-price or availability feed.
Affiliate Handoffs
Journvia may create an attributed partner link after you choose a disclosed offer. Attribution uses campaign or click identifiers - not your name, email or precise location. Booking and payment happen on the named provider’s service under its policy.
On the public website, live Viator activities and promotional artwork load only after you select “Show activities.” That action sends the destination text you entered, your network request information and standard browser information directly to Viator so it can render its widget and measure attributed interactions under Viator’s privacy policy. Klook search and promotional widgets similarly load only after you select “Explore with Klook,” which sends standard browser and network request information directly to Klook. Journvia does not send your account identity or saved-trip record with either request.
The Travelpayouts White Label flight search loads only after you choose “Load live flight search” on the flight-planning page or follow a flight-search results link. Your browser then contacts Travelpayouts, and the airports, dates, passenger selection, browser and network request information needed for the search are processed by Travelpayouts and its booking partners. Journvia does not send your account identity or saved-trip record to the widget.
Trip.com promotional artwork is also request-gated. Selecting “Show Trip.com promotional image” loads the advertiser-issued image from Rakuten Advertising and shares standard browser and network request information with that network. The ordinary Trip.com text link does not load third-party artwork before you select it.
Audience Measurement
The public website records cookieless daily aggregate counts such as landing views, planner opens and tool uses. Campaign labels and a coarse device class may be counted, but Journvia does not create a visitor profile or retain a raw network address for analytics. Browser Do Not Track and Global Privacy Control signals disable these events.
Retention & Security
We retain operational data only as needed for the feature, security, dispute handling and legal obligations. Support requests remain in the support queue for follow-up. Tokens are stored as non-reversible hashes, transport uses HTTPS, and sensitive document-vault content is encrypted on device.
Your Choices
Settings lets you download a portable JSON export and request account deletion. A deletion request revokes server sessions immediately and enters a 7-day processing period. Personal trip and profile data is then removed; records required for tax, payment integrity, fraud prevention or legal obligations may remain only in anonymised form.
Contact
Use the Journvia support form for privacy questions. Include “Privacy” as the category. For immediate safety issues, contact local emergency services or the relevant provider.