Trust and security

People stay in charge of the plan

Routite proposes; dispatchers decide. Every change is explained, approved and logged. This page also says plainly what is planned and what is not yet in place.

Our rules

  1. ExplainEvery moved stop has a reason
  2. ApproveA person or a rule they set
  3. LogWho, what, when, why
  4. LimitCopilot acts within your role

Stop 01 · Principles

What we will not compromise on

1

Approval by default

Nothing reaches a driver without approval unless you wrote a rule allowing it.

2

Reasons, not black boxes

Each change carries the solver's reasons, in words a dispatcher can check.

3

Stable plans

Re-solves penalise changes to drivers who are on track.

4

Honest numbers

We publish pilot results only with the partner's approval and the method attached.

5

Your data stays yours

Your history trains your models. Cross-customer learning needs your opt-in.

6

Humans can always override

Overrides are logged and respected by the next re-solve.

Stop 02 · Method

How a change gets approved

  1. 1propose

    Proposal

    Optimize produces a plan with a diff and reasons.

    Who Routite
  2. 2check

    Rule check

    Approval rules decide whether it can go through or needs a person.

    Who Rules you set
  3. 3decide

    Decision

    The dispatcher approves, edits or rejects in Copilot.

    Who Dispatcher
  4. 4record

    Record

    The decision, the person and the reasons are written to the change log.

    Kept Per your retention policy

Stop 03 · Regulatory context

Rules Routite helps you respect

Routite supports compliance work; it does not certify compliance. Responsibility for meeting these rules stays with the operator. SOC 2 and ISO 27001 are planned audits, not held certifications.
AreaExamplesHow Routite helpsStatus
Driver hoursEU drivers' hours rules, US FMCSA hours of serviceEncodes shift, break and drive-time limits as constraintsIn build
Data protectionGDPR, UK GDPRData residency by region, role-based access, retention settingsPlanned
Security assuranceSOC 2 Type IIControls and auditPlanned
Security managementISO/IEC 27001Information security management systemPlanned
Low-emission zonesCity clean-air zonesVehicle-type constraints per zonePlanned

Stop 04 · Audit trail

Every change, written down

The change log answers the questions that come up after a bad day: what moved, who approved it, and what the solver knew at the time.

Logs can be exported for your own audit or claims processes.

Change log · Zone 4

Example
  • 10:47:12re-solveVan 3 down · 11 stops proposed
  • 10:48:03dispatcher J.Approved with edit: stop 230 held
  • 10:48:04edgePushed to vans 1 and 4
  • 10:52:40ruleSwap within van 1 auto-approved
Example Entries are illustrative and show what is recorded for each change.

Stop 05 · Security

How data is protected

AccessRole-based access per region and depot; single sign-on planned.
EncryptionTLS in transit and encryption at rest in Routite cloud.
IsolationEach customer in a separate tenant; VPC and on-premises options planned.
KeysScoped API keys with rotation.
DisclosureReport a vulnerability to security@routite.com.
Sub-processorsListed before any pilot contract is signed.

Stop 06 · Questions

Questions security teams ask

Is Routite SOC 2 certified?

No. Routite is pre-launch. A SOC 2 Type II audit and ISO 27001 are planned; we will say when each is complete.

Can Routite guarantee hours-of-service compliance?

No tool can. Routite plans within the limits you encode and flags conflicts, but the operator remains responsible.

Do you train shared models on our data?

Not without your opt-in. By default your data trains only your own models.

Stop 07 · Destination

Next step

Send us your security questionnaire

We answer honestly, including where something is planned rather than done.