Privacy built around controlled security operations.

When you visit the public website, we may collect basic technical information such as browser type, device information, pages viewed, referring pages, approximate region, and cookie preferences.

When you start onboarding, we may collect business contact details, organization name, identity-provider information, and operational metadata needed to create or administer a workspace.

1000 Beacons is built around a zero-data-by-default posture. The marketing website does not collect customer security telemetry.

Customer telemetry, connector credentials, evidence trails, incidents, and response workflows belong in the controlled console and customer deployment path. The product architecture is designed so sensitive telemetry can remain in infrastructure the customer controls.

We use website and onboarding information to respond to inquiries, support pilot discussions, operate the public site, improve conversion paths, and prepare enterprise setup conversations.

We use workspace administration information to establish ownership boundaries, support account access, configure connectors, and preserve accountability around security-sensitive changes.

The public site and console may use hosting, analytics, email, identity, and infrastructure providers to operate the service. Optional analytics and marketing tools are controlled through the cookie preferences interface where applicable.

Enterprise deployments may use customer-selected cloud, identity, SIEM, endpoint, and data infrastructure. Those systems remain governed by the customer environment and the agreements that apply to that deployment.

Website and inquiry records are retained only as long as needed for sales, support, security, compliance, and operational continuity.

Console and deployment records follow the retention model configured for the customer workspace, including audit, incident, telemetry, and connector records where enabled.

You can reject optional cookies, reopen cookie preferences from the website footer, or contact us to ask about access, deletion, correction, or export of personal information associated with the public website or onboarding process.

For workspace records controlled by an enterprise customer, requests may need to go through that customer's administrator.

For privacy questions, pilot data handling reviews, or security architecture discussions, contact [email protected].