Trust Center Overview

Last updated: September 3, 2026

Proxara does the servicing work of a commercial insurance brokerage across the systems the brokerage already runs, and proves it was done. Every deployment runs inside a private environment provisioned for that one brokerage. This page is the short version of how that environment is built and what it holds. The documents below are the governing ones.

What the environment is

• One brokerage, one environment. Each customer runs in a dedicated cloud environment. No brokerage ever shares compute, storage, models or credentials with another.
• The book stays where it lives. Proxara reads evidence in the systems that already hold it: Microsoft 365, the agency management system, carrier channels, document stores. It holds what it derives from that evidence, never a standing copy of the book, and it is never the brokerage's system of record.
• Local models. The models that read documents, emails and carrier records run inside the environment. Nothing account-related is sent to an external AI service, and nothing the environment learns from the brokerage's corrections or issued policies trains a model shared with anyone else.
• Credentials outside model context. The credentials that act on the brokerage's systems live in the execution boundary, not in anything a model can read. A model can propose an action; only the execution boundary can perform one, and every action is performed exactly once.

What people see

Decisions that genuinely need a person arrive in Microsoft Teams as one bounded release, with the evidence and the exact action attached. The brokerage sets which kinds of work may proceed on their own, which are reported after the fact, and which wait for a named person. Coverage judgment, market strategy and binding stay with named people.

The record

Every action closes against five things: the evidence it started from, the meaning resolved from it, the authority it ran under, the exact payload that left, and the proof the receiving system gave back. That record builds while the work runs. Any account or event exports as a signed evidence package for audit, diligence or an E&O response.

What Proxara receives

Counts, codes and health signals about the environment, so we can operate it: what kind of work ran, whether it completed, which systems were reached and whether they answered. Not what was read, not what was asked, and no client name.

Retention and exit

Derived state, the evidence record and the model's learned adjustments stay inside the environment for the term of the agreement. On exit the brokerage receives its evidence record as signed packages, and the environment is destroyed, including the keys.

The documents

• Privacy Policy for proxara.ai
• Website Terms of Service
• Security Overview
• Sub-processor List

A pilot or a deployment runs under a signed agreement and order form, which take precedence over anything on this site. Questions: security@proxara.ai.