Firefox Add-on Privacy Policy

IMBAlino Browser Mesh Node · Last updated: September 14, 2026

This policy covers the IMBAlino Browser Mesh Node Firefox add-on only. The desktop application has its own privacy policy.

Overview

The add-on is a companion for the IMBAlino desktop application and does nothing on its own. It opens exactly one network connection — a WebSocket to ws://127.0.0.1:<port>/ws, the loopback address of your own machine — and waits for the local IMBAlino host to authenticate. The loopback address is hard-coded in the source; there is no setting that can point the add-on at a remote server. There is no telemetry, no analytics, and no third-party endpoint of any kind.

What the add-on can access

Once you have paired it with a local IMBAlino host, and only then, that host can ask the add-on for:

• Your open tabs — id, title, URL, active state, window
• Page content — the visible text, title and link destinations of a tab you direct it to (top frame only)
• Interactive elements — links, buttons and form fields with their accessible names and on-screen geometry
• Screenshots of a tab
• Actions on your behalf — click, type, select, press keys, scroll, navigate, go back/forward/reload, and open, activate or close tabs

What the add-on never accesses

• Cookies — never read, never transmitted
• Local storage — localStorage, sessionStorage and IndexedDB are never read
• Authentication headers and tokens — never read, never transmitted
• Password fields — their values are redacted to *** before anything leaves the page; only the fact that a password field exists is reported
• Your browsing history — the add-on does not request the history permission

Where your data goes

Everything the add-on reads is sent only to the IMBAlino host running on the same machine, over the loopback interface. Loopback traffic never leaves your computer — it does not reach your network, your router, or the internet. Nothing is sent to main.fish, to Mozilla, or to any third party.

What the IMBAlino desktop application subsequently does with that data is governed by the IMBAlino privacy policy and, where the Claude assistant is involved, by the Anthropic privacy policy.

Access control

No host can drive the add-on without a pairing token. The token is minted by the IMBAlino host on your machine and protected at rest by the operating system (Windows DPAPI; AES-GCM on macOS and Linux). A process that cannot present the token is refused before it can issue a single command. Until pairing succeeds, the add-on sits disconnected and does nothing.

What the add-on stores

In browser.storage.local, the add-on keeps only three values: the connection port, the pairing token, and a marker recording whether pairing was automatic or manual. No page content is ever stored by the add-on. Removing the add-on removes these values.

Permissions

• tabs — to enumerate your tabs and address the one you direct the assistant to
• <all_urls> — because you choose which page the assistant works on at runtime; the add-on cannot know those origins in advance
• storage — to remember the port and pairing token between sessions
• nativeMessaging — used for one single message, pairingInfo, so pairing needs no copy-paste. It is not a command channel and cannot read tabs or drive the browser.

Contact

Questions about this policy: support.imbalino@main.fish.