Frequently asked
questions

Not necessarily. Travia can orchestrate operations around your current tools, aggregate their data and digitalise the steps that are still scattered. Whether an existing tool is replaced is your decision, taken in the light of scoping.

Round planning, field execution, delivery traceability, incidents and alerts, fleet maintenance, performance analysis and integrations with your ecosystem.

Roles, statuses, alerts, forms, indicators and assignment rules are defined from your actual processes. That is the purpose of the scoping phase, before any deployment.

Through a mobile interface that brings together jobs, instructions, navigation, forms, photos, signatures and exceptions. It is designed to be used while stationary, including with gloves.

Actions carried out in the field are kept on the device and synchronised as soon as the connection returns. The job timeline keeps the actual time of each event.

Punctuality, service rate, execution time, kilometres, fuel consumption, incidents, capacity or maintenance — with views tailored to each role.

No. The values visible in the cockpit, the map and the simulator are explicitly demonstration data. No testimonial, customer reference or unverified gain is presented.

Interfaces, jobs and instructions can be presented in the working language planned for each team, in particular French, German and Italian.

A first conversation maps a priority workflow. A targeted demonstration is then prepared, with a clear scope and clear next steps.

It depends on the chosen scope, the quality of the available data and the availability of your teams. The method works in stages — scope, prototype, connect, deploy — so that a first real use happens before full roll-out.

Yes. Integrations are defined during scoping: APIs, imports, exports and automated flows, according to the systems already in place — ERP, TMS, telematics, HR, business intelligence.

No, as long as the data is accessible. Travia uses existing data flows rather than imposing hardware. The exact arrangements are checked during scoping, source by source.

Scoping identifies the missing master data and the order in which to make it reliable, so as to start with a limited scope whose data is usable.

An evaluation phase or a demonstration on your own flows can precede the subscription. Its duration, scope and conditions are set in writing.

The customer. NETZERO SWISS AG acts as processor within the meaning of Art. 9 FADP and Art. 28 GDPR, and only processes data on the customer’s documented instructions. The framework is published on the Data processing page.

On dedicated infrastructure in France, a state listed in Annex 1 DPO among those providing adequate protection within the meaning of Art. 16 para. 1 FADP. Any transfer to a state without adequate protection may only take place with the safeguards of Art. 16 para. 2 FADP.

Perimeters are separated by organisation, site, activity, role and job. Access follows responsibility, important actions are logged, public flows are encrypted and so are backups. Details are on the Data security page.

Location functions concern vehicles and jobs, and are activated by the customer within the scope it defines. Under Swiss law, Art. 26 ArGV 3 prohibits systems intended to monitor workers’ behaviour at their workplace, and Art. 328b of the Code of Obligations limits the processing of employee data to what is necessary. Configuration is the responsibility of the customer, who informs its teams.

No. Round proposals, arrival estimates and alerts are decision aids. No automated individual decision producing legal effects or significantly affecting a person, within the meaning of Art. 21 FADP or Art. 22 GDPR, is taken.

The public site sets a single cookie, and only when you change language: it keeps the chosen language for up to 182 days and reopens the site in that language. Without that choice, the language is inferred from your canton, without storing anything. No third party can access it, and the Cookies and trackers page lets you refuse storage in one click. No third-party audience measurement tool is integrated. The platform sets two strictly necessary cookies — authentication and security — and a display preferences cookie that can be refused. Details are on the Cookies and trackers page.

It remains exportable for thirty days. After that, it is deleted or anonymised within ninety days, subject to legal retention obligations. Each backup copy disappears thirty-five days after its creation.

According to the subscribed scope: activated modules, number of vehicles tracked, number of named users, sites covered, data volume and support level. Details are in the offer. Go-live and deployment support are invoiced separately.

Unless the offer provides otherwise, twelve months, renewed tacitly for twelve-month periods, with three months’ notice before each renewal date.

In Swiss francs, excluding taxes. When the publisher is subject to Swiss VAT, it is added at the statutory rate on the invoice date, the standard rate being 8.1% at the date this page was published. The invoice states the applicable status.

Yes. Additional licences are invoiced pro rata for the remaining period and aligned with the main renewal date. A reduction in scope takes effect at the next renewal.

Thirty days net from the invoice date. After that, default interest of 5% per year is due in accordance with Art. 104 para. 1 of the Code of Obligations.

Swiss law, excluding conflict-of-law rules and the Vienna Convention. The agreed place of jurisdiction is the registered office of NETZERO SWISS AG in Zurich, subject to mandatory jurisdictions.

A monthly rate of 99.5%, excluding planned maintenance and excluded cases, with a credit mechanism in the event of a shortfall. Details are on the Service levels page.

From 8:00 to 18:00 Swiss time, Monday to Friday, excluding public holidays in the canton of the registered office. Response times depend on severity, from two business hours for a critical incident to three business days for a request for information.

Routine changes are delivered without noticeable interruption. Planned maintenance is announced at least five business days in advance and in principle carried out at night.

By email, with a description, the steps to reproduce and the estimated impact. An acknowledgement is sent within three business days and a status update within fifteen business days. The publisher undertakes to take no action against anyone reporting in good faith, under the conditions set out on the Data security page: no access to third-party data beyond what is necessary, no degradation of the service, no disclosure before the fix.