Acceptable Use Policy

EmailFleet exists to run legitimate business mailboxes. The service sits on shared mail infrastructure, which means one customer's abuse can damage deliverability for everyone. This policy is enforced strictly and applies to every mailbox, domain, API key, and agent connected to the service.

Prohibited Uses

You may not use EmailFleet to send or facilitate:

• Unsolicited email of any kind. Cold outreach, cold email campaigns, and bulk prospecting are prohibited outright, regardless of volume, personalization, or opt-out links. There is no permitted volume of unsolicited mail.
• Mail to purchased, rented, scraped, or harvested address lists.
• Mailbox warm-up schemes, engagement farming, or any automated activity meant to manipulate sender reputation.
• Phishing, impersonation of any person or organization, or spoofed sender identities.
• Malware, fraud, or content that is illegal in the sender's or recipient's jurisdiction.
• Sending on behalf of a domain you do not own or control.

Permitted Uses

The service is built for transactional, operational, and conversational mail: replying to people who wrote to you, correspondence with existing customers and suppliers, receipts and notifications people expect, and the ordinary mail of running a business. Agent mailboxes carry the same standard. An agent may converse and transact; it may not prospect.

Technical Limits

Sending limits are enforced in the product: agent sends are limited to one recipient per message with a daily cap per mailbox, and no bulk sending endpoint exists. Hourly sending limits from our upstream infrastructure apply to all mailboxes. These limits are structural and not negotiable.

Enforcement

We monitor deliverability signals, bounce rates, and complaint rates across the fleet. Violations result in mailbox or workspace suspension, and serious or repeated violations end the account without refund. Our upstream mail infrastructure reserves the right to terminate service for abuse without notice, and we pass that risk through to the customer that caused it. If your use case might be near the line, write to hello@emailfleet.io before sending; we would rather answer a question than suspend a workspace.