ArcSolve Agent Site Access and Permissions

Effective Date: April 11, 2026

ArcSolve Agent Chrome Extension uses website access and browser automation permissions to inspect and operate pages involved in user-directed workflows. This document explains why those permissions are required and how they are limited.

1. Purpose of This Document

This document explains:

Why ArcSolve Agent needs broad website access
What browser automation permissions are used for
When tabs, windows, and tab groups may be created or changed
How users can control access and reduce risk

2. What ArcSolve Agent Does

ArcSolve Agent supports browser workflows such as:

Inspecting the current tab and available workflow tabs
Reading visible page content and DOM state
Navigating to user-requested URLs
Creating, selecting, grouping, or closing workflow tabs
Clicking elements and typing text during a user-directed workflow
Scrolling, waiting for page load, and reporting browser state
Maintaining a dedicated tab group or window for workflow continuity

3. Why `<all_urls>` Is Required

ArcSolve Agent uses host_permissions for <all_urls> because user-directed workflows may involve arbitrary websites. Chrome requires host permissions before an extension can inspect or operate a page.

The permission is broad because user workflows can be broad. ArcSolve Agent’s use is limited to pages involved in active user-directed workflows.

4. Why Browser Automation Permissions Are Required

ArcSolve Agent uses powerful browser permissions for controlled workflow execution:

Permission	Purpose
`debugger`	To observe and operate page state through Chrome debugging interfaces
`tabs`	To query, create, update, navigate, and manage workflow tabs
`tabGroups`	To group tabs associated with an Agent workflow
`windows`	To create or manage windows when workflow isolation is needed
`scripting`	To inject scripts for page inspection and workflow actions
`sidePanel`	To present Agent controls and workflow state
`storage`	To remember short-lived workflow state and authentication metadata
`identity`	To support Chrome extension sign-in
`activeTab`	To access the active tab after user interaction

These permissions are used for workflow execution, not advertising, hidden tracking, or unrelated background collection.

5. When Website Content Is Read

ArcSolve Agent reads website content when:

The user starts or continues a browser workflow.
The workflow needs current tab context.
The workflow needs visible page content or DOM state.
The workflow needs to find an element before clicking, typing, or scrolling.
The workflow needs to report browser state back to ArcSolve.

Agent is not intended to read unrelated pages outside the active workflow.

6. Tab, Window, and Group Management

ArcSolve Agent may create or update tabs, windows, and tab groups so that workflow pages stay organized and recoverable. It may:

Create a workflow tab or window
Group workflow tabs together
Remember a host tab
Reuse a tab in the workflow group
Navigate a workflow tab to a user-requested URL
Report available tabs back to the user or workflow

7. Data Transmission

ArcSolve Agent may transmit page observations, tab context, user instructions, workflow results, and browser operation results to ArcSolve services or configured AI providers when needed to run the user-directed workflow.

Reading a page locally does not always mean transmitting all page content. Transmission depends on the requested workflow and the context needed to complete it.

8. What ArcSolve Agent Does Not Do

ArcSolve Agent does not:

Sell user data
Use user content to train AI models
Use browser permissions for advertising
Continuously crawl unrelated pages in the background
Hide browser actions from the user
Bypass website access controls, paywalls, CAPTCHAs, or anti-abuse systems
Intentionally operate pages unrelated to the active workflow

9. User Controls

Users can control ArcSolve Agent by:

Starting workflows only when browser operation is desired
Stopping workflows when finished
Restricting extension site access in Chrome
Avoiding sensitive pages unless necessary
Reviewing actions on pages with real-world consequences
Signing out or removing the extension

11. Summary

ArcSolve Agent requires broad website access and browser automation permissions because it operates user-directed workflows across arbitrary websites. Those permissions are used to inspect page state, manage workflow tabs, and perform browser actions requested by the user. They are not used for advertising, hidden tracking, or unrelated background crawling.

For questions about this document, contact privacy@arcsolve.ai.