DAX Studio
Website Data Security UK: How We Protect Clients

When a firm hands us their client records, their payment flows or their internal workflow, they are handing us trust. A lettings agency holds tenant references and bank details. A clinic holds health notes. A lender holds affordability data. Lose any of it and the damage is not theoretical: it is fines, lost clients and a reputation that took years to build.

So here is how client data is kept safe on a custom build: the decisions that matter, what we do as standard, and what to ask whoever builds for you.

Security is a set of defaults, not a feature

The worst security mistakes are usually not clever attacks. They are boring: a password reused across accounts, a database left open to the public internet, an old staff login that was never removed. Most breaches we read about could have been avoided by getting the basics right and keeping them right.

So a build should start from secure defaults and work outwards. Encrypted connections everywhere. A database that answers only to the application and the people named to reach it. Secrets kept out of the code. Access granted per person, not shared. On our builds the basics come as standard: SSL everywhere, software kept up to date, two-factor sign-in on every admin account, and access only for the people who need it. These are not extras you pay more for. They are the floor.

Collect less, store less

The safest data is the data you never held. Before a single form or table is designed, ask what each field is actually for. If you do not need a date of birth to deliver the service, do not collect it. If a reference number will do instead of a full card number, use the reference.

This maps directly onto UK GDPR. Data minimisation is a legal principle, not a nice-to-have. It also shrinks the blast radius: if the worst happens, there is simply less to lose.

Set retention from the start too. Records that no longer serve a purpose should be archived or deleted on a schedule, rather than sitting in a table forever because nobody wanted to make the call.

Encryption in transit and at rest

Data moving between a visitor's browser and your server is encrypted by default now. That is the HTTPS padlock, and it is table stakes. We cover why in more detail in our piece on SSL and HTTPS.

Data sitting in the database matters just as much. It belongs on a managed database service that encrypts storage as standard, with the most sensitive fields encrypted again where the build calls for it. Backups need the same protection, because a backup is just a copy of everything you were trying to protect, sitting somewhere else. On our builds, your records sit in a database in a UK or EU data centre.

Access control that matches real roles

Many older systems have one problem in common: everyone can see everything. That is convenient until a laptop is lost or a disgruntled leaver still has a login.

Access should follow real roles, so people see only what their job needs. A front-desk account should not be able to export the full client database. An external contractor should get a scoped login that expires. Admin actions should be logged, so if a record is changed or deleted you can see who did it and when. On the portals we build, each client sees only their own records. For larger builds, our proposal sets out sign-in, roles, encryption, audit logs and backups in writing.

Strong authentication matters as much. Two-factor on anything that touches sensitive data is no longer optional for firms that take this seriously, and every admin account on our side signs in with it.

The real risk is rarely a Hollywood hacker. It is weak access control, data you never needed to collect, and backups you never tested. Fix those three and you are ahead of most organisations your size.

Keeping dependencies honest

A modern application leans on third-party code. That code gets security updates, and ignoring them is how old, known vulnerabilities get exploited months after a fix was available.

We keep the software a build depends on up to date as part of ongoing care, not as a panic job after something breaks. This is one of the quiet reasons website maintenance is worth paying for rather than treating a site as finished the day it launches.

For payments, use a specialist provider that is certified to handle card data, so card details never touch your own servers. Letting a specialist hold card data is safer than holding it yourself, and it narrows your compliance burden too.

Testing our own work

Writing secure code is one thing. Checking it behaves under pressure is another. Every input should be validated and sanitised, because the classic attacks (injecting commands through a form field, for example) rely on trusting data that should never be trusted.

Code should be checked before it ships, and for builds handling genuinely sensitive data we recommend an independent penetration test. An outside pair of eyes finds things the people who wrote the code cannot see. If you handle health, financial or legal records, this is money well spent.

Backups you have actually restored

A backup nobody has tested is a hope, not a safeguard. Backups should run automatically, sit apart from the live system, be encrypted and, above all, be restored for practice. The time to discover your backup is corrupt is not the morning after a ransomware attack. The databases behind our builds are backed up every day.

How far back recovery goes, and how quickly it can happen, should be set by what your business can tolerate. A clinic that cannot run without its booking data needs faster recovery than a brochure site.

Planning for the day it goes wrong

No honest team promises nothing will ever happen. What separates a controlled incident from a crisis is having a plan before you need it.

Under UK GDPR, a personal data breach that risks people's rights must be reported to the ICO within 72 hours. That clock is short. Know in advance who decides, who they call, what gets logged and how affected people are told. Deciding that under pressure, at midnight, is how mistakes compound.

What to ask whoever builds for you

If you are commissioning a custom build, these questions separate the serious from the casual:

  • Where is our data hosted, and is it in the UK or EU?
  • Who on your side can access it, and how is that logged?
  • How are backups encrypted and how often are restores tested?
  • How do you handle security updates after launch?
  • What happens, step by step, if there is a breach?

You want clear answers, not reassurance. Security on a custom build is really a product decision: it shapes what you collect, how you store it and who can reach it. We treat it that way from the first conversation on every platform we build. If your IT or compliance team has a security questionnaire, send it to us and we’ll complete it.

Get the defaults right, hold less, control access, test your backups and plan for the bad day. That is not glamorous work. It is the work that lets a serious firm sleep at night.

Related Insights

04 Start a project

Let's build
what's next.