Security & Data Protection
Candidate data deserves the same rigor as the evaluation.
Document validation
AI document validation runs before analysis, on by default, to catch unreadable or non-resume files before they reach the scoring engine.
The security measures, in depth
Application and file storage run on AWS in Frankfurt (eu-central-1).
Resume files encrypted in transit and at rest, and every request for a file is scoped to the account that owns it.
Every record carries the customer account it belongs to, and every request is scoped to that account.
Safeguards against manipulation like keyword stuffing and prompt injection, so scores reflect genuine qualifications.
What you can export if a decision is challenged
A PDF per candidate: every requirement scored out of 100 and grouped by how well it was met, each with the scoring explanation, deal-breakers flagged, and the overall score with its summary, strengths and concerns.
Data, security and governance
How is candidate data secured?
Resume files are encrypted in transit and at rest. Every record carries the customer account it belongs to, and every request is scoped to that account. Access is governed by role-based permissions, and safeguards against manipulation attempts like keyword stuffing are built in.
Where does the data run, and where does the AI processing happen?
The application and file storage run on AWS in Frankfurt (eu-central-1). Those two components are named deliberately: model inference runs on third-party AI providers, and we do not extend the Frankfurt statement to cover them. Bring the question to a demo call and we will go through the components involved.
What can we put in front of someone who challenges a decision?
In the app: the role's weighted criteria, per-requirement grades with citations from the resume, the score and the weighting behind it, and the audit trail. Each status keeps a record of who applied it, and because the criteria and the weighting are fixed on the role and stored with it, a past decision can be re-run and checked against the same standard. The PDF export is narrower: every requirement scored out of 100 and grouped by how well it was met, each with the scoring explanation, deal-breakers flagged, and the overall score with its summary, strengths and concerns. The citations, the weighting and the status history stay in the app.
We have to review the data-protection paperwork before we can sign. Where do we start?
Start with the privacy policy, then bring the specifics to a demo call. That is where we go through where the data runs, which components are involved, how candidate files are handled, and what you can export if a decision is challenged.
Still have a question?
Send it to us and we will answer it. If it is easier to talk it through, book a demo and we will go through the specifics on the call.
Read the privacy policy