How we protect shared sending reputation
Your numbers stay yours alone, but the infrastructure underneath is shared. Here's what that means.
On EmailFig’s platform plans your email goes out through infrastructure shared with every other customer. Your numbers aren’t shared: your deliveries, bounces, complaints, opens and clicks belong to your account alone and are never pooled with anyone else’s. What is shared is the infrastructure a receiving mailbox provider actually judges, and that’s why we check every campaign before it sends.
What’s shared and what’s yours
| Shared across customers | Yours alone | |
|---|---|---|
| Sending infrastructure the receiving provider sees | ✓ | |
| Your isolated sending identity | ✓ | |
| Bounce, complaint and delivery counts | ✓ | |
| Your Sending health dashboard card | ✓ | |
| Sending domain, DKIM and DMARC records | ✓ | |
| Suppression of hard bounces and spam complaints | ✓ |
Every message you send is tied only to your account, so if a problem starts, we can act on that one account rather than everybody. What the split can’t do is separate the part that matters most to Gmail, Outlook and Yahoo: they judge the infrastructure the message came from, and one sender blasting a scraped list drags down inbox placement for everyone alongside them. Closing that gap is why these checks exist.
The checks, and what each one is for
- Import quality. We check lists as they’re imported, so a purchased or scraped list can be stopped before its first email. See This list doesn’t meet our import quality bar.
- Link safety. We check every link in a campaign against a maintained blocklist of known-bad destinations before it sends.
- Automated content check. Runs on every campaign and every automation. Most clear it invisibly.
- A person, for some sends. Now and then a campaign gets a human read before it goes out. See My campaign is “in review”.
- Platform-wide suppression. An address that hard-bounced or filed a spam complaint anywhere on EmailFig is suppressed for everyone, and re-importing it won’t bring it back. See Suppressions: why an address can’t be re-added.
Keeping an eye on your own side
The Sending health card shows your hard bounce rate and complaint rate over a rolling 30 days, each against its budget, and reads Healthy, Needs attention or Sending paused. Treat Needs attention as a prompt to look at where those addresses came from. See Your deliverability health badge.
If you’d rather not share anything
EmailFig’s other plan family, BYOS, sends entirely through your own Amazon SES account: your AWS bill, your quota, your reputation, kept apart from every other customer. The acceptable use policy still applies and we still check campaigns, but the infrastructure isn’t shared. You make this choice once, at signup, and can’t change it later. Read Platform sending or your own Amazon SES: which to choose before you decide.