No protected characteristics
VerbatimCV never returns a candidate's date of birth, age, gender, photo, marital
status or nationality. When a CV includes them, as many European CVs do, the result says only that
they were there, in safety.excluded_fields_present. Your model or agent can't screen on
data it never receives.
"safety": {
"excluded_fields_present": ["photo", "date_of_birth"]
}
Why it matters
- Age, sex, marriage and race (which includes nationality) are protected characteristics under the UK Equality Act 2010, with equivalents across the EU and US.
- UK GDPR and EU GDPR expect you to process only the data you need. Not extracting these fields keeps them out of your systems.
- Models given a photo or birth year can be influenced by it even when told not to be.
What it doesn't do
Names, addresses and education can still correlate with protected characteristics, and VerbatimCV returns them because recruiting needs them. Removing these fields is one safeguard, not a bias audit. Keep a human in any decision that significantly affects a candidate.
Try it
Get a free API key (50 parses a month, no card), then:
curl https://api.verbatimcv.com/v1/parse \
-H "Authorization: Bearer $VERBATIMCV_API_KEY" \
-F file=@cv.pdf
Agents can use the parse_resume tool instead: uvx verbatimcv-mcp. See the
quickstart for Python, JavaScript and MCP setup.