Where your CV goes
Short version: your CV is processed in memory and never stored. No accounts, no database, no cookies, no analytics scripts. Below is every service that touches it, what each one receives, and what persists. When this behavior changes, this page changes in the same release.
The register
Cvlinter API (Fly.io) · runs the checks
Your browser uploads the CV file straight to our API in Amsterdam. Parsing, scoring, lint, matching, and the PDF export all happen in memory there. No database, nothing written to disk. Results are held briefly in server memory so repeat requests for the same CV don't re-run, then evicted.
Affinda · parses the file
The same commercial parsing engine real ATSs use. We send your CV file to Affinda's EU servers and ask them to delete the document as soon as the parse returns. We keep the extracted fields in memory only.
Anthropic · classifies wording
Three features send text to the Claude API: content lint sends your bullets and summary for classification, JD matching sends the job posting you pasted plus your bullets, and the fix flow sends one flagged sentence with the answers you typed. Anthropic does not train models on API data. The output schemas carry classifications or one revised sentence, nothing else.
Vercel · serves this site
Hosts the pages you're reading. Your CV never passes through it: the upload goes from your browser directly to the API.
What we record
One log line per parse: which checks fired and how often, section scores, file type, duration. Never the CV's content, your name, employers, skills, or the filename. A test pins this: CV content in a telemetry line fails the build. Like any web service, our hosts also keep short-lived infrastructure logs (IP addresses, timestamps). Our rate limiting counts requests per IP in memory and writes nothing.
What lives in your browser
Your theme choice, in localStorage. That's the complete list. Your report exists only on your screen: reload the page and it's gone, along with any fixes you approved.
What we never do
- Store your CV, on disk or in a database.
- Use your CV to train anything.
- Share it with anyone beyond the services listed above.
- Set cookies or load third-party trackers.