Data We Process
Account identity comes from Firebase authentication. Saved trips, itinerary requests, 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.
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.
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.
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.
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.
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.