Privacy policy

Monad is a unified environment for research and development, an Engram product, in closed beta. This policy covers the Monad website, the Monad web app, the Monad extension for Chrome, the Monad desktop apps and the Monad mobile app.

Monad is operated by Engram. It is the controller of the personal data described here.

• Monad collects what it needs to run your account and the sessions you start.
• Monad does not sell personal data, and does not use it for advertising.
• The Chrome extension sends data only to Monad, and only to carry out what you ask an agent session to do in your browser.
• The pages on this site load no analytics or advertising script.

The pages at monad.one (this page, the home page and the support page) load no analytics, advertising or tracking script. Your choice of light or dark theme is stored in your browser and is not sent to Monad.

When you join the waitlist, Monad stores the email address you enter. When you request access, it also stores the team name and the description of your work, if you give them. Monad uses these to decide on and tell you about beta access. Joining the waitlist creates no account.

To limit abuse, the API counts requests per network address for a short time. That count is held in memory and is not stored with your request.

Account

Your email address, and the name and picture on your profile. When you sign in with Google, GitHub or Apple, Monad receives your email address, name and picture from that provider. When you sign in with a password, an email code or your organization's single sign-on, the authentication service checks it. If you verify a phone number, Monad stores that number. Monad uses account data to sign you in, to show who did what in a shared project, and to send you service email.

Your work

Projects, sessions and everything in them: the messages you send, the files you add, what agents write and run, and the logs of that work. Connectors you set up and secrets you store, which are encrypted. Monad stores this to run your sessions and to show you their results. Each session runs on its own isolated cloud computer.

To run a session, Monad sends the session's messages, files and tool output to the model provider that runs it. When an agent searches the web, fetches a page or uses a connector, the query, the address or the request goes to the service that carries it out.

Usage and technical data

Records of model and compute use, for metering and billing. An audit trail of actions in an account. Your network address and browser type, which reach the servers with each request and are used for sign-in security and rate limits.

Cookies

The web app sets the cookies it needs to work: your sign-in session, the access code for the closed beta, and a few that remember a step in sign-in. It sets no advertising cookie.

The extension has one purpose: it connects your Chrome browser to your Monad account, so that an agent session you start can open, read and operate web pages in that browser while you watch.

What it can access

• Tabs. The titles and addresses of tabs, to choose and open the tabs an agent works in and to place them in a tab group named after the session. You choose whether an agent sees every tab or only the tabs it opens.
• Page content, through the Chrome debugger. In the tabs an agent works in, the session can read the page (text, structure, screenshots, network activity and, if a command asks for them, the cookies of that page) and can act on it (go to an address, click, type). Chrome shows its own notice while the debugger is attached.
• What you attach. When you attach a tab, a selection or a screenshot to a chat in the side panel, the extension reads that tab's visible text, the selected text or an image of the visible tab.

The extension does nothing on a page until you have signed in and either a session of your own account uses that tab or you attach the tab in the side panel. It does not ask Chrome for your saved history or bookmarks, and it does not work on the Chrome Web Store.

What leaves your browser, and where it goes

The extension talks to Monad only: the Monad API (api.monad.one) and the Monad web app shown in the side panel (app.monad.one). It sends data to no other host. It contains no analytics and loads no code from outside its own package.

• Sign-in. The tokens that sign the extension in to your account. Monad returns your account id and email address, which the extension shows in its settings.
• About this browser. The browser brand, the operating system, the extension version, the name you give this browser and your access settings.
• While a session uses the browser. The titles and addresses of the tabs it can see, the page content it reads, and the record that it attached and detached. This goes to your session through the Monad API.
• When you attach something to a chat. The text, selection or screenshot you attach goes to the Monad web app in the side panel, and then into your chat.

What a session reads in your browser becomes part of that session. It is stored with the session and is sent to the model provider that runs it, like the rest of the session's content.

What it stores

In Chrome, on your computer: the sign-in tokens, the server address, this browser's name, your access settings and the state of running sessions. On Monad's servers: the browser's name, brand, operating system, extension version, access settings and when it was last connected, and which sessions used it.

Your controls

• In the extension's settings, set Access to Without asking, Ask first or Off, and set Tabs to All tabs or Only tabs it opens.
• On any page an agent works in, select Take over or Stop. The shortcut Alt+Shift+K stops every agent in the browser.
• Sign out, or select Disconnect this browser, in the extension's settings. Removing the extension from Chrome also ends the connection.

Limited use

Monad uses the data the extension handles only to provide the feature described above: letting your own agent sessions use your browser. Monad does not sell this data, does not use or transfer it for advertising, and does not use or transfer it to determine creditworthiness or for lending. It is transferred only to the services that run your session, as this policy describes. Monad's use of this data follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Monad for desktop shows the Monad web app in its own window, so everything in the web app section applies. It checks Monad's servers for updates. If you let an agent use the computer, the app asks for the operating system permissions that needs (on macOS: Accessibility, Screen Recording and file access), and what the agent sees and does on the computer becomes part of your session. If the app crashes, it can send Monad the kind of error and the app version. It does not send memory dumps, screenshots or file paths with a crash report.

Monad Capture is a separate app that records your screen to a searchable timeline. It takes a screenshot about every 2 seconds, reads the text on it, and keeps both on your computer. Password managers and private browsing windows are skipped by default. Sync is your choice: to Monad, to your own storage bucket, or off. With sync off, the recordings stay on the computer.

The mobile app signs you in to the same account, so everything in the web app section applies. It asks for a device permission only when you use the feature that needs it: the camera and photo library to attach an image, the microphone and speech recognition for voice. If you allow notifications, Monad stores a push token for your device and sends notifications through the push services of Expo, Apple and Google. If you buy something in the app, the purchase goes through Apple or Google and a purchase service that records it against your account. The app contains no advertising or analytics SDK.

Monad uses other companies to run the service. Each receives only the data its job needs, and only to carry out that job for Monad.

• Hosting. Vercel (the website and web app) and Google Cloud (the API).
• Database and sign-in. Supabase.
• Agent computers. E2B runs the isolated cloud computers that sessions use.
• Models. The model provider that runs a session, reached through OpenRouter, or the provider whose key or subscription you connect. Langfuse records model requests and responses so that Monad can find and fix failures.
• Email. Resend and Mailtrap send service email.
• Connectors. Composio and Pipedream, when you connect an app through them.
• Voice. Hume and ElevenLabs, when you use voice.
• Web search and page fetch for agents. Tavily, Serper and Firecrawl.
• Payments. Stripe on the web, and Apple, Google and RevenueCat in the mobile app, if you pay for Monad.
• Sign-in and channels you choose. Google, GitHub or Apple when you sign in with them, and Slack when you connect a workspace.

Monad keeps your account and your work while your account exists. You can delete your account in your profile settings: deletion is scheduled after a 14-day grace period, and you can cancel it before then. When the account is deleted, your agents, sessions, messages, credentials and secrets are deleted with it. Billing records are kept for as long as the law requires. The steps are on the support page.

A waitlist entry is kept until you ask Monad to delete it.

To ask for a copy of your personal data, to correct it, or to have it deleted, email support@monad.one from the address of your account or waitlist entry. Use the same address for any question about this policy.

When what Monad collects or where it sends it changes, this page changes with it, and the date at the top changes too.