LEADFAILSAFE · PRELAUNCH
Cookie policy
Last updated October 22, 2026
Terms · Privacy · Security · Acceptable use · Cookies
Essential cookies
LeadFailsafe uses a session cookie to keep invited users signed in and security cookies/tokens to protect public forms. The withdrawal form uses __Host-lg_withdrawal over HTTPS (lg_withdrawal in local HTTP development), an HTTP-only, Secure-in-production, SameSite=Lax cookie lasting one hour. The cancellation form uses __Host-lg_cancel over HTTPS (lg_cancel locally) with the same protections and one-hour lifetime. Public receipt access through this cancellation cookie is also limited to one hour by the server. These cookies protect the confirmation flows; submitted notices remain recorded after the cookie expires. These are needed for requested functionality and abuse prevention. Session expiration is enforced by the application.
No advertising or visitor tracking
We have not installed third-party advertising cookies or a visitor analytics/RUM tracking script. External links lead to providers with their own cookie policies. Website monitoring runs in isolated browser contexts and does not reuse your personal browser session.
Your browser settings
You can delete or block cookies in your browser. Doing so can sign you out or prevent form submission. For questions, contact support@leadfailsafe.com.
Cancel contract — submit a cancellation notice while signed out.
Withdraw from contract — submit a notice independently of the voluntary refund guarantee.
Google connections follow the Google API Services User Data Policy, including Limited Use.