Privacy Policy

Who we are

Mailfully is a transactional email API operated by Even Flow Solutions LLC, a New York limited liability company (“Mailfully,” “we,” “us”).

For privacy questions, or to exercise any right described below, write to privacy@mailfully.com. We answer every request from a human.

Two different roles, and why it matters

Mailfully handles personal data in two distinct capacities, and your rights differ depending on which applies.

What we handle

Account and authentication data

Your name, email address, and organization name. If you sign in with GitHub or Google, we receive the profile identifier and email address from that provider. If you use a password, we store only a scrypt hash of it — never the password itself. Sign-in links and password-reset tokens are stored hashed and are single-use.

Billing data

Your plan, subscription status, and metered usage. Payment card details go directly to Stripe and are never stored on our systems; we retain only Stripe's customer identifier and the records needed to invoice you and meet tax and accounting obligations.

Message data

For each message you send we store the sender address, recipient addresses (to, cc, bcc, reply-to), subject line, HTML and plain-text bodies, custom headers, tags, attachment metadata, and the recipient domain. This is what makes the per-message debug log useful — you can see exactly what was sent. It also means message content lives in our database for the length of your plan's retention window.

For email we receive for you, we store the sender and recipient addresses, subject line, HTML and plain-text bodies, headers, attachments, the raw message, and the SPF, DKIM, DMARC, spam and virus results.

Delivery and reputation data

Delivery, bounce, complaint, and rejection events returned by the sending infrastructure, along with the provider's message identifier. Bounces and complaints add the affected address to your suppression list so we do not mail it again. We also compute aggregate reputation signals per sending domain and account.

Content scanning

Outbound messages are scored for abuse indicators, and a message may be quarantined if it looks like phishing, malware, or fraud. We retain the score and the action taken. This protects recipients and the shared sending reputation every customer depends on.

Technical data

IP addresses, timestamps, API key identifiers, and request metadata for the API and dashboard, used for security, rate limiting, abuse prevention, and debugging.

Dashboard activity

When you reach the sign-up or sign-in page from an ad or a link that carries campaign tags, or reach the sign-up page from another website (mailfully.com included), the dashboard stores a first-party cookie for up to 30 days holding the campaign tags (including an ad's search keyword), the website that sent you, the first mailfully.com page you opened, and whether you arrived from an ad, so we can tell which pages and campaigns bring new accounts. If you create an organization, we read it once and delete it; otherwise it expires on its own. When you create an organization, we also ask how you heard about Mailfully; answering is optional. When you visit mailfully.com, the marketing site keeps the first page you opened there, along with any campaign tags, ad click identifier or name of the website that sent you, in your browser's local storage, and passes them to the sign-up page when you click through to it. It uses them for up to 30 days from the visit they came from; after that they are ignored and removed or replaced on your next visit, and clearing your browser's site data removes them at any time. Inside the dashboard we record which pages you open and the setup steps you take, such as adding a domain or switching to test mode, and when an API request made with one of your keys is refused, we record the kind of error, the endpoint it was sent to, and the field it named. We use this to see where setup gets stuck and fix it. When you add a domain, we record the domain name we took from what you typed and a few facts about its form, such as whether it started with https://, never the full text: if you paste an email address, we keep only the part after the @. This record is ours alone. We don't use it for advertising or share it, and it is deleted when your account is deleted.

Website analytics

mailfully.com uses Plausible Analytics, which is cookieless and collects aggregate page views. It also loads the Google Ads tag, which sets cookies so we can tell which of our ads lead to sign-ups. We do not build behavioral profiles, and we do not sell data to anyone.

Support chat

Our websites and the dashboard carry a Crisp chat widget so you can reach a human. Opening it stores a conversation identifier in your browser, which is what lets us answer you rather than a stranger. If you are signed in to the dashboard we pass Crisp your email address so the conversation is attached to your account; otherwise the chat is anonymous until you tell us who you are. We keep the transcript for as long as the support history is useful and you can ask us to delete it.

Contact form

What you send through the contact form — your name, email address, company and message — is delivered to our team's inbox and kept in our systems so we can answer you and keep a record of the conversation. We don't use it for marketing, and you can ask us to delete it. An automated check, run through Anthropic (with OpenRouter as a fallback), reads the message to sort out unsolicited sales pitches; your name and full email address are not sent to it.

Why we handle it

• To deliver the email you ask us to send — the core purpose, and the basis for handling message data.
• To operate your account: authentication, team access, dashboard reads, and support.
• To see where people get stuck setting up their account, so we can fix it.
• To bill you accurately, including metered overage, and to meet tax obligations.
• To keep the platform safe: rate limiting, fraud scoring at signup, abuse detection, comparing new accounts with accounts we closed for abuse, and suppression handling.
• To protect deliverability for every customer through reputation monitoring.
• To comply with law and respond to lawful requests.

Where the GDPR applies, our legal bases are performance of a contract (operating the service you signed up for), legitimate interests (security, abuse prevention, deliverability, and improving the service), and legal obligation (tax, accounting, lawful requests). We do not rely on consent for the core service, and we do not use your data or your recipients' data to train machine-learning models.

Comparing accounts to prevent abuse

To protect our service from abuse, we compare technical details of new accounts with accounts we have closed for abuse. These details are the public DNS records of an account's sending domains, the domains its emails link to, brand names that repeat in its email subjects, and the title of the account's website. They also include the domain of its owner's email address, the IP address it signed up from, one-way codes made from owner email addresses, and a one-way fingerprint of the payment card, when there is one.

A match is a lead for a person to review. We pause an account automatically only when several independent matches point to the same organization and an automated check agrees. If your account is paused, write to contact@mailfully.com and a person reviews it.

For accounts in good standing, we keep the brand names, linked domains and owner email addresses only as one-way codes, not as the details themselves. We keep the other details while the account is open and delete them when the account is deleted. When we close an account for abuse, we keep its details, including brand names and linked domains in plain text, for as long as we need them to recognize the same organization if it signs up again.

If you ask us to erase your data, we delete it. For an account we closed for abuse, we keep only the one-way codes and the technical records needed to prevent fraud.

How long we keep it

Message content and logs are retained for your plan's retention window — 30 days on Free, Starter and Growth, 90 days on Scale, and 60 days on a Growth plan bought before October 19, 2026 — after which message content ages out of the readable log. Received email, with its attachments and raw message, is deleted at the end of the same window.

Suppression lists outlive that window by design. An address that hard-bounced or filed a complaint has to stay suppressed to stop us mailing it again; discarding the record would defeat its purpose and harm the recipient.

Account and billing records are kept for the life of your account and afterward only as long as tax, accounting, and legal-defense obligations require.

Aggregate reputation and usage statistics may be retained in aggregated form that no longer identifies individual recipients.

Subprocessors

We use the following third parties to run the service. Each is bound by contractual confidentiality and data-protection obligations, and each receives only what its function requires.

We will give notice before adding a subprocessor that handles customer message data, so you have a chance to object. Beyond these, we disclose data only when law requires it, to protect rights and safety, or in connection with a merger or acquisition — in which case the acquirer is bound by terms no less protective than these.

We do not sell personal data, and we do not share it for cross-context behavioral advertising.

Security

Data is encrypted in transit and at rest. Access follows least-privilege principles, API credentials are stored only as hashes with a lookup prefix (never the secret), and tenant data is isolated at the query layer so a request can only ever read its own organization's records. We log administrative access and maintain a documented incident-response process. No system is perfectly secure, but we treat this as a first-order engineering concern rather than a compliance checkbox.

International transfers and residency

Our default infrastructure runs in the United States. If you are in the European Economic Area, the United Kingdom, or Switzerland, transfers rely on the European Commission's Standard Contractual Clauses, and our Data Processing Addendum covers the required processor obligations. Customers who need data to remain in the EU can run on our EU region, where sending infrastructure and message-log storage stay in an EU region — write to us to provision one.

Your rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal data; to object to or restrict certain processing; and to withdraw consent where we rely on it. Residents of California and other US states with comprehensive privacy laws have rights of access, deletion, correction, and portability, plus the right not to be discriminated against for exercising them.

Email privacy@mailfully.com to exercise any of these. We verify the request, respond within the timeframe the applicable law requires, and will not charge you or degrade your service for asking. If you are in the EEA or UK you may also complain to your local supervisory authority.

Much of this is also self-service: you can export your message logs and suppression lists from the dashboard, edit your account details, remove a sending domain, and delete your own account, which removes your profile, your sign-in credentials and the invitations you sent. If you are an organization’s only owner, hand it over to a colleague first or write to us.

Deleting an organization is not self-service yet. You can ask us to delete your account at any time: reply to any email we send you, or write to privacy@mailfully.com, and we will do it for you. Separately, an account that has not verified a sending domain may be deleted automatically: after about seven days without one if it has never sent an email in test mode, or about thirty days after its last test-mode email if it has. Either way, an email warning that names the date always comes first.

After a deletion, whether you asked for it or it was automatic, we keep a record that it happened, so that we can answer questions about a past account and recognize a repeat signup. The record holds the organization’s name, the email addresses of its members, the domain names it added, the IP address it signed up from, and the dates and reason for the deletion. If you ask us to erase your data, the record keeps only that a deletion happened and when, except for an account we closed for abuse, which keeps what the section on comparing accounts describes. We also keep the billing records our payment processor holds, and backups for their retention window.

We may send occasional product news to the address you signed up with. Every such email carries an unsubscribe link, and you can ask us to remove you at any time.

Children

Mailfully is a developer tool sold to businesses. It is not directed to children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us data, write to privacy@mailfully.com and we will delete it.

Changes to this policy

We will update this page when our practices change and revise the date above. For material changes that affect how we handle your data, we will notify account owners by email rather than relying on you to notice a quiet edit.

Contact

Privacy questions and data-subject requests: privacy@mailfully.com. Security reports: security@mailfully.com. Abuse reports: abuse@mailfully.com.

Even Flow Solutions LLC, New York, United States.