Blind CVs in one click, not one evening of manual redaction.
One-click anonymization for public tenders, blind recruitment processes, and competitive bids - the same rules applied to every CV, every time.
What it does
The tender says candidate CVs must be anonymized. So the night before submission, someone works through 14 documents deleting names, photos, and employer references by hand - and misses the consultant's surname in a page footer, or the client name buried in a project description on page 3. One missed field can void a submission in a blind evaluation, and manual redaction gives you 14 chances to miss one. MagicCV makes anonymization a property of the export, not a task. Toggle it on any CV or full team pack and identifying details are stripped according to rules you configure - names, photos, and whichever other fields your process treats as identifying. The same rules apply to every consultant, every time, so a 14-person pack is as consistent as a single CV. Underneath, MagicCV is GDPR-by-design with EU data residency; the Trust Center covers the full compliance picture.
Why it matters
From an evening of redaction to a single toggle
Switch on anonymization at export and names, photos, and other identifying details come out - no manual find-and-delete pass, no footer or header that slips through, no second pair of eyes needed just to catch misses.
Your rules decide what counts as identifying
Blind recruitment processes and public tenders disagree about what must be hidden - some want employer names gone, some only names and photos. Configure which fields are stripped so each submission meets its specific requirement.
Whole team packs, identical treatment
Anonymize a 14-consultant pack for a public tender and every CV follows the same rules. In a blind evaluation, consistency is the requirement - one differently-redacted CV can identify a candidate by omission.
GDPR by design underneath
Anonymization sits on top of GDPR-by-design data handling with EU data residency, audit logs, and a DPA on Enterprise. Blind CVs are one output of a system built to handle personal data properly, not a patch on one that wasn't.
How this connects
“The RFP-to-CV reasoning is the part that surprised me. It surfaces the exact projects that match the brief instead of a generic profile dump.”
Tomas Lindqvist
Head of Delivery · Lindqvist & Co
Frequently asked questions
What exactly gets removed when a CV is anonymized?
Names, photos, and any other fields you configure as identifying - contact details, employer names, client names in project descriptions. You control the rule set, so the output matches what your tender or blind recruitment process actually requires.
Does an anonymized CV still use our template?
Yes. Anonymization strips content; the template controls presentation. A blind CV exports in the same fonts, layout, and branding as your standard CV, so the pack still looks like your firm - just without the identifying details.
Can we get the identified version back after the blind evaluation?
Yes. Anonymization is applied at export and never alters the underlying profile. Once the evaluation stage passes, export the same consultant's CV with anonymization off and you have the full version - no separate documents to maintain.
Is MagicCV GDPR-compliant?
MagicCV is built GDPR-by-design with EU data residency, and Enterprise plans add a DPA and audit logs. Anonymized exports are one part of that; the Trust Center covers data residency, retention, and processing in full.
Is MagicCV SOC 2 certified?
SOC 2 certification is in progress - we won't claim it before it's complete. Today MagicCV offers GDPR-by-design data handling, EU data residency, SSO and a DPA on Enterprise, and audit logs. The Trust Center has the current status.
Does this work for blind recruitment as well as tenders?
Yes. The same one-click anonymization covers blind recruitment screening - strip names, photos, and other bias-carrying fields before CVs reach reviewers, then share the identified version once a shortlist is agreed.
How do we know every CV in a pack was anonymized the same way?
Because the rules are applied by the system, not by whoever edited each document. Every CV in the pack passes through the same configured rule set at export, so there's no per-document variance to audit the night before a deadline.
From scattered CVs to a polished, on-brand pack in minutes.
See it on your own consultants, or start free today - no credit card.
GDPR by design · EU data residency · Free plan, no credit card