Privacy & data

The desktop app works with projects and tools in the environments you connect. When you use a model, prompts, attachments, tool results, and relevant source files can become part of the context sent to that provider.

Running a desktop app does not mean every operation stays on your device. Review the models, integrations, and environments you choose before working with sensitive information.

Model providers and connected services process requests under their own terms and privacy policies. Retention, training controls, and account settings depend on the provider and service you use.

Check the policy and settings for your selected provider, including whether you are using an API account, a subscription sign-in, or a local model.

Account sign-in and connected apps use authentication services. Begin sign-in from the desktop app so the result can return to the correct session.

The download service is configured to record request events, including the requested platform, release, download outcome, browser and operating system, and approximate country. These events help describe how desktop releases are delivered.

Choose providers and integrations that meet the requirements of your project or organization.

• Review the context and attachments included in requests.
• Disconnect integrations you no longer need and revoke their credentials with the provider.
• Keep your device and connected environments protected, and manage locally stored project data on those devices.