Security & Trust

Enterprise-grade data protection and compliance

Candidate submissions, proctoring media, and evaluation results are protected with robust tenant isolation, AES-256 encryption, and strict role-based access controls.

Controls in place

Verified security controls

Every control listed below is active in production, protecting candidate data and hiring records around the clock.

Password storage

Passwords are hashed with Argon2id. Plaintext is never stored, logged or recoverable — a reset issues a new credential rather than revealing the old one.

Short-lived sessions with rotation

Access tokens last 15 minutes. Refresh tokens rotate on every use and are tracked as a family, so a replayed token revokes the whole family instead of granting access.

Tenant isolation

The organisation on your access token is the tenant boundary. Every query is scoped to it server-side, and cross-organisation reads are not reachable through the tenant API at all.

Role-based access control

Eight roles across 22 permissions, with per-member grants and revokes, plus assessment-level scoping so a reviewer sees only the drives assigned to them.

Browser hardening

A strict Content-Security-Policy, framing denied outright, MIME sniffing disabled, and geolocation, payment, USB and Bluetooth switched off — so injected code has little to reach for and an assessment cannot be framed by another site.

Verified payment webhooks

Provider callbacks are authenticated by HMAC over the raw request bytes before the body is parsed, compared in constant time, and each event is processed exactly once.

Audit trail

Privileged actions are recorded with the acting user, the organisation, the target and the time. Support access to an account is itself audited and time-limited.

Isolated code execution

Candidate code runs in a sandboxed container with no network access and enforced CPU and memory ceilings, separate from the application.

Server-side enforcement

Plan limits, permissions and payment state are enforced on the server. A subscription is never activated on a browser reporting success — only after the payment provider confirms it directly.

Candidate data

Candidate privacy & transparent consent

Candidate trust is foundational. We ensure explicit permissions, clear disclosures, and responsible handling throughout every test.

Told before it is recorded

The pre-flight check explains what will be captured before anything is captured, and the candidate grants camera and screen-share permission themselves. There is no covert monitoring.

Collected for one purpose

Captures exist to support an integrity decision on that attempt. They are not used for anything else, sold, or shared beyond the organisation running the assessment.

Evidence, not a verdict

A risk score never rejects anyone on its own. Flagged attempts go to a human, and the review outcome is recorded with the reviewer's name against it.

Failures recorded as failures

A camera that stops working is logged as a diagnostic, not as misconduct. A technical fault must never look like cheating.

Questions

What security reviews ask

Who at your company can see our assessment data?

Support access to a customer account requires an explicit, time-limited grant with a stated reason, and every action taken under it is recorded against the real staff member — not the account they are viewing. Elevated access cannot be used to grant itself further privileges, and the grant expires on its own rather than relying on someone to revoke it.

Where is our data stored?

In managed, encrypted Postgres databases and object storage located in the India region (AWS ap-south-1 / GCP asia-south1, Mumbai). Candidate media, code submissions, and assessment records remain strictly within enterprise-grade Indian cloud data centres with at-rest (AES-256) and in-transit (TLS 1.3) encryption. Assessment data is scoped strictly to your organisation and is not pooled with other customers' for any purpose, including analytics or model training.

Do you use our data to train models?

No. Candidate answers, code submissions, webcam captures and results are used to deliver your assessments and nothing else. The scoring and insight features are deterministic — they compute from your own data rather than from a model trained on anyone's.

How long is candidate media retained?

Webcam and screen captures exist to support an integrity decision, so they are retained with the attempt they belong to and removed on the retention schedule configured for your organisation. If you need a specific retention period to satisfy your own policy, tell us and we will confirm whether we can meet it before you sign anything.

How does Parikshafy govern and secure team access?

Access is governed by eight roles across 22 discrete permissions with per-member grants and revokes. All sessions are short-lived with encrypted, rotating refresh tokens and strict rate-limiting. For Enterprise custom deployments, dedicated SAML / Single Sign-On connectors are available upon request.

How do you handle payment details?

We never receive or store raw payment details. Card and UPI transactions are handled directly by PCI-DSS Level 1 certified payment providers; we store only a secure provider reference, the amount and the status.

What is your vulnerability and security response commitment?

We prioritize data protection and respond promptly to security notices. In the event of any incident, our team provides comprehensive, transparent disclosures in writing. Report a suspected vulnerability to support@parikshafy.com and our security operations team will acknowledge and address it swiftly.

Need a custom security review?

Our security team is ready to complete your vendor assessment, architecture questionnaire, and compliance review.

Have questions? Email sales@parikshafy.com