Consent before covered AI features
Signed-in staff must accept the current AI usage policy before AI requests on covered routes, such as assistant, compliance review and generation requests, are processed.
AI governance
What is in place today, where people stay responsible, and what we do not claim.
Signed-in staff must accept the current AI usage policy before AI requests on covered routes, such as assistant, compliance review and generation requests, are processed.
The central AI call path removes common personal identifiers from prompts and from responses. Brokerages can add their own redaction patterns.
Broker owners can block specific AI providers. A blocked provider is denied and the denial is logged. Providers can also be marked no-training, which attaches a no-training request to the call.
Brokerages can turn off payload capture entirely or keep redacted payloads for 0, 7, 30 or 90 days. The default is 0 days.
AI calls are logged with provider, model, feature, token counts and whether a call was blocked. Where payloads are retained, the redacted text is stored encrypted.
Brokerages can connect their own provider credentials per provider, so requests run on their own provider account.