Where your data lives, and what we have not done yet.
The answers a security questionnaire asks for, in plain English. If a line here is out of date, that is a bug; write to security@recroid.com.
Hosting and data location
- Where it runs
- A single Azure virtual machine in Central India (Pune region). Application, database, file storage and queues run on that machine; nothing is hosted outside India except the sub-processors listed below.
- Data residency
- Candidate, company and college data is stored in India. AI requests send only the text needed for the task to OpenAI (see sub-processors).
- Encryption
- TLS 1.2+ on every connection (certificates renewed automatically). Passwords are hashed with bcrypt. Uploaded files are served through signed, expiring links.
Access and accounts
- Sign-in
- Email and password with verified email, Google or LinkedIn sign-in, optional two-factor (TOTP) for every role. Sessions can be reviewed and signed out from Settings.
- Tenant isolation
- Every company and college is scoped by organisation in the application layer on every read and write. Database row-level policies exist and are being enforced table by table.
- Roles
- Recruiter, hiring manager, interviewer, agency partner (link-scoped), placement officers with department scope, students and jobseekers. Platform administrators are Recroid staff only.
- Audit log
- Every material action (applications moved, offers approved, candidates viewed from a partner college, imports, exports) is written to an audit log the organisation can read.
Candidates' rights
- Consent
- Students decide whether partner companies may find them outside placement drives; off by default. Open-to-work is opt-in. Offer records carry a consent ledger under India's DPDP Act.
- Export and erasure
- Jobseekers can export their data and delete their account from Settings. Companies set a retention window after which rejected applications are removed.
- Honesty
- Automated screening records a reason the candidate can read. Recroid never applies in a candidate's name and never sells résumés.
Backups and continuity
- Backups
- Nightly database dumps, kept for fourteen days on the same machine. Off-site copies are not yet in place; that is the next infrastructure step and this line will change when it is done.
- Monitoring
- Error tracking (Sentry) and uptime checks on the public endpoints. Deploys are automated from a protected release branch and health-checked before traffic returns.
Sub-processors
- OpenAI
- Résumé parsing, job-description drafting, fit reads, interview practice and notes, the daily blog. Text only, no training on your data under the API terms.
- Resend
- Transactional email.
- Twilio
- WhatsApp notifications, only for organisations that switch them on.
- Stripe and Razorpay
- Billing. Card details never touch Recroid's servers.
- GitHub and People Data Labs
- Public-source candidate sourcing, only when a recruiter runs a web search; People Data Labs is capped and opt-in.
- Google, LinkedIn
- Sign-in only.
Not yet
- Certifications
- No SOC 2 or ISO 27001 yet. A gap analysis is on the roadmap after off-site backups.
- Single sign-on
- SAML and SCIM are planned against the first enterprise customer's identity provider.
- Penetration test
- An internal security audit closed its findings in September 2026; an external test is not yet scheduled.
Last reviewed 6 September 2026.