Privacy Policy
MonoAgent and MonoAgent Bridge, by Monoes
Last updated: October 20, 2026
Summary
- MonoAgent runs on your own computer. MonoAgent Bridge is the browser extension that connects your browser to it.
- The extension talks only to the MonoAgent app on your computer. It has no analytics, advertising or tracking, and it sends nothing to Monoes.
- The app needs a monoes.me account and checks for updates, so it does contact monoes.me. It sends no usage data, workflow content or page content when it does. Details are in the app section.
- We don't sell or rent your data, and we don't use it for advertising.
MonoAgent Bridge (Chrome extension)
What it does
It connects your own browser to the MonoAgent app on the same computer, so you can save pages, highlights and tasks, ask questions about the page you are reading, record steps, and run your automations in the browser you are already signed in to. It does nothing on its own: it needs the app installed, running and paired with a token you paste once.
Data we collect
None. The extension has no analytics, advertising or tracking, and it makes no requests to Monoes or any server other than the app on your computer.
Data handled on your device
When you trigger an action, the extension reads what that action needs and passes it to the MonoAgent app over a connection to 127.0.0.1:
- For a save, highlight, task, recording or chat question: the page text, address and title, and your selection.
- When you open a page: its address, so the app can return highlights you saved there.
- For sign-in checks and automations: cookies for the site involved.
- A recording withholds password, card, one-time-code and similar fields, and removes login codes and tokens from recorded addresses.
The extension also keeps its settings in browser storage: the pairing token, the connection port, the chosen profile, and saves or tasks waiting until the app is running. Removing the extension deletes them.
Data sharing
We don't sell, rent or share this data with anyone. We don't use it for advertising, credit decisions, or anything unrelated to the extension's single purpose: connecting your browser to the MonoAgent app on your computer. The use of information received from browser APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements.
Permissions
| Permission | Why it is needed |
|---|---|
Access to all sites (<all_urls>) and content scripts | Automations, page saving, highlighting and the recorder work on whichever site you point them at, so there is no fixed list. Nothing is read from a page until you save, highlight, record, ask the chat or run an automation step. On load, the extension only asks your local app which highlights you saved for that address. |
activeTab | Save or highlight the current page when you press the shortcut or the toolbar button. |
scripting | Run the save, highlight and recorder code in the page and read the result back. |
tabs, tabGroups, webNavigation | Open, find, group and wait for tabs during an automation, and know when a page has finished loading. |
debugger | Send real keyboard and click events, and run steps on pages whose security policy blocks scripts. It attaches only to a tab being automated, and detaches after 30 seconds without traffic. |
cookies | Tell an automation whether you are signed in to a site, and carry that session to your own local MonoAgent profile. Cookie values go only to the local app. |
storage | Remember the pairing token, the chosen profile, and saves and tasks waiting while the app is not running. |
alarms | Keep the connection to the local app alive and retry it. The extension’s background worker goes to sleep otherwise. |
contextMenus | The “Add selection as task” and “Add page as task” right-click entries. |
sidePanel | The extension’s main interface. |
Keyboard shortcuts (commands) | Save the page, save a selection, highlight, and add a task. These are the shortcuts you see in chrome://extensions/shortcuts. |
Remote code
The extension loads no code from the internet. All of its own code is bundled in the package.
It does run JavaScript that your own MonoAgent app sends it, for example an automation step that reads a page. That connection is limited to your computer (127.0.0.1) and to an app paired with your token. The extension refuses an unpaired app, and refuses any non-local server unless you allow one for a single save.
Third-party services
The extension itself contacts none. If you use the chat or summary features, the MonoAgent app sends the text you chose to the AI provider you configured in the app. That is governed by the provider's terms and your app settings, and is covered under the app section.
Your control
- Nothing is read or sent until you trigger it: a shortcut, a menu entry, the side panel, a recording or an automation you run.
- Remove the pairing in the side panel or with
monoagentcli extension reset. - Remove the extension at any time to stop all activity and delete its stored data.
MonoAgent (desktop app)
What it is
MonoAgent is a workflow-automation app that runs on your own computer. Your workflows, run history, saved pages, highlights, tasks, CRM data and crash reports stay on your machine, in ~/.monoagent/. Credentials are kept in an encrypted vault. You can delete any of it from the app.
Data we collect
No analytics, usage counters or device identifiers. MonoAgent doesn't report what you run, which workflows you have or how often you use it. It makes network requests in these situations only:
- Signing in to monoes.me.A monoes.me account is required. Signing in, staying signed in and signing out send your email address (when you sign in by email code), a sign-in token and the app's client ID. monoes.me sees which account, when, and the IP address of the request. Nothing else is sent: no workflow content, file paths or page content. Without a connection the app keeps working for 24 hours after the last successful contact.
- The workflow library. Only when you list, install or publish library items. Publishing uploads the item you choose.
- Updates. The app checks for a signed release at start and every 24 hours. The server sees your IP address and a default user agent, with no account or device identifier.
- Your own workflows. Steps you build call the services you configure (HTTP, email, social platforms, AI providers).
- Crash reports. Written to a local file. They are filed to GitHub only if you set
MONOAGENT_CRASH_REPORT=1and have themonomindCLI installed.
AI providers
If you use AI features such as chat, summaries or AI workflow steps, the app sends the text you chose to the provider you configured, using your own key or account. That provider's privacy policy and your settings govern what happens next, not this policy. Pick a provider you trust, or use a local model.
Data sharing
We don't sell, rent or share your data, and we don't use it for advertising. The full list of what the app sends, and how sign-in data is stored on disk, is in the Mono Agent security policy.
Your control
Your local data is yours to delete. Sign out from the app to revoke its sign-in. For data tied to your monoes.me account, see the monoes.me Privacy Policy.
Children
MonoAgent and MonoAgent Bridge are not directed at children under 13.
Changes to this policy
We'll update the date at the top and post the changes on this page.
Contact
Questions or requests: hello@monoes.me.