LEADFAILSAFE · PRELAUNCH
Privacy policy
Last updated October 22, 2026
Terms · Privacy · Security · Acceptable use · Cookies
Contact and scope
This policy covers LeadFailsafe’s website, inquiries and invited monitoring accounts. The operator can be reached at support@leadfailsafe.com for privacy questions or requests. It does not replace the privacy policies of the websites you choose to monitor.
Information we process
We process inquiry names, email addresses and messages; account emails, workspace membership and settings; approved website URLs, workflow definitions and synthetic field values; execution results, screenshots, resource timings and incident history; alert destinations and delivery records. Login and abuse-prevention records can include hashed identifiers and hosting request metadata. Public pages and evidence can contain personal information even when the test values are synthetic.
Purposes
We use this information to respond to inquiries, authenticate accounts, run authorized checks, match configured receipts, send requested alerts and reports, provide support, prevent abuse and operate the service. An inquiry is not consent to unrelated marketing. We do not sell personal information or use connected mailbox information for advertising or general-purpose AI training.
Google connections and Limited Use
A mailbox connection is optional and separately authorized. Receipt verification uses the granted read permission to locate synthetic test messages and inspect matching receipt data; it does not require you to manually watch the test inbox. A separate sending permission may be used for authorized backup service notices. Access scope can technically cover more messages than those our matching logic selects. We do not use this grant to delete or modify mailbox messages. LeadFailsafe’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You may revoke access in your Google Account. Human access to Google data is restricted to specific user-consented support, security investigations, legal obligations or other exceptions permitted by that policy.
Service providers and sharing
Our current service uses Render for hosting/database, Amazon Web Services SES for email, Google Workspace/Gmail for support and authorized receipt or backup-email connections, and Cloudflare for domain/web delivery services. Private source code and build automation use GitHub. Payment handling would use Stripe if activated. Alert integrations share incident names and dashboard links with destinations you configure, including Slack, compatible Teams, PagerDuty. Those providers process relevant data under their own terms. We may disclose information when required by law or to protect security. We do not include submitted form values or credentials in incident integration payloads.
Retention
Automated cleanup removes run screenshots, filmstrips and captured field/trace evidence after approximately 14 days and receipt-event records after 14 days. Ordinary run metrics, reports, integration delivery records and audit metadata are generally kept for 90 days; run records linked to incidents may persist longer. Completed application email queue records are generally removed after 30 days. Received withdrawal and cancellation notices and their durable acknowledgment/outcome copies are retained separately for required contract, statutory-rights and dispute handling; expired unsubmitted drafts are cleaned up. Account configuration, inquiry records, incident history, unresolved delivery records and suppression records can remain while needed for service, support or abuse prevention. Provider mailboxes, logs and backups have their own retention and may outlive deletion from the active application. We do not promise automatic erasure of every record after 90 days.
Choices and requests
Contact support@leadfailsafe.com to request access, correction, export or deletion, or to close your account. We may verify identity and authority before acting. Some records may be retained for legal obligations, unresolved disputes or security; we will explain applicable limitations. Stop monitoring before removing a receipt connection. Revoking an integration does not retract previously delivered messages.
Cookies and international processing
We use essential login/session, contact-form, cancellation-form and withdrawal-form security cookies. We have not installed advertising cookies or a visitor analytics/RUM script. Monitoring browsers may encounter cookies on the target website in an isolated test context. Service providers may process data in the United States or other countries; we do not claim regional data-residency guarantees. Any legally required processing agreement or transfer terms must be arranged before onboarding data that requires them.
Children and updates
The service is intended for business use by adults, not for children. Do not knowingly send children’s personal data or regulated sensitive data without a separate agreed arrangement. Material changes will be dated on this page and communicated to active accounts when appropriate.
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.