Candidate data privacy, built into recruiting
Recruiting collects personal data from people who are not your employees yet. Stavis Recruit records their consent, keeps CVs in private storage, limits who sees what with fixed roles, logs every change, and lets an admin export or anonymise a candidate's data when they ask.
Candidate privacy and control
- Consent at the source
- Fixed roles
- Audit trail
- Data requests
What you can do
Consent at the source
Every application stores the consent scope and the version of the privacy notice the candidate saw. AI processing has its own consent.
Fixed roles
Admin, recruiter and member, plus job roles. Interviewers see only the candidates of their jobs.
Audit trail
Every change to a job, candidate, offer or approval is logged with who and when, in the same transaction.
Data requests
Export everything held about a candidate, or anonymise them: identity replaced, CVs deleted from storage, screening answers removed.
How it works
- 1
Collect with consent
The application asks for consent before anything is sent.
- 2
Work with limits
Each person sees only the jobs and candidates their role allows.
- 3
Answer requests
An admin exports or anonymises a candidate's data with a reason, and the action is logged.
Frequently asked questions
Where are CVs stored?
In private object storage, never in the database, and opened only through signed links for people who may see them.
Can a candidate ask for their data to be deleted?
Yes. An admin can anonymise the candidate. Their identity is replaced and their CVs and screening answers are deleted, while anonymous hiring numbers stay correct.
Who can see a candidate?
Admins and recruiters, and the hiring team of the jobs the candidate applied to.
Is personal data written to logs?
No. Logs carry IDs, not names, emails or phone numbers.
See Stavis Recruit with one of your open jobs.
Bring a role you are hiring for now. We will publish it, screen a few CVs and walk you through to the offer.
