Agent Browser Gateway
Privacy Policy

Privacy Policy

This policy explains how Agent Browser Gateway handles browser data, extension permissions, local logs, and user choices.

Last updated: May 4, 2026

1. Scope

This Privacy Policy applies to Agent Browser Gateway ("ABG"), managed by ArcManagement, Inc. ("ArcManagement", "we", "our", or "the product"), including the Agent Browser Gateway Chrome extension, the macOS Agent Browser Gateway app, the abg command-line interface, locally installed ABG plugins, and the website at agent-browser-gateway.com.

ABG is designed as a local bridge between your browser and AI agent tools you choose to run. ABG does not operate a hosted browser service or a cloud account system.

2. Summary

  • ABG does not collect analytics, telemetry, advertising identifiers, or crash reports.
  • ABG does not sell user data.
  • ABG does not expose all tabs by default. A tab must be explicitly shared by the user.
  • Browser data requested through ABG is handled locally between the extension, the macOS gateway, the CLI, and the agent process you authorize.
  • If you use ABG with an AI agent or another tool that sends data to a third-party service, that service's own terms and privacy policy apply to what you send through it.

3. Data ABG handles

ABG can handle browser data only for tabs you choose to share or commands you choose to run. The table below describes the main categories of data involved.

Category Examples Purpose Where it is stored or processed
Extension settings Random extension identifier, operation approval setting, optional profile label Identify a local extension connection and remember user preferences Chrome extension local storage on your device
Shared tab metadata Tab ID, title, URL, origin, sharing timestamp, optional expiration timestamp Track which tab has been explicitly shared and revoke access when needed Chrome session storage, gateway memory, and local audit log entries
Page content Visible text, selected DOM content, HTML, Markdown, table data, element descriptions Let the local CLI or authorized agent inspect the shared tab Transferred from the extension to the local gateway over loopback when requested
Screenshots and annotations Full or partial tab screenshots, annotation comments, selected text, coordinates, selectors Help the user and agent refer to visible page regions or selected text Processed locally; screenshots may be saved to a local path chosen by the CLI command
Console and network information Console messages, request URL, method, status, type, MIME type, duration, response size Debug the explicitly shared tab Buffered in extension memory for the shared tab and returned locally on request
Network response body Response body for a specific network request ID Debug a request when the user or authorized agent explicitly asks for it Fetched locally through Chrome debugging APIs and returned to the local CLI
Operation inputs Selectors, text to type, coordinates, file paths, destination URLs, keyboard events Perform a command requested by the local CLI or authorized agent Processed locally by the extension and gateway; operation records are logged locally
Audit log Timestamp, extension ID, tab ID, URL, action name, agent identifier, limited details Provide a local record of ABG reads, operations, permits, and revocations ~/Library/Logs/AgentBrowserGateway/audit.jsonl on your Mac

Website data

The public website does not use forms, cookies, analytics scripts, advertising tags, or tracking pixels. The website may be hosted by GitHub Pages, which may process standard server logs such as IP addresses and request metadata for security and service operation according to GitHub's own policies.

4. Chrome extension permissions

ABG requests only the extension permissions needed for its user-facing local browser sharing features. The extension declares no host_permissions.

Permission Why ABG uses it
activeTab Access the active tab only when the user explicitly shares it.
scripting Read selected page content and perform structured operations in a shared tab.
tabs Read tab title, URL, and lifecycle events so ABG can list and revoke shared tabs.
storage Store local settings and session-scoped tab sharing state.
debugger Capture screenshots, console messages, network information, file uploads, and input operations for a tab the user has shared.
alarms Keep the extension service worker connected to the local gateway while Chrome is running.

5. Data sharing and third parties

ABG does not send browser data to servers operated by ABG. Data moves locally between the Chrome extension, the macOS gateway, the abg CLI, and the local agent process or shell command you authorize.

ABG is agent-agnostic. If the agent tool you use sends prompts, screenshots, page content, logs, or other information to a remote AI provider or third-party service, that transfer is performed by that agent or service, not by ABG. Review the privacy policy and configuration of the agent you use with ABG.

ABG may include locally installed plugins. Plugins can transform page content before it is returned to the CLI. Install plugins only from sources you trust.

6. Security measures

  • The gateway listens on 127.0.0.1, not on a public network interface.
  • The gateway accepts WebSocket connections only from browser-extension origins.
  • The Chrome extension declares no host_permissions.
  • Sharing is scoped to explicitly permitted tabs and is revoked on origin change or tab close.
  • Operation approval mode is enabled by default for write actions.
  • The gateway support and log directories are created as owner-only directories.
  • The audit log file is created as an owner-readable and owner-writable file.
  • ABG does not provide an agent command for arbitrary user-supplied JavaScript execution.

7. Retention

  • Extension settings remain in Chrome local storage until changed, reset, or uninstalled.
  • Shared tab state is session-scoped and can be cleared by revoking a tab or restarting Chrome.
  • Console and network buffers are held in extension memory and cleared when a tab is revoked or closed.
  • Audit log entries remain on your Mac until you delete them.
  • Screenshots saved by the CLI remain at the output path until you delete them.

8. Your choices

  • Do not share a tab unless you want the local agent workflow to inspect or operate it.
  • Use the extension popup or abg revoke to revoke a shared tab.
  • Keep operation approval mode enabled for a second local confirmation step.
  • Review local audit logs with abg audit or by opening the audit log file.
  • Delete local screenshots or audit logs from your Mac when you no longer need them.
  • Uninstall the Chrome extension and macOS app to stop using ABG.

9. Chrome Web Store Limited Use disclosure

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

ABG uses browser data only to provide or improve its single purpose: user-authorized, local, per-tab browser access for AI agent workflows. ABG does not use browser data for advertising, credit eligibility, resale, or unrelated profiling.

10. Changes to this policy

We may update this policy as ABG changes. Material updates will be reflected by the "Last updated" date above. If a future version changes how user data is collected, used, stored, or shared, the policy and Chrome Web Store disclosures should be updated before that version is published.

11. Contact

For privacy questions about Agent Browser Gateway, contact: contact@arcm.co.jp. ArcManagement, Inc.: https://arcm.co.jp.