01
Zero-log session content
BrowserCity is built so browsing history, page content, screenshots, recordings, cookies, local storage, and keystrokes are not retained as vendor logs by default.
Trust Center
Private infrastructure for sensitive automation.
Build live-web automation without handing a vendor a retained copy of your browsing history by default. Our trust posture starts with a zero-log session architecture and strict data boundaries.
Privacy architecture
Trust by reducing what exists
Our default posture is not "collect everything and promise restraint." It is to keep session content out of persistent logs entirely, while acknowledging that network delivery still requires routing metadata.
02
Ephemeral browser runtime
Sessions run in isolated browser containers with session-scoped runtime state that is destroyed when the session ends.
03
Control-plane metadata only
Operational records are scoped to account, billing, abuse prevention, lifecycle events, and the routing metadata needed to deliver traffic—not retained page-content logs.
04
Client-controlled artifacts
Your code can request screenshots, PDFs, traces, or extracted data. Those artifacts return to your client; BrowserCity does not turn them into a retained vendor log.
Data boundaries
Know where your data lives
We strictly separate your browsing session content from the operational and billing metadata we need to run the service. Session content stays out of retained vendor logs by default, while the metadata boundaries stay explicit.
For the exact commitments, read the full Zero-Logs Policy.
| Boundary | Examples | Default treatment |
|---|---|---|
| Session data plane | URLs visited, page content, cookies, local storage, screenshots, recordings, keystrokes | Not retained by BrowserCity by default |
| Control plane | Session ids, API requests, lifecycle status, errors, timing, account and project references | Used to operate, support, secure, and bill the service |
| Billing and usage | Session duration, plan, proxy class, byte counts, invoice-related metadata | Retained as needed for accurate billing and abuse prevention |
| Network delivery | Destination/routing metadata processed by infrastructure or proxy providers | Processed as needed to deliver traffic rather than retained as BrowserCity browsing-history logs |
| Client exports | Artifacts your code explicitly requests or stores from a session | Controlled by your application and storage choices |
Security without the marketing fluff
We can support your enterprise evaluation with detailed architecture reviews, but we won't claim certifications or guarantees we don't have.
- Dedicated browser sessions rather than shared customer runtime state.
- No built-in session recording or persistent request-log product surface.
- Internal access should be scoped to operational metadata, not session content.
- Security and privacy questions can be reviewed with the team before production rollout.
The full policy, ready for your legal team
When your security or procurement team needs the binding terms, send them straight to the Zero-Logs Policy or reach our privacy team directly.
[ 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.