Data and privacy
Operated by MARTHA TRADE PTE. LTD. (Martha trade). Contact: [email protected]
Data we store
We store your account username, password-derived value, recovery-code hash, sessions and authorizations; deletion, disconnection and credential-change records without mail or passwords for isolated restore checks; connected email addresses, incoming server settings and client credentials; message subjects, sender and recipient addresses, Message-ID headers, dates, plain-text bodies, synchronization and delivery status, and processing instructions saved for your agent. A username is not a verified email identity. When sending is on for a mailbox, as it is by default for a newly connected mailbox, we also store its SMTP connection settings and credentials (by default an encrypted copy of the login you entered for receiving), and outgoing draft recipients, subject, plain-text body, sender, confirmation and submission status.
Mailbox credentials, Webhook URLs and keys, email bodies and custom instructions are encrypted with an application key. Subjects, sender and recipient addresses, Message-ID headers, dates and operational status are stored as database metadata. The encryption key is configured separately from the database. The service must decrypt credentials to receive mail continuously; this is not end-to-end encryption. SMTP credentials must be supplied explicitly and are never copied from incoming-mail credentials. SMTP credentials and outgoing draft recipients, subject and body are encrypted at rest with the application key.
Duplicate prevention: for each mailbox we keep a SHA-256 hash of the Message-ID header of every collected email that has a valid one, linked to the internal ID of the first copy. Copies of that email in other folders or labels, moved messages and resent copies with the same Message-ID are then treated as one email instead of new mail; while the first copy is retained, an email that reuses its Message-ID with a different sender or subject is kept as separate mail. The hash is used only to avoid duplicates. It is kept after retention deletes the message, so a later copy is not collected again, and is deleted when you delete the mailbox from the connector or delete your account. Encrypted backups follow the backup retention described below.
If you open the dashboard from a link with public campaign tags (utm_source, utm_medium, utm_campaign, utm_content) and then create an account, we store those tags with your account to count which channels lead to signups. If you arrived from an X ad, we also store X's click ID (twclid) and send it to X's Conversion API, together with the event name and time, when you sign up, first connect a mailbox and first authorize an AI agent, so X can count conversions from our ads. We send X no username, email address, IP address or mail data. We do not store other link parameters, and the tags and click ID are deleted with your account. The operator’s usage report shows only aggregate counts of signups, setup steps and AI processing, based on per-account setup timestamps and counters that are deleted with your account.
Sign in with Google
Google sign-in is optional and does not automatically connect a Gmail mailbox. Sign-in, account linking and identity confirmation redirect you to Google. We request basic identity scopes (openid, email, profile) and identify your account using its stable Google identifier and verified email address. The email address is encrypted. This sign-in flow does not retain Google names, avatars, access tokens or refresh tokens, and does not request Gmail reading, sending or management permissions.
Short-lived authorization state and security checks protect sign-in requests. Identity reconfirmation is short-lived, bound to your current session and usable once. Existing accounts must be linked to Google by you; matching email addresses do not automatically merge accounts. Accounts created through Google have no local password and require Google identity reconfirmation before deletion. Account deletion also removes the Google link stored by this service. Google processes its own sign-in information under its own terms and privacy policy.
If you create your account with Google, we send one welcome email to that verified address with our community and support links. Accounts without Google sign-in and connected mailbox addresses never receive it. Reply “unsubscribe” and we will not email you again.
Optional mailbox authorization
Connecting Gmail or Microsoft mail requires separate consent from account sign-in. Gmail initially requests gmail.readonly; Microsoft requests delegated Mail.Read, User.Read for mailbox identity and offline_access. An existing mailbox can separately request gmail.send or delegated Mail.Send when you enable sending. Every outgoing draft still requires your review and confirmation in InboxMCP. We encrypt mailbox access/refresh tokens and synchronization checkpoints, and retain the provider identifier and email address to bind authorization to the verified mailbox. Pausing collection retains this connection; disconnecting or deleting the account removes its saved credentials and provider sync state. Restoring a backup requires fresh mailbox authorization. Availability is shown in mailbox setup.
How data is used and shared
Incoming mailbox access uses read-only IMAP or provider APIs. When you connect a mailbox, collection and sending are turned on by default; you can untick either before saving or turn them off later. To turn sending on, InboxMCP signs in once to the provider's matching SMTP server with the login you entered for receiving, and stores it encrypted. An agent can prepare drafts only with its separately granted email:send permission, which starts unticked, and nothing is sent until you review and confirm each draft in InboxMCP. Recipient addresses and message content go to the selected outbound provider and recipients only when you confirm sending. Enabling Grok delivery sends each new message's subject, sender, date and up to 4,000 body characters, with your processing instructions, to the Routine Webhook you confirm. That platform analyzes the message and decides whether to notify you. Only connect mailboxes you are entitled to process.
When connecting agents through OAuth, you select their mailboxes and tick each permission separately: reading is required, and sending starts unticked and needs its own confirmation. An existing authorization never gains permissions; reconnect to add one. Agents can read authorized mail and saved instructions, and separately request permission to prepare outgoing drafts for your confirmation. Outgoing drafts are encrypted and follow the same account retention rules. We do not automatically retry a send with an uncertain outcome. With decision permission, agents can stop remaining local delivery and retries for an event; requests already sent may still complete. Pausing collection does not revoke MCP access or disable sending. Manage sending separately and revoke agent permissions under Authorized agents.
Claude, ChatGPT, Grok Bot and other compatible AI clients connect through standard MCP with OAuth; Grok Bot can optionally also receive new mail through your own Routine Webhook. As of October 4, 2026, InboxMCP is published and visible in the public Claude Directory as a Community connector; OpenAI plugin version 0.1.2 remains in review and is not published. Client compatibility and native proactive notifications must be verified separately. Muse has received all required application materials, but does not yet have an available adapter in this service. HTTP acceptance, an agent decision and delivery of a device notification are distinct states.
Outgoing mail review and submission
Outgoing drafts contain plain text, without attachments, and use a fixed sender from your authorized mailbox. The recipients and content are immutable: each draft needs your own review and confirmation in InboxMCP before one submission attempt. Agent or email content cannot grant that confirmation. Accepted means the outbound provider accepted the message, not that recipients received it. An uncertain result is not retried automatically; check the provider or sent mailbox before preparing another send. During sign-in or provider authorization, the browser may temporarily store only an opaque draft ID and creation timestamp in sessionStorage for up to 20 minutes to return you to the review. This record contains no mail content or credentials and is consumed on return.
Hosting and retention
With permission to save processing progress, we retain a separate checkpoint, batch leases and acknowledgements for each AI connection. If, when reconnecting, you choose saved progress that belongs to another AI connection, that progress moves to the new connection and the other connection’s authorization is revoked. These operational records do not change source mail or prove that a notification arrived. A client that supports MCP Events may explicitly subscribe to signed callbacks: the callback receives event and mailbox identifiers and a login-required message link, while the AI retrieves mail and your saved instructions using its authorized tools. Callback addresses and signing secrets are encrypted. Inactive event subscriptions and their secrets are removed after 30 days; delivery records are also removed with the source event. No external state service is required for the built-in batch workflow.
Cloudflare provides website hosting, DNS and HTTPS reverse proxying. The mail backend's isolated containers and persistent database currently run in Google Cloud us-central1 (Iowa, United States). Cloudflare network processing may involve other regions; processing is not necessarily confined to the United States. Network and hosting providers process connection information needed to serve requests.
Server logs: to secure and troubleshoot AI connections, the service logs OAuth steps: an AI client registering (with the name it reports and its callback addresses without query parameters), authorization starting with the requested permission names, your approval with the granted permission names and the number of mailboxes you selected or your denial, and the authorization code exchange. It also logs rejected authorization and token requests as fixed reason codes, client registrations rejected because of their callback addresses, with the name and addresses the client supplied (query values redacted), and requests to the MCP endpoint without valid sign-in, with their method and outcome, including the name an AI app reports when it tries to connect before signing in. Clients are identified by an opaque fingerprint and the name they report. We do not write access or refresh tokens, authorization codes, state values, passwords, mail content or your mailbox addresses to these entries. The application keeps no per-request access log. Server logs, which can also contain technical error messages, are rotated within three 10 MB files per service and discarded whenever the service is redeployed.
Message bodies and events are retained for 30 days by default after receipt by the connector. Cleanup retains body-free synchronization cursors and deduplication records to avoid delivering old mail again. If an AI connection had deferred a removed email, a body-free notice (event ID, mailbox and times) is kept until that connection has been told, then for one more retention period, and is deleted with the connection's mailbox scope. Accounts and connection settings remain until you delete them. Encrypted backups target a 30-day retention period, with daily cleanup. Cleanup may run the next day or require operator intervention after an outage; this is not a strict expiry guarantee. Backup restores pause monitoring and revoke sessions and agent authorizations by default. Administrators must reconcile deletions, disconnections and credential changes made since the snapshot before restoring public service. Outgoing drafts and their submission records are retained for 30 days by default from creation, subject to the same cleanup schedule.
Subscriptions and PayPal
When paid checkout is enabled and you choose to subscribe, you leave the dashboard to approve payment on PayPal. We send PayPal the selected plan, an internal checkout reference and return addresses, not your mail content, mailbox credentials or agent instructions. We do not collect payment-card numbers, bank login credentials or your PayPal password in the dashboard. PayPal processes payment, payer and device information under its own privacy statement.
We store the link between your account and the subscription, PayPal subscription and payment identifiers, plan and interval, currency, amounts, payment dates, paid-through dates, status and verification records. The approval link is encrypted. These records verify access, prevent repeated payment processing and support cancellations, refunds or disputes. PayPal responses may include payer information, but the integration does not persist payer profiles or raw payment responses. Ordinary billing metadata is not encrypted at the application-field level.
Subscription and payment records remain in the application while the account exists. Account deletion is blocked until subscription cancellation is confirmed; deletion removes the account-linked subscription and payment records. Provider event identifiers and refund or dispute payment identifiers retained separately to prevent repeated processing are not automatically removed with account deletion. Encrypted backups follow the retention described above. Deleting an inboxmcp account does not delete records held independently by PayPal; contact us with questions about billing records.
PayPal Privacy Statement ↗Your controls
You can pause delivery, disconnect a mailbox and clear its credentials, delete mailbox copies from the connector, revoke an agent’s OAuth grant, sign out all devices, or delete your account after password verification (Google-only accounts reconfirm their linked Google identity). A PayPal subscription must have confirmed cancellation before account deletion. The connector cannot recall data already sent to an agent; manage that data on the receiving platform. You can separately disable outgoing mail. Deleting a mailbox or account also deletes its outgoing settings, credentials and drafts; accepted mail cannot be recalled by this service.
This service does not run a mail classification model, score importance, filter messages by their content, or operate a user-notification engine. How an external agent handles messages depends on that platform's service and your settings. Contact the address above for data questions or requests.
Language preference
When you choose a language, we save only that language code in browser storage until you clear it and in a preference cookie that lasts up to one year. The cookie is shared by inboxmcp.ai and its subdomains so the website and workspace use your choice. It contains no account or email data and is not used for advertising or analytics. Clearing browser site data resets the preference; English is the default.