Frequently Asked Questions

CVNex is an AI-powered recruitment automation platform that captures CVs directly from your email inbox, extracts and structures candidate data, builds a searchable candidate database, and scores candidates against job descriptions — turning a manual screening process into an automated pipeline from inbox to shortlist.

CVNex is designed for three main types of recruitment teams: technical recruiters who need precise skill matching, outsourcing and RPO companies managing CV volume across multiple client accounts, and large corporate HR teams that need a single, consistent hiring pipeline across many departments.

No. CVNex is a cloud-based platform accessed entirely through your browser. You connect your recruitment inbox once during setup, and CVNex handles CV capture, parsing, and dashboard access without any local software installation.

CVNex can function as a standalone candidate database and ATS-style system, or as the CV intake and structuring layer that feeds a cleaner, pre-screened candidate pipeline into your existing ATS. Most teams start by using CVNex for parsing and JD matching, then decide whether to consolidate fully.

CVNex parses PDF CV attachments received via email, regardless of layout — single-column, two-column, skills-first, or chronological formats are all supported. The AI extraction is built to handle the formatting variety typical of real-world candidate submissions, not just clean templates.

CVNex maintains a high parsing success rate across standard CV layouts, with structured fields for name, contact details, skills, work experience, and qualifications. Any CV that the system can't confidently parse is flagged in the email log for manual review rather than silently dropped.

You paste or upload a job description, and CVNex's AI matching engine compares it against your structured candidate database, producing a ranked list with a percentage match score per candidate, along with a breakdown of matched skills versus missing skills relative to the JD.

CVNex logs every inbound email in the Email Log, including ones without a valid CV attachment. These are marked with a "Failed" or "Rejected" status so your team has full visibility into what was processed, what wasn't, and why — nothing is silently discarded.

Yes. CVNex uses encryption in transit and at rest, role-based access controls, and audit logging to protect candidate and account data. See our Privacy Policy for full details.

CVNex supports GDPR-aligned workflows including consent tracking, right-to-delete requests, and audit trails. As the data controller, your organisation remains responsible for ensuring lawful basis to collect and process candidate CVs — CVNex acts as your data processor under our Terms of Service.

No. CVNex does not use your candidate CV data to train third-party AI models without your explicit consent. Your data is used solely to deliver the parsing, matching, and analytics features within your own account.

CVNex is operated by DevNexi, based in Colombo, Sri Lanka, with infrastructure providers chosen to meet enterprise security and reliability standards. For specific hosting or data residency requirements, contact our team directly.

Pricing depends on CV processing volume, number of seats, and which features your team needs (parsing only, or full JD matching and analytics). Reach out to our team for a plan tailored to your hiring volume.

Yes — you can get started with CVNex without a credit card to test CV parsing and JD matching on your own inbox before committing to a paid plan.

Yes. RPO and outsourcing providers managing multiple client accounts can request volume-based and multi-account pricing structured around total CV throughput rather than per-seat costs alone. Contact us to discuss your account structure.

Yes. CVNex supports multiple connected inboxes and candidate pools, letting outsourcing and RPO providers keep client accounts separated while running every CV through the same consistent parsing and structuring pipeline.

Yes. CVNex routes every CV through one shared intake pipeline regardless of department, giving HR a single, centrally auditable source of candidate data while still allowing department-specific JD matching for each open role.

Yes. The candidate database supports searching and filtering by extracted skills, tools, and technologies — so technical recruiters can quickly surface candidates with specific experience, such as a particular cloud platform or framework, across the entire CV pool.

Yes. Candidate records and dashboard analytics can be exported for reporting, client delivery, or integration with downstream systems such as your ATS or BI tooling.