Route Planner

Security

Companies stay apart. The rest is a plain list.

Several courier firms share one system, so the first thing to get right is that they cannot see each other. This page says what we have done and, further down, what we have not.

1Isolation

One database, separate drawers.

Your rows and another company’s rows sit in the same tables, and the database decides which ones a request may see. If we wrote a bug in an endpoint, the database would still refuse to hand over another company’s data. That is the point of doing it there rather than only in application code.

Company ACompany BCompany Casks for Bstops here

2Who sees what

Four roles.

Accounts are created by an admin. The company account signs in with the company number. Drivers and dispatchers sign in with their email. Everyone has a password. There are no invitation links.

A driver
Their own routes and their own history. Not other drivers, not other companies.
A dispatcher
Their company's routes, stops and drivers. Cannot manage users.
A company admin
Everything in their own company, including accounts and zones.
The platform operator (super admin)
Creates and suspends companies and sees usage and system health. Can act as a company when support needs it, in a session that lasts an hour and is written to an audit log.

3In place

What is done.

4Other people’s servers

Where data leaves our server.

Reading messy files. When a language model is switched on to read a photo or a messy file, the contents of that file are sent to a model provider through OpenRouter. When it is off, or unavailable, a simpler rule-based reader on our own server does the job with less skill. Either way, a person checks the result.

Map tiles. The pictures of the map in the browser and the app are loaded from a public tile service built on OpenStreetMap data. Addresses and routes are not sent there, only the requests for map squares.

Address search, road distances and route ordering all run on our own servers.

The honest bit

What is not done.

We would rather you read this here than discover it later.

  • Certifications

    No SOC 2, no ISO 27001. We are not going to say we are compliant with something we have not been audited against.

  • An independent security test

    Not done yet. We have reviewed our own code more than once, which is not the same thing.

  • Monitoring and alerting

    Error tracking, uptime monitoring and alerts are part of the work before real customers, and are not finished.

  • Encrypted storage on the phone

    The app's local database leans on the phone's own protection. Encrypting it ourselves is planned.

  • A track record

    In pilot, nothing has been through years of real use. Treat it accordingly and start with data you can live without.

Found a hole, or want to ask how something works? Write to hello@routeplanner.example. Or read how we handle the data you give us on this site.