RezumateSomewhere in your job search, someone told you to run your resume through an "ATS checker." You found a free one, uploaded your PDF, and got a score. Fair trade, right? Before you do that again, it's worth actually looking at what's inside that file — because it's more than the text you see when you open it.
Your resume file is not just text
A resume is either a PDF or a DOCX, and both formats carry more than the words on the page.
A DOCX file is a zip archive. If you rename one to .zip and open it, you'll find a folder of XML files, including docProps/core.xml, which routinely stores the document author's name, the company the template was created under, and a revision/edit count. If you built your resume by copying an old one from a previous job and editing it, that metadata sometimes rides along — occasionally including a previous employer's name in the "company" field, left over from a template.
A PDF has its own metadata block (the /Info dictionary, or newer XMP metadata) that can store the creating application, author, and creation/modification timestamps. It's usually harmless — but it's also usually never scrubbed, because most people don't know it's there.
Where the file actually goes when you "check your ATS score"
Here's the part that matters more: when you upload that file to a free resume checker, the file leaves your device, travels to a server, and gets stored somewhere, at least temporarily, so it can be parsed and scored. That's true even for well-intentioned tools. A few questions worth asking before you upload anywhere:
- Is this resume stored after the score is generated, or deleted immediately?
- Is my contact information (name, phone, email, address) used for anything beyond scoring?
- Does the privacy policy actually say, in plain language, what happens to the file?
- Is the "free" score a lead magnet for a recruiting or resume-writing upsell?
Many free ATS checkers are, structurally, lead-generation funnels. That's not necessarily malicious — it's just the business model — but it means your resume, with your full career history and contact details, is the product being processed to generate a lead, not just a document being scored.
What "processed locally" actually means, technically
The alternative is parsing and scoring the file entirely on-device — no upload step at all. Concretely, that means: the app reads the text layer straight out of the PDF or DOCX using local system libraries, runs keyword extraction and scoring in-process, and never opens a network connection to send the file or its extracted text anywhere. There's no server log of your resume because there's no server in that path. If you turn off Wi-Fi and cellular data, the analysis still works, because it never needed the network to begin with — a decent practical test if you want to check any tool's claim, not just ours.
What to actually do with this
You don't need to panic-scrub metadata from every resume you send. But it's reasonable to:
- Save your resume as a fresh export from a template, rather than editing a decade-old file in place.
- Read the privacy policy of any "free checker" before uploading, specifically the retention section.
- Prefer tools that explicitly process on-device, or that you can test with the network off.
- Treat your resume with the same caution you'd treat a document that lists your full address and phone number — because it is one.
I built Rezumate around this exact idea: it does resume parsing, ATS-style scoring, keyword matching, and bullet rewriting entirely on your iPhone, without uploading the file anywhere.