Chrome Extension

Privacy Policy

Job Application Assistant

Effective date: March 12, 2026 · Last updated: March 12, 2026

💡 Summary

      Short version: This extension processes data entirely on your own machine. Nothing you type, upload, or analyze is ever sent to our servers — because we don't have any. The only outbound connection is to a local proxy server you run yourself at 127.0.0.1:3737.
    

This policy explains in full what data the extension accesses, where it goes, and how it is stored.

📋 What Data Is Accessed

The extension accesses the following data, strictly to provide its core features:

Data	When accessed	Purpose
Active tab page content	Only when you click Analyze Current Page	Extract job posting text for AI analysis
Resume text or file	Only when you paste or upload it	Match your experience to the job requirements
Settings you enter	When you save settings	Remember your provider, model, and proxy URL preferences
Proxy token	When you save settings	Authenticate requests to your local proxy server

🔒 Where Your Data Goes

All data stays on your machine. The extension makes exactly one type of outbound request: an HTTPS-equivalent call to your local proxy server at http://127.0.0.1:3737 — a server you install, run, and control.

No data is sent to our servers (we have none).
No data is sent to any analytics, advertising, or tracking service.
Job posting content and resume text travel only to 127.0.0.1 (your loopback address).
Your proxy server then forwards requests to the AI provider you configure — under your own API credentials.

      The AI provider that receives your data is determined entirely by your own proxy configuration, not by this extension.
    

💾 How Data Is Stored Locally

The extension uses Chrome's built-in storage APIs. No data is written to external databases or file systems.

Storage	Contents	Lifetime
`chrome.storage.local`	Settings (provider, model, proxy URL, temperature), parsed resume analysis, encrypted proxy token ciphertext	Until you clear it via Settings → Clear Cache, or uninstall the extension
`chrome.storage.session`	AES-256-GCM encryption key for the proxy token, cached job analysis results, background task status	Cleared automatically when the browser closes

🔑 Proxy Token Security

The proxy token you enter is never stored in plaintext. It is encrypted using AES-256-GCM before being written to disk:

The encryption key lives only in chrome.storage.session — cleared when the browser closes.
The ciphertext lives in chrome.storage.local — unreadable without the session key.
The token is never rendered into the page DOM.
After a browser restart, you are prompted to re-enter your token.

🌐 Third Parties

This extension has no relationship with any third-party service. We do not integrate any analytics SDK, ad network, crash reporter, or telemetry library.

If your local proxy forwards requests to an AI provider (OpenAI, Anthropic, Google, etc.), that provider's own privacy policy governs how they handle the content you send. You configure this on the proxy side — the extension is unaware of which provider your proxy uses.

🛡️ Chrome Permissions Used

activeTab — Read the current tab's content when you click Analyze, scoped to that single tab and action.
scripting — Execute a text-extraction function in the active tab to retrieve job posting content.
tabs — Query the active tab's URL to key the session cache per page.
storage — Persist settings and cached results using Chrome's local and session storage APIs.

The extension also declares host permission for http://127.0.0.1:3737/* and http://localhost:3737/* to communicate with your local proxy. No other host permissions are requested.

👶 Children's Privacy

This extension is intended for job seekers and is not directed at children under the age of 13. We do not knowingly collect any information from children.

📝 Changes to This Policy

If this policy changes materially, the updated version will be published at this URL with a new effective date. Continued use of the extension after a policy update constitutes acceptance of the revised policy.

✉️ Contact

Questions about this privacy policy? Open an issue on the project's GitHub repository or reach out via the Chrome Web Store listing page.