Privacy Policy

1. Overview

MailLogic.io provides custom domain email forwarding, SMTP sending, API sending, DNS verification, usage logging, and billing features. This Privacy Policy explains what we collect, how we use it, and how to contact us.

2. Information We Collect

• Account information, such as your Google sign-in email address, authentication user ID, profile information returned by Google, and account settings.
• Billing information processed through Stripe, such as Stripe customer ID, subscription ID, plan, billing status, billing periods, and related webhook events. We do not store full card numbers.
• Domain and email configuration data, such as domains, DNS verification records, forwarding addresses, SMTP accounts, API keys, and block lists that you configure.
• Google Sheets data that you explicitly select for Batch Send. The spreadsheet and worksheet names are used for the browser selection summary, and the displayed cell values are submitted as the recipient snapshot. MailLogic does not request access to unselected Drive files.
• Email delivery metadata, such as timestamps, queue IDs, message IDs, sender and recipient addresses or domains, client IPs, authenticated SMTP users, API key IDs, spam scores, delivery direction, server type, and blocked reasons.
• Operational logs and security data, such as IP addresses, request metadata, browser or device information, and error logs.

3. Email Content

MailLogic processes email content as needed to provide forwarding, SMTP delivery, Batch Send, replies, spam filtering, abuse prevention, and security. Batch Send temporarily stores recipient values and message templates while a batch is queued or processed, then purges that temporary payload when the batch reaches a terminal state. Reply content is retained according to the configured reply-retention period. Outside features that require content, the dashboard is designed around delivery metadata and does not intentionally store message bodies as normal product records.

4. Google Sheets Integration

When you choose Google Sheets as a Batch Send source, Google Picker lets you select a spreadsheet and the Google Sheets API returns the selected worksheet's displayed values directly to your browser. MailLogic requests the limited drive.file scope and receives only the worksheet snapshot that your browser submits for validation and sending. Google OAuth access tokens stay in browser memory, are not sent to the MailLogic backend, and are not stored in MailLogic databases. This is a one-time snapshot import, not a continuous synchronization.

MailLogic's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

5. How We Use Information

• To create and secure your account.
• To provide email forwarding, SMTP sending, API sending, Batch Send imports, DNS verification, logs, and dashboard features.
• To process subscriptions, enforce plan limits, and handle billing status through Stripe.
• To detect spam, phishing, malware, abusive sending, account compromise, and other harmful activity.
• To troubleshoot, monitor reliability, improve the service, and respond to support requests.
• To comply with legal obligations and enforce our Terms of Service.

6. Service Providers

We use third-party service providers to operate MailLogic, including Google for authentication and user-selected Sheets access, as well as providers for hosting, infrastructure, billing, DNS, logging, monitoring, and email-related services. These providers process information only as needed to provide their services to us.

7. Sharing

We do not sell your personal information. We may share information with service providers, when required by law, to protect MailLogic and its users, to investigate abuse, or as part of a business transfer such as a merger, acquisition, or asset sale.

8. Security

We use technical and organizational safeguards designed to protect account, billing, domain, and email metadata. No internet service can guarantee perfect security, but we work to limit access, monitor abuse, and reduce unnecessary data retention.

9. Retention

We retain information for as long as needed to provide the service, maintain security, comply with legal obligations, resolve disputes, and enforce agreements. Imported Google Sheets values follow the Batch Send temporary-payload lifecycle described above. Google OAuth access tokens are not retained by the MailLogic backend. Some operational logs and abuse-prevention records may be retained after account closure when necessary to protect the service.

10. Your Choices

You may disconnect Google from the Batch Send interface, revoke MailLogic access in your Google Account permissions, update account settings, delete configured domains or keys, cancel billing through Stripe where available, or contact us about account deletion or data questions. Disconnecting clears the current imported snapshot in the browser and requests revocation of the in-memory Google token. Some information already submitted for an active batch or required for legal, billing, security, or abuse-prevention purposes may need to be retained for the applicable period.

11. International Use

MailLogic may process information in countries where we or our service providers operate. By using MailLogic, you understand that information may be processed outside your country or region.

12. Changes

We may update this Privacy Policy as the service changes. The effective date above shows when this page was last updated. Material changes may be announced through the dashboard, the website, or another reasonable method.

13. Contact

Questions about this Privacy Policy can be sent to [email protected].

14. Connected AI services and OAuth integrations

You may choose to connect MailLogic to third-party AI clients, such as ChatGPT (OpenAI) or Claude (Anthropic), or other compatible services through OAuth and MCP or similar integrations. These connections are initiated or authorized by you.

When you authorize and use a connection, MailLogic may provide the connected service with information needed to fulfill your requests within the permissions you grant. Depending on the request, this may include domain names and DNS/configuration status; email addresses, forwarding destinations, display names and email-account settings; usage and capacity information; delivery metadata such as sender, recipient, timestamp, status and delivery reason; forwarding-test status and diagnostic information; and configuration/action results and related operational metadata. The current MCP integration does not provide message bodies, inbox-reading access, or general email-sending or Batch Send authority.

Access is limited by the permissions you grant through the authorization flow. You may revoke a connected application's MailLogic access through MailLogic's Connected Apps controls or other applicable account controls. Once information is provided to a third-party service at your direction, that service's own privacy policy, retention practices and terms may govern its handling of the information. Revoking MailLogic access does not itself delete information already held by that service.

Some workflows, such as automatic DNS setup with a supported DNS provider, may return a private authorization URL and direct you to that provider for authorization or configuration. Information submitted to or handled by that provider is subject to its own terms and privacy practices.