Your orders do not sit in a shared table
Every company gets its own database. Not a row tagged with a company id in a shared table — a separate database.
Why this is not the same as access control
In most systems every customer data sits in the same tables, separated by a condition in the query. One mistake in that condition and a customer sees somebody else data.
Here the separation is physical rather than logical: each company has its own database and its own database user. A query that forgot to filter by company still has nowhere to go for another company data.
Where the data physically sits
- The European Union. Servers and file storage in a Frankfurt data centre. For hosting there is no transfer outside the EEA.
- Backups. Taken regularly, restorable to a chosen date.
- Provider credentials are encrypted. Keys for a GPS provider or for e-invoicing are stored encrypted, not as text in a settings screen.
Who sees what inside your company
Access to sections is set by roles. A dispatcher need not see financial amounts; an accountant need not see vehicle tracks.
Modules are installed separately: if you do not take accounting, its tables do not exist in your database at all.
What we do not do
We do not pool customer data into shared analytics and we do not use it for our own trips. We are a transport company, and we understand how this question looks from your side — which is why we answer it with architecture rather than a promise.