BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)

---

# Browser agent security for enterprise: isolation, secrets, zero retention

> Browser Use Cloud is SOC 2 Type II compliant. Every run gets its own isolated browser. The server types credentials on hosts you allow, so the task only carries an alias. Recording is off by default, Zero Data Retention projects never record, and agents can run in Frankfurt. Every claim below links to the page or doc that states it.

[HTML page](https://browser-use.com/security) · [SOC 2](https://browser-use.com/security/soc2) · [DPA](https://browser-use.com/dpa) · [Enterprise](https://browser-use.com/enterprise.md) · [Secrets docs](https://docs.browser-use.com/cloud/guides/secrets.md) · [EU deployment docs](https://docs.browser-use.com/cloud/eu-deployment.md)

## What Browser Use Cloud does, with the source

- **Audit.** SOC 2 Type II, audited by Accorp Partners for July 17 to October 17, 2025. Report on request from support@browser-use.com. [SOC 2](https://browser-use.com/security/soc2)
- **Encryption.** TLS 1.2 or higher in transit, AES-256 at rest. Infrastructure vulnerability assessment and penetration testing. [DPA, Schedule C](https://browser-use.com/dpa)
- **One browser per run.** Every run gets its own isolated session: a browser, a proxy exit and a model context. [Web agents](https://browser-use.com/web-agents) V4 agent browsers have a four-hour hard timeout; stop yours with `PATCH /api/v4/browsers/{id}` and `{"action":"stop"}` when done. [Browser lifetime](https://docs.browser-use.com/cloud/guides/concurrency.md)
- **Credentials.** V4 `secretBindings` give each credential an `alias` and the `allowedDomains` where it may be typed. The server types it into the focused field, and only while that field is on an allowed host (the check is against the field's frame, so embedded payment frames need their own host). The value is encrypted at rest, kept out of the worker payload, and ends with the run. Once typed it is on the page like any input. [Secrets](https://docs.browser-use.com/cloud/guides/secrets.md) · [Create run](https://docs.browser-use.com/cloud/api-v4/runs/create-run.md)
- **Password vault.** Connect 1Password with a read-only service account on a dedicated vault (`opVaultId` + `opVaultAllowedDomains`), or bind single fields for least privilege. Username, password and TOTP are typed by the server. [1Password](https://docs.browser-use.com/cloud/guides/1password.md)
- **Recording.** Off by default for API browsers and runs. Opt in with `enableRecording` on `POST /api/v4/browsers` or `browserSettings.record` on a run. [Recording](https://docs.browser-use.com/cloud/browser/live-preview.md)
- **Zero Data Retention.** Part of the custom data policy on enterprise agreements. ZDR projects never record, even when a request asks to, and `POST /api/v4/sessions/{id}/purge` deletes a session's data on demand. Some features, such as the 1Password vault, are off on ZDR projects. [Enterprise](https://browser-use.com/enterprise.md) · [Purge session](https://docs.browser-use.com/cloud/api-v4/sessions/purge-session.md)
- **Login state.** Cookies, localStorage and logins live in a profile you load by `profileId`. The docs recommend one profile per end user. [Profiles](https://docs.browser-use.com/cloud/guides/authentication.md)
- **Network.** A managed residential proxy by default, your own proxy on any account (`customProxy`), or no proxy for internal sites (`proxyCountryCode: null`). [Proxies](https://docs.browser-use.com/cloud/browser/proxies.md)
- **Region.** EU deployment in Frankfurt at `https://api.eu.browser-use.com/api/v4` with its own API key. Agents and browsers run there, and prompts, screenshots, recordings and profiles stay in EU storage when kept. Account, billing and some audit metadata stay in the US, and secret bindings are not available there. [EU deployment](https://docs.browser-use.com/cloud/eu-deployment.md)
- **Model provider.** Bring your own model key, so prompts and page content go to your provider account. [BYOK](https://docs.browser-use.com/cloud/guides/billing.md)
- **Live view.** Every browser has a live URL to watch or take over. Treat it as a credential: a view-only embed is a UI restriction, not a server permission. [Live preview](https://docs.browser-use.com/cloud/browser/live-preview.md)
- **Spend limits.** A monthly spend cap per API key (a soft limit) and a cost cap per V4 run. [Billing](https://docs.browser-use.com/cloud/guides/billing.md) · [FAQ](https://docs.browser-use.com/cloud/faq.md)
- **Contract.** DPA covering GDPR and UK GDPR, with EU Standard Contractual Clauses. Incident notice within 72 hours. Published sub-processor list with ten days' notice of new ones, except urgent security replacements, which are announced as soon as possible. Customer personal data destroyed within 90 days of termination; archived backups are isolated and deleted or anonymized later under the deletion policy. [DPA](https://browser-use.com/dpa)
- **HIPAA.** HIPAA support on enterprise plans, as part of a custom data policy. Not on the EU deployment. [Enterprise](https://browser-use.com/enterprise.md)

## Secret binding example

```python
import os
from browser_use_sdk.v4 import BrowserUse

# The task names an alias. The server types the value,
# and only into a field on an allowed host.
with BrowserUse() as client:
    run = client.runs.create(
        "Log in to https://portal.example.com with portal_password",
        secret_bindings=[{
            "alias": "portal_password",
            "source": {"type": "inline", "value": os.environ["PORTAL_PASSWORD"]},
            "allowedDomains": ["portal.example.com"],
        }],
    )
```

## Questions to ask any browser-agent vendor

1. **Which audit, which type, which dates?** SOC 2 Type I checks one point in time; Type II covers a period of operation. Ask for the report and its period, not a badge.
2. **Does the model ever receive my credentials?** Ask how secrets are tied to hosts, whether that check covers embedded payment frames, and whether they outlive the run.
3. **Is every run a separate browser?** A shared browser carries cookies from one task into the next. Ask where login state lives and how one user's profile is kept from another's.
4. **What is recorded by default, and can retention be zero?** Recordings and screenshots of logged-in pages are sensitive data. Ask what is kept, for how long, and whether you can purge a session now.
5. **Where does each kind of data live?** A region claim should name what stays in the region and what does not, such as billing and audit metadata.
6. **Can I bring my own proxy and model key?** Your own egress and your own model account keep traffic and prompts under contracts you already have.
7. **Who can open the live view?** A live browser URL usually grants control. Ask whether view-only is enforced by the server or only by the UI.
8. **What does the DPA promise?** Look for an incident notice deadline, notice before new sub-processors, and a deletion deadline after you leave.

## FAQ

**What is the most secure browser agent for enterprise?**
Judge it on evidence you can check: a current SOC 2 Type II report, credentials the model does not handle, a separate browser per run, recording off unless you ask, a zero data retention option, a regional deployment and a DPA with an incident deadline. Browser Use Cloud documents each of these, and every line above links to its source.

**Is Browser Use SOC 2 compliant?**
Yes. Browser Use is SOC 2 Type II compliant, audited by Accorp Partners for the period July 17 to October 17, 2025. Email support@browser-use.com to request the report.

**Does the AI model see my passwords?**
With V4 secret bindings or 1Password, the task names an alias and the server types the value into the focused field, only on hosts you allowed. The value is encrypted at rest and kept out of the worker payload. Once typed it is on the page like any input, so scope each binding to the narrowest host that works.

**Does Browser Use record browser sessions?**
Not by default. API browsers and runs record only when you set `enableRecording` or `browserSettings.record`. Zero Data Retention projects never record, even when a request asks to.

**What does Zero Data Retention cover?**
Zero Data Retention is a project setting, part of the custom data policy on enterprise agreements. ZDR projects never record, and you can purge a session on demand, which redacts its records and deletes its files, recordings and downloads. Some features, such as the 1Password vault, are unavailable on ZDR projects.

**Can browsers and agents run in the EU?**
Yes. The EU deployment runs agents and browsers in Frankfurt with its own endpoint and API key. Prompts, screenshots, recordings and profiles stay in EU storage when kept. Account, billing and some audit metadata stay in the US, and the docs list every exception.

**Can I use my own proxy?**
Yes, on every account and without a subscription. Pass `customProxy` when you create a browser, or `browserSettings.customProxy` on a run. You can also turn the managed proxy off.

**Is there a DPA?**
Yes. The DPA covers GDPR and UK GDPR with EU Standard Contractual Clauses, commits to incident notice within 72 hours, and gives ten days' notice of new sub-processors except urgent security replacements. Customer personal data is destroyed within 90 days of termination; archived backups are isolated and deleted or anonymized later under the deletion policy.

**Does Browser Use support HIPAA?**
HIPAA support is available on enterprise plans as part of a custom data policy. It is not available on the EU deployment. Contact sales@browser-use.com.