Security and setup

We agree responsibilities and verify the safeguards below before production use.

Access and protection

Personal accounts with role-based access. Administration requires multi-factor authentication. Data in transit and stored booking data are encrypted. Significant changes are logged.

Data protection

We process booking data according to your organisation’s instructions. A data processing agreement sets out responsibilities, retention and deletion. We document processing locations, subprocessors and safeguards for any international transfers.

Integrations

We agree the required system integrations and messaging channels, then test the data flow.

Maintenance and recovery

Backups and restoration are tested before launch. We agree responsibilities for support, security updates and incidents, along with recovery targets.

From pilot to launch

We assess your current workflow and the integrations needed. We agree scope, pricing and measurable goals before setup. Bookings, changes, customer messages and safeguards are tested before production use.

How do we measure the benefit?

During the pilot, we compare booking handling time and kilometres driven with your current way of working.

How emissions are estimated

The estimate uses the additional distance and the vehicle’s emissions factor. The comparison is the most likely way the same service would run without WayLess. We disclose sources and uncertainty. Estimated avoided emissions are kept separate from the organisation’s own emissions inventory.

Updated 29 October 2026 · Aittaja Oy