Menu
ProductReplay & DevToolsSignalsCall qualityWhy (AI)Live AssistCanvas recordingPrivacy & complianceSelf-hosted
SolutionsHealthcare & virtual careEngineeringSupportProduct teamsKiosks & monitoring
MorePricingDocsCompareTrust centerChangelogGlossaryAboutContactPress kit
Start free Talk to sales Log in

Everything a review needs.

The page your compliance officer will link.

How data is protected, where it lives, who processes it, and how to get the paperwork, in one place.

Controls, stated plainly.

  • Encryption

    TLS 1.2 or newer in transit. AES-256-GCM at rest with a data key per end user wrapped by a per-tenant KMS key. Erasure destroys the key.

  • Masking

    You choose what is hidden: text, inputs, and images, on the device before upload. Passwords, card details, and one-time codes stay hidden either way. A server-side scanner quarantines suspected leaks.

  • Access control

    Single sign-on (SAML and OIDC), a passkey or authenticator app, and roles from owner to read-only. On Business and Enterprise, owners and admins can limit sign-in to chosen networks, and can name accounts that may still sign in if that list locks people out.

  • Audit

    Immutable audit log of every replay view, export, unmask, live-assist action, AI query, and admin change, retained six years.

  • Residency

    Customer data is stored in the United States.

  • Isolation

    Row-level security and per-tenant keys by default, and a PHI enclave for Enterprise.

  • Resilience

    Multi-AZ managed data stores and nightly backups with continuous log archiving, kept inside the residency boundary.

  • Secure development

    Tagged releases are signed and ship a software bill of materials; images are scanned for known vulnerabilities and pull requests for secrets and risky dependencies; memory-bounded load tests and chaos tests run in CI; privacy review on every collector change.

Stored in the United States.

Customer data stays in the United States.

Who else touches data, and why.

Subprocessor list
SubprocessorPurposeLocationDataBAA
Amazon Web ServicesCloud infrastructure: compute, object storage, databases, KMS, email deliveryUnited StatesAll customer data, encrypted at rest with per-tenant keysYes
ClickHouse, Inc.Managed analytics database for flattened event dataUnited StatesEvent metadata (no replay pixels, no masked text)Yes (dedicated tier)
AI inference provider (non-PHI tenants)AI analysis for tenants that do not process PHIUnited StatesMasked session dataNot used for PHI tenants
AI inference provider (PHI tenants)AI analysis for PHI tenantsUnited StatesMasked session dataYes
Grafana LabsPlatform observability (metrics, logs, traces of our own services)United States / EUOperational telemetry only; never payloadsNot required
StripeBilling and paymentsUnited StatesBilling contact and payment detailsNot required
GitHubSource control integration, when connected by the customerUnited StatesRepository metadata, PR draftsNot required

Named AI inference providers, with their regions and BAA status, are listed in the DPA and available under NDA. Customers receive 30 days' notice by email to their organization owners before a new subprocessor is added.

Request the paperwork.

A DPA, a BAA, or a security review. Tell us who you are and what you need.

A human replies within one business day with the documents or a scheduled review.

Security disclosures: hello@backstory.io. We acknowledge within two business days and do not pursue researchers acting in good faith.

Fields marked * are required.

Free for 1,000 stored sessions a month, with unlimited seats. Create a workspace and add one script tag.

Start