Data guidance and permission boundaries

Your work stays yours. Here is how we protect it across Remy and the Corepass platform, and how the rules change by plan. The Trust Center has the full detail.

1. Model training

Model training is off by default for Team workspaces, and only administrators and owners can change the setting. Enterprise data is never used to train models.

Individual plans have separate model-improvement settings: Help improve Remy is required for Free and on by default with user controls for Pro and Max.

Remy Contributor is separate. Individual Free accounts are automatically opted in; paid accounts require explicit opt-ins on a per-project basis. Remy Contributor is not available for Team or Enterprise workspaces.

For what a session can include and how each setting works, see Help improve Remy and Remy Contributor. Team and Enterprise rules are in Team and Enterprise privacy.

2. Encryption and access

Stored data is encrypted, and so is data traveling between your device and Corepass, and between Corepass and the providers that help us run the Services. Encryption sits alongside access controls, so people who should not see the data cannot reach it.

In a team workspace, roles decide who belongs. Administrators manage members and can review usage and repository activity. They cannot read the content of a member’s private conversations.

Enterprise can connect your own identity system. Single sign-on (SSO), directory sync (SCIM), and custom role-based access controls let administrators set who is allowed in and what each role can do.

3. Computer and browser use

When Remy works with your apps, browser, or coding environment, it uses relevant information to understand and complete your task. This can include page content, files, screenshots, and tool results.

Tools may run on your device while models process information in the cloud. Running a tool locally does not mean all processing stays on your device. Relevant context may be processed by Corepass services or selected model providers under applicable terms and agreements.

The Remy in Chrome extension sends browser data to the local companion app. See the Remy in Chrome privacy notice for extension-specific handling.

To keep each task inside the boundaries you intend:

• Limit files, apps, and connected accounts to what the task needs.
• Close unrelated sensitive content and handle passwords and sign-ins yourself.
• Review important actions, such as sending messages or changing files.
• Monitor unfamiliar content that could mislead an assistant, and stop unexpected activity.

On a team, follow your workspace requirements before connecting accounts or working with confidential information. For more, see Computer use and cloud privacy.

4. Data retention

Personal information stays for as long as we reasonably need it to run the Services, keep them secure, and meet legal obligations. How long that is depends on the product, the kind of information, how it is used, and the law that applies. When we no longer need it, we delete it or remove what identifies you, subject to backups and records we are required to hold.

An Enterprise agreement can set its own retention period, so the organization chooses how long Corepass stores its business data.

Changing model-improvement settings does not delete session history or clear browser data. Retention and privacy rights are described in the Privacy Policy.

5. Security

Administrative, physical, and technical safeguards are part of how Remy and the Corepass platform run. They are sized to the risk of handling your data, in the product itself and in the infrastructure that hosts it.

If we learn of a security breach that may affect your content or personal data, we notify you as applicable law requires. Keeping your credentials safe, and using the account security features available to you, is part of that protection.

6. Learn more

The Trust Center has every article for Individual, Team, and Enterprise plans. For questions about a workflow, email support@corepass.com.