No retained browsing history
Browsing history is not stored as a BrowserCity activity log by default; traffic delivery may still require destination/routing metadata.
Zero-Logs Browser API
Run live browsers without creating a retained session-content log
Browser automation touches sensitive data: logins, internal tools, and customer workflows. We provide the hosted browser infrastructure, but we do not retain session content, page recordings, or a browsing-history log of session URLs by default.
Why it matters
A browser API should not be a shadow data lake
When you run automation on third-party infrastructure, you risk exposing your IP, your customers' data, and your scraping targets. Our zero-log posture keeps session content and client-requested artifacts out of BrowserCity databases by default, while operational logs, billing records, routing metadata, and provider metadata remain governed by the legal policy.
No session replay product
BrowserCity does not provide a vendor-side recording pipeline for retained page content, video, or keystroke playback.
Ephemeral session storage
Cookies, local storage, and browser profile state live with the session runtime and are destroyed when that runtime ends.
Exports go to your client
If your code requests screenshots, PDFs, markdown, traces, or other artifacts, they are delivered to your application instead of becoming retained BrowserCity activity logs.
How it works
Ephemeral state. Explicit outputs.
Zero-log doesn't mean you fly blind. It just means you control the artifacts. Tell the browser to take screenshots, extract markdown, or save traces, and we stream them directly back to your application without retaining copies on our servers.
01
Create a browser
Start a hosted browser session through the API, Playwright, REST, or MCP.
02
Run your automation
Navigate, click, extract, screenshot, and complete the work your application asked for.
03
Receive explicit outputs
Requested artifacts return to your client during or shortly after the session, depending on the API flow.
04
End the session
The browser runtime is torn down and session-scoped browser state is discarded.
Zero-Logs Policy
Open Zero-Logs PolicyRead the exact data-handling commitments
This page explains how the zero-logs browser API behaves in practice. For the precise terms — what BrowserCity does not retain by default, and which operational and routing metadata is still processed to run your traffic — see the full Zero-Logs Policy.
[ 08 / 08 ] — Get Started
Give your AI agents the web.
We're in private beta — request access and we'll get you set up. Private sessions by default.