Where it runs and what it controls
A short summary for security and procurement reviews. The documentation has the detail.
BrowserBox runs on Windows, macOS or Linux machines that you operate. The browser, its profile and the pages it loads stay on that machine; the user's device receives a stream of the session.
Copy and paste, uploads, downloads, printing and developer tools are each allowed or denied by policy. A deny-by-default profile adds a navigation allowlist, blocks private-network access and encrypts the browser profile at rest.
Policy decisions are logged with sensitive fields redacted, so you can show what was permitted and what was refused.
Serve a session over HTTPS on your own hostname, behind nginx, through a Cloudflare tunnel, a ZeroTier network or a Tor onion service. You choose the transport and who can reach it.
BrowserBox is commercial software activated with a product key (bbx certify). Seats are concurrent users. Terms are in the license agreement.
License agreement, privacy policy, terms, and notes for regulated teams.
Report a security issue
Email support@dosaygo.com with the subject "BrowserBox security report". Include the version, the platform and the steps to reproduce. Please do not open a public issue for a vulnerability.