Acceptable use policy

Email only works if the network can trust senders. This policy is short because the rule is simple: send wanted mail, honestly identified.

Facts verified 2026-07-17 — corrections: hello@emailfast.dev

Not allowed

• Unsolicited bulk email. Purchased, scraped, or harvested lists; sending without consent; re-adding unsubscribers.
• Deception. Forged senders, misleading subjects, phishing, impersonation.
• Malicious content. Malware, credential harvesting, link-cloaked exploits.
• Illegal content under EU law or the law of your sending jurisdiction.
• Abuse of the platform — attempting to bypass suppression, quotas, content policy, or another tenant's isolation.

How enforcement works

Most enforcement is structural: every send — REST, SMTP, browser SDK, compatibility endpoints, broadcasts, automations — passes through one admission gate: idempotency, suppression, quota, and content policy in a single checkpoint no ingress can skip. Complaint feedback loops suppress a recipient on the first spam report; reputation breakers throttle sending patterns that look like abuse before mailbox providers have to react.

When policy enforcement triggers, a human reviews it. You'll get specifics — what tripped, on which sends — not a form letter. Appeals: hello@emailfast.dev.

Platform-integrity limits — separate from billing

Some limits exist to protect the network and other senders, not to sell you a bigger plan. They apply on every plan, including free:

• "Unlimited" means unbilled, not unbounded. Unlimited contacts and the unlimited test sandbox mean we don't bill for them. Anti-abuse and platform-integrity limits still apply and are not a pricing mechanism — you can't be upsold past them.
• Sandbox fair use. The test sandbox is unlimited for genuine testing (it never sends real mail). Automated load far beyond documented rate limits — using the sandbox as free compute rather than to test your sending — may be throttled.
• New-sender ramp. New sending domains start with conservative volume that expands as clean sending history accumulates. This protects your own deliverability and is explained in the product before it ever affects a send.

These protections are what let the overage promise on the pricing page be true for accounts in good standing: billing and abuse-defense are separate systems.

Reporting abuse

Received something abusive sent through Email Fast? Forward it with headers to abuse@emailfast.dev. Complaint-loop reports are also ingested automatically.