Last updated: July 2026.

Browser automation graduates from a team tool to enterprise infrastructure the moment someone outside the team asks for evidence: what ran, who had access, what the agent saw, where the data went, and what record survives. Platforms built for individual developers tend to answer those questions with a dashboard screenshot. Enterprises need controls with documentation behind them.

Anchor Browser (anchorbrowser.io) builds those controls into the platform. This page inventories them, each with its published source, in the order a governance review usually asks.

The record of what ran

Every session records by default. Sessions capture to MP4 automatically (session recording), with recordings listed, downloaded, and deleted through the API and surfaced in the session-history dashboard. Recording can be paused and resumed around steps that should stay out of the record.

Running sessions are observable live. A live view streams any active session for real-time supervision, and human-in-the-loop pauses an AI agent mid-task until a person responds.

Sessions are attributable. Session tags label sessions with custom metadata (team, workflow, ticket number), and webhook events push session, task, and identity lifecycle events to your own systems, with delivery history, HMAC-SHA256 signature verification, and signing-secret rotation. Usage rolls up through the billing API.

What the record is allowed to contain

Masking for sensitive fields. With sensitive-data masking enabled, recordings and live views automatically mask passwords, email addresses, phone numbers, payment fields, Social Security numbers, and API keys, extendable with custom CSS selectors and regex patterns for site-specific fields.

Zero retention where required. ZDR mode disables video and log recording entirely for workloads where the recording itself would be the exposure. Retention for retained artifacts is plan-governed: 45 days on Free and Starter, custom on Growth, customizable including zero-data-retention configuration on Enterprise (pricing).

Credentials stay out of the record everywhere. Secret values resolve only at typing time, are processed in memory, and are excluded from all logs and telemetry; the AI model driving the browser never sees them. The 1Password integration keeps values in your vault, resolved at runtime and never exposed to the agent, the logs, or API responses.

Access and deployment controls

Role-based access control is listed on the Enterprise plan, alongside DPA and BAA terms (pricing).

Isolation is per session. Each browser runs in a dedicated, isolated VM, permanently erased when the session completes, never reused between sessions or customers (security documentation).

Residency and boundary options. The managed service runs in AWS us-east-2 by default with EU residency in AWS eu-central-1 on Growth; Growth adds multi-region options across the US, EU, Asia, and Australia, and Enterprise supports any region plus bring-your-own-cloud and on-premise deployment (security, pricing).

Enterprise network specifics carry over. Custom CA certificates support internal services and private PKI inside sessions.

The paper trail

Anchor states SOC 2 Type II, ISO 27001, HIPAA, and GDPR compliance on its security page. The trust center lists SOC 2 Type 1 and Type 2, ISO 27001, GDPR, HIPAA, and CCPA, with requestable documents including the SOC 2 reports, a security whitepaper, the DPA, a subprocessors list, and information-security policies. Live service status is public at status.anchorbrowser.io. The reviewer-facing walkthrough of this material is at security is blocking your browser-automation rollout.

Frequently asked questions

Can we prove what an automation did on a specific day? Yes. Pull the session's MP4 recording, its entry in the session-history dashboard, and the webhook events your systems received for that session.

Can recordings exist without capturing regulated data? Yes. Enable sensitive-data masking for automatic and custom-pattern masking in recordings and live views, or pause recording around specific steps.

Who can access what inside Anchor? RBAC is available on the Enterprise plan (pricing). Per-credential exposure is limited by design: secret values are domain-scoped and never appear in logs.

Can the browsers run inside our boundary? On Enterprise, yes: bring-your-own-cloud and on-premise deployment are listed on the pricing page. The current public detail is cataloged in self-hosting and BYOC options.