ArcSolve Agent Privacy Notice
Effective Date: May 27, 2026
ArcSolve Agent is a Chrome extension that executes user-directed browser workflows from a side panel. This document explains how website data, tab state, browser operation results, and account information are processed during Agent workflows and during integration with the ArcSolve Desktop browser runtime.
ArcSolve uses information processed through its Chrome extensions in accordance with the Chrome Web Store User Data Policy, including the Limited Use requirements. Information received from Chrome APIs or Google APIs is used solely to provide or improve the user-directed browser workflows and the ArcSolve AI / Desktop browser runtime integration features, and is not used for personalized advertising, data sale, or credit evaluation purposes.
1. Scope
This document applies to the ArcSolve Agent Chrome extension. ArcSolve Distill handles web clipping and document intake, and ArcSolve Translate handles PDF and selected-text translation; those extensions are governed by their own separate notices.
2. Data Processed by Feature
| Feature | Data That May Be Processed | Purpose of Processing |
|---|---|---|
| Side panel and account | Account session, email, profile, project information | Login, ArcSolve API requests, UI display |
| Agent session | Session ID, title, host tab ID, window ID, tab group ID, list of workflow tabs | Maintaining workflow continuity |
| Tab and window management | Tab URL, title, status, group, active tab, window information | Creating, selecting, moving, and cleaning up workflow tabs |
| Page reading | Page title, URL, visible text, DOM structure, role/name/ref, links, form field information | Allowing the Agent to understand page state and select the next action |
| Browser actions | Clicks, input, scrolls, key presses, navigation, downloads, dialog state, execution results | Carrying out user-directed workflows |
| Visual information | Screenshots, screen state, element positions | Visual inspection and element targeting |
| Diagnostic information | Console messages, network metadata, navigation state | Debugging and identifying causes of operation failures |
| AI / browser runtime conversation | User instructions, ambient tab context such as current workflow tab URL/title, tool results, AI responses, Desktop browser tool requests and responses | Running AI chat and Desktop browser runtime workflows |
| Local settings | Theme, accent color, font size, monospace font setting | Preserving the user’s environment |
Under the Chrome Web Store privacy disclosure categories, ArcSolve Agent may process Personally Identifiable Information, Authentication Information, Personal Communications, Web Browsing Activity, User Activity, and Website Content. Personal Communications may apply where the user directly initiates an Agent workflow on a page such as webmail, chat, DM, or a collaboration tool. “Web Browsing Activity” does not mean storing the user’s entire browsing history; it means processing the URL, title, navigation state, and network metadata of workflow tabs to the extent necessary to perform the operation. “User Activity” refers to Agent tool requests, browser actions, tool results, and workflow review states. Health Information, Financial and Payment Information, and Location Information are not collected by ArcSolve Agent as dedicated data categories.
3. When Data Is Read
The ArcSolve Agent content script may load on permitted sites, but its default behavior is to wait for browser tool requests and to reset transient element references upon page navigation.
Website data may be generated or read in the following situations.
- When the user starts or continues an Agent workflow
- When ArcSolve Desktop requests the Agent extension to execute a browser tool through the same-machine browser-runtime bridge
- When a workflow needs to read the current tab, the Agent tab group, or a specific URL
- When a browser tool requests page text, DOM, accessibility-like structure, links, form fields, screenshots, or console/network metadata
- When the user directs a browser action such as a click, input, scroll, key press, or navigation
Mere installation does not automatically transmit the body content or screenshots of visited pages to the ArcSolve servers. Transmission occurs when an Agent workflow or Desktop browser-runtime integration requires browser tool results.
4. When Data Is Transmitted and to Whom
| Trigger | Data That May Be Transmitted | Recipient | Purpose |
|---|---|---|---|
| Arc AI mode | User messages, ambient tab context, page observations, tool results, AI responses | ArcSolve API and the configured AI providers | Executing AI-powered browser workflows |
| Desktop browser runtime | Browser tool requests and results, session state | ArcSolve Desktop native messaging host | Relaying Desktop AI/Codex integration and browser runtime |
| Login | OAuth requests, token exchanges, account profile | ArcSolve Auth service and the login provider | Authenticating the ArcSolve account |
| Project / document state lookup | Authentication tokens, project/document requests | ArcSolve API | Displaying the Agent UI and document state |
User input and tool results transmitted in Arc AI mode may, depending on the selected model, be forwarded to the configured AI providers, including OpenAI, OpenRouter, and Google Vertex AI. Detailed recipients and cross-border transfer information are governed by the Privacy Policy.
The Desktop browser-runtime integration may communicate with the local desktop runtime through the Chrome native messaging host registered by the user-installed ArcSolve Desktop application. This path is intended for Desktop integration on the same user device, and additional external transmission may occur depending on the Desktop AI/Codex configuration and execution environment.
5. Locally Stored Data
| Storage Location | Examples | Retention Standard |
|---|---|---|
chrome.storage.sync | Theme, accent color, font settings | Until changed by the user or until the extension is removed |
chrome.storage.local | OAuth refresh tokens and other long-term login continuity information | Until logout, token revocation, or extension removal |
chrome.storage.session | OAuth access tokens, Agent session, tab group / window / tab state | Until the browser session ends or the workflow terminates |
6. Permission Summary
| Permission | Reason for Use |
|---|---|
<all_urls> host permission | Executing Agent browser tools on user-directed arbitrary web pages |
debugger | CDP-based screenshots, input, scrolling, and observation/manipulation of console, network, and navigation |
alarms | Scheduling reconnect backoff for the Desktop native messaging host |
downloads | Observing download start and completion states during user workflows |
identity | ArcSolve login based on Chrome Identity |
nativeMessaging | Connecting to the user-installed ArcSolve Desktop native host |
scripting | Re-injecting the content script when no content receiver is present |
sidePanel | Displaying the Agent UI and workflow state |
storage | Storing settings, sessions, tokens, and Agent tab state |
tabGroups | Creating and managing the Agent workflow tab group |
tabs | Querying, creating, selecting, moving, navigating, and closing tabs |
webNavigation | Keeping auxiliary targets opened from a workflow tab within the same workflow boundary |
windows | Inspecting and creating windows used by workflows |
ArcSolve Agent does not currently use the activeTab or clipboardWrite permissions.
The web-to-extension bridge declared in externally_connectable.matches is restricted to the single ArcSolve web origin https://arcsolve.ai/* in production builds. Staging packages use https://staging.arcsolve.ai/* only, and development builds may additionally include localhost. Production builds do not include staging.arcsolve.ai, www.arcsolve.ai, or localhost in this allowlist.
7. Remotely Rendered Code
ArcSolve Agent may display Markdown diagrams or sandboxed rich previews contained within ArcSolve workflow responses. The packaged Markdown renderer includes Markmap, Mermaid, KaTeX, and sandboxed preview code used for user-visible Agent responses. The current Agent Markmap path uses the packaged markmap-lib/no-plugins entrypoint and does not fetch executable Markmap assets from external package CDNs at runtime.
This renderer and preview path is limited to diagram and preview content that is visible to the user within the Agent UI. It is not used for browser automation, debugger actions, authentication, tab access, or background data collection.
Browser workflow automation is performed through declared Chrome extension APIs such as debugger, tabs, windows, tabGroups, and scripting, and through the ArcSolve Desktop native messaging host. OAuth tokens are isolated within the background service worker authentication flow. Sandboxed component / artifact previews run inside iframe documents that have no access to Chrome extension APIs and communicate with the host UI only through a restricted message protocol.
8. What ArcSolve Agent Does Not Do
ArcSolve Agent does not do any of the following.
- Automatically transmit page body content or screenshots to the server in the absence of a user-directed workflow
- Advertising, retargeting, or data sale
- Processing for credit evaluation or loan screening purposes
- Using user content as training data for AI models
- Continuous background crawling of websites that the user has not requested
- Intentional circumvention of website access controls, paywalls, CAPTCHAs, or anti-abuse systems
Cases in which a person reads user content are limited to specific situations such as the user’s explicit support request, security incident investigation, fulfillment of legal obligations, and aggregated or de-identified internal operations.
9. User Controls and Rights
Users may control data processing through the following methods.
- Decide directly whether to start an Agent workflow
- Stop a workflow or close the side panel
- Restrict site access through Chrome extension settings
- Refrain from running Agent workflows on sensitive sites
- Disconnect the ArcSolve Desktop connection
- Log out of ArcSolve or remove the extension
- Request access to, correction of, deletion of, or suspension of processing of personal information
For inquiries and to exercise rights, please contact [email protected]. Detailed procedures are governed by the Privacy Policy.
10. Related Documents
11. Chrome Web Store Reviewer Summary
This English summary is provided for Chrome Web Store review convenience. The Korean text above is the authoritative notice.
- ArcSolve Agent loads a content script on allowed sites, but page content is generated and transmitted when the user runs an Agent browser workflow or ArcSolve Desktop sends a same-machine browser-runtime request.
- Browser tool results may include tab context, page text, DOM/accessibility-like data, form fields, screenshots, console/network metadata, and operation results.
- Arc mode sends user instructions and tool results to ArcSolve services and configured AI providers. Desktop browser-runtime integration can relay browser tool requests and results through the ArcSolve Desktop native messaging host.
- For Markdown diagram and preview rendering, Agent uses a packaged renderer and sandboxed preview path. The current packaged Markmap path does not fetch executable Markmap CDN assets at runtime. Renderer and preview code is limited to user-visible diagram/preview rendering and is not used for browser automation, debugger actions, authentication, tab access, or background data collection.
- Sandboxed previews do not have Chrome extension API access and communicate with the host UI only through a limited message protocol.
- ArcSolve does not sell user data, use it for personalized advertising, or use user content to train AI models.
- Production builds allow only the single ArcSolve web origin
https://arcsolve.ai/*inexternally_connectable.matchesfor the web-to-extension bridge. Staging packages allowhttps://staging.arcsolve.ai/*only, and development builds may addlocalhost. This invariant is enforced by the release-gate diagnostic test (apps/arcsolve-extension-agent/tests/diagnostics/browser-runtime.diagnostic.test.ts). - Chrome Web Store data disclosures: Personally Identifiable Information, Authentication Information, Personal Communications, Web Browsing Activity, User Activity, and Website Content may be handled for user-started Agent workflows. Health, financial/payment, and location data are not collected as dedicated data categories.