Under the hood

How we locked down TrustPoint

TrustPoint holds the proof that the right people are insured and safe to be on a building site. That's exactly the kind of information that has to be airtight. Here's how we keep it that way, in plain English first, then the detail for the technically minded.

The plain version

Strip away the jargon and the job comes down to four things.

Everyone gets their own locked drawer

A builder only ever sees the contractors they actually work with. A contractor only sees their own paperwork. Nobody can wander into anyone else's records.

A logbook written in permanent ink

Every important action is written into a sealed logbook that can't be quietly edited or have a page torn out. If anyone tried to change history, it would show.

It can prove what was true on the day

If a safety regulator asks "was this crew compliant last Tuesday?", TrustPoint can show exactly what was valid on that date, not just how things look today.

Real licences, not just claims

A contractor can't simply say they hold a licence. TrustPoint checks the official government registers, so what you see has been confirmed at the source.

We tried to break in, on purpose, before anyone real could.

Before TrustPoint went near a paying customer, we put it through round after round of security audits where the whole goal was to break it. Find the gap a determined attacker would go for, then close it and check it stayed closed. Every finding was fixed and re-tested. That isn't a one-off box we ticked either; it's part of how we keep building it.

For the techies

The disciplines, not the blueprint. We'll happily build the same rigour into your project.

access control
Every read and write is governed by an explicit relationship between two parties, with least-privilege roles layered on top. You can only ever reach data you are entitled to, by construction rather than by hoping the UI hides it.
tamper-evident log
A cryptographically chained, append-only audit trail. Each entry is sealed against the one before it, per organisation, so any insertion, edit or deletion breaks the chain and is detectable rather than silent.
append-only records
Compliance documents are never edited in place. A new version supersedes the old, so the full history is preserved and nothing is quietly overwritten.
point-in-time
Status is computed and snapshotted over time, so the system can reconstruct exactly what was valid on any past date. That is the whole point when a regulator asks after the event.
injection-safe
Every database query is parameterised and every value rendered to a page is escaped, so the classic injection and cross-site-scripting routes are closed by default, not as an afterthought.
request integrity
Anti-forgery tokens on every state-changing action, rotated after use, so requests can't be forged or replayed against a logged-in user.
auth hardening
Rate limiting and per-account lockouts on sign-in, one-time codes stored only as hashes, and verified email before an account is trusted.
safe links
Anything sensitive referenced in a URL is signed and time-limited, never a guessable id that could be walked by changing a number.
integration safety
Outbound connections, including webhooks and register lookups, are hardened so they can't be tricked into reaching internal systems they shouldn't.
verified at source
Licences and company details are checked against official government registers, so credentials are confirmed rather than self-declared.
transport
Strong TLS, HSTS and a full set of security headers, with no third-party trackers anywhere in the product.
discretion
The one thing we deliberately leave out is the exact stack and internals. We'll tell you the disciplines we work to, but we don't hand an attacker the map.

Done properly

Security isn't a feature you bolt on at the end. It's how the thing is built.

Assume someone's trying

We build as though an attacker is already poking at it, because on a live platform they are. Defences are layered, so one slip isn't game over.

Provable, not just claimed

A tamper-evident record and point-in-time history mean TrustPoint can prove what was true, which is worth far more than a promise that it was.

This is how we build

The same care goes into everything we ship. If your project handles anything that matters, this is the standard it gets held to.

Building something that has to be airtight?

Compliance platforms, customer data, payments, anything where getting it wrong is expensive. That's the work we like.

Start a project