Privacy policy

Who we are

PairBrowse is run by PairBrowse Inc. ("PairBrowse", "we", "us"). For anything about privacy, write to team@pairbrowse.com.

This website

pairbrowse.com is a set of static pages. It sets no cookies, uses no analytics or tracking, loads no advertising or third-party scripts, and has no forms or sign-up. Fonts, images and video are served from this site itself. Its security policy stops pages from loading anything from elsewhere.

The site is hosted on Cloudflare Pages. To deliver pages, Cloudflare handles each request, including your IP address and browser details, and may keep standard technical logs under its own privacy policy. We do not add any analytics on top.

Links to GitHub and other sites take you to services with their own privacy policies. If you email us, we use your message and address only to reply.

The software

PairBrowse runs on your own computer. There is no PairBrowse account, and the plugin, helper and browser send us no usage data, telemetry or crash reports. We do not see your browsing, your prompts or what you type into forms.

PairBrowse does not judge clicks with another model or service: deciding whether a click needs your approval happens on your computer, and nothing about a click leaves it.

What stays on your computer

PairBrowse keeps its data in ~/.pairbrowse on the machine the browser runs on. Everything there is created private to your user account. It includes:

• Browser sessions: each session is its own browser profile, separate from your everyday Chrome, with its logins, cookies and site data, and the saved list of its tabs.
• Passwords you save, in secrets.env, readable only by you. Each works only on the HTTPS sites you list for it.
• Remembered details such as company name, addresses and contact details, which you can see, edit and remove in the Profile panel. Passwords, PINs, verification codes and card and bank numbers are never remembered.
• Saved runs, playbooks and pre-submit reviews, so a half-finished job can resume later.
• Logs of what the agent did, with card numbers and sensitive fields masked.
• Copies of files you upload through PairBrowse, in files/uploads.
• Who used each session: participant names, the app they used and the kind of computer (Mac, Linux or Windows, never the computer's own name). Nothing about what they did.
• Settings in config.json, the downloaded browser and runtime, and on a Mac with the native browser a description of your Mac's own browser characteristics, kept in mac-host-profile.json until the browser version or hardware changes.

Files that websites hand over are saved to your Downloads folder, as in any browser. To remove everything, uninstall the plugin and delete ~/.pairbrowse. In a cloud session these files live in the cloud container and are reset when the session ends.

Anything running as your user can read files in your home folder, so PairBrowse cannot protect this data from malware already on your computer.

What your AI provider sees

PairBrowse works through the AI app you use, such as Claude Code or Codex. To do a task, your agent reads the pages it works on: page snapshots, text, form fields and, when needed, screenshots. That content, and your prompts, go to that app's AI provider and are handled under your agreement with them, not by us.

• Saved passwords are never shown to the model. The agent sees only a password's name, and the value is masked in everything it reads back, including snapshot files.
• Screenshots cannot be masked, so none is sent while a saved password shows anywhere on the page. Other content in a screenshot, card fields included, shows as it is on the page.
• Remembered details are used to fill forms you ask the agent to fill, so the agent can see them.

Point your agent only at pages you are comfortable sharing with your AI provider.

Sharing and join codes

Nothing is shared with anyone unless you invite them. When you do:

• Join codes go through a Cloudflare Quick Tunnel, which carries the traffic (encrypted to Cloudflare). Nothing of your session is sent until you click Allow for that person. The tunnel closes with the last code, and codes end when you revoke them or PairBrowse stops.
• What crosses: tab addresses (cut down for watchers, and stripped of parameters that look like sign-in links, tokens or personal details), titles, values typed in form fields, tab order, pointer positions, who is doing what, and short text messages.
• What never crosses: cookies, storage, logins, saved passwords, remembered details, files or a picture of your screen. Password, card, one-time-code and similar fields cross only as "filled" or "empty". Sites you keep saved passwords for cross as their address only.
• Invite links for the live view work over a private route you set up, such as your tailnet or SSH, and show everything on screen in your signed-in browser. They end after 24 hours by default, or when you revoke them.
• Your prompts to your agent are never shared. PairBrowse never sees them.

The full rules are in the sharing docs and the security notes.

Other connections

Besides the websites you open, PairBrowse connects to the internet only to fetch what it needs, at pinned versions:

• the browser, once, from the PairBrowse GitHub release or Playwright's download;
• its runtime packages, from a lockfile with checksums, when it installs or updates;
• cloudflared, once, the first time you make a join code.

Those downloads reach GitHub, the npm registry and the other publishers, under their own policies. Text you type into the PairBrowse address bar that is not an address is searched on Google, as in an everyday browser.

Your choices and rights

Because PairBrowse keeps your data on your computer, you control it directly: view and edit remembered details and passwords in the Profile panel, delete sessions, or remove ~/.pairbrowse entirely. We hold no PairBrowse data about you. If you have emailed us and want that correspondence deleted, or have any other privacy request, write to team@pairbrowse.com. Depending on where you live, you may also have the right to complain to your data protection authority.

Changes

If what PairBrowse or this website collects changes, we will update this policy before the change ships and note it in the repository. The date at the top shows the latest version.

Contact

Privacy questions: team@pairbrowse.com. See also the terms of use and licenses.