Security & data

Know where your work lives.

An agent on your Mac runs in a virtual machine on your Mac. A cloud agent runs on a cloud machine at Fly.io. Either way, Murmello saves versions of the agent’s work in its own storage, in AWS in the United States.

Where agents run

Each cloud agent has its own Linux machine at Fly.io, created for it and removed when the agent is ended or archived. Each agent on your Mac has its own Linux virtual machine, run by Apple’s Virtualization framework through a helper inside the app. It sees only the folder you granted it, read-write or read-only, or the copy Murmello keeps for it, and nothing else on your Mac.

An agent has the open internet by default, like a laptop. A profile can limit it to Only these addresses, in Advanced → Network; package registries and its AI provider are added for you, and everything else is blocked. An agent on your Mac can’t reach your local network or your Mac’s own services, whichever you choose. Murmello’s own internal addresses are always blocked. Your Mac connects out to Murmello over an encrypted connection; Murmello never connects in.

What an agent may do

A profile sets each of an agent’s tools to Allow, Ask or Deny. With Ask, the agent shows you the command and waits for your answer. Root access, on unless you turn it off in a profile, gives the agent password-less sudo on its own machine so it can install system software. It applies only inside that agent’s virtual machine, not to your Mac or to other agents.

Agents reach each other only along the lines you draw between them on a board or in a team, and only when their profile has Work with other agents on. Without a line, an agent can’t reach anyone.

A connection is an MCP server run by whoever provides it. When an agent uses it, that server receives the agent’s tool calls, and any token or key you give it. Add connections from providers you trust, and limit one to Only these tools where you can.

What saved versions hold

As an agent works, Murmello saves a version of its workspace: at the end of each reply, every ten minutes while a reply runs, when it waits for your answer, and before it sleeps. A version holds the agent’s files, each repository’s git history, its tool’s own history and memory, and the conversation. Caches and installed dependencies such as node_modules, .venv and build folders are left out. Files git ignores, such as .env, are kept. Sign-in files are never saved in a version.

This applies to a folder you grant on your Mac too: versions of that folder’s contents leave your Mac and are stored by Murmello, so the agent can move to the cloud, be restored or be forked. The folder’s path is not sent, only its name. Don’t grant a folder that holds secrets you don’t want stored with us.

Versions are stored in AWS (us-east-1), encrypted at rest. The database that lists them, your profiles and your account is encrypted at rest too.

Sign-ins and credentials

When you add a sign-in you choose where it is kept. In Murmello’s vault, it is encrypted using AWS Key Management Service and bound to your account; it is handed to an agent’s machine only while that agent runs, and kept there in memory. Only on this Mac, it stays in your Mac’s Keychain: Murmello’s servers hold only a reference to it, and only agents on that Mac can use it. Either way, a renewed login is saved back where it came from.

If you connect GitHub, its token is encrypted the same way and stays on Murmello’s servers: no agent’s machine ever holds it. Imports, pulls and pushes happen only when you ask.

Coding tools and your code

Claude Code, Codex and OpenCode connect to their own providers from the agent’s machine when you use them. What they send and how it is processed depends on the provider, your account and your settings. Your messages to an agent, and its replies, pass through Murmello’s servers between the app and the agent.

Dictation

Hosted dictation sends microphone audio through Murmello’s service to ElevenLabs for transcription. Murmello holds audio in memory during the utterance and returns the text without retaining audio or transcripts. Usage duration is recorded to meter your allowance.

Retention and deletion

A cloud agent asleep for 30 days is archived: its cloud machine is removed and every version stays; Restore brings it back. When you end an agent, its saved versions are deleted 30 days later, and backup copies within 30 days after that. Versions a fork of it still builds on are kept while the fork exists, and large files (over 16 MiB), which your agents share, are kept until your account is deleted. Nothing else deletes versions automatically. Caches of installed tools expire on their own within 60 days. Disconnect this Mac, with “Also remove the files”, removes the virtual machines and their files from your Mac; your folders are left as they are.

When your account is deleted, all of its stored agent files are deleted: every saved version, the large files kept once for the account, and leftovers from transfers. Storage keeps replaced or deleted copies for up to 30 days, after which they are gone. For account deletion, contact support@murmello.ai.

Details and contact

Read the privacy notice and subprocessor list for the full policy and providers. Report a security concern privately to support@murmello.ai; do not include passwords or API keys in your message.