Topics
Pragmatic GDPR practice for German-speaking HR teams - without lawyer language, with concrete thresholds.

What GDPR practically requires from you in recruiting comes down to six points. I list them here the way a data protection officer would check them in an audit.
Myth 1: 'We need a separate, hand-signed consent in a Word doc per application.' Wrong - the consent in the careers-page privacy notice is enough, as long as it's specific.
Myth 2: 'We have to keep everything for 10 years because of anti-discrimination law.' Wrong - 6 months after rejection is enough for the legal claim window. Longer retention needs a different legal basis.
Myth 3: 'KI in recruiting is forbidden.' Wrong - pre-sorting with human decision is fine. Forbidden is auto-decision with legal effect without a human.
Three of the six duties can be automated by an ATS. Information via a built-in GDPR clause on the careers page. Retention via a per-candidate retention window with auto-anonymisation on expiry. Right of access via self-service export. The other three (lawful basis, minimisation, erasure) remain human decisions, but the ATS helps keep them consistent.
FAQ
Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.
Read next
GDPR checklist for recruiting 2026 - clean, step by step
Six concrete GDPR duties + three common myths, with software defaults to tick off.
Read
Why KI in recruiting is more than a trend - and how to tell the difference
How recruiting substantively changes with KI - beyond the hype.
Read
How to write fair rejections without spending hours on them
A real rejection template, three anti-patterns, and why 'unfortunately it didn't work out' is the wrong sentence.
Read