Private browser work should stay local.

Local processing

AgentTab connects a local runtime to your signed-in Chrome profile. Browser work and the task state needed to coordinate it remain on your device. AgentTab is not a proxy for your browser traffic and does not route browser data through an AgentTab-operated server.

The local runtime may retain task state or a local receipt needed to safely resume work or show its status. That information remains under your device and account controls.

Information AgentTab handles

AgentTab handles browser information only to carry out the browser work you or an agent you connected requests. Depending on the request, that can include:

• The address, title, text, page structure, form state, and screenshots of tabs the agent's task opened or you let it adopt.
• Your bookmarks, when the agent searches, reads, creates, renames, moves, or (after your approval in the AgentTab popup) removes one.
• Your browsing history, when the agent searches it to find a page you visited. AgentTab never deletes history.
• Recently closed tabs and windows and tabs open on your other signed-in devices, when the agent lists or reopens one.
• Your download list, including file names and saved locations, when the agent finds, cancels, pauses, or resumes a download. AgentTab cannot open, reveal, or delete a downloaded file.
• Chrome's coarse idle state (active, idle, or locked), when the agent checks whether you are likely to see a notice. AgentTab never records keystrokes.

When you use the optional 1Password integration, the local host fills a selected login field directly in the page. The credential value is never returned to the agent and is never stored by AgentTab.

How that information is used

That information goes only to the local agent that made the request, through Chrome Native Messaging and an operating-system channel private to your user account. It is used only to perform the request. It is not sent to the developer, not used for advertising, profiling, or creditworthiness, not sold, and not shared with anyone. No person at AgentTab can read it.

The local agent you connect, and any model or service that agent uses, is software you choose. What it does with the information it receives is governed by that software's own terms and privacy practices.

Storage and retention

The extension stores only the state it needs to recover across restarts, such as task status, pause state, attention notices, and display preferences, in Chrome's extension storage. Removing the extension removes that storage.

The local host keeps task records and a local audit log on your computer, in a directory private to your user account. They are never uploaded, and you can delete them at any time. Bookmark, history, session, and download results are not written to AgentTab logs or audit records.

No telemetry or data brokerage

AgentTab does not collect personal data for analytics, advertising, profiling, or product telemetry. It does not sell or share personal data. It does not operate a remote AgentTab service that receives your browser content, credentials, cookies, storage, or task activity.

When an agent uses a website

An agent can interact with a third-party site through the Chrome profile you choose to use. That site can receive information through the actions you direct, just as it can when you use the site yourself. Those sites have their own terms and privacy practices. AgentTab does not become the recipient of that site data or a middle layer for it.

Security boundaries and limits

Task ownership limits agent execution and coordination to visible task workspaces. It is not cookie, identity, or browser-profile isolation. Standard mode does not provide raw cookies, storage, passwords, arbitrary JavaScript, raw Chrome DevTools Protocol access, or coordinate actions.

For passwords, passkeys, 2FA, CAPTCHAs, payment secrets, and other human-only input, AgentTab shows a Needs your attention notice. The person completes that input directly in Chrome; the agent asks for it in chat and verifies the page itself afterward, and AgentTab does not capture the person's keystrokes.

Commit stages recognizable sends, publishing, purchases, deletion, uploads, authorization, and permission grants for review. This is a best-effort safety measure. Prompt injection and page behavior can still create risks, and Commit cannot guarantee recognition of every external effect.

Changes and contact

If AgentTab's handling of information changes, this page will be updated and its effective date revised before the change ships. For questions about this policy, open an issue on the AgentTab issue tracker or use the support page.