Fetchii Browser Helper — Privacy Notice

1.What the extension can access, when, and why

1.1 Cookies (cookies permission)

What: The cookies your browser already holds for a specific website.

When read: Only at the moment you initiate one of the following actions:

1. You select "Download with Fetchii" / "Record with Fetchii" from the right-click context menu.
2. You click the "Send Current Page" button in the extension popup.
3. You retry a login-required download from inside the Fetchii desktop app, and the app asks the extension to provide cookies for that specific URL.

The extension does not read cookies in the background, on a schedule, or while you are simply browsing.

Which cookies: For the URL you are acting on, the extension reads cookies for the page's domain and for ancillary domains the same site uses to serve authenticated content (for example, CDN or media subdomains that share the same login session). This is necessary because video-streaming sites typically split authentication and media delivery across more than one domain.

What happens to them: Cookies are encoded into a standard Netscape cookie-jar text format and handed to the Fetchii desktop app once, in a single Native Messaging call. The extension does not keep a copy, does not transmit them over a network, and does not share them with any third party.

Retention inside the extension: None. The cookie payload is built in memory on demand and discarded after it is sent to the desktop app. Anything the desktop app stores is governed by the Fetchii app privacy policy.

1.2 Active tab URL (tabs permission)

The URL of the currently active browser tab is read only when (a) you click "Send Current Page" in the popup, or (b) the active tab changes, so the extension can update the right-click menu label between "Download with Fetchii" and "Record with Fetchii" depending on whether the current page is a live stream. The URL is used in memory only — not logged, not stored, not transmitted anywhere except to the local Fetchii desktop app when you trigger a send.

1.3 Right-click menu (contextMenus permission)

Lets the extension add the "Download with Fetchii" entry to the browser's right-click menu on pages, links, videos, audio, and images. Without this permission the extension's primary way of receiving user input would not exist.

1.4 Native Messaging (nativeMessaging permission)

Lets the extension talk to the Fetchii desktop app installed on the same computer through Chrome's built-in local IPC channel. This is not a network connection. Messages never leave your machine. If the Fetchii desktop app is not installed, the channel cannot open and the extension has no way to function.

1.5 Host permissions: <all_urls>

Two narrowly scoped purposes:

• Content script (in-page helper). A small script runs in the page so that (a) when you right-click on a feed-style page the extension can identify which specific post/video your right-click was over, and (b) the extension can detect whether the current page is a live stream and label the menu correctly. This script runs entirely inside your browser. It does not read form fields, passwords, personal text, or page bodies; it does not send anything anywhere; it does not modify pages beyond a brief in-page toast that confirms a send.
• Cookie reading on arbitrary domains. Because you may want to download from any of the thousands of sites Fetchii supports, the extension cannot know in advance which domains will be involved. Cookies are read only for the specific URL you act on (see §1.1) — never broadly, never preemptively.

2.Where data goes

The only recipient is the Fetchii desktop app on the same computer, and it receives only the URL you acted on (and, when applicable, cookies for that URL) at the moment you trigger an action. The transport is Chrome's local Native Messaging — not a network connection.

The extension does not:

• Send any data to any remote server, including any server operated by Entromoonic.
• Use any analytics SDK, tracking pixel, advertising identifier, or fingerprinting library.
• Include any third-party JavaScript loaded from a remote origin.
• Share data with any third party for any purpose.

There is no telemetry channel from the extension. Anonymous, opt-in usage metrics that the Fetchii desktop app collects (TelemetryDeck / Sentry, both user-controllable) are governed by the Fetchii app privacy policy and are unrelated to the extension.

3.Retention

Inside the extension itself:

• Cookies: not retained. Built on demand and discarded after the single Native Messaging send.
• URLs: not retained. Passed through to the desktop app and not logged.
• Page content: not retained, not logged, not transmitted.
• User preferences: the extension stores none.

Anything the desktop app retains is governed by the Fetchii app privacy policy.

4.What we explicitly do not do

• We do not sell or transfer your data to third parties.
• We do not use your data for advertising, profiling, audience targeting, or behavioral analysis.
• We do not determine creditworthiness or use your data for lending purposes.
• We do not train machine-learning models on your data.
• We do not collect personally identifiable information (name, email address, phone number, government ID, payment info).
• We do not collect location, health, financial, or communications data.
• We do not track or store your general browsing history. The extension only sees a page URL when you explicitly act on that page.
• We do not run any code that exfiltrates page contents. The content script is reviewable in the extension package.

5.Children

The extension is not directed to children under 13 and we do not knowingly process any data from children. The extension performs no profiling regardless of user age.

6.Security

The Native Messaging channel between the extension and the desktop app is restricted by Chrome to the specific extension ID bdjdfkomlnnkpomgephgnkgkbmgnioah. Other extensions cannot use the same channel. The desktop app accepts messages only from this extension ID. All communication is local — it never traverses a network and is not exposed outside your machine. The extension contains no third-party scripts and no remotely loaded code.

7.Your rights

Because the extension does not transmit data off your machine, there is no remote data set we hold about you that you can request, correct, or delete. Everything the extension touches is either discarded after use (URLs, cookie payloads in transit), or owned by the Fetchii desktop app on your computer, where you can view, export, or delete it via the app's preferences. To exercise any data-protection right against the Fetchii desktop app, see the rights section of the Fetchii app privacy policy or email privacy@fetchii.app.

8.Changes to this notice

We will update the "Last updated" date at the top of this page when this notice changes. Material changes (for example, a new permission added, or a change in what is read or when) will be announced in the Fetchii app's release notes and on this page.

9.Contact

Appendix: Permissions at a glance

Quick reference for Chrome Web Store reviewers.