Built to be
relied upon.
An inspection report is only useful if nobody can doubt it later. These are the measures that make a SafeTrace Field report stand up.
Tenant isolation
Every organisation's data is separated by row-level security in the database. One operator company can never read another's jobs, photographs or reports, even if the application layer had a bug.
Tamper-evident reports
On issue, SafeTrace Field freezes a snapshot of the whole job and computes a SHA-256 fingerprint over it. The fingerprint is printed on the PDF and shown on the verification page. Any change to the content produces a different fingerprint.
Photograph integrity
Each photograph is hashed when uploaded and the hash is stored with the job. Photographs are private: they are served only to signed-in operators of the owning organisation, or embedded in a report's PDF.
Versions and audit trail
Issued versions are never overwritten. A revision produces version two with its own fingerprint while version one stays on record. Every edit, result change, draft, check and issue is logged with who did it and when.
Data residency
Database, authentication and file storage run in Sydney. The application runs in Sydney. Backups are taken daily.
Sign-in
Email and password with secure, HTTP-only session cookies. Password resets go through a one-time link to the registered email.
Payments
Card details never touch SafeTrace Field. Subscriptions are handled by Stripe, and SafeTrace Field stores only the subscription status.
Independence
The AI drafter cannot invent values: every number in a narrative is validated against the register before it is shown to you. Vigilance checks are deterministic, so the same job always produces the same findings.