Context Pilot — Privacy Policy

Effective date: July 2026

Single purpose: Context Pilot is an AI-conversation efficiency toolkit. Every feature exists to help you use fewer tokens, keep less context, and move conversations between AI chat tools (Claude, ChatGPT, Perplexity, Grok, Gemini) faster — Caveman Mode compresses replies, the usage tracker shows how much you're using, Continue Elsewhere carries context between tools, Prompt Power-Ups speed up common prompts, and the PDF converter gets outside documents into a chat efficiently. All five features serve that one purpose; none of them do anything unrelated to it.

Summary

Question	Answer
Does Context Pilot send your data to the developer's servers?	No. Context Pilot has no backend server. It never has.
Does it use analytics, ads, or trackers?	No.
Does it sell or share data with third parties?	No, never, under any circumstance.
Does it load any remote code?	No. All code ships inside the extension package (enforced by its Content Security Policy, `script-src 'self'`). Nothing is fetched and executed from the internet.
Where is data stored?	Only in your browser, via `chrome.storage.local`. It never leaves your device except to the AI platform you're actively using.

What Data Is Collected and Why

Data	Purpose	Where it's stored
Message counts and estimated token counts per platform, per day	Powers the Usage Today stats in the popup and options page	`chrome.storage.local`, until you clear it or uninstall
Feature toggle states (Caveman Mode on/off, Continue Elsewhere default scope)	Remembers your preferences between sessions	`chrome.storage.local`
Prompt Power-Ups snippet library	The bundled list of prompt templates shown in the popup	`chrome.storage.local`, loaded once from a file bundled in the extension
Conversation text you choose to transfer via "Continue Elsewhere"	Carries your conversation to the destination AI tool	Staged in `chrome.storage.local` for a maximum of 5 minutes while the destination tab opens, then automatically deleted. See "Continue Elsewhere" below.
Your organization ID on claude.ai (from the `lastActiveOrg` cookie)	Required to call Claude's own usage API for accurate usage bars	Not stored — read fresh from the cookie each time, used only to build a request URL to claude.ai

What Is Never Collected

No conversation content is ever sent anywhere except to the AI platform you're already talking to.
No account credentials, passwords, API keys, or session tokens are read, stored, or transmitted.
No browsing activity outside the five supported AI chat domains is observed.
No personally identifying information (name, email, IP address, device ID) is collected by the extension.
No data is used for advertising, retargeting, or building any kind of user profile.

Feature-by-Feature Data Handling

Caveman Mode

Appends a compression instruction to your own message before it's sent, entirely inside your browser. It doesn't read, store, or transmit anything beyond the message you were already about to send.

Usage Tracker

Counts messages you send and estimates token usage locally, purely from text already in your browser tab. On claude.ai specifically, it additionally reads Claude's own usage API response (see "Native Usage Tracking on claude.ai" below) for exact numbers instead of estimates.

PDF to Markdown

Runs entirely on your device using the bundled pdf.js library. No PDF file or its contents are uploaded anywhere. The converted text lives only in the popup's memory and disappears when you close the popup, unless you choose to download it or insert it into a chat yourself.

Prompt Power-Ups

Matches keywords you type against a bundled local list of prompt templates to suggest one. No text you type is sent anywhere for this matching — it happens in-browser.

Continue Elsewhere

When you choose to transfer a conversation, the extension reads the current conversation (your own data, already loaded in your logged-in session — via Claude's native API on claude.ai, or the visible page text on other platforms), formats it, and hands it to the destination tab you're opening. Because the destination page needs a moment to load before it can receive the text, the formatted conversation is held in chrome.storage.local for up to 5 minutes, scoped to that specific new tab, and is deleted immediately once delivered (or automatically after 5 minutes if never delivered). This is the only case where conversation text touches persistent storage, and it never leaves your browser — no server is involved.

Native Usage Tracking on claude.ai

On claude.ai only, Context Pilot reads Claude's own API responses — using your existing logged-in session and your browser's normal network requests — to show exact (not estimated) session and weekly usage bars, a token count, and a prompt-cache countdown next to the chat input. This includes:

Reading the lastActiveOrg cookie (via document.cookie, not a special browser API) to identify which organization's usage to request.
Requesting Claude's /api/organizations/{orgId}/usage endpoint directly from your browser, and reading the usage data Claude's own page already streams to itself.
Computing an approximate token count locally using a bundled tokenizer (gpt-tokenizer, MIT licensed) — no text is sent anywhere for this calculation.

Every one of these requests goes only to claude.ai, using your existing session, only while you're on claude.ai. None of it reaches Context Pilot's developer or any third party. This technique is the same approach used by the open-source Claude Counter extension.

Content Scripts and Technical Resources

Content scripts run only on these domains:

claude.ai
chatgpt.com / chat.openai.com
perplexity.ai
grok.com / x.ai
gemini.google.com

On chatgpt.com, perplexity.ai, grok.com/x.ai, and gemini.google.com, these scripts read DOM elements already visible on the page (the chat input box, message bubbles, rate-limit banners) to power the extension's features, and do not intercept network requests on those sites. On claude.ai, an additional script reads Claude's own network responses as described above.

Two files are marked as "web accessible resources," meaning a web page can request to load them directly:

lib/pdf.min.js and pdf/pdf.worker.min.js — the bundled PDF-parsing library, exposed so the extension's own popup page can load it. It does not run on any site automatically.
content/native/claude-bridge-injected.js, exposed only to claude.ai — the script that reads Claude's usage/conversation API responses described above.

Permissions — What Each One Is For

Permission	What it's used for
`storage`	Saves your settings and local usage stats in `chrome.storage.local`, described above. No cloud sync.
`activeTab`	Lets the popup read the URL of your current tab only when you click the extension icon, solely to check whether it's a PDF file (for "Convert Current Tab") or one of the five supported AI platforms (to show platform-specific controls).
`scripting`	Injects the bundled PDF-parsing script into the current tab only after you click "Convert Current Tab" — never automatically, never on page load.
`host_permissions` (claude.ai, chatgpt.com, chat.openai.com, perplexity.ai, grok.com, x.ai, gemini.google.com)	Required so the extension's content scripts can run on each of the five AI chat platforms it supports — reading the chat input and message DOM, and, on claude.ai only, reading Claude's own API responses. The extension does not request access to any other site.

Data Retention and Deletion

Settings and usage stats persist in chrome.storage.local until you clear them from the Options page ("Clear All Usage Data") or uninstall the extension, either of which deletes everything immediately. The one exception is Continue Elsewhere's temporary transfer buffer, which self-deletes within 5 minutes regardless of any action on your part, as described above.

Compliance Statement

Context Pilot collects and uses only the data described on this page, strictly for the features described above. Nothing is sold, rented, or shared with advertisers, data brokers, or any third party for any purpose. No Context Pilot employee or developer has access to any data described here — it never leaves your browser to reach us in the first place.

Changes to This Policy

If this policy changes in a way that affects what data is collected or how it's used, the updated version will ship with the next extension update and be reflected on this page with a new effective date.

Contact

For questions about this privacy policy, contact us via Ask About AI.