Opt-out
Opt-Out and Do-Not-Contact Policy
How RevLeak OS should handle unsubscribe, no, and do-not-contact signals before live outreach.
Last updated: June 8, 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 already models stop rules for replies, bookings, not-interested, and do-not-contact outcomes. Live sending stays blocked until those rules are enforced with a real provider.
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, and launch approval are complete.
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.