Ryze Browser Helper — Privacy Policy

None. The Ryze Browser Helper extension does not collect, store, or transmit any personal data to Ryze servers or any third party.

The Extension stores two small values in Chrome’s local extension storage, entirely on your machine:

• Native host name — the identifier string for the Ryze Desktop App’s Native Messaging host (the browser helper protocol; e.g. io.ryze.cookie_bridge). This is a static configuration value, not personal data.
• Pairing token — a randomly generated UUID that lets the Extension re-connect to the correct Ryze Desktop App instance after the browser restarts. This token has no meaning outside your local machine.

Neither value contains personal data, and neither is ever transmitted to Ryze servers or any remote endpoint.

Ryze Browser Helper monitors whether you are signed into LinkedIn in your browser. When it detects a sign-in or sign-out event, it passes your LinkedIn session state to the Ryze Desktop App that is running on the same computer — using the browser helper protocol (Native Messaging API). This protocol is built into Chrome for secure local communication.

Native Messaging is a secure, OS-mediated communication protocol built into Chrome. It works as follows:

1. The Ryze Desktop App installer registers a native host manifest on your machine (a small JSON file in a system directory) that tells Chrome which executable is allowed to receive messages from this Extension.
2. When the Extension needs to pass session data, Chrome launches the registered Ryze process and pipes messages through standard I/O — entirely within your operating system. No network socket is opened.
3. No website, browser extension, or third party can intercept or observe this channel.

The Extension has no content scripts. It does not inject code into LinkedIn pages or any other website. It does not read the text, DOM, or content of any page you visit.

The Ryze Browser Helper extension does not:

• Send any data to Ryze servers or any remote server
• Read, store, or log the contents of your LinkedIn cookies
• Read or modify the content of any web page
• Run advertisements or analytics scripts
• Track your browsing history or activity
• Share any data with advertisers, data brokers, or third parties
• Operate independently of the locally-installed Ryze Desktop App

The Extension is entirely inert without the Ryze Desktop App. If the desktop app is not running, messages sent via Native Messaging fail silently and no data is stored or queued.

Because the Extension collects no personal data, there is no personal data to retain or delete on our end.

The two local storage values (native host name and pairing token) are kept in your browser’s extension storage until you uninstall the Extension or clear extension data. They are never transmitted off your device.

Your LinkedIn session data (cookies) is used only in memory by the Ryze Desktop App at the moment it is received. It is not written to disk by the Extension, is not stored on Ryze servers, and is not retained after the desktop app processes it.

The Extension declares three Chrome permissions. Here is exactly what each one is used for:

• cookies (linkedin.com) — Detects when you sign in or out of LinkedIn by watching for changes to your LinkedIn session cookie. The Extension checks only whether the session cookie exists; it does not read cookie values for any other purpose and does not access cookies for any domain other than linkedin.com.
• nativeMessaging — Sends session state updates to the Ryze Desktop App via Chrome’s Native Messaging API. All communication is local to your machine.
• storage — Stores the native host identifier and pairing token described in Section 1.

If you have questions about this policy or the Ryze Browser Helper extension, please contact:

Ryze Labs LLC
30 N Gould St Ste N
Sheridan, WY 82801
United States
privacy@ryze.so

For general Ryze privacy inquiries, see also the Ryze Privacy Policy.