Continuity and exit

The install runs in your environment and needs nothing from Proxara to keep working. That decides most of what follows.

If Proxara is down

Nothing stops. The install keeps reading, checking and running loans, because nothing it does at run time calls a Proxara service. New releases simply wait in the queue until the registry is back.

If Proxara were gone

The install keeps running the release it has, under your keys, in your subscription, with every resource already yours. Nothing in it expires or switches off. What would stop is new releases, so the rules would stop following changes to the agency guides from then on; each result says which rule versions it used.

If your own environment is attacked

• Kept apart: the install sits in its own private network. It reaches your other systems only through the connections in Every connection, with credentials your team can revoke from Key Vault in one step.
• Your LOS stays the record: every result is written into your LOS as the loan is worked. The install holds working copies, not the file of record.
• Rebuilt from the release: your IT can rebuild the install from the same signed release with the same installer, and open loans are read again from your LOS.
• No backup copies of loan files, on purpose: a loan deleted at close stays deleted, with no earlier version to bring back. Key Vault keeps a deleted secret for 90 days, and no one can erase it sooner.

When you stop using Proxara

Delete the install’s resource group and its app registration in your Entra ID, and remove the Custom Tool from Encompass. Azure keeps the deleted Key Vault recoverable for 90 days and then erases it. Every resource and every record was always in your tenant, so there is nothing to hand back, nothing to export from Proxara and nothing left with Proxara. The results already written into your LOS stay where they are.