Security
What we hold, and what we will not claim.
Your workspace holds client names, addresses, movements and money. This page states how that is handled, and it also states the badges we have not earned rather than implying them.
Where it lives
Operations data is hosted in the EU.
Where the records sit, who they belong to, and what we will never do with them.
EU hosting
The records the product runs on: enquiries, bookings, clients, drivers, vehicles and invoices.
Tenant isolation
Queries are scoped to the tenant that owns the record.
Your client list is not a product
No marketplace, no selling your work on, and no contacting the clients in your workspace.
Transport encryption
Traffic between the browser, the driver portal, the client portal and the workspace runs over TLS.
AI processing, named
Quote drafting and email parsing run on Anthropic's Claude models as a sub-processor. The AI drafts against your rate rules and a person approves before anything reaches a client.
Who sees what
Four audiences, four different views.
A driver, a partner and a corporate booker all touch the same job. None of them sees the same thing, and none of them sees what you see.
Your team
Roles decide who sees finance and who is allowed to change a price.
Drivers
The portal shows their assigned jobs. Not your rates, not the margin, and not the rest of the night.
Partners
A tokenised link scoped to that leg. Not your client relationship, and not your sell price.
Clients
The portal is scoped to the account that booked.
Money
We never hold a card number.
The safest way to handle card data is to never receive it. Payments run through your own Stripe account, not through ours.
You are the merchant of record
The payment link belongs to your own Stripe account, so the client pays you rather than us.
Card data stays with Stripe
4fleet stores the payment status. There is nothing card-shaped here to leak.
Your subscription is separate
What you pay 4fleet and what your clients pay you are two different flows.
Leaving
The exit is documented, not just permitted.
A vendor that makes leaving awkward is telling you something. Here is ours, in writing.
Export during the trial
Operational data leaves the workspace before you have paid anything, which is the only honest time to test it.
Export as a paying customer
The same export stays available once you are on a plan. Getting your data out is not a retention lever.
Take it before you close
Export first, cancel second. It is the same advice we give about the system you are leaving now: read the switching plan →
Say what it doesn't do
Badges we have not earned.
Most security pages are a wall of logos. This is the part of ours that says no.
No certification logos we do not hold
Ask us for an attestation and you get a straight yes or no, not a badge on a page.
No uptime figures we have not measured
Ask what the last quarter actually looked like.
Anything incomplete is labelled partial
Where a capability is half-built, the feature index says partial rather than shipped.
Security questionnaire from a corporate client? Send it over and we will answer it as it is written, including the rows where the answer is no. Send the questionnaire →
Free trial
Test the exit first.
Open a trial, import a week of work, then export it back out before you have paid a cent. That is a better answer than anything on this page.
7-day free trial. No credit card required. Trial allowances apply: 2,000 AI operations, 150 bookings and 5 users; bookings continue above the allowance without automatic charges.