What phoneAFriendForAgents keeps, and why

Your email address, when you sign in from an MCP client or request an API key. It is your account name.

The call briefs your agent sends: who to call, the phone number, the questions, who the call is on behalf of, and any context, constraints, call window, language, or attachments the agent includes.

The caller's report: the text the person writes back after the call.

Technical details: the name and version of the MCP client your agent announces, your IP address (for rate limiting and in server logs), timestamps and durations of requests, and a usage log of tool calls in which long text is trimmed and attachment contents are replaced by their size.

The server receives nothing else from your conversation. It sees only what the agent passes to a tool. It does not read Claude's memory, chat history, or files, and it does not collect conversation data for logging or any other purpose.

To place the call: the brief, with any attachments, is emailed to the person who makes the call. They read it, dial, and reply.

To return the report to your agent and count the call against your monthly allowance.

To enforce limits, keep the service working, and investigate problems.

We do not sell data, show advertising, or use your data to train models.

The person who makes the call sees the brief and writes the report.

The business that is called hears the questions and the name given in on_behalf_of.

Google: briefs and reports travel through a Gmail mailbox over SMTP and IMAP, so Google processes them as email.

Fly.io hosts the server and its storage in the United States and retains server logs briefly.

No one else. We do not share data with anyone beyond these, except where the law requires it.

Call records (a one-line summary, the phone number, who asked, when, and the report) are stored on the server's encrypted volume and kept until you ask us to delete them.

The emails carrying the full brief, attachments, and report stay in the mailbox used to make calls. A deletion request covers them too.

Sign-in codes expire after ten minutes. Access tokens expire after 30 days and refresh tokens after 180 days; expired tokens are removed seven days later. Tokens and API keys are stored only as hashes.

The usage log is a file capped at 50 MB that rolls over once, so at most the most recent 100 MB of activity is kept.

Write to rmtonmoy232@gmail.com from your account address to ask what we hold about you, or to delete your account and its records. Disconnecting the connector in your client revokes its token.

Send only what the call needs. The caller needs the questions and the facts the business may ask for; nothing in a brief should be more personal than that.

phoneAFriendForAgents is not for anyone under 18.

If this policy changes, the new version appears here with a new date. Questions go to rmtonmoy232@gmail.com; see also Support and the Terms.