Resume Gap — Privacy Policy

Last updated: 26 October 2026

What data is processed

Your resume files. PDFs you drop onto the "My resumes" page are read inside your browser, converted to text, and stored in chrome.storage.local. The file itself is never uploaded anywhere. Removing the extension deletes this data with it.

The posting you scan. Only when you press "Scan this page" is the text of the currently open tab read. That text stays in memory and is not saved, apart from the AI cache described below. Your browsing is not tracked in the background.

Your AI settings. If you enter an API key, it is kept in the same local storage. Browser storage is not encrypted; keep that in mind on a shared computer.

Data sent to third parties

In the default configuration, none. The dictionary-based comparison runs entirely in your browser.

If you enable the optional deep analysis — that is, if you enter your own API key — a trimmed version of your resume text and the posting text is sent to the provider you selected: Anthropic, OpenAI, Google, or an endpoint you define yourself. The request goes from your browser directly to them; there is no server of ours in between. How that data is handled on their side is governed by that provider's own privacy policy.

While this feature is off, no network request is made at all.

Cache

So that the same posting and the same resume are not analysed twice, the AI result is stored locally. This exists to stop you spending tokens you have already spent. The storage is still on your device; it does not leave.

Deleting your data

• A single resume: the × on its card on the "My resumes" page
• All of them: the "Delete all" button on the same page
• Everything: remove the extension from Chrome — the storage goes with it

Advertising, analytics, tracking

None of it. No analytics SDK, no pixel, no cookie, no usage telemetry.

Contact

Questions or reports: k.erenmaden1@outlook.com