Skip to main content
Private

Privacy Policy by Architectural Design

This Privacy Policy explains how our resume keyword scanner handles your data. The short answer is: we do not collect it, we do not process it on our servers, and we do not have access to it. Our privacy architecture is built on technical isolation, not legal promises.

1.1 Public Site Analytics & Future Advertising

The public website currently uses Google Analytics to understand page visits and improve navigation. Analytics may process technical information such as a page URL, browser details, approximate location, and a pseudonymous identifier according to Google's own policies. The resume, job description, editor contents, local AI prompts, and analysis results are not sent to Analytics by the application.

If advertising is introduced, this policy will be updated before ad code is deployed to explain the advertising cookies, third-party vendors, and available privacy choices. The interactive workspace will continue to keep document content in the browser unless the product clearly says otherwise.

1. Zero Server Logs & Zero Data Collection

This website does not use tracking databases, external server processing, or server logs for your text document files. When you paste your resume or upload a PDF or DOCX file, the file contents are read entirely inside your browser. Our web servers never receive the text, never store the document, and never log the filename. There is no user registration system, no authentication cookies, and no analytics beacon capturing your resume content.

Standard web server access logs may record the HTTP request path and timestamp for security purposes, but these logs do not contain your resume text, job descriptions, or any content you enter into the application interface. We do not sell, share, or monetize user data because we do not have user data.

2. Strictly Local Browser Processing

All document parsing and keyword analysis is executed strictly inside the visitor's secure browser runtime context. We use well-established open-source client-side libraries for this purpose:

  • mammoth.js — Parses DOCX files into plain HTML/text directly in the browser.
  • pdf.js (Mozilla PDF.js) — Extracts text from PDF files using a local JavaScript worker.
  • Native JavaScript string processing — Tokenizes job descriptions, weights keywords, and computes match scores using in-memory arrays.

These libraries operate entirely within your browser's same-origin sandbox. They do not make outbound network requests with your document content. The parsed text exists only in your device's RAM for the duration of your session.

2. Local Browser Storage

All session history, draft resumes, target job descriptions, and custom notes are stored locally on your device using Web Browser IndexedDB and localStorage. Clearing your browser data completely removes all stored workspace content.

3. WebLLM Local AI Privacy

If you choose to use our optional AI resume bullet rewriter, AI models are cached into your browser’s IndexedDB via WebGPU / WebLLM. AI inference runs 100% offline on your device GPU/CPU. No prompt data is sent to external API endpoints.

4. Standard Privacy Analytics

We use lightweight, privacy-focused web analytics solely to measure aggregate site performance and visitor metrics (e.g. page views, country of origin). Analytics scripts do not capture or record candidate document contents or personal information.

5. Third-Party Advertising & Cookie Disclosure

We may partner with third-party advertising networks, such as Google AdSense, to display advertisements on public pages of our website. Third-party vendors (including Google) use cookies, including the DoubleClick DART cookie, to serve ads based on a user's prior visits to our website or other websites on the Internet.

Google's use of advertising cookies enables it and its partners to serve ads to users based on their visit to our site and/or other sites on the Internet. You may opt out of personalized advertising by visiting Google Ad Settings or by visiting aboutads.info.

6. Contact Us

If you have any questions about this privacy policy or our technical architecture, please contact us via our secure Contact Page.

Last updated: August 2026