The platform sees land records. It is built for that responsibility.
A short, honest read of how borrower and parcel data is handled, who gets to see what, and what the platform will and will not do with it. No overclaimed certifications, no compliance theatre.
Encryption in transit and at rest
All traffic between the institution's systems, the workspace, and the verification engine runs over modern TLS. Records at rest are encrypted with key material scoped per institution.
Role-based access
Loan officer, risk analyst, and institution administrator see different surfaces of the same record. Access to raw source documents is scoped, logged, and reviewable per user.
Data retention, per record
Retention windows are set per institution and per record class. Source documents, extracted records, and score histories carry their own retention rules, so nothing lingers by accident.
Audit trail, not a log dump
Who looked at which record, when a score was overridden, and what was captured in the field - all attached to the parcel record and readable by the institution's own audit team.
A decision-support platform. Not the lender.
The platform verifies records and generates a decision-support score. It never books a loan, never disburses money, and never acts as the lender of record. Final lending decisions remain with the institution's own credit policy and human review.
Data handling, stated plainly
The platform stores the parcel record and the documents used to build it. It stores the score, the drivers, and the flags for audit. It does not store borrower KYC beyond what is needed to key a parcel record to a loan application inside the institution.
Compliance posture
The platform's compliance posture is stated per contract and per region - not painted with badges. Where a certification is in-flight, that is stated; where one has landed, evidence is available under NDA. Public claims are matched to public reality.
Where the human decides
Underwriter overrides are a first-class action inside the platform, not a workaround. The reason for the override is captured on the file, and every override rolls up into the portfolio view so the credit committee can see the pattern.