EXAMPLE · NOT A REAL CLIENT
What a production check
report looks like.
This is an example. The app, the findings and the counts are made up to show what the written report contains. It is not a real client's report. Yours will be about your software.
01 SUMMARY
Eight findings.
Three to fix first.
AppAn online booking app for a home-services business (made up), built with an AI coding tool.
CheckedSecurity, backups and environments, code and maintainability, privacy and DPDP.
Result8 findings: 3 high, 3 medium, 2 low.
| Area | Findings | Most serious |
|---|---|---|
| Security | 2 | High |
| Backups and environments | 2 | High |
| Code and maintainability | 2 | Medium |
| Privacy and DPDP | 2 | Medium |
02 FINDINGS
What we found,
what it means, what fixes it.
FINDING 01 · SECURITYHigh
The database key is visible in the browser.
- What we found
- The key that gives full access to the database is in the code every visitor's browser downloads.
- What it means for your business
- Anyone who looks can read, change or delete every customer record.
- What fixing it involves
- Issue a new key, keep it on the server only, and add rules so each user reaches only their own records.
FINDING 02 · SECURITYHigh
Customer records open without a login.
- What we found
- The page that lists bookings returns every customer's name, phone number and address to anyone with the link.
- What it means for your business
- Personal data is exposed. If it is found, you have a breach to report and customers to tell.
- What fixing it involves
- Require a login on every page and record, then test that one customer cannot see another's.
FINDING 03 · BACKUPSHigh
No backup has ever been restored.
- What we found
- Automatic backups are switched off, and nobody has tried a restore.
- What it means for your business
- One bad change or one mistake could lose your bookings and customer list for good.
- What fixing it involves
- Turn on daily backups, run a test restore, and write down the steps.
FINDING 04 · ENVIRONMENTSMedium
Test and live share one database.
- What we found
- Changes are tried out against the database your customers use.
- What it means for your business
- A test, or an AI tool following an instruction, can change or delete real data.
- What fixing it involves
- A separate test copy, and a release step with a way to roll back.
FINDING 05 · CODEMedium
No tests on login or payments.
- What we found
- Nothing checks that sign-in and checkout still work after a change.
- What it means for your business
- A small change can stop customers paying, and you find out from them.
- What fixing it involves
- Tests on these two paths, run before every release.
FINDING 06 · CODELow
Only the builder knows how it fits together.
- What we found
- No set-up notes, and the same logic is copied in several places.
- What it means for your business
- Every change takes longer and risks breaking something else. A new developer starts from zero.
- What fixing it involves
- Set-up notes now. Tidy the copied logic as those parts are next changed.
FINDING 07 · PRIVACYMedium
Consent is not recorded.
- What we found
- The sign-up form collects phone numbers and addresses but keeps no record of what the person agreed to.
- What it means for your business
- If a customer or a regulator asks, you cannot show consent.
- What fixing it involves
- Store what was agreed and when, and let people withdraw it.
FINDING 08 · PRIVACYLow
No record of who viewed personal data.
- What we found
- Staff accounts can open customer records and nothing logs it.
- What it means for your business
- After an incident you cannot say who saw what.
- What fixing it involves
- Log each view of personal data and keep the log.
The privacy findings are engineering work, not legal advice: your legal advisor decides what applies to you.
03 FIX ORDER
What to fix,
in what order.
- First
- Findings 1, 2 and 3. Customer data is exposed and nothing can be recovered if it is lost.
- Next
- Findings 4, 5 and 7. These stop the next change, or the next question about consent, from becoming a problem.
- Then
- Findings 6 and 8. Lower risk, and cheaper to do alongside other work.
04 WHAT HAPPENS NEXT
A call, then a quote.
You decide.
- 01 · Walkthrough call
- We walk you through the findings and answer your questions.
- 02 · Quote
- We send a quote to fix what we found, priced to the work.
- 03 · Your decision
- You decide whether to go ahead. The report is yours either way.
Get this for your own software.
The check is free. We need read-only access to your code and hosting, and we sign an NDA before we start.