Privacy

Your resume stays on your device.

The privacy boundary is enforced by the architecture and browser policy, not a marketing promise.

Browser processing

The browser app reads the selected file into a dedicated Web Worker. Parsing and report generation happen in memory on the device.

The site has no backend, upload route, login, advertising, analytics, telemetry, remote model, error-reporting SDK, or third-party script.

Network policy

Every public HTML page sends this browser policy:

connect-src 'none'

This blocks fetch, XMLHttpRequest, WebSocket, EventSource, and related connection APIs. The app cannot send a resume or job description to a server through those mechanisms.

Normal navigation links still work when a user clicks them. Scanning does not require a connection after the static files have loaded.

Storage and reports

ATS Readback does not use cookies, IndexedDB, localStorage, or sessionStorage for resume data. Reloading the page clears the in-memory result.

Downloaded JSON, Markdown, and HTML reports contain extracted resume text and may contain contact details. Treat them like the original resume.

CLI processing

The command-line package reads local files and writes to standard output or an explicitly selected output file. It contains no telemetry or network call.

Verify the claim

The complete browser app, worker, parser, build scripts, and tests are public. The strongest privacy guarantee is not a promise on this page; it is the small, inspectable code path and the browser policy that blocks connections.