Trust Center Overview
Proxara lets an accounting or tax firm use Claude on its client work without client identities leaving the firm. Staff ask Claude about a client, and Proxara answers from the firm’s Outlook, SharePoint, OneDrive, Teams, Karbon and CCH Axcess with names and identifiers replaced by codes such as P-7KQ2M. Staff see the real names in the Proxara window inside Claude. Claude can propose a client email, a Karbon update or filing a document, and a person approves each one. For a single file, Proxara Redact on Windows saves a copy with names and identifiers replaced by tags, and restores them later.
This page summarizes what happens to the firm’s information. The documents below give the detail.
When someone asks Claude about a client
| Step | Where it happens | What is kept afterwards |
|---|---|---|
| The person signs in once with their Microsoft account | Microsoft, then Proxara’s sign-in service | The person’s name, email and role in the firm’s own database |
| Claude asks Proxara for what it needs | Claude, then Proxara’s sign-in service, which checks the person and the firm | Nothing beyond the audit record |
| Proxara reads the firm’s systems with that person’s access | The firm’s own application on Microsoft Azure, United States | The firm’s client record: names and identifiers and their codes, which documents mention whom, facts with their evidence, all encrypted. Document contents are not kept. |
| A model reads documents it has not read before | A model Proxara runs on its own Azure GPU | Encrypted results, which expire. No AI provider reads the documents. |
| Claude receives the answer with codes in place of names and identifiers | Claude, under the firm’s own agreement with Anthropic | Whatever Anthropic’s terms provide |
| The person sees the real names | The Proxara window inside Claude, from the firm’s own application | Nothing new |
| Claude proposes an action and the person approves it | The Proxara window, then the firm’s own system | The action, who approved it and the receipt |
When someone redacts a file on Windows
| Step | Where it happens | What is kept afterwards |
|---|---|---|
| The employee selects a file and chooses Redact | The employee’s Windows PC | The original file, unchanged |
| The file is sent over HTTPS for processing | Proxara’s redaction service on Microsoft Azure, United States | Nothing from the file itself. It is held in memory for the job and discarded no later than 15 minutes after the job’s last activity. |
| A model reads the file and marks sensitive values | A model Proxara runs on its own Azure GPU | Nothing. No AI provider receives the file. |
| Tags replace the marked values and the copy is checked | Proxara’s redaction service | Encrypted records of each protected value and its tag, and encrypted evidence for restoring this copy |
| The copy is saved beside the original | The employee’s PC | The redacted copy |
| The employee chooses what to share with an AI assistant | The employee’s own session with the assistant | Whatever the assistant’s own terms provide |
| The employee restores a saved result | Proxara’s redaction service, then the employee’s PC | A restored copy beside the result |
What it does not do
- It does not watch what employees type or upload. What someone types or attaches in Claude itself goes to Anthropic directly, as it would without Proxara.
- It reads only the systems, sites and mailboxes the firm’s administrators connect, and each person sees only what they can already open.
- It does not change anything in the firm’s systems unless a person has seen the action with the real names and approved it.
- It does not send the firm’s documents to an AI provider to be read.
When a file cannot be redacted
Redaction fails closed. Proxara returns a copy only when the copy has been redacted and checked, or when a complete read found nothing to protect, in which case the copy is identical to the original and says so. In every other case the file is refused, no copy is made and the original stays where it was. Nothing is sent anywhere unredacted.
Codes, not anonymity
Codes and tags pseudonymize. The same person or organization gets the same code each time it is recognized, and figures and context remain, because that is what makes the work possible. Someone who knows the client may still recognize them from context. Detection is not perfect: testing has found both missed identifiers and useful text removed. Staff review what they share and what they approve.
Documents
- Security Overview: architecture, data handling, access and known limits
- Sub-processor List
- IRC Section 7216 and Proxara: facts and questions for the firm’s tax counsel
- Master Subscription Agreement
- Data Processing Addendum
- Product Privacy Notice
- Service Levels and Support
- Acceptable Use Policy
- Website Privacy Policy
- Website Terms of Service
- Cookie Policy
- HIPAA: no Business Associate Agreement is offered
Security questions go to security@proxara.ai. Please do not send client documents by email.