Safety Consent And Governance

Crawler operator points Browserbase sessions at a site whose robots.txt disallows the path they want.

Honor robots.txt at the operator layer before issuing page.goto. Browserbase does not centrally enforce robots — it is operator responsibility. Document policy exceptions (e.g., authorized customer-own targets) explicitly.

Enterprise prospect asks for SOC 2 Type II report and GDPR DPA.

Surface the Browserbase compliance posture as documented [REQUIRES-VERIFICATION on current report dates and DPA terms]. Pair with the operator's own DPA covering the data they collect via Browserbase. Do not assert report contents without retrieving the current artifact.

New customer onboards a target site that Browserbase has flagged as ToS-sensitive.

Require customer attestation of ToS-compliant authorization (own site, explicit agreement, public-data carve-out) before enabling stealth + proxies + captcha for that target. Persist the attestation for audit.