AnonymizeDocs
FeedbackLog in

Solutions · Recruiting privacy workflow

Focused workflowUpdated Aug 14, 2026

Anonymize resumes before AI screening.

Open each resume in your browser, review names and contact details plus any links or identifiers, replace accepted values, verify the export, then screen the anonymized copies.

Local-first Reviewable Verified export

Try it free See the workflow

A local resume review workspace for preparing CVs before AI screening
Original stays on this device
For recruiters, HR teams and hiring managers who use AI to screen or compare candidates.

Why this workflow matters

Keep the useful context. Remove the unnecessary identity.

Resume screening with AI should focus on skills and experience, not on who the candidate is. AnonymizeDocs removes names, contact details and social links locally, then lets you compare reviewed copies.

The goal is a working copy that still makes sense to an AI tool: relationships stay consistent, while accepted names, contacts, addresses and document-specific identifiers become controlled replacements.

A practical sequence

From original file to AI-ready copy.

Four checkpoints
01

Select resumes locally

Choose each PDF or DOCX resume from your device. Originals are never uploaded.

02

Review candidate identifiers

Check names, emails, phone numbers, addresses and social or portfolio links before replacement.

03

Keep skills and history readable

Work history, education, skills and certifications remain visible so AI can compare candidates fairly.

04

Verify and export

Recheck each output, download the anonymized copies, then screen them with the AI tool.

Document-specific review

What gets checked before export?

The detector suggests candidates; you decide what changes. For this workflow, start with the fields below and add custom findings when the document contains a unique name, project, matter or identifier.

Candidate names and aliases Emails, phone numbers and addresses Social profiles, portfolio and personal links Custom values you add for a specific role

Privacy boundary

What stays on your device.

  • The original resumes are not uploaded to AnonymizeDocs.
  • Extracted text, findings and replacements remain in the browser session.
  • Account and purchase data are separate from document content.

Human checkpoint

What still needs your judgment.

Redaction is a preparation step, not a diversity or compliance tool; recruiters remain responsible for fair and lawful screening decisions.

A verified export confirms accepted values were handled. It does not promise that an automated detector found every sensitive detail.

Illustrative before-and-after document preparation workflow

What a useful output looks like

Readable enough for analysis. Safer to share.

Stable placeholders let the AI distinguish one party from another without receiving the original names. Keep the clauses, dates and relationships the task needs; replace the details that identify the people, companies or matter.

Original identity-bearing valuesReview accept, ignore or editOutput reviewed placeholders or permanent redaction mode

Before you share the copy

Questions people ask about this workflow.

Can AI still compare candidate experience after redaction?

Yes. Work history, education, skills and certifications stay visible while identifying details become placeholders.

Can I anonymize a batch of resumes?

Yes. Process each resume locally and download the reviewed copies; no file leaves the device.

Does this remove social links from resumes?

Links are detected as findings and can be replaced along with names and contact details.

Continue with the right depth

Related workflows and guidance.

For recruiters

CVs, candidate notes and hiring documents prepared for AI without uploading originals.

Redact HR records

Onboarding forms and personnel notes with employee identifiers removed locally.

Supported files

Which PDF and DOCX features are handled locally.

Core workflow

Redact a PDF before ChatGPT — then verify the copy.

Prepare an AI-ready PDF in your browser by reviewing names, contacts, addresses and identifiers, then verify the exported copy before uploading it.

Core workflow

Redact a DOCX before ChatGPT: text, images and export.

Prepare a Word document for ChatGPT by reviewing text, tables, headers, footers and embedded images locally before sharing a verified copy.

Core workflow

Offline-ready document redaction in your browser.

Cache the browser processing resources once, disconnect if needed, and review supported PDF or DOCX findings on your device before AI upload.

Local document workspace

Review your next file in the browser.

Keep the original local, make the decisions yourself, and export a copy you can inspect.

Try it free