Explicit authorization
Bind approvals to exact actions, accounts, audiences, budgets, and expiry. Changed scope needs renewed approval.
The security principles guiding our implementation. This page is not a claim of certified production security.
Bind approvals to exact actions, accounts, audiences, budgets, and expiry. Changed scope needs renewed approval.
Design for tenant isolation, least-privilege access, protected credentials, and access logging.
Keep a record of research, plan versions, approvals, connector actions, and experiment results.
Treat websites and retrieved documents as data, never as permission to change instructions or execute actions.
Enforce usage caps, bounded retries, spend limits, and a way to stop connected execution.
Ask only for necessary information and define retention, deletion, and vendor terms before launch.
Security reporting: email hello@expandwith.me. Do not send passwords, API keys, or unnecessary sensitive information.