Privacy policy for the site, trials, and metadata-first governance records.

Last updated May 14, 2026. This page summarizes what Faultline collects, what it does not collect by default, and how to contact the team about privacy or procurement review.

Data collection

What Faultline may collect.

Public website and intake

Analytics events from public site visits, including pages viewed and CTA interactions
Information submitted through email intake or booking flows, such as company, role, repository count, and stated pain points
Email correspondence sent to hello@gofaultline.dev or security@gofaultline.dev

Product and trial records

Account, organization, role, and authentication metadata
Source-free scanner snapshots containing repository facts, package signals, findings, ownership, policy, and suppression metadata
Audit events, evidence export metadata, digest recipients, and integration delivery status

Data boundary

What Faultline does not require by default.

Not collected by default

Source code
Full ASTs or compiled artifacts
Production runtime traces
Customer application secrets
Developer workstation contents
Private incident notes unless explicitly supplied by the customer

Subprocessors

Operational services used by Faultline.

Faultline may use infrastructure, analytics, billing, scheduling, source hosting, and email services including AWS, Google Analytics, Stripe, Calendly, GitHub, and AWS SES. Enterprise agreements can review subprocessors, retention, and deployment model during procurement.

Contact

Privacy and data requests.

Send privacy, deletion, access, or procurement questions to hello@gofaultline.dev. Security-specific questions can be sent to security@gofaultline.dev.