Privacy Policy
A plain read of what the platform sees, why it sees it, how long it keeps it, and what it never does with it. Written for the credit teams and audit reviewers who actually read these.
What the platform sees
The platform sees three classes of data: parcel records (the land, its owner, its history), the documents used to build those records (RTCs, registry exports, field captures), and workspace usage data (who looked at what, and when). It does not see borrower KYC beyond what is needed to key a parcel record to a loan application inside the lending institution.
Why the platform sees it
Parcel records are used to verify ownership and generate the eligibility score for the lending institution operating the workspace. Source documents are stored so every extracted field can be traced back for audit. Usage data is stored so the institution can run its own access-review process.
Who the data is shared with
The parcel records and source documents for a workspace are visible only to that workspace and its authorised users. Data is not sold, not rented, and not shared with a borrower's competitors or any unrelated third party.
Aggregate, anonymised patterns may be used to improve regional model calibration - each institution controls this through its contract, and the default is opt-in, not opt-out.
How long the data is kept
Retention windows are set per institution and per record class in the master service agreement. Source documents, extracted parcel records, and score histories carry their own retention rules so that nothing lingers by accident. On termination, records and documents are removed or returned according to the agreement.
How the data is protected
All traffic runs over modern TLS. Records at rest are encrypted with key material scoped per institution. Access is role-based - loan officer, risk analyst, administrator - and every access to a source document is logged inside the parcel record's own audit trail.
Your rights as an end-institution
The institution operating the workspace owns the verified parcel records for its book. It can export, redact, or delete those records at any point through the workspace and through a support request. Underwriter overrides and access history remain visible to the institution's own audit reviewers.
Cookies and site analytics
The public website uses only the cookies required for the site to function and for basic, aggregated analytics. The verification workspace itself uses only the session cookies required to keep an authenticated user signed in.
Changes to this policy
Any material change to how the platform handles parcel or workspace data will be notified to each institution operating a workspace before the change takes effect. Minor clarifications are made in-place and are visible on this page.
Reaching us on privacy questions
Privacy questions from an institution operating a workspace should go through the named contact on the master service agreement. General questions can be routed through the contact page on this site.