Security overview

Proxara runs inside your own Azure tenant, or on your own servers. The borrower’s documents, the model that reads them and every result stay there, under your sign-in and your keys. Proxara holds no account, credential or role in it.

• Where it runs: Your IT runs one installer under its own permissions. It creates a private network, a dedicated GPU and encrypted storage in your own subscription, and every resource belongs to you. Nothing is shared with another lender.
• How files are protected: Files are encrypted at rest with AES-⁠256 under keys in your own Key Vault, and in transit with TLS. People sign in with their Microsoft accounts under your MFA rules, and every view, export and deletion is logged by name.
• How long files are kept: Documents, page images and the facts read from them stay while the loan is worked, and an open loan is never deleted on a timer. They go when the loan officer closes the loan, or after 90 days untouched, a number your shop can change. Every deletion is logged.

Architecture

One private deployment in your tenant. A model reads each page on your own GPU, with no route to the internet, and code does the rest. The only thing that comes from Proxara is a signed release, checked before it runs.

Architecture lists every part of the install and where it runs, and Every connection lists each connection that crosses the edge of your tenant.

Four layers around every loan file

The loan file sits inside your encryption keys, inside your private network, inside your Azure tenant. Proxara holds none of the four.

The PDF

The same two pages, to send to your IT and security lead: download the security overview. The questions they ask first are answered in Security questions.