Privacy Policy

Tripvia is a mileage tracking mobile application for individuals and teams to easily track and report their business trips for expense reporting, reimbursement, and tax record-keeping, operated by Weblio s. r. o., Jilemnického 1142/12, 040 01 Košice, Slovakia, IČO 57 696 497 (weblioapp.com). For privacy questions contact info@weblioapp.com.

We collect only the data you explicitly provide or that is required for the app to function:

• Email address and password (for authentication via Supabase)
• Full name, company name, company registration / Tax ID (optional, for report headers)
• Vehicle details (name, plate number, fuel type, odometer)
• Trip data: start/end addresses, distance, date, purpose
• A record of changes to your trips: when a trip is changed or deleted after it was entered, the old and new values, the time, and who made the change
• GPS location data when background tracking is enabled
• Subscription and purchase status (plan, billing period, renewal date) if you subscribe
• Your plan history, if you subscribe or unlock past months: purchases, renewals, plan switches, cancellations, refunds and month unlocks, with the price, currency, offer and store transaction ID the store reports
• Crash and performance diagnostics (device type, OS version, app errors)
• Bug reports you send from the app: your description, an optional screenshot, and device details (model, OS and app version)
• If you join an organisation (company/team): its leader sees your name and the trips you record for it

We use your data to provide the trip logging, reporting, and subscription features of the app. Trip data is used to generate trip and expense reports, including for tax record-keeping, at your explicit request.

We also use some of it for two further purposes, based on our legitimate interest:

• Support and refunds. To handle a support or refund request, we look at your plan history and at how the account was used in the months you paid for: the number of trips, the reports generated and the months unlocked.
• How our plans are used. We look at plan histories in aggregate, for example how many people switch plans or cancel, to understand how our plans are used.

Authorised Tripvia staff can view an account’s plan history and a summary of its use (trips, reports and month unlocks per month) to handle support and refund requests.

We do not sell, share, or use your data for advertising or profiling.

The record of changes keeps your logbook credible for tax purposes. In Germany and Austria the app shows it and prints it in logbook reports, as tax rules there expect; in other countries it is kept but not shown. It is deleted with the trip or with your account.

Background location tracking is optional and must be explicitly enabled in the app settings. While active, a persistent notification shows tracking is running (Android foreground service requirement). Location data is used only for automatic trip detection. Raw GPS coordinates are stored temporarily and then processed into trip records. You can disable tracking at any time in Settings.

Paid plans are billed and processed entirely by Google Play (Android) or the App Store (iOS) — we never see or store your payment card details. We use RevenueCat to manage subscription status across devices. RevenueCat receives your purchase receipt and a pseudonymous account identifier (your Tripvia user ID) from the store, and forwards each purchase event to us: purchases, renewals, plan switches, cancellations, refunds and month unlocks, each with the price, currency, offer and store transaction ID. The app uses them to unlock the features and months you paid for.

Restore purchases moves the purchases of the store account on your device to the Tripvia account that is signed in. If they belonged to another Tripvia account, that account loses them.

We keep a history of your plan changes (purchases, renewals, switches, cancellations, refunds and month unlocks) for the purposes in section 3. It is deleted with your account.

In an organisation, the leader sees the organisation’s plan and, when the organisation has more members or vehicles than its plan allows, which members and vehicles are paused.

Data is stored securely on Supabase (supabase.com) servers in the EU region. All connections are encrypted via HTTPS/TLS. Row Level Security, enforced at database level, limits each user to their own data. The only exceptions are the ones this policy names: an organisation’s leader (sections 2 and 5) and authorised Tripvia staff (section 3).

Your data is retained for as long as you have an active account. You can delete your account and all associated data at any time in the app (menu (☰) → Account → Delete account), as described at tripvia.net/delete-account, or by emailing info@weblioapp.com. Generated reports stored in cloud storage are also deleted upon account deletion. Trips you recorded for an organisation remain available to its leader.

As a user in the EU/EEA you have the right to: access your personal data, correct inaccurate data, request erasure, restrict processing, and data portability. To exercise these rights contact info@weblioapp.com.

• Supabase (database, auth, storage) — supabase.com/privacy
• Google Maps / Places API (address search, routing) — policies.google.com/privacy
• Google Takeout data processed locally and on our servers only when you initiate an import
• RevenueCat (subscription management) — revenuecat.com/privacy
• Google Play / App Store (payment processing) — respective store privacy policies
• Sentry (crash and error diagnostics) — sentry.io/privacy

This app is not intended for children under 16. We do not knowingly collect data from children.

We may update this policy. The current version is always available in the app under Settings → Privacy Policy, and at this URL. Significant changes will be communicated via the app.