Privacy
Privacy Policy
How RevLeak OS handles business, lead, payment, and workflow data during managed pilots and staged rollout.
Last updated: June 8, 2026
Data we expect to process
Business account details, business contact information, quote records, lead contact fields, service requested, quote value, notes, recovery statuses, payment event metadata, and audit/report activity.
Payment card data is not stored by RevLeak OS. Checkout and card entry stay hosted by the configured payment provider, such as PayPal, Stripe, Square, or another approved processor.
How data is used
To generate recovery drafts, organize human approval queues, classify replies, prepare proof reports, create onboarding records, and show operators what work is ready or blocked.
AI drafting is kept behind a feature flag. Live customer data should not be sent to an AI provider until provider terms, data handling, and customer consent are approved.
Security posture
RevLeak is operating in paid-pilot mode while the self-serve customer portal is hardened. Customer data access is limited to approved workspaces and human-reviewed recovery workflows.
Access to inboxes, calendars, or payment accounts must use OAuth or provider-hosted flows. RevLeak OS should not ask customers for email or card passwords.
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.