Privacy Policy

Last updated 22 July 2026. Applies to the Job Fill browser extension.

The short version

Job Fill does not collect, transmit, or receive any of your data. Everything it stores stays in your own browser. There is no account, no server, and no analytics provider. The extension makes no network requests.

What the extension stores

All of the following is written to your browser's local extension storage (chrome.storage.local) on your own device, and nowhere else:

• Contact details you enter — name, email, phone, postal address
• Links you enter — LinkedIn, GitHub, portfolio, personal site
• Work history, education, and skills
• Work authorization answers and salary expectations
• Any resume file you upload, and text extracted from it
• Answers you save to application questions
• Corrections you record when a field is filled wrongly
• Applications you log to the tracker
• Demographic information (gender, race/ethnicity, veteran status, disability status) — only if you choose to enter it

None of this is sent anywhere. It is readable only by the extension, on the browser profile where you entered it.

Sensitive categories

Demographic and EEO information is treated as sensitive. It is optional, it is stored separately in the interface, and it is never written into any form unless you explicitly enable that in Settings. Leaving those fields blank means the extension has nothing to fill and will skip such questions entirely.

Resume files are stored as-is so they can be attached to file-upload fields. If a resume is a PDF, its text is read on your device to suggest values for your profile. That reading happens entirely within your browser; the file is not uploaded anywhere for processing.

What is transmitted

Nothing. The extension contains no code that sends your profile, resume, answers, or browsing activity to any server, including ours.

The extension includes an optional usage-statistics setting, disabled by default. No collection endpoint is configured, so enabling it currently causes events to accumulate in local storage and go nowhere. If a backend is ever added, it will be stated in the release notes and in an updated version of this policy, it will remain opt-in, and it would carry only event names, timestamps, the applicant-tracking platform in use, and counts of fields filled — never form content, resume content, or answers.

Permissions

storage

Saves your profile and settings in the browser.

activeTab and scripting

Allows the extension to act on the page in the current tab when you click Fill.

Host access to five domains

Greenhouse, Lever, Workday, iCIMS and Ashby. The extension requests access to these applicant-tracking systems specifically, rather than to all websites. On any other site it does not run and has no access to page content.

Third parties

There are none. The extension uses no analytics service, no advertising network, no error-reporting service, and no external APIs. It bundles the open-source PDF.js library to read resumes, which runs locally and makes no network requests.

If you install from the Chrome Web Store, Google collects installation statistics under its own policies. That is between you and Google; the extension neither controls nor receives that data.

Your control

• Export. Settings → Export everything as JSON produces a complete copy of your stored data.
• Delete. Removing the extension deletes everything it stored. Individual answers, corrections, and tracker entries can be deleted from the Settings page at any time.
• Verify. You do not have to take the claims on this page on trust. Open Chrome's DevTools on the extension's own pages and watch the Network tab while you use it: transmitting your data would require a network request, and you will see none. The extension is also distributed as readable JavaScript, so its behaviour can be inspected directly in the files you install.

Children

Job Fill is intended for job seekers and is not directed at children under 13. It collects nothing, from anyone, of any age.

Changes

If this policy changes materially — in particular if any data ever begins leaving your device — the change will be described in the release notes for the version that introduces it, and the date at the top of this page will be updated. Continuing to use an older version keeps its behaviour; nothing changes on your device until you install a new build.

Contact

Questions about this policy can be raised as an issue on GitHub.