Keep master lists private
Approved senders scrub against assigned lists without receiving the underlying suppression records.
Suppression management for email and SMS
Manage email and SMS suppression lists. Give approved partners a controlled way to scrub their files, without handing over your master database.
Already have an account? Sign in
june-reactivation.csv
184,210 rows
sms-promo-wk24.csv
62,480 rows
partner-leads-0611.csv
9,118 rows
Clean file
suppressed rows removed
Give approved partners matching access, not a copy of your master suppression list.
Send with a better exclusion process
Approved senders scrub against assigned lists without receiving the underlying suppression records.
Apply your litigant and licensed blacklist data alongside opt-outs. Keep email and SMS risk lists separate and assign the right exclusions to each sending partner.
Receive deduplicated eligible contacts with approved original columns, plus job counts and the suppression-list versions used.
Risk-list matching depends on authorized data and a verified scrubbing connection. Your existing risk datasets must be loaded and mapped before use. Matching does not establish consent, check deliverability or guarantee legal protection. Discuss your exclusion lists.
Built for teams in
What it manages
Each list is either email or SMS. Records are cleaned the same way when you add them and when partners upload, so matches don't depend on formatting.
Jane.Doe@Example.com
→ jane.doe@example.com
Trimmed and lowercased. Malformed addresses are flagged as invalid.
SMS
+1 (415) 555-0134
→ +14155550134
Validated and normalized to E.164. National numbers require an explicit country; ambiguous values are rejected.
MD5
5d41402abc4b2a76…
→ matched as hash
Hashes are stored and compared as they are, on either channel.
How it works
01
Invite
You invite a partner by email, assign lists and set a monthly limit.
02
Upload
The partner uploads a CSV of emails or phone numbers.
03
Review allowance
Valid, duplicate and invalid counts are shown against what's left this month.
04
Scrub
Records are matched by MD5 against only the lists assigned to that partner.
05
Download
The partner gets their original rows back, with suppressed rows removed.
For companies managing suppression lists
| List | Channel | Entries | Updated |
|---|---|---|---|
| Global email opt-outs | 2,418,903 | Today | |
| SMS opt-outs | SMS | 311,580 | Today |
| Litigator & complaint list | 48,112 | Jun 3 | |
| Retail brand — unsubscribes | 906,247 | May 29 |
For partners sending campaigns
Sample email network
750K / month
Sample lead partner
250K / month
Sample SMS network
100K / month
Try the review screen
Choose a sample file and adjust how much of the month is already used. The decision follows the same rule the product applies when a job is submitted.
spring-winback.csv
Drag to see how the decision changes as the month's allowance is used.
Processing decision
Ready to scrub
This job reserves 48,200 rows. 41,800 remain available. Usage counts once on success.
Every nonblank data row, excluding the CSV header, counts when an accepted job completes successfully. Duplicate and invalid rows count. Analysis uses no allowance. Email and SMS share one company allowance.
Privacy by design
Matching happens on our servers. A partner can only open their own uploads and clean files. Access rules are enforced in the database, not just hidden in the interface.
A partner can see
A partner can't see
Partner usage by month
Sample dataLimit: 250,000 records / month · April reached the limit
Monthly limits
FAQ
A walkthrough with sample data: lists, a partner invitation, an upload, and a clean download.