Terms of Service
Effective August 16, 2026
Applies to the AgentBrowser website (getagentbrowser.com), the hosted control plane and API (app.getagentbrowser.com), the console, the MCP server, the Python SDK, and related client software (collectively, the “Service”).
This is the detailed backing document for the short terms published at getagentbrowser.com/legal. Where they differ on a factual point about what the product does, this document governs.
Contracting entity: Transition 2 Consulting Inc (“we,” “us,” “our”), operating AgentBrowser.
Governing law/venue: the laws of the State of Delaware, USA (see §10).
1. What the Service is
AgentBrowser is a browser-automation platform: it runs real headless Chrome browser sessions (“hosted sessions”) on our infrastructure, exposes them to your automation/agents over an API, MCP server, and Python SDK, and provides supporting features — a credential vault for origin-bound login injection, session recording, reusable managed identities, webhooks, and usage-based billing. Self-hosted deployment of the render-node and control-plane software is also supported; this document covers the hosted service unless stated otherwise.
2. Your account
Keep your account, API keys, node registration credentials, and vault credentials confidential. Tell us promptly if you believe any of them has been compromised. You're responsible for activity performed with credentials under your control until they're revoked. Service accounts (non-human principals used for automation, P2-206) are subject to the same responsibility as a human account member who created them.
3. Acceptable use
Use of the Service is governed by the Acceptable Use Policy, which is incorporated into these Terms by reference. In short: you may use AgentBrowser only for lawful browser automation on systems and data you're authorized to access, and you're responsible for complying with the terms of any third-party site or service your automation touches.
4. What's actually enforced — plans, limits, and controls
These aren't marketing claims; they're the same limits the product enforces in code, so you should expect exactly this behavior, not more or less:
- Plan-tier limits. Each plan (Free/Pro/Scale) has an included monthly instance-hours allotment, an included storage allotment, and a hard cap on concurrent live sessions (
internal/billing.Plan). Paid plans meter usage beyond the included amount; we do not silently throttle you without telling you why — quota and limit rejections return a typed error identifying the plan and the limit hit. - Storage quota. Uploading or recording more than your plan's included storage is rejected before the bytes are written (
cmd/gb-server/artifact_quota.go) — you get a clear 402 response identifying the plan and limit, not a silent failure or partial write. - Optional consequence-based spend approvals. If you configure a spend/consequence policy on your workspace (P2-207), an action that would exceed it doesn't execute automatically — it pauses the session in a human-takeover state and waits for you to approve or deny it, using the same idempotency mechanism as normal execution so an approved action runs exactly once, never twice. This is opt-in; it does not run unless you configure it.
- Egress boundary on hosted sessions. A hosted browser session can only navigate to public HTTP(S) URLs (or
about:blank) — it cannot be used to reach loopback, private-network, or link-local/metadata addresses. Configured webhook delivery targets are subject to the same boundary. This exists to keep hosted automation from being usable as a pivot into internal networks, including ours. - Vault redaction. Credentials injected through the vault are never returned to your automation's output — see the Privacy Policy §1.3 for exactly how that works and its limits.
5. Service availability
This is early-access, actively-developed software. Features may change, and the Service may be unavailable at times, including for maintenance and incident response. Features identified in the console, docs, or API responses as preview, pending, or unsigned are provided for evaluation and may change or be removed without the notice a generally-available feature would get. To the extent permitted by law, the Service is provided without warranties of uninterrupted operation or fitness for a particular purpose (see §7).
6. Suspension
We may suspend or restrict access needed to protect users, infrastructure, the public, or to enforce the Acceptable Use Policy. Where practical, we'll tell you why.
7. Warranty disclaimer and limitation of liability
THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR SECURE. TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, DATA, OR GOODWILL, ARISING FROM YOUR USE OF THE SERVICE.
TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THE SERVICE WILL NOT EXCEED THE TOTAL FEES YOU PAID US IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM.
8. Compliance status — what we do not claim
We do not claim SOC 2 certification, ISO 27001 certification, or completion of an independent penetration test as of this writing. Both are tracked as separate, explicitly not-yet-complete work (SOC 2 evidence collection and an external pentest). If a claim of either appears anywhere else in our marketing before that work is actually complete, it is an error — this document is the authoritative statement of compliance status.
9. Termination
You may stop using the Service and delete your account at any time; see the Privacy Policy §2.4 for exactly what account deletion does and does not erase today. We may terminate or suspend your account for a material breach of these Terms or the Acceptable Use Policy.
10. Governing law
These Terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws principles. Any dispute arising out of or relating to these Terms or the Service will be brought exclusively in the state or federal courts located in Delaware, and you consent to the personal jurisdiction of those courts.
11. Changes
We'll update the effective date above when these Terms change. Continued use of the Service after a change constitutes acceptance of the updated Terms.