The firm decides what AI may see, join, infer, say, and do.
Proxara applies that decision to every request.
Trust records are never disclosed for review work.
withheld for this purpose
Client letters wait for the advisor’s confirmation.
held until she confirms
The model receives stand-ins, never client names.
the model sees [Client_9C4]
Five permissions decide each piece of work.
One request passes all five, in this order.
Outlook
SharePoint
Salesforce
Trust records
Connecting two records is its own permission.
Four modes, set by the firm, per kind of work.
Both records answer to one stand-in.
Which mode applies is set with the work itself, in the console.The console
One request. Three policies. Three outcomes.
The request never changes. The policy does.
Review work, approved. All four sources take part.
Completed.
Policy is written around kinds of work.
Rules attach to an approved kind of work, never to a person’s general access. A firm holds many of these.
Defined and revised in the consoleClient review preparation
KarbonInfrastructure, not oversight.
Encrypted at rest.
Each identity is encrypted under its own key, so the store holds no usable plaintext on its own.
How keys are held
Granular crypto-shredding for right-to-deletion.
CCPA/CPRA · GDPR Art. 17Per-identity keys, so erasing one key erases one person without hunting copies through logs and backups.
What a reviewer can check
Isolation by account.
Every identity belongs to one firm’s own account and carries its own key, so nothing is shared between firms.
Where it runs
Oversight that can be demonstrated.
Supervision rules ask a firm to show how automated work is overseen. Proxara records which person or agent asked, and the permissions the work ran under.
What was approved, run and confirmedEverything resolves to one person.
Put the firm’s policy in charge of every request.
Tell us the rules the firm needs enforced, and a person will reply.
Talk to us