The audit

What we check

Eleven areas, in order of what tends to matter most. For each one, here's what we're asking and why it's your concern and not just your developer's.

A white lighthouse on a green headland above a bright blue sea
  1. Who owns it

    Which account owns the app, the database, the web address and the bills? Is it the business, or one person’s personal email? What would happen if that login were lost? Who owns your system?

  2. Open data

    Can someone who isn’t signed in read your customers, prices or orders? Can one signed-in customer read another’s? This is the most serious thing we regularly look for. Access rules explained

  3. Secret keys

    Are the codes that unlock your database and outside services hidden, or are they sitting in code that every visitor’s browser downloads? Secret keys explained

  4. Signing in

    Who can create an account? Is the email address confirmed? Can someone guess or reset their way in? Is two-step sign-in on for the accounts that matter?

  5. Who can do what

    How many people are administrators, and do they need to be? Does the app itself enforce the roles, or does it just hide the buttons? Can a former employee still sign in? A leavers’ checklist

  6. Connectors and spreadsheets

    What moves data between your systems, what login does it use, and what could it change? Who can edit the spreadsheet your app trusts? Spreadsheets and connectors

  7. Silent failure

    If a nightly copy stopped, an order email went astray or a payment failed, who would be told, and when? Often the honest answer is “a customer, eventually”.

  8. Getting it back

    Are there backups? Has anyone ever tried restoring one? Are they held somewhere that survives losing the account?

  9. Personal data

    What personal data do you hold, where does it go, and who can reach it? Does your privacy notice cover the system? We aren’t lawyers, but we can show you the facts your adviser would need. UK GDPR and your app

  10. People

    How much depends on one person? Could somebody else keep it running for a fortnight using what’s written down? Key-person risk

  11. Everyday use

    Does it work properly for each kind of user, on the devices they really use? We note what’s broken or confusing, and what would make the system better.

What we don’t do

We won’t attack your system in ways that could bring it down, we won’t test other companies’ services beyond your own use of them, and we won’t download your data to prove a point. We stop at the point of proof and tell you what we found.

We also don’t grade your code for style. A system can be untidy and safe, or tidy and wide open, and what matters is what could happen to your business.

Last updated 6 November 2026.

Find out where you stand.

Tell us what you’ve built. We’ll agree the scope and the price with you before anything starts.

Talk to usSee an example report