Last updated: 10 August 2026. This policy applies to the Agtweb browser extension and local
bridge for Chrome, Chromium, and Firefox.

Agtweb's single purpose is to let a user-installed local agent inspect and automate browser
pages when a connected local client requests an automation action.


Depending on the requested action, Agtweb may handle:

• website content, including text, HTML, links, layout information, form fields and current
  field values, and screenshots;
• browsing and website activity, including tab and frame URLs and titles, search terms,
  navigation, clicks, typing, scrolling, and form interaction;
• authentication information, such as account identifiers or credentials, and files supplied
  by the local client for entry or upload; and
• recent-download metadata, including filenames or local paths, source URLs, sizes, status,
  and time.

This data may contain personal or sensitive information. Agtweb uses it only to perform the
requested action and return the result to the connected local client.


Data passes through browser native messaging to the user-installed agtweb-bridge, then over
a loopback connection to the connected local client on the same computer. Agtweb has no
developer-operated backend, analytics, advertising, or telemetry. The developer does not
receive this data.

At the local client's direction, Agtweb may navigate to websites, send a web-search query to
Google, or submit typed data and files to a selected website. Those are ordinary browser
requests to the selected sites. A connected agent or model provider may also store or transmit
results under its own configuration and privacy terms; those systems are outside Agtweb's
control.


Agtweb does not persist the data listed above. Request data remains in process memory until the
request or transfer finishes or the process stops. The installer stores only a random bridge
token and port. The default setup restricts the bridge to localhost, requires the token, and
limits native-host access to the configured Chrome, Chromium, and Firefox extension identities.


Firefox treats native-messaging transfer to the local bridge as data transmission outside the
add-on. The Firefox package therefore declares authenticationInfo, browsingActivity,
searchTerms, websiteActivity, and websiteContent.