Clear controls. Known boundaries.
How Trexia protects your account, your clients' information and the requests sent to AI providers.
How we protect accounts and data
Encryption
TLS for data in transit with HSTS. AES-256-GCM field encryption for sensitive data such as contact details, integration tokens and two-factor secrets.
Sign-in
Passwords are hashed with bcrypt, repeated failed sign-ins lock the account, and users can turn on authenticator-app two-factor with recovery codes.
Single sign-on
Brokerages can connect SAML or OIDC single sign-on and provision users with SCIM.
Access
Role-based permissions, with each brokerage's records kept separate from other accounts.
Audit log
Brokerage admins can review platform actions and export the log as CSV or JSON.
Request protection
CSRF protection, rate limits on the API and sign-in, and file-type checks on uploads.
Requests to AI providers
One gateway
Every AI request goes through one gateway that requires an account context, so requests are attributed and logged.
Redaction first
Personal information is redacted before a request reaches an AI provider.
Brokerage settings
Brokerages can block providers, set how long AI request logs are kept and bring their own provider keys.
Your data
Your rights
- Request access, export, correction or deletion
- Withdraw consent for optional processing
- We do not sell personal information
Report a concern
- Email support@trexia.com with "Security" in the subject
- Include steps to reproduce and affected URLs
Reviewing Trexia for your brokerage?
Send your security questionnaire or questions to our team.