Security and compliance, built in.

How we protect your data, your clients and your reputation, from guardrails and human review to encryption and audit logs.

Who can see what, and why

Security starts with deciding what each agent needs. The intake agent needs to create contacts and book consultations. The research agent may need no client data at all. We write these scopes into the blueprint, and your administrator approves them before any connection is made. Role-based access and least-privilege permissions then keep each agent inside its scope. If a scope has to widen later, that is a change you approve, not a quiet default.

Human checks that sit beside the technology

Technical controls are only half the picture. The other half is process, and the agents are built around it. Encryption, access controls and audit logs are listed above. What matters for daily use is the way they combine. A lawyer can open the log for a matter, see what an agent read and wrote, and check that it stayed within its scope. That is the check you will use most often.

• Lawyers approve legal outputs before use
• Sensitive actions wait for a named person
• Urgent or unclear matters go to staff
• Audit logs are reviewed in monthly check-ins

Questions to ask any vendor, including us

Ask where data is stored, who at the vendor can see it and how access is removed when a person leaves. Ask how retention works and whether your data is used to train public models. Ask what happens when an agent is unsure. Our answers to those last two are on this page, and we are happy to walk through the rest on the discovery call. Review them with your own IT or compliance lead.

Questions,
answered.