Public guide / User control

Privacy and data controls

Local storage and provider transmission are separate. Choose both deliberately.

Before sending

Requests may include source context, attachments, command output, screenshots, and—when a browser task needs it—active-tab details. Select a provider whose terms and data controls match your needs. Local inference does not prevent a separate feature from calling a configured hosted service.

Protect credentials

Save provider credentials through the dedicated credential controls. Do not include API keys in prompts, screenshots, source files, or tickets. Check custom endpoints and environment settings before a run.

Remove local records

Use the product's session and data controls where available. Browser users can clear extension storage or uninstall the extension; VS Code and CLI users can remove their local extension/CLI data through their application or operating-system controls. Provider-held data follows the provider's policy.

Public screenshots

Do not publish screenshots containing customer names, private repository details, access tokens, internal URLs, or real session content. The product screenshots on this site use sample data.

Read the complete Privacy Policy.