Security
Your key, your agent, your conversations.
Melony is a thin layer between your team and your agent platform. Here’s exactly what passes through it and what it keeps.
The API key stays server-side.
Each agent has one API key, held by its owner. The owner pays the platform as usual; teammates never get a key.
- Never in the browserThe browser talks only to Melony’s API. The key isn’t in any page, streamed event or API response the UI uses.
- Separate from app dataKeys live on the API host, not in the database. Database rules deny clients any access to key material.
- Checked on every requestEach chat request verifies your sign-in and membership before Melony calls the platform with the owner’s key.
What Melony stores
The minimum needed for sign-in, membership and private chats.
| Data | Details |
|---|---|
| Your profile | Email and name from Google sign-in. |
| Agent settings | Display name, platform, the platform’s agent ID, owner, and environment and vault IDs. Never the API key or vault secrets. |
| Members and invites | Who is on each agent, their role, and pending invites by email until they’re claimed or cancelled. |
| Chat access index | Session ID, who started it, whether it’s shared, and when. Not the conversation. |
| On the API host only | The per-agent API key and per-person daily message counts. |
What Melony never stores
- Messages or conversation text
- Token counts or platform execution state
- Vault credentials or secret values
- Your agent’s model, instructions, prompts or tools
Private by default, shared on purpose.
Neither platform tracks which person owns a session, so Melony keeps a small access index to enforce it.
- New chats are privateOnly the person who started a chat can see it.
- Sharing is explicitThe creator can share a chat with everyone currently on the agent, and only the creator can unshare or delete it.
- No owner backdoorThe agent owner can’t open other people’s private chats.
Roles and limits
Three simple roles. Limits are enforced on the server: up to 3 teammates per agent, pending invites included, and 100 messages per person per day.
Owner
Creates the agent, holds the only API key, rotates it, grants or revokes admin, and can delete the agent. The owner can’t be removed.
Admin
Invites and removes members and manages environment settings. Can’t rotate the key, delete the agent or promote anyone to admin.
Member
Chats with the agent. Doesn’t manage the roster or the key.
Frequently asked questions
Can teammates see the agent owner’s API key?
No. The key is stored on Melony’s API host, not in the database the browser reads. It never appears in a browser, in a streamed response, or in any API response the UI uses.
Can the agent owner read my private chats?
No. A chat is visible only to the person who started it until they share it. Requests for a chat you may not see return “not found” without calling the platform.
Does Melony train on or keep my conversations?
Melony doesn’t store conversations at all. They live on OpenAI or Anthropic as sessions of your agent, under that platform’s data policies for your account.
Does Melony run tools or approve tool calls?
No. Tools run on the agent platform. Melony shows tool activity in the chat but never executes tools or grants approvals.