Sending Policy
What you may send through Sendwax, the permission we expect you to have, and the limits we enforce automatically.
Why this exists. Every account on Sendwax sends through shared infrastructure. A single sender mailing a purchased list does not just hurt themselves — it moves the reputation that decides whether everyone else's receipts and password resets reach the inbox. This policy is the line, and section 4 describes the limits we enforce in code rather than by asking nicely.
1. Permission
You may only send to people who gave you permission to email them, and you must be able to show where and when they gave it.
Permission means
- They entered their address on your site, in your product, or on paper, knowing they would hear from you.
- They bought from you, signed up, or opened an account — for mail about that relationship.
- They asked you to contact them.
Permission does not mean
- A list you bought, rented, swapped, scraped, or had appended.
- Addresses guessed or generated from a pattern (
info@,sales@, first.last@). - An address collected for one purpose and used for another — a checkout is not a newsletter opt-in.
- Someone who unsubscribed, however long ago.
- A conference badge scan, unless they were told they were joining your list.
Consent goes stale. If an address has not heard from you in two years, treat it as cold and re-confirm before mailing it in bulk.
2. What you may not send
- Unsolicited bulk email of any kind.
- Deceptive mail — forged headers, a misleading From identity, or a subject line that misrepresents the content.
- Phishing and credential harvesting, or anything impersonating another person or company.
- Malware, or links leading to it.
- Content that is unlawful where it is received, or that infringes someone's rights.
- Mail on behalf of a third party that hides who is actually sending.
- Anything routed through Sendwax to evade a suspension elsewhere.
We also do not accept the categories that generate complaints faster than any list hygiene can absorb: pharmaceuticals, "work from home" and get-rich-quick offers, adult content, gambling where it is not licensed, cryptocurrency promotion, debt relief, and lead-generation lists sold on to third parties.
3. What every account must do
| Authenticate | Verify your sending domain (SPF and DKIM) before sending from it. We will not send from an unverified domain. |
| Register senders | A From address must be added and approved. Owning a domain is not authority to send as every mailbox on it. |
| Honor unsubscribes | Marketing mail carries a working unsubscribe, including one-click. Suppressions are enforced at send time by us — do not route around them. |
| Physical address | Marketing mail must carry a real postal address. Set it under Account → Workspace. A mailbox service is fine. |
| Keep lists clean | Remove hard bounces and complainers. We suppress them automatically; re-adding them is a breach of this policy. |
| Warm up | A new domain sending a large volume on day one will be filtered. Build up over a couple of weeks. |
Transactional mail — receipts, password resets, alerts someone asked for — does not need an unsubscribe link and is not stopped by a marketing opt-out. It is still subject to everything else here.
4. The limits we enforce
These are not guidelines. They are thresholds in the code, evaluated on a rolling 24-hour window, and crossing one pauses sending on the account automatically.
| Measure | Sending pauses at | Applies once |
|---|---|---|
| Hard bounce rate | 3% of messages sent | 200 messages sent in the window |
| Complaints | 3 complaints | 100 messages sent in the window |
| API requests | 300 per minute, per API key | always |
| Monthly volume | your plan's allowance | always |
The bounce and complaint thresholds sit deliberately below the ones our upstream provider reviews accounts at, so a problem is stopped while it is still ours to fix rather than after it has become everyone's. The minimum volumes exist so that two bounces on a ten-message test do not trip anything.
5. What happens when a line is crossed
In most cases the breaker pauses your sending before a person looks at it. When that happens you will see the reason in your dashboard, queued mail is held rather than dropped, and the API returns a clear error instead of silently accepting messages.
- Automatic pause. Clean up the list or fix the source of the bounces, then contact us to lift it.
- Rate reduction. We may lower your limits while a problem is investigated.
- Suspension. For deliberate abuse, or a pause you keep working around.
- Termination. For the conduct in section 2, without notice where mail is actively causing harm.
We would rather help you fix a list than close your account. Tell us early; a bounce problem explained in advance is a conversation, the same problem discovered by our provider is not.
6. Reporting a sender
If you received mail sent through Sendwax that breaks this policy, send it to abuse@sendwax.com with the full message headers — the headers are what let us identify the account. We investigate every report.
To stop hearing from a particular sender, use the unsubscribe link in their message; that takes effect immediately and we enforce it at send time.
7. Changes
We will update this policy as sending norms and our own provider's rules change, and revise the effective date above. Material changes are announced by email before they take effect. This policy forms part of the Terms of Service; where they cover the same ground, the Terms govern.
8. Contact
Questions about whether something is allowed — ask us before you send it: support@sendwax.com, or via the contact page.
Sendwax · State of Florida, United States