Connections and setup
Security and data
Understand the boundaries among your browser, Suparagent, your execution environment and connected providers.
Know where each part runs
Your browser connects to Suparagent. In the hosted preview, the service routes your workspace to its account sandbox. In a self-hosted setup, the installation runs in the environment you manage. An assigned Docker computer is a separate option and is not the same thing as the hosted account sandbox.
Providers receive the information they need
The AI provider receives prompts and context for a turn. A connected app receives requests for the action you authorize, and a website receives traffic from the configured computer or browser. Each provider’s terms and privacy practices apply. Share only the files and account access needed for the task.
Review permissions and protect credentials
- Check the engine, approval mode and requested action before work begins.
- Do not paste credentials into chat, a skill or agent memory.
- Treat routine webhook URLs as secrets and rotate an exposed URL.
- Keep backups of files you need to retain, especially when using an external sandbox provider.
Preview scope
Provider, package and long-running-work qualification is still in progress. Suparagent does not claim a compliance certification or service-level guarantee on this page. For a security concern, contact support privately.
Need help with a setup? Contact the Suparagent team.