Remy in Chrome privacy notice

What Remy in Chrome is

Remy in Chrome connects your browser to the Remy desktop application or CLI running locally on the same device.

The extension allows Remy to read, inspect, and interact with browser tabs when you ask it to perform a browser-related task, such as testing a page, debugging an issue, or inspecting page content.

The extension does not operate independently of the local Remy companion app.

When Remy can access a tab

Remy in Chrome does not act on browser tabs until you complete the browser-pairing step.

When Remy is actively controlling or inspecting a tab, a visible on-page indicator is shown.

The extension accesses browser content only as needed to perform the action you requested.

Data the extension can access

When you ask Remy to work with a browser tab, the extension may access:

• Visible page content
• Page structure and accessibility information
• Screenshots of the active tab
• Console messages
• Network request and response metadata
• Tab URLs and titles
• Information required to click, type, scroll, or interact with page elements
• Information required to evaluate JavaScript in the page context
• Information required to open, switch, close, or group tabs

The page you ask Remy to work with may contain personal or sensitive information. The extension does not specifically search for or classify that information. It accesses page data only as part of the browser action you requested.

Where browser data goes

The extension sends browser data only to the Remy desktop application or CLI running locally on the same device.

Communication between the extension and the local Remy companion app uses Chrome’s Native Messaging API.

The extension itself does not independently transmit browser data to a Corepass server or third party.

The Remy companion app may process information received from the extension as part of completing your request. Any server-side processing or third-party model processing performed by Remy is governed by the Corepass Privacy Policy.

Data stored by the extension

The extension stores a limited amount of information locally in Chrome:

1. Whether you accepted or declined the browser-pairing step.
2. A randomly generated identifier for the browser installation so the local Remy companion app can recognize the browser across restarts.

This information is stored using Chrome’s local storage APIs.

Removing the extension removes this extension-managed local data.

What the extension does not do

Remy in Chrome does not:

• Sell or rent browser data.
• Use browser data for advertising.
• Use browser data for unrelated analytics.
• Independently transmit browser data to a Corepass server or third party.
• Act on browser tabs before the browser-pairing step is completed.
• Silently control a tab without showing the active-tab indicator.

Your controls

You control whether Remy can connect to Chrome.

You can:

• Choose whether to connect Remy to Chrome.
• Disconnect Remy from the extension options page.
• Stop an active browser task from Remy.
• Remove the extension at any time.

Disconnecting prevents the extension from continuing to act on browser tabs.

Remy companion app

Remy in Chrome is designed to work with the Remy desktop application or CLI.

This notice only describes the browser-extension portion of the data flow. How the Remy companion app processes prompts, files, code, browser content, or information sent to service providers is covered by the Corepass Privacy Policy.

Children’s privacy

Remy in Chrome is a developer tool and is not directed to children.

Changes to this notice

We may update this notice when the extension or its data practices change.

When we make changes, we will update the “Last updated” date above. Material changes may also be reflected in the Chrome Web Store listing or other appropriate product notices.

Contact

For privacy questions, contact support@corepass.com.

Corepass, Inc.

For information about Corepass’s broader privacy practices, see the Corepass Privacy Policy.