Opt-out
Opt-Out and Do-Not-Contact Policy
How RevLeak OS handles unsubscribe, no, stop, complaint, and do-not-contact signals during managed pilots.
Last updated: June 17, 2026
Core rule
If a recipient replies no, unsubscribe, stop, not interested, or asks not to be contacted, future recovery messages to that recipient must stop.
The recovery engine models stop rules for replies, bookings, not-interested, complaints, and do-not-contact outcomes. During managed pilots, operators record and honor those signals manually.
Managed-pilot handling
Opt-out, complaint, and do-not-contact requests can be sent through the customer portal request center or support inbox.
Operators verify the workspace, contact, channel, and request source before any future manual follow-up list is used.
RevLeak OS does not use no-reply account/system email for recovery outreach, sales outreach, campaign resend, or customer follow-up.
Email requirements
Commercial email must use accurate sender information, non-deceptive subject lines, a physical mailing address, and a clear way to opt out.
Opt-out handling must be easy for ordinary recipients to understand and must not require unnecessary personal information.
SMS boundary
SMS is disabled until consent tracking, carrier registration where required, STOP handling, suppression-list testing, and launch approval are complete.
Live provider sending remains blocked until opt-out, do-not-contact, reply-stop, bounce, complaint, and suppression handling are proven end to end.
Paid-pilot note
RevLeak OS currently operates managed paid-pilot workflows. These pages describe product guardrails and should be reviewed by qualified counsel before broader self-serve launch.