A separate database per client
Not a shared table with a client column and a filter on every query. Each client gets its own PostgreSQL database. A filter is a line of code someone can forget; a separate database isn’t.
03 · Security & privacy
Private by construction, not by promise
You can put your most sensitive work in here. Not because we promise to be careful, but because one client’s data is physically unable to reach another’s, and nothing you hold ever leaves hardware we run.
UK-resident · encrypted at rest · never pooled, never sold, never used to train AI
Own database
per client, never a shared table
UK
dedicated hardware we run
Local only
the assistant never calls a cloud AI
DPA
signed before you go live
Isolation
Can another client’s data reach mine?
No. And not because a query is written carefully. Every system says client data is separated; the question worth asking is what the separation is made of. Yours is a separate database — that’s the failure we designed out first.
A scoped role that cannot reach anywhere else
The credentials your automations run as can reach your database and no other. Even one written wrongly has nowhere else to go, because there’s no shared credential anywhere in the system.
Isolation by construction, not by convention
The test we hold ourselves to isn’t “would a query leak across clients”. It’s “could it, by any route”. That’s the one failure we treat as unrecoverable, so it’s designed out rather than guarded against.
Where it lives
Where does my data actually live?
On dedicated hardware red-route owns and runs, in the United Kingdom. Being straight about it: the hardware’s ours, not yours. We run it, encrypt it and carry the responsibility for it as your processor. That’s the point of the arrangement, not a caveat on it.
Dedicated hardware we run, in the UK
Your data sits on machines red-route owns and operates in the United Kingdom. Not pooled in a hyperscaler region, not replicated to wherever capacity was cheapest this quarter.
Never at your premises
We never install hardware at a client site. You get the privacy of dedicated machines without becoming responsible for a box in a cupboard.
Encrypted at rest, with encrypted backups
Full-disk encryption on every machine, and encrypted backups held off the primary box. Each production box runs with a second as an encrypted replica and warm standby.
Per-client encryption keys where it matters
For sensitive work — youth services, safeguarding-grade records — your data gets its own encryption key by default. Available to any client who wants it. It also means the data can be permanently retired on request: destroy the key and it is unrecoverable.
Access
Who can actually get in?
Your team, the partners you approve, and nobody else. The only things a stranger can reach are your login page and the forms you deliberately publish. That’s the whole list.
Only the portal is reachable
Your portal and its forms are the only things exposed to the internet. The database, the admin tooling, the automation editor, backups and server management aren’t reachable from outside at all.
Everything internal stays internal
Traffic between the automation layer and your database never leaves the machine. Sending your data out across the public internet to reach a database sitting on the same hardware isn’t a shortcut we take.
Your own domain is the only front door
Portal, API and form routes are all served under your domain, same-origin. No red-route address ever appears in a partner’s browser.
Staff tooling is locked separately
Our own admin screens sit behind their own access control, restricted to red-route staff. You never get a login to them, and our access is technical only. We don’t make your decisions or act inside your portal as you.
AI
Does the assistant send my data anywhere?
No, and there’s no version of this where it does. It’s the commitment most likely to get quietly walked back once a product gets busy, so here’s exactly where the line is — and what happens when the model is down.
The assistant runs on hardware we run
It uses a model on the same dedicated hardware your data sits on. What it needs is fetched on our server, narrowed to the person asking, and handed to that model. None of it travels to a third-party AI provider.
There is no cloud fallback
If the model’s unavailable, the assistant says it can’t answer. It doesn’t quietly fail over to a hosted AI, because that would defeat the whole arrangement at exactly the moment nobody was watching.
Nothing is used for training
Your data is never sold and never used to train any model — ours or anyone else’s. We’re the custodian of it, not the product being funded by it.
Claude is a build tool, not a runtime dependency
AI agents build and maintain the platform, working from written specifications and invented data. No part of your portal calls a third-party AI while it’s running.
Governance
What is mine, and what if I leave?
Holding your data carries a legal duty of care, and that’s settled in writing before anyone logs in. Underneath the paperwork, three things are yours.
Your data is yours
We process it on your instructions and nothing else. We don’t train AI on it, we don’t mine it, we don’t sell it, and we never send it to a third-party AI.
Your configuration is yours
How the system is shaped around your workflow — your roles, records, forms and automations — belongs to you and leaves with you.
Your key is yours alone
Your data sits in its own encrypted database with its own key, shared with no other client. We hold that key as your processor. When you leave we destroy it, and your data becomes unrecoverable — in the live system and in every backup.
We are your data processor
Under a data-processing agreement signed before you go live, with documented security measures — including how long records are kept, which is your policy written down rather than a default nobody chose. You remain the controller: it is your data and your decisions.
Some records need a stricter path
Anything that needs a stricter path sits on its own, with its own storage, opened only by people you have specifically granted it to, and kept out of exports, lists and anything the assistant can see. How protected records are handled →
Leaving is a supported operation
You can have your data out in a usable form, at any point, without negotiating for it. An exit that depends on our goodwill isn’t an exit.
Worth saying plainly
What we do not claim
We don’t say the hardware is yours or that you control the infrastructure — it’s ours, and we run it. We don’t claim certifications we haven’t completed. And we don’t describe the portal as safe for your own end customers, because it’s built for your organisation and the partners you approve, and that boundary is part of what makes the rest of this hold.
That is the due diligence. Now the price.
If you’re responsible for sensitive information, bring the rest of your list and we’ll answer it. Better than a brochure. If you’d rather see the numbers first, they’re one click away.