Privacy Policy
Last updated: November 6, 2026
This Policy explains how FailSafe handles personal information collected through getfailsafe.com, its public forms, and its product demonstration. It does not replace a signed service agreement, a product-specific privacy notice, or the privacy terms of a third-party service. Assessment data shared for a paid engagement is handled under the applicable written agreement.
1. Information we collect
The information collected depends on the feature you use. It may include:
- Contact and inquiry details, such as name, work email, company, phone or Telegram handle, service interest, website or GitHub URL, and message.
- Assessment request details, such as the target website URL, requested test type, and notes you choose to submit. Do not include credentials, source code, private keys, personal data, or restricted target details.
- Grant and report-request details, such as project name, company, role, ecosystem, funding stage, project links, and the information you provide in an application or download form.
- Demo access details, including your work email, verification status, and selected settings in the guided demonstration. If you complete the demo, its configuration choices may be included in a notification to FailSafe.
- Technical and request information processed by the website and its providers, which may include IP address, browser and device attributes, request timestamps, and security or rate-limit events.
- Website analytics, including canonical page paths and a limited set of events such as page views, navigation, CTA interactions, and confirmed form completions.
2. How information is used
We use information to:
- Respond to inquiries and administer requests, applications, downloads, and demo access.
- Review authorized assessment requests and contact you about the request or demo interest you submitted.
- Operate, secure, maintain, and improve the website, forms, and demonstration, including detecting abuse and enforcing rate limits.
- Understand site performance and engagement through analytics.
- Meet legal obligations, resolve disputes, and protect FailSafe, users, and other parties.
Our custom analytics events use a fixed set of event names and approved categories. They exclude form message text, submitted email addresses, target URLs and arbitrary page query strings. Landing-page measurement may retain validated Google advertising click identifiers (gclid, gbraid and wbraid) to connect an ad visit with later activity. Google Analytics may separately process standard technical information when its script is requested or used.
3. Email and service providers
When you submit a form, its information is sent to FailSafe and may be delivered to our shared business inbox or to you by Resend, our configured email delivery provider. Demo access codes are sent to the address you provide. A verified demo request and, if you finish the demo, selected run settings may be sent to FailSafe so our team can respond to your request.
The production website uses Google Analytics 4 for site measurement and Google Ads to measure advertising and offer interest. Google may process advertising identifiers and ad-click information under its own settings and policies. Our code honors the Global Privacy Control signal by disabling these Google Analytics and Google Ads destinations when that signal is detected. The Google tag script may still be requested by the browser. Theme preference is stored in browser local storage. The interactive demo uses a secure, HTTP-only access cookie that expires after seven days.
We also rely on website hosting, infrastructure, and security providers to deliver the site and protect it from abuse. These providers may process limited request or device information for those purposes. Pricing links may take you to the SWARM portal and a Stripe checkout. The marketing website does not collect payment card numbers; the portal and payment provider handle payment data under their own notices and terms.
Where analytics is permitted and browser identifiers are available, measurement cookies may connect a visit to getfailsafe.com with activity on app.getfailsafe.com. A verified paid order may be reported to Google Analytics with its amount, currency, product category, a hashed transaction identifier, and browser or session identifiers. These purchase events exclude customer names, email addresses, payment card details and assessment targets. A qualifying attributed purchase may also be measured in Google Ads. Analytics does not establish whether credits were granted; billing records are maintained separately.
Missing or blocked analytics identifiers can prevent purchase measurement. We do not replace missing browser identifiers with customer email addresses or account identifiers. Our analytics settings honor Global Privacy Control; blocking analytics does not prevent payment or credit fulfilment.
4. When information is disclosed
We disclose information to service providers that help us operate the website, deliver email, provide analytics, and protect the service. We may also disclose information to our personnel who need it to respond to your request; when required by law or valid legal process; to investigate security incidents or protect rights and safety; or as part of a business reorganization, subject to appropriate safeguards. We do not authorize service providers to use form contents for their own unrelated marketing.
5. Sensitive security information
Public forms and the product demo are not approved channels for secrets or sensitive assessment data. Do not submit passwords, API keys, private keys, source code, personal data, exploit payloads, or detailed production architecture. If you are planning an assessment, first agree the scope and approved transfer method with FailSafe. Service-specific access, retention, and data handling are set in writing before assessment data is provided.
Customer assessment data is not used for model training or fine-tuning by default. Any such use requires explicit customer permission in a separate written agreement.
6. International processing and retention
FailSafe operates from San Francisco and Singapore, and our service providers may process information in other countries. Where required, we use appropriate safeguards for international transfers. We retain personal information for as long as reasonably needed for the purpose it was collected, to operate and secure the service, to meet legal obligations, and to establish or defend claims. Retention can differ between a form submission, provider logs, and a contractual service record.
7. Your choices and privacy rights
You can ask us to access or correct personal information you provided, or withdraw consent where consent is the basis for processing, subject to applicable law and legitimate recordkeeping requirements. If applicable privacy law gives you additional rights, such as deletion, portability, or an opt-out, you may submit a request using the contact details below. We may need to verify your identity and clarify the request before acting.
Where California privacy law applies, rights may include knowing, correcting, or deleting personal information, opting out of sale or sharing, and limiting certain uses of sensitive personal information. We do not use website form submissions for targeted advertising. You may send a privacy request to our contact address below. We will handle it under the law that applies to your request.
To exercise a privacy choice or submit a request, email [email protected] with “Privacy Request” in the subject. You may also change cookie settings in your browser. Blocking cookies may affect demo access or site preferences.
8. Security
We use administrative, technical, and organizational measures intended to protect information under our control. No website, email, or transmission method can be guaranteed secure. Do not send restricted security information through public forms or ordinary email. If you believe information submitted to the website is at risk, contact us promptly at the address below without including secrets in your message.
9. Children
The website and services are intended for organizations and business users, not children. We do not knowingly seek personal information from children. Contact us if you believe a child has submitted information so we can review and address the request.
10. Changes to this Policy
We may update this Policy as our website, data handling, or legal obligations change. The date at the top shows when the current version was last updated. Material changes will be reflected on this page.
11. Contact
For privacy questions or requests, email [email protected] with “Privacy Request” in the subject. Please do not include credentials, private keys, exploit details, or other sensitive security information.