Your post, point by point
You listed five things. Here is where each one lives, including the two I have not done.
- 01
“Secure company-specific user access and data separation”
Sign in as Northgate, open the separation test, and try to read Halden's data. The database refuses, and you watch it refuse. Then switch the same page into prototype mode and watch the identical request succeed.
Separation test - 02
“An administrator portal giving us oversight across the platform”
Sign in as Medena. Every client, every programme, one view. You can drop into a client's results exactly as they see them, and the platform records that you did.
Medena oversight - 03
“Secure, GDPR-compliant data storage”
Erase an individual and watch every trace of them disappear across every table, including the second copy that reporting tools leave behind. The erasure is written to a log the application has no permission to rewrite. The database sits in London.
Governance - 04
“Testing, bug fixing and deployment”
Deployment is the page you are reading. Behind it, a browser signs in as a client administrator, runs all three separation tests, erases a person, checks the log, then signs in as Medena. Twenty six assertions, run against this live site every time it deploys and again every morning. If separation ever stops holding here, I find out before you do.
Runs on every deploy - 05
“Ongoing development, maintenance and updates”
Nothing to show. This is the part that is a conversation rather than a screen, and the part most people underestimate. Under UK GDPR a reportable breach gives you seventy two hours, and seventy two hours does not pause for one person's annual leave.
Not shown
What is real here, and what is not
A demonstration that quietly fakes the difficult part is worth nothing, so here is the line, drawn plainly.
- Separation enforced by the database itself, not by application code
- Sign in, sessions and the claims that decide what you can reach
- Erasure that actually removes a person from every table
- An append-only audit log the application cannot rewrite
- A Postgres database hosted in London
- Both client companies, and every employee in them
- Every score, every comment, every department
- No real personal data exists anywhere in this system
- No monitoring, no backups policy, no disaster recovery
- No email, no onboarding, no password reset
The right-hand column is not a list of things I could not do. It is the list of things that separate a convincing demonstration from a platform you can put in front of a client, and working through it properly is the job you advertised.