Privacy Policy for Jobweave (Chrome Extension)

• Your Jobweave connection token. A token you generate yourself in the Jobweave web app (Settings → MCP Connections) and paste into the extension. It authenticates the extension as you against your own Jobweave account.
• The URL of the page you're viewing, whenever you switch to a new tab or page while the extension is open — used to check whether that page is already tracked, and whether it looks like a job posting worth an auto-detected summary card.
• Whether the page you're viewing has job-posting markup on it— a yes/no check that runs automatically, on pages whose URL doesn't already look like a job posting, to decide whether to show that same auto-detected card. This check never leaves your device: the result is a single yes/no value used only by the extension itself.
• The rendered markup of the page you're viewing, only when the extension actually extracts a job posting — either because you clicked “Scrape this page,” or because auto-detection decided the page looked like one — and only if Jobweave's first attempt (fetching the page itself) came back empty, the common case for a job board that builds its page with JavaScript.
• Contact details from your linked resume (name, email, phone, location, LinkedIn, website, GitHub), only when you click “Autofill this form” — fetched from your Jobweave account and written into the current page's form fields.

The extension only reads a page's URL and checks it for job-posting markup — it never reads or sends the page's actual content — unless you either take an explicit action (Scrape/Autofill) or automatic detection decides the page is a job posting worth extracting. It never reads anything from a page you aren't currently viewing.

The connection token is the only thing stored by the extension, in chrome.storage.local — on this device only. It is never synced through chrome.storage.sync or any Google account.

Nothing else is stored persistently. A scraped page's URL/markup and an autofilled resume's contact details exist only in memory for the duration of that one action and are discarded immediately after. What a job posting's URL was found to contain is kept in memory for as long as the browser keeps the extension running, purely to avoid re-reading a page you've already visited — never written to disk, and cleared automatically whenever the browser reclaims that memory.

Every use above exists to do exactly what its feature name says: track a job application, check if one already exists, fill a form, or draft an outreach message. Nothing is used for advertising, analytics, or any purpose beyond the feature you triggered.

None. The extension talks to exactly one backend: your own Jobweave account (the Jobweave web app and its MCP server, both operated by Jobweave). No analytics, no ad networks, no third-party APIs.

Nothing is shared with any third party. Data flows only between your browser and your own Jobweave account.

The connection token is removed the moment you sign out in the extension, or the moment the extension is uninstalled (chrome.storage.local is extension-scoped and is cleared with it). Nothing else is retained anywhere.

If what the extension collects or how it's used changes, this policy will be updated and the “Last updated” date above will change accordingly.

catesandrew@gmail.com