ArcSolve Agent Privacy Notice

Effective Date: April 11, 2026

This document explains what data ArcSolve Agent Chrome Extension may process, when that data may be read or transmitted, and how users can control that behavior. This notice is an extension-specific supplement to the ArcSolve Privacy Policy.

ArcSolve’s use of data collected through the Chrome extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

1. Scope

This notice applies to data processed by ArcSolve Agent. ArcSolve Agent is a browser-side workflow extension that lets user-directed ArcSolve workflows inspect and operate browser tabs in a controlled side panel environment.

ArcSolve Agent is separate from ArcSolve Distill and ArcSolve Translate. Distill focuses on reading, clipping, and document intake. Translate focuses on PDF viewing and translation. Agent focuses on controlled browser workflow execution.

2. Data the Extension May Process

ArcSolve Agent may process the following categories of data when the user starts or continues an agentic browser workflow:

Data Category	Examples	Purpose
Tab and window context	Tab ID, window ID, URL, title, loading status, tab group, active tab state	Selecting and managing workflow tabs
Page content and DOM state	Visible text, element labels, links, form fields, page structure, accessibility-like element descriptions	Understanding page state and completing user-directed workflow steps
Browser interaction results	Navigation result, click result, typed input result, scroll state, keyboard action result	Reporting workflow progress and next possible actions
Screenshots or visual page state	Visible page area or rendered page state when needed for a workflow	Visual inspection, element targeting, and user review
User instructions	Workflow prompts, commands, constraints, and confirmations entered by the user	Guiding the workflow
Authentication state	OAuth token metadata and session state	Authenticated ArcSolve service requests
Local workflow state	Agent group ID, host tab ID, remembered tabs, short-lived workflow context	Maintaining continuity across tabs and extension service worker restarts

3. When ArcSolve Agent Reads Data

ArcSolve Agent reads data in the following situations:

The user opens or starts an ArcSolve Agent workflow.
The user asks the agent to inspect a page, tab, or browser state.
The workflow needs to navigate, create, select, group, or close tabs.
The workflow needs to read visible page content or DOM state.
The workflow needs to click, type, scroll, press keys, or wait for navigation on a page.
The workflow needs to report tab context or page state back to ArcSolve.

ArcSolve Agent is not designed to passively collect every page the user visits. Its browser access is tied to user-directed workflows and the tabs involved in those workflows.

4. When Data May Be Transmitted

ArcSolve Agent may transmit data when a requested browser workflow requires ArcSolve services or configured AI providers. Examples include:

Feature	Data Transmitted	Destination	Trigger
Workflow planning and execution	User instructions, tab context, page observations, tool results, and derived outputs	ArcSolve services and configured AI providers	User starts or continues an agent workflow
Browser state reporting	URLs, titles, tab lists, selected page content, visible page state, and operation results	ArcSolve services	User-directed workflow needs browser context
Account sign-in	Authentication request and OAuth token exchange data	ArcSolve Auth services and identity provider	User signs in

ArcSolve Agent does not sell user data and does not use user content for advertising or third-party marketing. ArcSolve does not use user content to train AI models.

Additional details about cloud infrastructure, AI providers, and cross-border transfers are available in the main Privacy Policy.

5. Data Stored Locally

ArcSolve Agent may store the following data locally in Chrome extension storage:

Workflow continuity state: Host tab ID, agent tab group state, remembered tabs, and short-lived workflow context.
Authentication token metadata: OAuth state required for authenticated ArcSolve requests.
UI state: Side panel state and local settings needed to run the extension.

Local state is used to maintain the user’s active workflow and recover from extension service worker restarts. It is not used for advertising or unrelated tracking.

6. What ArcSolve Agent Does Not Do

ArcSolve Agent does not operate in the following ways:

It does not sell user data.
It does not use user content to train AI models.
It does not use processed data for advertising or third-party marketing.
It does not continuously crawl unrelated websites in the background.
It does not intentionally bypass website access controls, login requirements, paywalls, or anti-abuse systems.
It does not complete purchases, submit forms, or change account settings without user-directed workflow context.
It does not access pages unrelated to the active user-directed workflow.

Because ArcSolve Agent can operate browser tabs, users should supervise workflows and avoid granting broad tasks on sensitive sites.

7. Third-Party Services

Data processed by ArcSolve Agent may be sent to ArcSolve services or configured third-party AI providers used to fulfill requested workflows. These providers are described in the main Privacy Policy.

8. Permissions Used by the Extension

ArcSolve Agent uses the following permissions:

Permission	Purpose
`host_permissions` (`<all_urls>`)	To inspect and operate user-directed workflow pages across arbitrary domains
`activeTab`	To access the current tab after user interaction
`debugger`	To observe and operate pages through Chrome debugging interfaces for controlled workflow actions
`identity`	To support Chrome extension sign-in flows
`scripting`	To inject scripts needed for page inspection and workflow actions
`sidePanel`	To show the ArcSolve Agent side panel
`storage`	To store workflow continuity state and authentication token metadata
`tabGroups`	To group and identify tabs used by an agent workflow
`tabs`	To create, query, update, and manage workflow tabs
`windows`	To create or manage windows needed for workflow isolation

ArcSolve Agent uses these permissions to execute user-directed browser workflows. It does not use them for advertising, hidden tracking, or unrelated background data collection.

9. User Rights

Users may request access to, correction of, deletion of, or suspension of processing of personal information by contacting the Data Protection Officer at [email protected].

For full details on user rights, the Data Protection Officer, and remedy institutions, see the Privacy Policy Sections 12 and 14.

10. User Controls

Users can control ArcSolve Agent data handling in the following ways:

Start workflows only on pages they intend ArcSolve Agent to inspect or operate.
Stop the workflow when browser operation is no longer needed.
Avoid using Agent on sensitive account, financial, medical, legal, or private communication pages unless necessary.
Review workflow actions before relying on outputs or continuing sensitive steps.
Use Chrome’s extension site access controls.
Sign out of ArcSolve.
Disable or remove the extension in Chrome.

12. Summary

ArcSolve Agent can inspect and operate browser tabs in user-directed workflows. It may process tab context, page content, DOM state, screenshots or visual state, user instructions, and browser operation results. It uses powerful browser permissions for workflow execution, not advertising, hidden tracking, or unrelated background crawling. Users should supervise workflows and use extra caution on sensitive sites.

For questions about this document, contact [email protected].