The rules the pipeline enforces.
These are not aspirations. Each rule below is a check in the send pipeline; a message that fails one does not go out. Accounts that try to route around them get closed, not warned twice.
Evidence or no send
Every message must carry one specific, timestamped finding about the recipient’s own product, produced by the customer’s own system during that day’s run. If a run produces nothing worth saying, the pipeline sends nothing. There is no fallback template.
Enforced at build timeDaily caps hold
A hard daily cap per account, set by plan: 25 on Starter, 50 on Operator, 200 on Pro. Sends are spread across a sending window with minimum five-minute spacing and an irregular gap between them, so no account fires a burst. The cap cannot be raised by request or by splitting across accounts, and no plan sends thousands: the largest account on this system sends 200 proofs on its busiest day, not 10,000.
Enforced at send timeOne contact per recipient
Each recipient address receives exactly one proof email per matched launch, ever. No sequences, no follow-ups, no “bumping this to the top of your inbox”. If the first email did not start a conversation, a second one will not.
Enforced at match timeUnsubscribes are honoured immediately
Every email carries a one-click unsubscribe. No login, no survey, no confirmation email. Suppression applies to the sending account instantly and is permanent. A “STOP” request by mail suppresses the address across the whole platform within the hour.
Enforced at send timeSpam complaints suppress globally
A spam complaint from any mailbox provider suppresses that address for every account on the platform, not just the sender who triggered it. Complaint rates are watched by hand, not by a trigger. An account sitting above 0.1%, which is the threshold the big mailbox providers use, gets paused while we look at it, and an account that gets there twice is closed.
Enforced platform-wideBounces have two different fates
A permanent bounce (5xx) kills the address on the first response, for all accounts, forever. A temporary failure (4xx, full mailbox, greylisting) retries on a fixed schedule of 1 hour, 6 hours, 24 hours, and then parks the address for 30 days. Temporary failures never kill an address, and never retry forever.
Enforced at deliveryRecipients come from public launches only
Addresses are collected from products that launched publicly that morning (directories, Show HN, Product Hunt) and matched against what the customer sells. No uploaded lists, no purchased data, no scraping of unrelated sites. The source of every address is logged and shown to the customer.
Enforced at sweep timeThis page describes technical enforcement. The legal version of these obligations lives in the terms; how recipient data is handled lives in the privacy policy. Questions: support@mail.proofdrop.net.