Trust Center overview
The documents that govern this website and describe where the product’s data goes: what each one answers, and the short version of all of them.
Updated 2026-09-22
This is a draft. Counsel reviews it, and every other document here, before the site goes live.
The Trust Center holds the documents that govern this website and describe where the product's data goes. There are four: the privacy policy, the terms of service, the security overview, and the sub-processor list. This page says what each one answers and gives the short version of all of them.
One sentence
Proxara reads the documents a mortgage business already holds and prepares what its people decide on. Everything in the Trust Center follows from that sentence. The product runs inside the customer's own Azure account, installed by the customer's IT, and nothing goes to Proxara. The decision, the submission and the signature are the customer's.
The documents
| Document | What it answers |
|---|---|
| Privacy policy | What this website collects and when, what happens to a report request sent through the form, and how to withdraw consent. |
| Terms of service | What the site is and is not, and the law that governs it. |
| Security overview | Where the product runs, what leaves (nothing to Proxara), what comes in from our side, and how a security team can check it. |
| Sub-processor list | Who hosts what for this website, and why the product itself has no sub-processor. |
The short version
- For the public-record report, nothing of yours is needed. It is built from public records.
- The product runs in the customer's own Azure account. The customer's IT installs it under its own permissions, and Proxara holds no credential, role or standing access.
- The document-reading model runs there at a pinned version. Nothing is sent to a public model service or to Proxara.
- This website collects nothing until you say yes to analytics. It has no place to put a loan file, and it asks for none.
- People answer what the record cannot settle, submit and sign. The system prepares and never submits.
What these documents are not
None of them is a customer agreement. An engagement runs under a signed agreement. Where a signed agreement and a page here differ, the agreement governs.
Reading order
The person who runs the work reads the security overview, which is written for them. A security team reads it too, then asks for the install template and the data statement. Everyone should read the terms once.
Who to write to
- Questions about the product or a report: support@proxara.ai
- A security concern: security@proxara.ai
- A privacy request: privacy@proxara.ai
Proxara Inc., 28 Geary Street, Suite 650, San Francisco, CA 94108.