Everyone who touches your data
Subprocessors.
These are the companies we rely on to run Murmello. This is the complete list — if a provider is not here, it does not handle your data. It accompanies our privacy notice.
Effective October 31, 2026 · Tomas Godoy Pastore · support@murmello.ai
Handling your content
These providers can process the things you put into Murmello.
| Provider | What it handles | Where |
|---|---|---|
| Amazon Web Services ↗ | Our servers and storage: the saved versions of your agents' work (including versions of folders you let an agent use on your Mac), the caches of your agents' installed tools, the database holding accounts, profiles, agents and usage records, the encryption keys protecting your saved credentials and GitHub connection, the early-access waitlist, and outbound email. Through Amazon CloudFront, it also delivers the app, its updates and the Linux image agents on your Mac run on. | United States (us-east-1) |
| Fly.io ↗ | The cloud machines (Sprites) cloud agents run on: while an agent runs there, its files, its tools, the commands it runs, and the sign-ins handed to it. Each agent has its own machine, removed when the agent is ended or archived. Agents on your Mac do not use Fly.io. | United States (Fly.io places each cloud agent’s machine near our server in Virginia, which creates it) |
| ElevenLabs ↗ | Dictation audio, streamed while you speak and returned as text. We ask them not to log the content of these requests, and neither we nor they retain the audio or the transcript for you. | United States |
Handling your account and payments
| Provider | What it handles | Where |
|---|---|---|
| Stripe ↗ | Payments, subscriptions and invoices. Stripe holds your card details; we never see them. We hold only your Stripe identifiers, plan and payment status. | United States |
| Cloudflare ↗ | DNS and delivery for this website and the update feed. It sees connection information such as IP address and requested URL, not your files or audio. | Global edge network |
| Google ↗, GitHub ↗, Apple ↗ | Sign-in, if you choose that provider. They confirm your identity and give us your email address. They do not receive your files or audio. | United States |
Not a subprocessor: your AI provider
Murmello does not include AI model usage. You connect your own account or API key for a supported coding tool (Claude Code, Codex or OpenCode), and your prompts and code go from the agent's machine to that tool's provider under your own agreement with them, billed by them. We store your credential encrypted, or you keep it only in your Mac's Keychain, so an agent can act as you, but we are not a party to that relationship and it is not covered by this list. Check that provider's own terms for how it handles your code.
Not a subprocessor: GitHub, when you connect it
If you connect GitHub to import, pull or push repositories, GitHub receives what you push and sends what you import, under your own agreement with GitHub. This happens only when you ask.
Not a subprocessor: connections and skills you add
A connection is an MCP server you choose, run by its own provider. When an agent uses it, that server receives the agent's tool calls and any token or key you give it, under your own agreement with that provider. Skills come from the sources you pick when you add them. Neither is covered by this list.
International transfers
These providers process data in the United States, Fly.io included (it places each cloud agent’s machine near our server in Virginia), except Cloudflare, which serves from its global network. If you are in the EEA, the UK or Switzerland, we rely on the European Commission's Standard Contractual Clauses, and the UK Addendum where relevant, as the transfer mechanism.
Changes
We will update this page before adding a provider that handles your content, and the effective date above will change with it. If you want to be told directly when that happens, email support@murmello.ai and we will add you to the notice list.