ArcSolve Translate Site Access and Permissions

Effective Date: April 11, 2026

ArcSolve Translate Chrome Extension uses website access permissions to detect PDF links and load PDFs from arbitrary domains in its built-in viewer. This document explains what permissions are used and why.

ArcSolve Translate was previously referred to as ArcSolve Light in some legacy documentation or store materials.

1. Purpose of This Document

This document explains:

What ArcSolve Translate does
Why it needs website access
What it reads during PDF detection
When PDF text is translated
How users can control access

2. What ArcSolve Translate Does

ArcSolve Translate provides the following features:

Detect PDF links or PDF-like embedded resources on web pages
Show a lightweight viewer trigger when a PDF is detected
Open PDFs in a built-in viewer
Render PDF pages using PDF.js
Extract PDF text in the browser
Translate PDF text when the user explicitly requests translation
Cache translation results only for the browser session

3. Why `<all_urls>` Is Required

ArcSolve Translate uses host_permissions for <all_urls> because PDFs may be hosted on arbitrary domains. Chrome requires host permissions before the extension can detect PDF links, inspect PDF-related element attributes, or load PDFs in the built-in viewer.

The permission is broad because PDF sources can be broad. The extension’s use is narrow: PDF detection, PDF viewing, PDF.js loader injection, and user-requested PDF translation.

4. What Is Read During PDF Detection

During PDF detection, ArcSolve Translate reads only the minimal page structure needed to determine whether a PDF is present, such as:

Element tags
Link href attributes
Embedded object or iframe sources
MIME type or URL patterns associated with PDFs

PDF detection does not read the full page text, collect page content, or transmit data.

5. When PDF Text Is Transmitted

PDF text is transmitted only when the user explicitly requests translation.

Feature	Data Transmitted	Destination	Trigger
PDF translation	Extracted PDF text and target language	Google Translate API (`translate.googleapis.com`)	User requests translation

If the user only detects or views a PDF, PDF text is not transmitted to Google Translate.

6. Permissions Used by ArcSolve Translate

Permission	Purpose
`host_permissions` (`<all_urls>`)	To detect PDF links and load PDFs from arbitrary domains
`scripting`	To inject the PDF.js loader script when the user opens a PDF in the viewer and to reconnect content scripts if needed
`storage`	To store ephemeral viewer session data and session-scoped translation cache

ArcSolve Translate does not use these permissions for advertising, hidden tracking, analytics, or unrelated background data collection.

7. What ArcSolve Translate Does Not Do

ArcSolve Translate does not:

Read full page text unrelated to PDF detection
Collect browsing history
Require user accounts
Collect analytics or telemetry
Use user content to train AI models
Send PDF text to Google Translate unless the user requests translation
Store PDF content persistently
Automate browser actions

8. User Controls

Users can control access by:

Restricting site access in Chrome extension settings
Choosing not to use translation
Closing the browser to clear session-scoped cache
Disabling or removing the extension

10. Summary

ArcSolve Translate uses website access so it can detect and load PDFs from arbitrary domains. It reads minimal page structure for PDF detection, renders PDFs locally, and transmits PDF text only when the user explicitly requests translation through Google Translate.

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