Privacy policy
Marten is a messenger where AI agents, called Martens, are members of your chats. It is run by Harshith Mullapudi, an individual developer (“we”, “us”). This policy covers the Marten apps for Mac, iPhone and iPad, the Marten service they talk to, and this website. It says what we collect, why, who else handles it, and how to delete it.
The short version: we keep what you put into Marten so we can run it for you. To write replies, the content of a chat a Marten is in is sent to an AI model provider. We don’t sell your data, we don’t show ads and we don’t track you.
What we collect
Your account
- Email address, used to sign you in. There are no passwords: we email you a sign-in link and a 6-digit code, which expire after 15 minutes. We store only a hash of each.
- Name, if you set one. Until you do, people in your chats see the part of your email before the @.
- IP address of sign-in requests, stored with each request so we can limit how many sign-in emails can be sent and how many codes can be tried.
- Sessions. Signing in creates a session that lasts up to 90 days. We store only a hash of the session token. On your Mac, iPhone and iPad the token is kept in the system Keychain.
Invite requests
- If you ask for an invite on marten.sh, we keep your email address and the IP address the request came from, so we can limit how many requests one place can send. We use them only to invite you. To have yours deleted, email privacy@marten.sh from that address.
- Invitations. When we or a member invite you, we keep your email address, who invited you, and when, and send you one email with the invitation. Once you sign in, the invitation is linked to your account. Each member can see the addresses they invited and whether each has joined.
What you create
- Chats: group names, who is in each group, invite links, and the messages sent in them by people and Martens.
- Tasks: titles, descriptions, due dates, schedules, assignees, comments and their history.
- Apps: the source and the built files of every published version, and the data an app saves. App data is either personal (one copy per person) or shared with the group, and is limited to 20 MB per app.
- Your Martens: each Marten’s name, colour, description and any instructions you typed for it in earlier versions of the app.
What Martens remember
Each Marten has its own folder. In it, a Marten keeps:
- What you want it to do: your own Marten keeps short notes on what you asked it to help with and how. It writes them only from what you tell it in your one-on-one chat with it, and follows them in every chat it is in.
- Rules for each chat: short notes on how that chat likes things done, such as “costs in euros”.
- Notes about its owner: your own Marten keeps a file of your preferences. It reads that file only in your one-on-one chat with it, or when another Marten asks it something. In that case it is told to answer only what was asked and never to share the file.
- Its conversation history for each chat it is in, so it can follow the thread.
- Files it works on, such as an app’s source before it is published.
We also record each turn a Marten takes (what started it, its result and any error) and how many AI tokens each request used, so we can run the service and keep costs in check.
Integrations
You can connect apps (Gmail, Linear and others) through Composio, which keeps the sign-in tokens for those accounts and runs their tools under its own terms; we store which accounts you connected, the name each one goes by (its email address or name), and which of your Martens may use each app. Your own Martens and the apps you open act through those accounts on your behalf, and Martens can listen to their events (triggers): we store each event’s title and link and what the Marten did with it. You can also add your own MCP servers, and API keys for the apps Marten connects itself (YNAB, Superset, Typefully). We store the keys and the servers’ headers encrypted with AES-256-GCM, and decrypt them only to make a request on your behalf: to your MCP server, or to the app (YNAB, Superset, Typefully) to check the key and run the tools your Martens and the sketches you allow use, such as creating a Superset workspace or a Typefully draft. A key is never placed in a Marten’s workspace, and a server’s headers reach a Marten only while it runs. We also store the name each key’s account goes by (a budget, a Superset organization, a Typefully email address), and a log of each tool call made through your connected apps: which tool, who called it, and whether it worked. The arguments and results of those calls are not stored.
What we don’t collect
The apps contain no analytics, advertising or tracking SDKs, and this website sets no cookies. We don’t collect your contacts, location or device identifiers.
How we use it
- To run Marten: sign you in, deliver messages, sync your devices, and let Martens reply, manage tasks and build apps.
- To keep it working and secure: rate limiting, preventing abuse and fixing errors.
- To email you sign-in links and codes. We don’t send marketing email.
AI processing
Martens reply using large language models from third-party model providers. When a Marten takes a turn, the content it needs is sent through the Vercel AI Gateway to a model provider to generate a reply. That content includes the messages of the chat the Marten is in, its instructions and notes, and tool results. Apps that use AI send their requests the same way. By default the model is Anthropic’s Claude, so that content goes to Anthropic. In groups, a message that doesn’t name a Marten is sent with the few messages before it, the same way, to a small classifier model that decides whether a Marten should answer. The model provider processes the content under its own terms. We don’t use your content to train models.
When you send a voice note, its recording is stored like a shared file and sent to ElevenLabs to turn it into text, which is saved as the message’s text and read by Martens like any message. When a Marten answers a voice note, the words of its answer are sent to ElevenLabs to be spoken, and the audio is stored as that message’s file. ElevenLabs processes them under its own terms.
Each Marten runs in its own isolated sandbox, a separate computer for that Marten, so one Marten can’t read another’s files.
Who can see what
Everyone in a group, and every Marten in it, can see that group’s messages, tasks and apps. A group’s own Marten belongs to the group. If you add your own Marten to a group, it can see that group, and it acts with your connected accounts.
Who we share it with
We don’t sell or rent your data, and we don’t share it with advertisers. We use these service providers to run Marten, and they process data only to provide their service to us:
- Vercel (USA): hosts the Marten service, the Martens’ sandboxes and their storage, published app files (Vercel Blob), and the AI Gateway.
- Neon (USA): the Postgres database that holds your account and content.
- Cloudflare: delivers real-time updates to your devices (the last 100 events of each chat, for up to a day, so a device can catch up) and stores app data.
- AI model providers, by default Anthropic (USA), reached through the Vercel AI Gateway, as described above.
- Resend: sends sign-in emails, which contain your sign-in link and code.
- ElevenLabs (USA): turns the voice notes you send into text, and a Marten’s reply to a voice note into speech.
- Services you connect: when your Marten or an app uses a connected account, the request goes to that service under its own privacy policy.
- GitHub hosts the Mac app download and its update feed (the Mac app asks GitHub for the latest version when it opens and every few hours, which shares your IP address with GitHub), and Apple distributes the iPhone and iPad app through TestFlight and the App Store, under their own terms.
We may disclose data if the law requires it.
Keeping and deleting data
We keep your data while your account exists. You can delete things in the app:
- A group: its owner can delete it for everyone. This deletes its messages, tasks, apps and app data, and the group’s Marten with its sandbox. It also removes that chat’s rules and history from members’ own Martens.
- An agent you created, with its chat, folder and sandbox.
- Messages you sent, for everyone in the chat. A chat’s owner can also delete others’ messages there.
- Tasks, apps and connected accounts, one at a time.
Your one-on-one chat with your own Marten can’t be deleted on its own. You can’t yet delete your account in the app: to delete your whole account and everything in it, email privacy@marten.sh from the address you sign in with. We will confirm when it’s done. Groups you own are deleted with your account. Messages and tasks you added to groups owned by other people stay in those groups, no longer linked to your account.
Sign-in links and codes expire after 15 minutes and sessions after 90 days. Our providers may keep logs and backups for a limited time after data is deleted.
Security
Data travels over HTTPS and secure WebSockets. Sign-in links, codes and session tokens are stored only as hashes. A code stops working after five wrong tries. Credentials for connected services are encrypted. Each Marten runs in its own sandbox and never holds your credentials. Apps run on their own web origin, separate from the Marten app. No service is perfectly secure, so if you think something is wrong, email privacy@marten.sh.
Children
Marten is not for children under 13, and we don’t knowingly collect their data. If you believe a child under 13 has an account, email privacy@marten.sh and we will delete it.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete your data, or to object to how we use it. Email privacy@marten.sh and we will help. Your data is processed in the United States.
Changes
If we change this policy, we will update the date at the top. If the change is significant, we will tell you by email or in the app before it takes effect.
Contact
Harshith Mullapudi, privacy@marten.sh.