Introduction

Proxara connects a firm to AI without protected client information reaching the model. Two products carry that: Proxara Connect, the hosted connector that joins the firm's AI assistant to Microsoft 365 through the firm's own environment with nothing installed on any device, and Endpoint Protection, the device agent that covers everything typed and uploaded on managed machines. Every governed interaction joins a record an examiner can verify. These docs explain how both work and how to run them.

What Proxara does

With Proxara Connect, an employee asks the firm's AI assistant for work that lives in the firm's systems; Proxara retrieves what that employee is permitted to see, replaces protected references with consistent stand-ins inside the firm's environment before anything reaches the model, and shows the employee the real result in a view inside the conversation. With Endpoint Protection, a native agent on each device captures AI traffic through the operating system's proxy path, decrypts a connection only on positive evidence that the destination is an AI service, and seals sensitive values into reversible tokens before a prompt leaves. In both cases the model sees stand-ins, the employee gets the real answer, and the interaction joins one signed record. Proxara never blocks a site, the posture is best effort with a coverage record rather than a promise that every value is always removed, and anything Proxara cannot inspect is reported rather than hidden.

How these docs are organized

• Guides explain how Proxara works, how to set it up, and how to run it across a fleet.
• Notes record what changed, release by release.
• Trust Center holds the architecture, the security and compliance posture, and every governing document.
• FAQs answer the questions teams ask first.

Who these docs are for

Compliance officers, security teams, and IT teams deploying Proxara, plus anyone evaluating whether it fits a regulated firm.

Where to start

New readers should start with How Proxara works, then Choosing Connect or Endpoint for which product a firm runs first. The Connect quickstart is the no-install path and the Endpoint quickstart is the fleet rollout. For the security and compliance detail, go to the Trust Center.