# Proxara mortgage LOs

> Proxara does the work a mortgage business does by hand behind every loan, inside the systems it already runs. A model reads what was said or written and points at the words; code checks every figure and decides what goes where. The real AUS and the customer's own people make every decision, and no borrower data is used to train a model.

## Proxara for lenders and broker shops

The loan officer's assistant. It hears a loan officer's work calls on their own number and does what an assistant would after each one: the application typed into Encompass, the lead and who sent it in the CRM (Total Expert), the follow-up on their Outlook calendar, and one question in Teams: pull credit, run DU and send the disclosures? On the officer's yes it pulls credit, runs DU or LP and sends the Loan Estimate through the lender's own Encompass, asks for the documents DU lists in the company's own borrower app and checks each paper as it lands, through to the pre-approval and on to closing. The officer is asked only what is theirs to decide: credit, DU and the disclosures (one button), each message before it goes, and who an unknown number was. Borrowers never see Proxara; they hear from their loan officer, from the officer's own number and mailbox, and send documents through the company's borrower app. Nothing new is installed for officers or borrowers. No audio is kept: each side of a call is turned into words as it's said, and a call is kept as the facts it settled, each with the words that said it, and a summary. A model reads the words; code checks every figure against them and decides what is written where; DU or LP judges the loan. It runs in Proxara's own Microsoft Azure in a US region, or in the lender's own Azure, and no borrower data is used to train a model.

- [Proxara for lenders](https://lenders.proxara.ai/): the product on one page.
- [How it works, for lenders](https://lenders.proxara.ai/how-it-works): one borrower's first call, through the officer's one question to the documents and on to closing.
- [Questions, for lenders](https://lenders.proxara.ai/faq): what loan officers, their managers and their IT ask.
- [Security, for lenders](https://lenders.proxara.ai/security): for a lender's IT. No audio kept and nothing used to train; what's kept of a call; where it runs; who it hears; every system it connects to and what a call passes through.

## Company and documents

- [Company](https://lenders.proxara.ai/company): who is building it and how to reach them.
- [Blog](https://lenders.proxara.ai/blog): how the income is worked out in code, how a findings report is read and worked round by round, what stays in the lender's tenant, and the one installer.
- [Trust Center](https://lenders.proxara.ai/docs/trust-center/overview): for a security review of the loan officer's assistant. Where it runs and every connection it makes, access and logging, encryption and keys, what's kept of a call and when it's deleted, the model's role, releases and updates, incident response, continuity and exit, the FTC Safeguards Rule element by element, the privacy policy, the terms, the sub-processors and the security questions answered. The two-page [security overview](https://lenders.proxara.ai/proxara-security-overview.pdf) is its PDF.

## Boundary

For lenders, Proxara never pulls credit, runs DU or LP or sends disclosures without the loan officer's yes, sends no message to a borrower or agent without it until the officer lets that kind go, and never calls a loan approved until the AUS says so; it never produces an adverse action. Corrections are kept as history, never overwritten.