What we keep, and who else sees it

What we keep

We keep what our customers and their people put into the service, for as long as it is needed:

• Accounts: the names, email addresses and roles of the people who use the panel.
• Where vehicles are and were, as their devices report it, and what a vehicle reports about itself when its package includes vehicle data. Each customer chooses how long this is kept; older data is deleted.
• Routes and their history, the photos that prove a stop was done with the place they were taken, and the issues found at a site.
• Callback requests from our home page: name, company and phone number, deleted 90 days after we called.
• Security reports: what the sender wrote and the contact they chose to leave.

Who else sees what

We neither sell our data nor give it to anyone for their own use. We use no advertising or analytics services and send no email. These companies see some of it while doing their part:

• OpenFreeMap (openfreemap.org) draws our maps. When a map opens, your browser loads it straight from OpenFreeMap, which therefore sees your IP address and the area and zoom of every map you look at, and so roughly where your fleet drives. It gets no cookie, no account and nothing from our database.
• Fly.io runs our servers and Aiven runs our database, both in Frankfurt, Germany. They store and process everything above on our behalf.
• Cloudflare carries the traffic between your browser and our servers and sees your IP address and the pages you open.
• If you turn on notifications, your browser's maker delivers them: Google for Chrome, Mozilla for Firefox, Apple for Safari, Microsoft for Edge. They see when a notification reaches your device and how large it is, not what it says, because it is encrypted for your browser alone.
• When a planner searches for an address, our server asks OpenStreetMap's search service (Nominatim) for it. It receives the words searched for, from our server, and nothing about you.
• When stops are sorted by road, our server sends the places of those stops, and nothing else, to OpenRouteService, run by HeiGIT in Heidelberg, Germany.
• When a driver opens a stop in Google Maps, Apple Maps or Waze, that app receives the place of the stop. The driver chooses the app.
• Our devices reach us over a mobile network. The network operator carries their encrypted traffic and, as with any phone, knows which cell a device uses.

Your rights

You may ask what we keep about you, and have it corrected or deleted. Most of it belongs to the customer you work for, so ask them first. You can also leave your number with the form on our home page and we will call you back.