ArcSolve Distill Privacy Notice
Effective Date: May 13, 2026
ArcSolve Distill is a Chrome extension that helps users read, clip, and save web pages, PDFs, and YouTube content as ArcSolve documents. This document describes how data is read, transmitted, stored, and retained in the course of using ArcSolve Distill.
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 only to the extent necessary to provide or improve the extension’s single purpose, and is not used for personalized advertising, data sale, or credit evaluation purposes.
1. Scope
This document applies to the ArcSolve Distill Chrome extension. Personal information processing for the ArcSolve web, desktop, and mobile applications, as well as for other extensions, is governed by their respective documents and the Privacy Policy.
2. Data Processed by Feature
| Feature | Data That May Be Processed | Purpose of Processing |
|---|---|---|
| Side panel current-tab synchronization | Current tab URL, title, document identifier, content type, resource metadata | Display the current page state and determine clipping eligibility |
| Page reading/copying | Web page body text, structured Markdown, links, image/video/audio URLs and metadata | Copying, summarization, document creation, page analysis |
| Selection clipping | Text and structure of elements selected by the user | Copying and documenting the selected region |
| Rectangle capture | The image region within the visible area of the active tab selected by the user | Clipboard copying |
| PDF processing | PDF URL, PDF file bytes, extracted text, page information | PDF viewing, extraction, upload, summarization, document creation |
| YouTube processing | YouTube URL, video ID, title, available subtitle languages, transcript text | Reading, summarizing, and documenting video content |
| ArcSolve account features | Login session, email, profile information, project/folder information | Authentication, selection of save location, ArcSolve API requests |
| AI features | User input, extracted text, document content, summarization requests, AI responses | AI summarization, chat, document processing |
| Local settings | Theme, accent color, font, side panel state, summarization cache | Maintaining the user’s environment |
Under the Chrome Web Store privacy disclosure categories, ArcSolve Distill may handle Personally Identifiable Information, Authentication Information, Personal Communications, Web Browsing Activity, User Activity, and Website Content. Personal Communications may apply only when the user directly summarizes, clips, saves, or parses pages that contain communications, such as webmail, chat, or DMs. Web Browsing Activity does not mean that the entire browsing history is stored; rather, it means that requested URLs, current/open tab URLs and titles, and page navigation events are processed within the scope of feature execution. Health Information, Financial and Payment Information, and Location Information are not collected as dedicated data categories of ArcSolve Distill.
3. When Data Is Read
ArcSolve Distill may read data in the following situations.
- When the user opens the side panel to view the current tab
- When the user executes page copy, selection clipping, rectangle capture, PDF opening, PDF upload, YouTube reading, link reading, “Add to ArcSolve,” or AI summarization
- When the user requests URL parsing through an allowed external connection from the ArcSolve web app
- When it is necessary to verify whether the requested URL matches an already-open tab, or to open a background tab in order to process a request
While the side panel is open, the URL, title, content type, and resource metadata analysis of the current tab may be refreshed automatically. By contrast, page body text, selected regions, PDF content, YouTube transcripts, and AI transmissions are processed only when the user invokes the relevant feature or when an allowed request is made from the ArcSolve web app.
4. When Data Is Transmitted and to Whom
| Trigger | Data That May Be Transmitted | Recipient | Purpose |
|---|---|---|---|
| Login and session verification | OAuth requests, token exchange data, account profile | ArcSolve Auth service and login provider | Maintaining login state, API authentication |
| Project/folder lookup | Authentication token, account-scoped request | ArcSolve API | Displaying save locations |
| Document creation/saving | URL, title, extracted text, selected content, PDF or YouTube transcript, user-entered notes | ArcSolve API, ArcSolve storage | Document creation and retention |
| PDF upload/extraction | PDF file or text extracted from the PDF | ArcSolve API, PDF processing infrastructure | PDF documentation and text extraction |
| AI summarization/chat | User input, page text, PDF/YouTube text, tool results | ArcSolve API and configured AI providers | Generating AI responses |
| YouTube transcript reading | YouTube URL or video identifier | YouTube/Google services or ArcSolve processing path | Reading the user-requested video text |
ArcSolve’s AI providers, infrastructure providers, and cross-border transfer matters are described together in the entrustment and cross-border transfer sections of the Privacy Policy. If a feature is not used, the data transmissions required for that feature do not occur.
5. Locally Stored Data
ArcSolve Distill uses Chrome extension storage for the following purposes.
| Storage Location | Examples | Retention Standard |
|---|---|---|
chrome.storage.sync | Theme, accent color, font settings | Until the user changes them or the extension is removed |
chrome.storage.local | Side panel open state, OAuth refresh token | Until logout, token revocation, or extension removal |
chrome.storage.session | OAuth access token, PDF viewer session, summarization cache | Until the browser session or task ends |
| ArcSolve servers | Documents, notes, extraction results, and AI results saved by the user | Until the user deletes them or the account is terminated. Items subject to statutory retention follow the Privacy Policy |
The PDF viewer session payload is removed after it is read by the viewer. The summarization cache is a short-lived cache that reduces duplicate processing when the user revisits the same page during use of the extension.
6. Permissions Summary
| Permission | Reason for Use |
|---|---|
<all_urls> host permission | Required in order to read arbitrary web pages, PDFs, YouTube pages, and links requested by the user |
activeTab | Performs user-requested capture and page actions on the currently active tab |
identity | ArcSolve login based on Chrome Identity |
storage | Storage of settings, sessions, tokens, and caches |
sidePanel | Display of the ArcSolve Distill side panel |
clipboardWrite | User-requested copying of text/images |
scripting | Guaranteed injection of content scripts, frame resource scanning, PDF.js loader injection |
webNavigation | Tracking page loads and frame state to keep current-tab analysis up to date |
7. Remote Rendering Code
ArcSolve Distill may render user-requested Markdown diagrams or AI-generated rich preview blocks within the extension UI. The production package bundles the Markdown renderer, including Markmap, Mermaid, KaTeX, and sandboxed preview runtime code. The current production path uses the no-plugins Markmap renderer and does not fetch external executable CDN assets at runtime, although CDN URL strings may remain in packaged renderer code as inactive loader or allowlist strings.
This path is limited to displaying diagrams/previews in the side panel Markdown viewer. It is not used for authentication, page parsing, clipping, background collection, browser automation, or token handling. ArcSolve OAuth tokens are isolated within the storage/session flow of the background service worker and are not provided to the diagram renderer, content scripts, or sandboxed preview frames.
When an interactive component/artifact preview is displayed, that preview runs inside a sandboxed iframe document that does not have access to Chrome extension APIs. This iframe communicates with the extension UI only through a limited-purpose message protocol covering rendering state, size, theme, and user-triggered prompts.
8. What ArcSolve Distill Does Not Do
ArcSolve Distill does not use user data for the following purposes.
- Personalized advertising, retargeting, or providing data to advertising networks
- Sale to data brokers or information resellers
- Credit evaluation, loan screening, or insurance screening
- Background web crawling unrelated to user requests
- Automatic account-side saving of every visited page that the user has not chosen to save
- Use of user content as training data for AI models
Human review of user content is limited to specific cases such as the user’s explicit support request, security incident investigation, performance of legal obligations, and aggregated/de-identified internal operations.
9. User Controls and Rights
Users may control data processing through the following methods.
- Restricting site access scope from Chrome extension settings
- Closing the side panel or disabling/removing the extension
- Choosing not to use the clipping, summarization, or upload features on sensitive pages
- Deleting documents saved in ArcSolve
- Logging out of the ArcSolve account or requesting account deletion
- Requesting access to, correction of, deletion of, or suspension of processing of personal information
For inquiries and exercise of rights, please contact [email protected]. Detailed procedures follow 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 Distill reads web pages, PDFs, YouTube transcripts, selected content, screenshots, and links only to provide user-facing clipping, document intake, and AI features.
- Current-tab metadata can be refreshed while the side panel is open. Full page text, selected content, PDF data, YouTube transcripts, and AI payloads are processed when the user requests the relevant feature or when an allowed ArcSolve web origin requests URL parsing.
- Data may be sent to ArcSolve services and configured AI providers to provide document creation, storage, summarization, and AI responses.
- For Markdown diagram and preview rendering, Distill uses packaged renderer and sandboxed preview code. The current production path does not fetch external executable CDN assets; CDN URL strings may remain in packaged JavaScript as inactive renderer or allowlist strings. ArcSolve conservatively discloses this renderer surface in Chrome Web Store review. This path is limited to diagram/preview display and is not used for authentication, parsing, clipping, browser automation, background monitoring, or token handling.
- 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.
- Chrome Web Store data disclosures: Personally Identifiable Information, Authentication Information, Personal Communications, Web Browsing Activity, User Activity, and Website Content may be handled for the requested Distill workflow. Health, financial/payment, and location data are not collected as dedicated data categories.