Consent Management
---
Current Status
URLCV does not yet provide a candidate-facing consent form or recruiter UI to record consent. A consent record model exists for future work, but today you should collect and store consent outside the platform.
---
How to Handle Consent Now
- Collect consent through your own web forms or emails and keep the evidence (timestamp, consent text, method, IP/device if captured)
- Record consent status in your ATS/CRM or internal register
- Use anonymisation and NDAs on submissions when you do not have consent for full identity sharing
- Handle withdrawals manually and stop any processing or marketing that relied on that consent
- Granular consent types (processing, marketing, profile sharing, retention, international transfers, automated processing, and custom types)
- Evidence capture (timestamp, IP, user agent, consent text/form version)
- Withdrawal tracking with audit log entries
- Linking consent to privacy notice versions
- Make withdrawal as easy as giving consent (reply-to email or simple form)
- Store the exact wording the candidate agreed to alongside the date/time
- Keep marketing consent separate from processing consent so you can continue lawful processing under legitimate interest where appropriate
- Pair your consent records with LIAs and the GDPR Audit Log in URLCV to show a consistent compliance story
- GDPR Audit Trail — Audit logging
- Legitimate Interest Assessments — LIA management
- Privacy Notices & ROPA — Privacy notice management
---
Planned Scope
---
Tips for Recruiters
---