TRUST CENTER
Security Overview
Layered execution boundaries
Mattheus separates AI preparation from signing and submission so each live action can be checked, approved, traced, and revoked through the controls available for its venue.
AI layer
Researches, drafts, composes, previews, and explains actions without direct signing authority.
Policy layer
Evaluates configured limits, approved destinations, balances, allowances, simulations, feature gates, certification, and venue state; unsafe or out-of-scope requests are blocked.
Approval layer
Records explicit approval for the exact preview. Interactive approval is short-lived and cannot be reused after a material payload change.
Signing layer
Signs only after the required approval and checks. Credentials and signing material must remain scoped and protected.
Execution and evidence layer
Submits or broadcasts the action and records order status, fills, receipts, errors, and resulting portfolio state so the lifecycle can be audited.
Revocation
Stop, cancel, close, rotate, and revoke controls complement pre-execution safeguards. Venue-specific permissions may require separate revocation at the wallet, broker, exchange, or protocol.
Responsible disclosure
Do not send secrets through support. Security reports should include reproducible, redacted details and use the verified support channel available during controlled beta.
AI layer
Researches, drafts, composes, previews, and explains actions without direct signing authority.
Policy layer
Evaluates configured limits, approved destinations, balances, allowances, simulations, feature gates, certification, and venue state; unsafe or out-of-scope requests are blocked.
Approval layer
Records explicit approval for the exact preview. Interactive approval is short-lived and cannot be reused after a material payload change.
Signing layer
Signs only after the required approval and checks. Credentials and signing material must remain scoped and protected.
Execution and evidence layer
Submits or broadcasts the action and records order status, fills, receipts, errors, and resulting portfolio state so the lifecycle can be audited.
Revocation
Stop, cancel, close, rotate, and revoke controls complement pre-execution safeguards. Venue-specific permissions may require separate revocation at the wallet, broker, exchange, or protocol.
Responsible disclosure
Do not send secrets through support. Security reports should include reproducible, redacted details and use the verified support channel available during controlled beta.