Your data belongs to you.
Updated 13 October 2026. The controller for the processing described below is Batitrax, a French SASU registered under SIREN 106 479 587, at 47 rue Vivienne, 75002 Paris, France, publisher of the Rouliva service. Contact: contact@rouliva.eu.
Data collected
Rouliva processes account and contact data, vehicle and mileage settings, schedules and usual places, projects, trips and locations needed to reconstruct them, expenses, receipts, expense reports, preferences, technical security information, aggregate usage milestones and billing data. Calendar data is accessed only if you voluntarily connect Google Calendar.
Purposes and legal bases
Data is used to create and secure accounts, detect and reconstruct trips, calculate allowances, prepare expense reports, synchronise devices, provide support, measure service activation and retention in aggregate, and manage subscriptions. Processing relies as appropriate on performance of the contract, consent, legal obligations or our legitimate interest in securing the service.
Cookies and local storage
The public website contains no advertising trackers. Technical storage remembers your cookie choice and, if you change language, your display preference until you change them or delete the site data. Session and security cookies are essential only when you use the application. With your consent, Rouliva may also remember the country selected for pricing and measure website visits, landing pages, visit sources and device types with a pseudonymous identifier. This identifier expires after no more than 13 months and its lifetime is not extended on each visit; the session identifier disappears when the tab is closed. The corresponding traffic data is deleted from the server after 25 months. No IP address or email address is stored for this measurement. You can refuse or withdraw your consent at any time using the “Manage cookies” button; refusal removes previously stored optional preferences.
Background location
Rouliva collects location data to detect and record business trips even when the app is closed or not in use. Tracking runs only when enabled and during the days and hours selected by the user. It can be paused or disabled at any time. Location data is never sold or used for advertising.
Trip addresses
To convert departure and arrival coordinates to addresses, Rouliva first uses the Android geocoding service on Android devices. On iPhone and the Web, and if the Android service fails, the lookup is handled by Rouliva servers. When the company country is France, IGN’s geocoding service (Géoplateforme) is queried first; Google Maps Geocoding may be used as a fallback or for other countries when configured. Departure and arrival positions may therefore be sent to the geocoding provider used. The full route is not sent for this lookup. Resolved addresses are stored in your account and synchronized across your devices.
Optional features
Google Calendar is read in view-only mode to match appointments with trips. When receipt analysis is used, the image is processed by the AI model installed on the Rouliva server and is not sent to an external AI provider. These features can be disabled independently.
Recipients
Data is available to authorised account users and, only as necessary, to hosting, email, payment and calendar providers. Stripe processes website payments; Google Play processes purchases in the Android app; Apple processes App Store purchases on iPhone and iPad. Rouliva does not sell or rent personal data.
International transfers
Some international providers may process data outside the European Economic Area. Such processing relies on an adequacy decision or recognised safeguards, including the European Commission standard contractual clauses.
Retention
Service data is retained for the life of the account and deleted within 30 days of a verified request. Residual backups are overwritten within 90 days. Security logs are kept for up to 12 months, contact requests for 3 years after the last exchange, and invoices or accounting records for the applicable statutory period, generally 10 years.
Security
Transfers use HTTPS. Passwords are stored as Argon2id hashes; sessions, roles and access are controlled. Offline data remains in app storage until synchronisation. Safeguards are reviewed regularly.
Your rights
You may request access, correction, deletion, restriction, portability or objection where applicable, and withdraw consent without retroactive effect. Contact contact@rouliva.eu. Proportionate identity verification may be required. You may also contact your competent data protection authority.
Account deletion
Request deletion from the app settings or at https://rouliva.eu/en/suppression-compte. The account and associated data are deleted except where retention is required by law. Deleting the account does not cancel Google Play or Apple (App Store) subscriptions: cancel them separately through the relevant store. For a website subscription paid through Stripe, use ‘Manage my subscription’ before requesting deletion.
Children and changes
Rouliva is intended for professionals and is not designed for children. Material policy changes will be announced in the app or through an appropriate channel before taking effect.
Google Calendar: data accessed
Connecting is optional. Rouliva requests only calendar.events.readonly and reads your primary calendar. Requested fields are event IDs, status, title, location, start/end dates and times, calendar time zone, and attendee self/responseStatus flags to exclude declined events. Event descriptions, attachments and attendee names or email addresses are not requested. OAuth tokens are stored encrypted on the server.
Google Calendar: purpose and retention
Rule-based location and time matching proposes or fills an editable trip title; no AI model performs this matching. An optional setting matches times only, even without a location, with a 30-minute tolerance. On synchronisation, the working cache retains events from 45 days in the past to 90 days in the future; incremental updates may receive changes outside that window before filtering. Disconnecting Calendar in settings deletes the connection tokens and server calendar cache. Titles already copied to trips and expense reports are not automatically removed. You can revoke access in your Google account and request deletion at contact@rouliva.eu. The general retention and backup periods below still apply.
Google Calendar: recipients and geocoding
Rouliva processes data on its infrastructure hosted by o2switch and OVHcloud and synchronises it with your devices. An event location string may be sent to Google Maps Geocoding, when configured, or to the Android geocoding service provider to obtain coordinates. This geocoding request does not include the event title, participants or OAuth tokens. Titles copied to trips may appear in expense reports, approval workflows and exports/API responses accessible to recipients you authorise. Hosting providers and, for requested deliveries, email providers process data only to support these features. No raw, aggregated, anonymised or derived Google data is sold or transferred to AI providers for model training.
Self-hosted AI and Google data separation
Receipt recognition is separate: receipt images are processed on Rouliva servers using PP-OCRv6_small_det and PP-OCRv6_small_rec, with PP-LCNet_x1_0_doc_ori for orientation and UVDoc when unwarping is needed. These are self-hosted models, not third-party AI API calls or on-device processing. The Calendar integration does not send its events, tokens or derived trip titles to the OCR engine, its correction collection or any model provider. Google data is not used to create, train, fine-tune or improve AI/ML models, including foundational or general-purpose models. This prohibition includes aggregated, anonymised and derived data.
Google Limited Use commitment
Rouliva’s use of data received from Google Workspace APIs, including derived data, complies with the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. This data is not used for advertising, sold or used to train AI. References: https://developers.google.com/terms/api-services-user-data-policy and https://developers.google.com/workspace/workspace-api-user-data-developer-policy.