Trust and security

VHire holds assessment results, interview recordings, identity documents and contact details for people who are looking for work. This page is written for the person in your organisation who has to sign off on that, and it is deliberately specific. Talgrid Tech Private Limited operates the platform.

Where data lives

Application data is held in a managed PostgreSQL cluster, with edge read replicas and object storage on Cloudflare's network. Files — résumés, assessment recordings, proctoring media, interview recordings, message attachments — are held in separate object stores, each scoped to a single purpose rather than pooled.

Separation between customers

Tenant separation is enforced in the database, not only in application code. Row-level security is forced on tenant-scoped tables, and the credentials the services connect with cannot bypass it. Services connect through least-privilege logins that are permitted to execute a named set of functions and nothing else, with separate credentials for separate jobs, so a fault in one path cannot read another's data.

Government identity documents

Identity documents are handled apart from everything else. A dedicated service is the only holder of the encryption key, so no other part of the platform can decrypt them. Values are encrypted with AES-256-GCM at rest. For Aadhaar the ciphertext is held in a separate store with only a reference in the record, so the document and its pointer are never in the same place.

• Raw values are never written to logs and never returned by ordinary APIs
• Disclosure is restricted to platform-owner level and is recorded with who, what and when
• The store is write-mostly: the product reads a reference, not the document

Access control inside your account

Permissions are granular and checked per route rather than per screen. You decide who can see compensation, who can reveal a marketplace candidate, who can approve interview feedback and who can change billing. Roles are configurable, and teams can be organised into pods with their own managers.

Candidate consent

Consent, suppression and opt-out are first-class in the data model rather than a flag on a mailing list. A marketplace profile is only returned to an employer after a live check of consent, blocks and entitlement. Reaching a candidate debits your balance and grants access in a single operation, so there is no state in which you have been charged for a record you cannot see, or can see one you were not charged for. Every reveal is recorded against your account.

Recruiting outreach is checked against consent and suppression records before it is sent. Automated outreach includes a one-click unsubscribe under RFC 8058; other recruiter messages include an opt-out instruction. An unsubscribe is recorded in suppression state and blocks later outreach.

Assessment and proctoring data

A proctored session records what the candidate was told it would record. That covers webcam images for identity verification, screen activity and browser focus, optional audio, device and environment information, and the responses themselves. The candidate is informed before the session begins.

• Proctoring media is stored separately from assessment results
• A trust score and an event list are produced; raw media is not exposed in ordinary reporting
• Reports state their own limits, including that a score is a screening signal rather than a hiring decision

Interview recordings

Interviews run in the platform are recorded with a transcript, and both stay attached to the candidate record. Written summaries are generated from the transcript and are labelled as drafts to be checked. Feedback goes through an approval step before it is visible outside the panel.

What we do not claim

Stating this plainly saves everyone a round of questions during review.

A data processing agreement is available. If your security review needs answers this page does not give, write to us and we will answer in writing rather than in a call.