Built so the person who signs off can say yes.

Kill switches, retention controls, and audit exports are product features, not warning labels. This page is written for the people who sign off: your security lead, your data protection officer, your CFO.

The summary your security lead asks for first

Tenancy

Workspace isolation

Your signals, scores, and Plays live in your workspace.

Access

Least privilege, on the record

Access to customer workspaces is least-privilege and itself audit-logged, under the access and security provisions of the DPA.

Bounded writes

Writes only where a Play names

No unbounded API calls, no channels outside the Play definition. The action model is the security model.

Scope boundaries, stated plainly

Scope

Bryn watches where you point

The beacon, telemetry, and CRM scopes are explicit configuration. Nothing outside the configured scope is collected, and the scope itself is visible in the product.

No phone home

Your signal, no one else's model

What Bryn learns from your workspace stays in your workspace: it learns from your own audit log alone.

Jurisdiction

Built for the US.

Bryn is built for the US. Companies and people on US traffic are identified, scored and acted on in full. Visitors from other countries are handled at the company level only, with no person-level outreach. Identification can be suspended by region, segment, or Play in one click. The audit log captures the suspend. Bryn waits. You decide when.

Erase

Account trails, erased on demand

The erase runs on demand, and the erase itself is logged as an erase. An auditable gap is better than a silent one.

The questions that come up at sign-off

How does Bryn know who's visiting?

Bryn matches a visit to a company and, when possible, a person, using what happened on your site and licensed business data. It shows you what it matched and what it used to decide.

What does Bryn keep, and can I take it out?

Every visit it matched, every score, decision and run, time-stamped. Export it as CSV or JSON at any time. Erase on demand, and the erase itself is logged.

Does Bryn act without my approval?

Bryn acts only inside Plays you approved, rules you set once. For sensitive ones, Approve mode holds each run for one click. The kill switch stops everything, and the stop is logged.

The record is the product. Retention is under your control

Every signal, score, decision, and run is time-stamped, source-traced, and replayable. Export the log as CSV or JSON at any time. Erase on demand. Retention windows are configurable per workspace.