Auditable security model
Row-level policies, isolated authorization functions reviewed one by one, an explicit role model. Access control is readable, not scattered through application code.
Public sector & institutions
The question is not how we protect your sensitive data. It is why our system does not hold any.
For an HR consultancy we built a job-weighting module. The exercise starts from the client’s payroll file: salaries, named individuals, the organisation’s most sensitive document.
The workbook is parsed in the browser. It is never uploaded. It reaches no server, so there is no backup, no log, no subprocessor.
The job titles. Names and salaries are not filtered out after reading — they are never read.
"This organisation has n occurrences of this title." Nothing else is persisted.
Title, expected, received, remaining, status, history. Individual tracking is impossible by construction — a cost we accepted.
The answer to "where is our salary data stored in your system?" is: nowhere. No privacy policy can match that answer, because a policy describes an intention and an architecture describes a constraint.
See the full architectureRow-level policies, isolated authorization functions reviewed one by one, an explicit role model. Access control is readable, not scattered through application code.
Contrast, full keyboard navigation, semantic structure, reduced-motion preferences respected. A procurement requirement as much as a principle.
Written scope, visible weekly deliveries, versioned and reversible database migrations, handover documentation.
The code, the database and the access are yours. We document third-party takeover at delivery, not at departure.
Override justifications are persisted, timestamped and attributed. A later audit can reconstruct who approved what, and on what grounds.
Automatic failure alerts, scheduled backups, client-side error capture with a user-facing reference code.
A formal document made to circulate internally: legal identity, methodology, data posture, accessibility, references. It carries the named personnel that procurement procedures require.
In preparation. Available on request by email.
Request the dossierFor consultations, requests for information and administrative documents:
We can attend a scoping meeting or respond in writing to a request for information.