Security & data
Your talent pool stays your talent pool.
Candidate data is the most valuable thing an agency owns. Here's how we keep it separate, how AI touches it, and where we stand on UK data protection.
Separation
Walls, not promises.
One agency, one workspace
Every record — candidates, roles, notes, files — belongs to one agency, and every request is filtered by that agency on the server. Search vectors carry the same scope.
Separate from our job-seeker app
Recruiter data lives apart from the ApplyForge job-seeker platform. The only link is an opt-in hand-off you trigger, with the candidate’s consent.
Client pages show client-safe fields
Share links expose only what a client should see. Internal notes and screening outcomes never leave your workspace. Links can be revoked at any time.
How AI is used
It helps recruiters investigate. It doesn't decide.
AI is useful in recruitment only if you can check its working. That shapes every feature.
Grounded in your data
Matching, candidate answers, screening questions and summaries are built from the candidate’s own CV, profile and notes — and cite where they came from.
Gaps are shown, not hidden
If the evidence for a requirement isn’t there, ApplyForge says so in orange rather than inflating a score.
A recruiter approves what clients see
AI drafts; your recruiter edits and sends. Nothing is submitted on anyone’s behalf.
No training on your data
We don’t train models on your candidates or notes, and AI requests go through a business API whose inputs aren’t used for model training.
Controls
The basics, done properly.
Encrypted in transit
TLS on every request between your browser, our API and our providers.
Hashed credentials
Passwords are hashed with bcrypt. API keys are stored only as a hash and shown once.
Short-lived sessions
Access tokens last 30 minutes; refresh tokens rotate and can be revoked.
Signed webhooks
Every webhook is HMAC-signed with a timestamp; endpoint secrets are encrypted at rest.
Seats and per-role access
Owners control who has a seat and which roles each recruiter can see.
Integration audit log
Key creation, revocation and webhook changes are logged for owners to review.
UK GDPR
Clear roles, documented process.
For the candidate data you upload, your agency is the controller and ApplyForge acts as your processor, under a written processing agreement. For your own account and seats, we are the controller.
Lawful bases, retention periods and how we handle subject-access and erasure requests are set out in the Privacy Policy, aligned with the UK GDPR, the Data Protection Act 2018 and PECR.
Processing agreement
Available on request for every agency.
Erasure
Delete a candidate and their files from your workspace; integrations are notified.
Subject access
Documented process for access and portability requests.
Your retention policy
You decide how long candidates are kept, in line with your own lawful basis.
Questions we get asked
Security FAQ
Can another agency ever see our candidates?
Do you train AI models on our CVs?
What happens to candidate data if we leave?
Where is data hosted, and who are your sub-processors?
Can clients see our internal notes?
Something not covered? privacy@applyforge.co.uk
Try it on real data, safely.
Your sprint workspace is private to your agency from the first upload.
No card required · No ATS migration · Set up around a real vacancy