Privacy Policy

• Loopback only. The extension opens a WebSocket to ws://127.0.0.1:<port> — your own desktop app, on your own machine. It has no remote backend and contacts no third-party server. Its only host permission is 127.0.0.1 (loopback); it grants no access to any public or LAN address.
• Import via URL sends just the current tab's job URL to the local app, which fetches and parses it.
• Scan page captures the current page's rendered DOM only when you click "Scan page", and sends that HTML only to the local app (for logged-in pages a headless fetch can't reach). Nothing is captured in the background or on page load.

• activeTab — read the URL and (in Scan mode) the DOM of the tab you clicked, only on that click. No standing access to any site.
• storage — store the pairing token locally so you only pair once.
• scripting — MV3 requires this to inject the Scan-mode capture on demand; its reach stays limited to the active tab.

No broad host access (<all_urls>), no tabs permission, no webRequest, no remotely-hosted code, no eval. Everything is bundled at build time.

The only value the extension persists is the pairing token — a one-time secret you copy from the app's Settings — kept in chrome.storage.local. It is used solely to authenticate to your local desktop app and is never sent to any remote server. No telemetry, no analytics, no external API.

When you run an AI feature (tailoring a résumé, analysing a job, writing a cover letter), the app sends the relevant résumé / job-posting / cover-letter text to the AI provider you choose and configure, authenticated with your own API key.

• Local models — Ollama runs models on your own machine (default; keyless, nothing leaves the computer).
• Cloud providers — OpenAI, Anthropic, Google Gemini, Ollama Cloud, and any OpenAI-compatible endpoint (LM Studio, OpenRouter, Groq, Together, DeepSeek, Azure, etc.) via a base URL you set.
• Local CLI agents — Claude Code, Codex, and the Gemini CLI, run as child processes under your own logged-in CLI.

When you pick a cloud provider, the content you generate over is sent to that provider and is governed by that provider's own privacy policy and terms — not by us. We are not a party to that exchange; the request goes straight from your machine to the provider you chose, under your key. If you stay on a local model (Ollama), that text never leaves your computer.

To rank job matches the app computes embeddings for your résumé and the postings. By default these are computed locally with Ollama (nomic-embed-text), so the text stays on your machine. If you explicitly configure a cloud provider for embeddings, the same "your text → your chosen provider, under your key" disclosure above applies.

To find and import jobs, the app makes outbound requests to the job boards you search. Most boards (e.g. Greenhouse, Lever, Workday) are fetched over plain HTTP; aggregators that need a real browser session (e.g. LinkedIn, Indeed, Glassdoor) are driven through a local Chromium instance using a per-board profile so your login persists on your machine. These requests go to the job boards themselves — not to us. We run no proxy or intermediary; there is no AI Job Hunter server in the path.

Résumés, job and application history, embedding vectors, and settings are stored locally on your machine, in the operating system's standard per-application data directory. Secrets — AI provider API keys and saved board passwords — are kept in your operating system's keychain / credential store, never in plain-text files. None of this is uploaded anywhere by the app.