Privacy Policy — Chrome extension

Last updated: August 3, 2026

This page covers the PageVeyor Chrome extension only. Google Drive storage, the drive.file scope, and the fact that no data passes through PageVeyor servers are described in the privacy overview, which applies to both products. For the Android app, see the app policy.

Data you provide

PDF files you upload, add by URL, or open from your Drive library
PDF page images and extracted page text used for analysis
AI-generated page notes, and the analysis output language you choose
Your library structure — folders, documents, and trash
The API key for your chosen AI provider, an optional custom model name, and an optional API Base URL
Google account authorization used to reach your Drive

Storage in your browser

API keys. Your key is stored in chrome.storage.local as AES-GCM ciphertext only. The encryption key is a non-extractable CryptoKey held in IndexedDB, so the key material cannot be read out of the browser — not by the extension, and not by anything reading the profile's files.
Settings. Provider, model, optional custom API Base URL, analysis output language, display language, and the connected Drive folder are stored in chrome.storage.local in plain form. None of them are secrets.
PDF cache. Downloaded PDFs are cached in an IndexedDB database named pageveyor-pdf-cache so reopening a document does not re-download it.
Analysis progress. When you analyze a whole document, progress checkpoints are stored locally so an interrupted run can resume.

Browser permissions and why they are needed

identity — signing in to Google to obtain a Drive access token
storage — the settings and encrypted key described above
sidePanel — showing PageVeyor in Chrome's side panel
tabs — detecting whether the current tab is a PDF, so you can analyze what you are already viewing
Access to googleapis.com for Drive, and to the AI endpoints generativelanguage.googleapis.com, api.openai.com, and api.anthropic.com (or any custom API Base URL you explicitly configure and grant permission to)
Access to other sites is not granted at install time. When you add a PDF by URL or configure a custom API endpoint, the extension asks Chrome for permission to that specific origin at that moment, and you can decline.

The Google Picker helper page

Chrome extensions cannot load Google's Picker script directly, so choosing your Drive folder opens a small helper page hosted at pageveyor.com/picker.html in a popup window. The extension passes your Google access token to that page over postMessage — never in the URL — and the page uses it solely to render Google's own file picker. The token is not stored, logged, or sent anywhere else, and both sides verify each other's origin before exchanging anything. The page returns only the folder you picked.

AI providers

The extension uses your own API key (BYO-key). When you analyze a page, its extracted text, a trimmed amount of surrounding page context, and the rendered page image are sent to the provider you selected:

Google Gemini
OpenAI
Anthropic

Requests go from your browser straight to that provider's API, never through a PageVeyor server. Because you supply the key, usage is billed to your own provider account and is governed by that provider's privacy policy and terms.

Deleting your data

Removing the extension from Chrome deletes everything it stored in your browser — settings, the encrypted API key and its encryption key, the PDF cache, and analysis checkpoints.
You can disconnect from Drive inside the extension, which clears the stored folder link and the cached PDFs.
Content synced to Drive is removed by deleting the PageVeyor folder in your Google Drive, or by revoking PageVeyor's access from your Google account.

Contact

For privacy questions: support@pageveyor.com