Where Your Client Data Goes, and Where It Doesn’t.
Your clients’ policies, loss runs and financials pass through this software. Here is exactly how they are handled, what we retain, and what we will never do with them.
The Short Version
Encryption
AES-256 at rest, TLS 1.3 in transit. Encrypted on our servers and every time data moves between you and the platform.
Account isolation
Every account runs isolated. Your client data is never visible to another brokerage and never commingled with another tenant's.
Never used for training
Your documents, your client information and your workflows are never used to train AI models. That is architectural and contractual, and it extends to every third-party model provider we use. It is not a setting that can be changed.
Role-based access
Brokers, admins and support each get the access their role needs and nothing beyond it.
Complete audit trail
Every action, by the agent and by a user, is recorded with a timestamp and is exportable. The record a regulated account needs.
Deployment options
Multi-tenant cloud by default. On-premises and private cloud on request.
Where Your Data Sits, and Who Touches It
You upload it. The agent reads it, produces the work, and cites every figure back to the page it came from. The document stays in your account, visible to you and to nobody outside your brokerage.
The dashed line is your account boundary. The model-provider step is the only thing that crosses it, and it crosses under terms that forbid training on what it sees.
Every figure traces back to a source document
Your documents stay in the account after the work is finished. That is what lets the agent point at the page a number came from, months later. Delete a client or a conversation and the documents underneath go with it.
Every run is recorded and reproducible
What was sent to a model and what came back are recorded against the run. That is the difference between a record and a claim, and it is what an audit trail is for. The same encryption and access controls apply to it.
Three named providers, contractually barred from training
OpenAI, Anthropic and Google. A document goes to one of them only to produce the work you asked for, under terms that forbid training on it. No other third party receives client documents.
Your account is held in Canada
Your account, your client records and your uploaded documents sit on infrastructure in Toronto. Processing runs through the named providers above under a data processing agreement, on servers in the United States. If Canadian-only processing is a requirement for your brokerage, ask before you sign.
Cancel and your data is deleted
No retention period, no archive, no export window you have to remember to use.
Where We Are
| SOC 2 Type II | Controls implemented. Audit in progress. |
|---|---|
| Encryption | Live. |
| Account isolation | Live. |
| Audit logging | Live. |
| Role-based access | Live. |
We would rather show you the status than the logo. When the audit is complete this page says so, with the date.
The File Is Still Yours
You start every run. You read every output before it goes anywhere. Nothing is sent, filed or shared without you. When the agent cannot tie a figure back to a source document, it leaves the field empty and flags it rather than filling it in.
Your name is on the file either way. The software is built for that.
Questions from your IT or compliance team? Email info@brokeragentx.com.