Candidate data stays on your infrastructure.
Resumes, compensation details, interview notes — recruitment data is some of the most sensitive data a company holds. RecruitLite keeps it on servers you control, not a shared cloud tenant.
Most ATS products are SaaS — candidate PII sits on a vendor's servers, subject to that vendor's breach history and uptime. Under India's DPDP Act, that's a harder data-protection conversation than it needs to be. RecruitLite runs on your own server; there's no cloud tenant to secure, because there isn't one.
Choose a local AI provider for resume parsing and candidate matching, and that data never has to leave your network for the AI step either. A hosted provider is just as available if your team prefers it; it's a visible setting either way, never a hidden default.
What's in place
- 01
Role-based access control, enforced server-side.
- 02
Field-level access control on sensitive fields — restrict who can see compensation data, for example.
- 03
No telemetry, no phone-home — the application doesn't report usage data back to us.
- 04
Local-vs-cloud AI provider is a setting you control, visible in the product, not a hidden default.
Security here starts with where the data lives: on your own infrastructure, not a shared tenant. No SOC2 badge, no zero-trust claim, no certification we don't actually hold — what's listed above is what's actually in place, and that's the whole pitch.
Request the trial