Acceptable Use Policy

This Acceptable Use Policy ("AUP") governs every message routed through zevsend. It applies to customers, their sub-accounts, and any third party they grant access to via API keys. Violations get the offending account suspended, not throttled. Keeping a clean platform is the only way deliverability stays high for everyone.

1. What zevsend is for

zevsend is a transactional messaging API. The messages you send must be triggered by an end-user's explicit action in your product (signup, login, purchase, support request, account change, security event, etc.), or by a system event you have a legitimate business need to relay to a specific user (delivery confirmation, fraud alert, expiry notice).

Examples of permitted messages:

• Account verification codes and magic links
• Password resets and security alerts
• Order receipts, invoices, shipping notifications
• Support replies and ticket updates
• Calendar reminders and operational notifications the recipient configured
• Two-factor authentication codes

2. What zevsend is not for

zevsend is not a marketing or bulk-mail platform. The following are prohibited:

• Marketing campaigns, newsletters, drip sequences, lead-nurture flows
• Promotional content of any kind to recipients who did not request it specifically
• Sending to addresses obtained from purchased, scraped, rented, or otherwise acquired lists
• Sending to addresses you cannot demonstrate the recipient explicitly provided to you for this purpose
• Cold outreach, prospecting, or "sales engagement"
• Content unrelated to the action that triggered the message (e.g. attaching a marketing footer to a password reset)

3. Content that is always prohibited

• Phishing, credential harvesting, fraudulent impersonation of any individual, brand, or institution
• Malware, ransomware, spyware, adware, or any malicious payload
• Content that violates third-party rights (copyright, trademark, right of publicity)
• Illegal goods or services in any applicable jurisdiction (controlled substances, weapons, counterfeit items, etc.)
• Child sexual abuse material, content that sexualises minors, or any material exploiting children
• Adult sexual content, nude imagery, or sexual solicitation
• Content promoting violence, terrorism, self-harm, or hate against a protected group
• Gambling content where prohibited by the recipient's jurisdiction
• Cryptocurrency, ICO, "wealth-creation," or get-rich-quick promotions
• Multi-level marketing, pyramid schemes, or affiliate-aggregator content
• Pharmaceutical advertising outside legitimate regulated channels
• Lending or debt-collection messages that violate applicable consumer-protection law

4. Sender obligations

You must:

• Verify your sending domain via the DKIM/SPF/DMARC records we provide before sending live traffic.
• Honor unsubscribes immediately. Every email we deliver carries a List-Unsubscribe header (mailto + one-click HTTPS, RFC 8058). You must process unsubscribe requests received via that header within 24 hours. Suppression of opted-out addresses is your responsibility as much as ours.
• Identify yourself accurately in From, Reply-To, and sender-name fields. No spoofing of unrelated brands or individuals. Your sending domain must be one you legitimately operate.
• Handle bounces and complaints. When we surface a bounce or complaint via webhook, suppress that recipient promptly on your side too. We auto-suppress in our suppression list; you should not re-send via a different key or alias to circumvent that.
• Maintain low complaint rates. We monitor complaint rate per customer team. Sustained complaint rates above 0.3% trigger automatic sandbox reversion and human review.
• Respect rate limits. Do not attempt to circumvent per-team rate limits via multiple accounts, key rotation, or proxy services.
• Comply with applicable law in every jurisdiction where you have recipients, including CAN-SPAM (US), GDPR (EU), PECR (UK), CASL (Canada), and any local equivalents.

5. Enforcement

We reserve the right to:

• Suspend or terminate an account that violates this AUP
• Revert a team to sandbox state pending investigation
• Refuse to deliver specific messages that appear to violate this AUP
• Cooperate with law-enforcement and abuse-handling networks
• Update this AUP as patterns evolve; material changes are emailed to active customers

We act on the totality of evidence, not single bounced messages. Honest mistakes get a heads-up; coordinated abuse gets terminated immediately.

6. Reporting abuse

If you received a message via zevsend that violates this AUP, report it to abuse@zevsend.com. Include the message headers (full source) if possible. They contain the message id we need to trace the source. We respond to abuse reports within one business day.

7. Updates

This AUP can change. The effective date at the top of the page reflects the current revision. Material changes are announced via email to active customers.