Skip to content
DispatchMe
PricingAbout
Log inStart free
DispatchMe

Product

  • Product overviewHow bookings, dispatch and the apps fit together
  • DispatchWho to send, and why, in plain words
  • Driver appAccept or pass with a clock, then drive
  • Passenger appBook, see the fare and track the car
  • Online bookingA booking page and a widget for your site
  • Account customersCredit limits, cost centres, monthly invoices
  • Driver settlementsCommission or rent, balances, the weekly run
  • Partner overflowPass jobs to, or take them from, other offices
  • Driver complianceDocuments read and checked before work
  • Booking from messagesPaste a WhatsApp or email, get a draft booking
  • Caller IDWho's ringing, and their usual journey

Who it's for

  • Small fleetsFive to thirty cars, set up tonight
  • School and council contractsRepeat runs, arrive-by times, records
  • Airport transfersSeats, bags and pickups at the terminal
  • Several officesDrivers and jobs across offices

Resources

  • GuidesRunning a UK private hire office
  • Switching to DispatchMeBring your drivers, cars and customers across
  • IntegrationsMaps, messaging, flights and your website
  • SupportHelp for offices, drivers and passengers
  • Security and dataWhere your data lives and who can see it
  • Get the appsAndroid apps for drivers, passengers and offices
  • Pricing
  • About
Log inStart free
  1. Home
  2. Security
Security and data

Where your data lives, and who can see it.

DispatchMe runs on one server at Hetzner in Nuremberg, Germany, with its database on the same machine and closed to the outside. Everything travels over HTTPS, the database is backed up every night, and each member of your staff sees only what their role allows.

This page says what we do, and also what we don't do yet.

Where is the data kept?

  • One server at Hetzner in Nuremberg, Germany, running both the application and the PostgreSQL database
  • The database only accepts connections from the server itself, and the firewall lets in only web traffic and our own administration
  • Every connection is HTTPS, with certificates from Let's Encrypt that renew automatically
  • Browsers are told to use HTTPS only (HSTS, for a year), and the site sends a content security policy and other security headers
  • Uploaded documents are kept with your office's data and only served to people signed in to that office

Backups and monitoring.

Backups
WhatHow oftenKept
Database copyEvery night14 days
Automatic restore checkEvery Sunday: restores the latest copy and checks its row counts against the live databaseAlerts us if it fails
Whole-server backup (Hetzner)Every day7 days

The site is checked every minute from the server. If it stops answering, or a backup fails, we get an alert on our phones.

What we don't do yet

All backups are held at Hetzner in Germany; there is no copy with a second provider. Backups are not separately encrypted. The minute-by-minute check runs on the same server, so nothing outside watches it yet.

Who in your office can see what?

Every member of staff signs in as themselves and has a role. Every important action is written to an audit log you can read.

Roles and permissions

Eleven roles, from Owner and Operations Manager to Dispatcher, Finance, Customer Service and Read-only, built from 36 separate permissions. Add or remove a single permission for one person.

Passwords and sessions

Passwords are stored as salted scrypt hashes, never as text. Sign-in is rate limited. Sessions end after 12 hours unless someone chooses to stay signed in, and a password reset signs them out everywhere.

An audit log

Sign-ins, password resets, bookings, driver approvals, document reviews, exports, API keys and data erasure are recorded with who did it and when. So is any time our support staff enter your console.

Offices kept apart

Every request is tied to one office, and its data is filtered to that office. Files are stored under the office's own key and checked before they are served.

API keys and webhooks

API keys are shown once and stored only as a hash, with read or write scope and a rate limit. Webhooks go to HTTPS addresses only and every delivery is signed.

Drivers checked before they work

A driver can't go online until approved, with every required document reviewed and in date. Compliance

Which services process the data?

Some outside services do part of the work. The first group is used for every office. The second is only used when that feature is switched on. Our privacy policy has the full detail.

Service providers
ProviderWhat forWhen
HetznerThe server and database, in Nuremberg, GermanyAlways
TomTomRoutes, journey times and address searchAlways
postcodes.ioTurning postcodes into map positionsAlways
MigaduSending email from our own domain, such as password reset codesAlways
Expo and FirebasePush notifications to the phone appsAlways, for app users
Google MapsThe map on the office's screenIf the office chooses Google maps
AnthropicReading a pasted booking message into a draftOnly if AI reading is switched on
TwilioWhatsApp and text messages, calls between driver and passenger, and your office line for caller IDOnly for the features your office uses
FlightAwareFlight status for airport bookingsOnly if switched on
DVLA Vehicle Enquiry ServiceChecking a vehicle by its registrationOnly if switched on
what3wordsA three-word location for a pickupOnly if switched on

DispatchMe doesn't take card payments, so no card details pass through it. Passengers pay their driver.

Getting data out, and deleting it.

Export

  • Record of bookings, staff register, complaints log and driver and vehicle documents, as CSV or PDF for any dates
  • Reports as CSV
  • Every export is noted in your audit log
  • For a complete copy of your office's data, email us

Delete

  • Passengers can delete their account in the app, under Profile: their contact details go at once, and their name comes off booking records when the 12 months are up
  • Your office can erase a passenger's personal details; their past rides stay on your records without them
  • Rides are archived, not deleted: an office can archive a booking and restore it later
  • The record of each booking is kept for at least 12 months and can't be changed
  • How passengers and drivers ask for deletion: delete your account

Questions offices ask

Where is my office's data stored?

On one server DispatchMe runs at Hetzner in Nuremberg, Germany. The application and its PostgreSQL database are on the same server, and the database only accepts connections from that server.

How often is it backed up?

The database is copied every night and each copy is kept for 14 days. Every Sunday an automatic check restores the latest copy and checks its row counts against the live database. Hetzner also backs up the whole server daily, keeping 7. All backups are held at Hetzner in Germany.

Can I stop a dispatcher seeing prices or reports?

Yes. Each member of staff has a role, such as Dispatcher, Finance or Read-only, and you can add or remove single permissions for one person.

Does DispatchMe have two-factor sign-in?

Not yet. Passwords are stored as salted scrypt hashes, sign-in attempts are rate limited, and resetting a password signs that person out everywhere.

Can I get all my data out?

You can export the record of bookings, staff register, complaints log and documents as CSV or PDF, and reports as CSV. For a complete copy of your office's data, email us and we will prepare it.

Related

  • Privacy policyWhat personal data DispatchMe holds and why.
  • ComplianceDocuments, expiry alerts and the compliance export.
  • AboutWho we are and how DispatchMe is built.
  • ContactQuestions about security or data: email us.

Look round before you decide.

The live demo is a made-up London fleet: try the roles, the audit log and the exports. Or start free with your own office.

Start freeTry the live demo
DispatchMe

Taxi and private hire dispatch software for UK cab offices. Bookings, dispatch, drivers and passengers in one system.

support@dispatchme.co.uk

Get the Android apps

Product

  • Product overview
  • Dispatch
  • Driver app
  • Passenger app
  • Online booking
  • Account customers
  • Driver settlements
  • Partner overflow
  • Driver compliance
  • Booking from messages
  • Caller ID

Resources

  • Guides
  • Switching to DispatchMe
  • Integrations
  • Support
  • Security and data
  • Get the apps

Company

  • About
  • Contact
  • Pricing
  • Book a demo

Legal

  • Privacy policy
  • Terms of use
  • Delete your account

© 2026 DispatchMe. Hosted in Nuremberg, Germany.

DispatchMe is a trading name. The operating company is being registered; its name, number and registered office will appear here as soon as registration completes.