Embel Chrome extension

Privacy policy

Effective September 28, 2026.

What the extension does

Embel connects the Embel macOS app to a Chrome profile through Chrome Native Messaging. When you ask Embel to work in Chrome, the extension can inspect the selected HTTP(S) page and perform the requested browser operation. It refuses Chrome Web Store pages and does not support incognito tabs.

Information handled

Depending on the task and page you select, the extension may handle:

• task, tab, document, profile, and connection identifiers;
• page text, accessibility information, form values, page structure, canvas observations, network response bodies, and screenshots needed for the task;
• page addresses and titles for pages Embel is asked to inspect;
• page data that may contain personal communications, financial, health, or authentication information; and
• a local profile identifier, ownership and reconnect metadata, sign-in-wait metadata, and bounded task state.

The extension does not request or store provider API keys. Persistent Chrome storage is used for connection identity and recovery metadata, not for a general browsing-history database. Browser observations used during a task are bounded and held in memory unless the Embel app records task evidence under its own settings and retention rules.

Where information goes

The extension sends task data and relevant page data to the Embel app on the same Mac over Chrome Native Messaging. Embel may then send relevant task context to the AI or other service provider you select in Embel. The extension itself does not operate a hosted synchronization service for page data, sell personal information, serve advertising, or use page data for personalized advertising, credit decisions, or pricing.

Provider-side processing, retention, and deletion are governed by the provider selected in Embel and that provider's terms and privacy policy.

Limited use commitment

Embel uses page and browser context only to provide the requested browser assistance, verify the requested result, maintain the authenticated local connection, and improve reliability and security. It does not use this context for advertising, profiling, credit decisions, lending, or unrelated purposes. It does not sell the information or allow routine human access to page content. A provider receives relevant context only when needed to provide the task through the provider selected in Embel.

Your control and security

You choose when to ask Embel to work in Chrome. Task identity stays bound to the selected profile, tab, frame, document, and origin. The popup provides a Stop control for active browser work. The extension uses the fixed native host com.zlukav.mantle.browser and does not download executable code or load a remote extension script.

You can stop work in Embel, stop it from the extension popup, disconnect Chrome in Embel, or remove the extension from chrome://extensions. Removing the extension removes its Chrome-managed storage. Embel app records are controlled separately by the app's settings and data-lifecycle controls.

Contact

For privacy questions, visit embel.app.