Responsible Use Policy
Guidelines on acceptable lead recovery practices vs. forbidden surveillance.
Acceptable Use Cases
GetLostLeads is built to help businesses save lost opportunities due to friction. Permitted use cases include:
- Technical Recovery: Capturing lead data to reach back out to users who experienced browser crashes, network failures, or validation loops.
- Checkout Assist: Helping users who abandoned a checkout flow due to price, payment gateway errors, or timing friction.
- Friction Analytics: Identifying fields that cause high bounce rates (e.g. fields that take longest to fill or trigger validation errors).
- Explicit Consent Flows: Capturing inputs on forms where a clear disclaimer is present notifying users that input may be saved.
Prohibited Use Cases
We actively monitor and suspend accounts that use our platform for covert surveillance or invasive tracking. Prohibited behaviors include:
- Password / Credential Logging: Attempting to capture password fields, credit card CVVs, secret keys, or authentication tokens. (Our SDK blocks these fields client-side by default, but any bypass attempt is grounds for immediate termination).
- Search Bar Keylogging: Capturing keystrokes in search inputs or general text inputs to build profiles of user search intent.
- Covert Spying: Integrating the SDK on pages where visitors do not expect any form submission (e.g. general blog posts, reading layouts).
- Bypassing Consents: Disabling or ignoring consent signals when a visitor has explicitly opt-out of cookies or analytics tracking.
Compliance Monitoring
Our compliance team runs periodic audits on script configurations. If we detect high rates of sensitive field captures or tracking on non-form pages, the account will be placed on administrative hold immediately.