Legal · Browser extension privacy
Alluqi Bridge for Chrome Privacy Policy
How the Chrome extension handles requested browser data, transfers it locally to Bridge Desktop, and keeps product and provider boundaries clear.
Last updated · September 15, 2026
01 · Scope
A local connection to Bridge Desktop
Alluqi Bridge for Chrome connects Chrome to Alluqi Bridge Desktop on the same computer. This policy describes the browser-extension data path. It does not replace the privacy terms for Bridge Desktop, a configured model provider, or another Alluqi service.
02 · Browser data
Information handled
The extension handles tab titles and URLs, requested page titles and visible document text, and requested visible-tab screenshots. Requested page text and screenshots may include personal communications, user-generated content, identifiers, or other sensitive information visible on the selected page. It also stores a local pairing status.
03 · Purpose
How information is used
Information is used only to list or select tabs, open HTTP(S) pages, read requested page content, capture a requested visible tab, and show whether the extension is connected to Bridge Desktop.
04 · Native messaging
Local transfer to Bridge Desktop
Requested browser data is sent through Chrome native messaging to the fixed Bridge Desktop native host on the same computer. The extension does not directly transmit browser data to Alluqi servers or third-party services.
05 · Processing boundary
Model and provider processing
After browser data reaches Bridge Desktop, further processing depends on the model or provider configured in Bridge Desktop. A local model may process data on the user's computer. A hosted provider may receive data when the user configures and uses that provider. Users should review the terms and privacy practices of their selected provider.
06 · Retention
Storage and retention
The extension stores only its current pairing status in Chrome local extension storage until that status changes or the extension is removed. The extension does not persist page text or screenshots. Bridge Desktop and configured providers have their own storage and retention behavior.
07 · Package boundary
Security
The extension uses Chrome native messaging to communicate with the fixed local host com.alluqi.chromehost. The extension package contains its executable code and does not execute remotely hosted code.
08 · Deletion
User controls and deletion
Users control browser actions through Bridge Desktop settings and approvals. Closing Bridge Desktop disconnects the native data path. Removing the extension deletes its Chrome local extension storage. Users should use Bridge Desktop and provider controls for data retained outside the extension.
09 · Chrome APIs
Chrome API data use
Browser data is used only to provide or improve the extension's single purpose. It is not sold, used for personalized advertising, or made available for unrelated human review.
10 · Contact
Privacy questions
Privacy questions about Alluqi Bridge for Chrome may be sent to [email protected].