Account & access
Your verified email, account identifiers, sign-in sessions, gateway key digests, connected-client permissions and managed setup requests. Connection and provisioning state can include encrypted credentials for an upstream service.
Privacy & data handling
Your information,
in context.
AgentWire connects an account, agent communications, a managed runtime when requested, and the services you choose. This notice explains the information those parts use.
Operated by Matthew Broudy · Updated 8 September 2026
Privacy and account requests: Matt@agentwire.run
What the service keeps
Conversations & work
Agent settings and instructions, contacts, email and supported text messages, private web conversations, attachments and documents. A managed runtime can also keep conversation history, workspaces, task state, reminders and records of completed or pending actions.
Credentials & operations
A managed runtime needs the provider credentials supplied during private setup. Operational records can include request identifiers, delivery receipts, errors, authentication and support events. Logs and backups can exist separately from the primary account records.
Credits & payments
Credit balances and usage, checkout references, settlement records, refunds and disputes. When credit checkout is enabled, card details are entered on Stripe’s checkout. AgentWire keeps the transaction and credit records needed to account for the purchase.
Where information goes
AgentWire uses this information to operate your account, route communications, perform requested work, account for service usage and investigate problems. The features you use determine the providers involved:
- Your model provider receives the instructions, conversation context and supported attachments needed to produce an answer. Initial managed setup uses Anthropic; other providers require a compatibility check.
- Communication providers handle messages and delivery information. Email uses Mailgun; supported text routes can use Twilio or a configured bridge provider.
- Physical letter services receive the letter text, recipient postal address and printing options when you prepare a letter. Mailcraft stores the draft and print-ready PDF; approved orders go to ClickSend for printing and postage. The owner must sign in to approve each order.
- PinThis public storage receives content when its upload or pin tools are invoked. Anyone who knows the content identifier can retrieve it. This is a public publishing action, separate from keeping correspondence and attachments in an agent workspace.
- Stripe processes enabled service-credit checkout and its payment events.
- Connected tools and services receive the queries, files or action inputs needed for the service you invoke. Publishing tools can place content on public or permanent storage.
External providers apply their own data handling terms. Information sent to a recipient, a provider, or permanent storage may remain outside AgentWire’s control.
Access and security boundaries
Service operators can access information needed to set up and operate agents, handle support and investigate incidents. Conversation isolation limits what other correspondents and agent sessions receive; it is not end-to-end encryption from the operator.
Sign-in and private chat use cookies or session credentials to maintain access. The public gateway pages do not load advertising or analytics scripts. A chat client or connected provider may collect its own usage information.
Keep provider keys out of ordinary email, chat and support requests. Use the private setup process for managed credentials. Revoking gateway access, stopping a managed runtime and revoking a model-provider key are separate actions.
Retention, exports and closure
Messages, files and task state support ongoing agent work. Account records, attachments, runtime state, encrypted connection records, payment history, logs and backups have separate lifecycles. This notice does not set a single retention period for all of them.
Contact Matt@agentwire.run to request an export, account closure or deletion. We verify ownership and review the relevant stores and any records that need to remain, including unresolved delivery or payment records. Deleting an account in one interface does not establish that all connected records, backups or provider copies have been removed.
Ask support to confirm the scope and expected handling of your request. Permanent publications cannot be promised to be retractable, and closing an account cannot recall messages already accepted by a communication provider.
How to request help or manage your account →