Security & data
Who can access your evidence.
A verification contains property photos and loan information. Access depends on organisation membership, case permissions and the action the person is authorised to perform.
Reviewer responsibility
Software recommends; a named officer approves. No tranche is released automatically — the accountability stays with your team.
Append-only activity trail
Submission, comparison and reviewer events are recorded with their times. Comparison interpretations and developer review history are retained as separate records.
Organisation isolation
Each lender’s files, photos and decisions are scoped to their own organisation, with role-based access for officers, reviewers and administrators.
Capture checks
Guided capture records a capture token and available location metadata. Uploaded historical files and builder attachments are identified separately. These checks cannot establish authenticity on their own.
Hosting and service providers
The application uses Supabase for accounts and evidence storage, and Anthropic for model-assisted analysis. Review the data-processing terms and configured hosting locations before submitting borrower data.
Evidence access
Evidence and reports require authorised access. Builder report sharing is explicit and can be revoked. Revocation prevents further access; it cannot recall a copy already downloaded.
Before using live data
Agree who may submit, review and download records. Check your retention requirements and the data-processing terms. Automated findings support review; your authorised team remains responsible for inspection and lending decisions.
Talk to us
Bring your security questions.
Data-handling, access model, sub-processors, residency — happy to take your risk team through all of it before any pilot.
Book a review