High-sensitivity handling
Purpose limitation and minimal disclosure are central.
High-sensitivity background documentConsent requiredSandbox fixture data
Verify PCC document signals with high-sensitivity handling.
Review Police Clearance Certificate document signals, issuer/date consistency, and consent evidence without claiming direct police-source access or criminal-history conclusions.
- Sensitivity
- High
- Output
- Certificate signal
- Consent
- Explicit
- Review
- Recommended
Certificate signal
Focuses on PCC document evidence and consistency.
No direct-source claim
Does not claim direct police-source verification unless configured.
How verification works
A consent-first path from request to reviewable result.
1
Create a purpose-led request
Choose PCC, state the reason for verification, and invite the subject or enter fixture data in sandbox.
2
Capture explicit consent
The data principal sees the requester, purpose, and check type before any live verification starts.
3
Run the verification rail
PRAMAAN evaluates document signals and match evidence while keeping sensitive values minimized.
4
Review the report
Teams receive a masked, timestamped result with consent reference, signals, and review guidance.
What PRAMAAN checks
PCC signals built for reviewer decision support.
PCC verification must be handled carefully because it can influence background-related decisions.
Certificate number extraction
Extracts the visible PCC or certificate reference where present.
Issuing authority
Surfaces issuer, jurisdiction, or authority text for review.
Candidate name
Compares candidate identity fields with submitted profile context.
Issue date and validity
Flags old, expired, or unclear certificate timing.
Authenticity signals
Looks for document consistency, formatting, and tamper indicators.
Manual review pathway
Issuer mismatch, old certificate, or unclear language should be reviewed by a person.
Why this document matters
Why PCC needs extra caution
PCC documents can affect access, employment, and deployment decisions. Reports should stay limited to what the certificate supports.
High-sensitivity background workflow
Minimal disclosure
Manual review for ambiguous cases
Use cases
Designed for individuals, operations teams, and enterprise reviewers.
Employment onboarding
Support background-document review for relevant roles.
International hiring
Organize certificate evidence for cross-border employment contexts.
Security-sensitive roles
Route certificate signals through careful review.
Domestic worker verification
Use explicit consent and minimal disclosure for home-access roles.
Facility staff verification
Attach certificate evidence to site-access files.
Contractor deployment
Review PCC timing and issuer consistency before deployment.
Consent and DPDP guardrails
High-sensitivity background document handling
PCC workflows should require explicit consent, purpose limitation, minimal disclosure, audit trails, and manual review where needed.
Explicit consent required
Purpose limitation
Minimal disclosure
Audit-ready trail
Manual review where needed
Sample report preview
Masked, specific, and designed for human review.
Every preview uses dummy sandbox data, a consent reference, a timestamp, document-specific signals, and bounded report language.
Sample sandbox report — no real PII
PCC document signal
- Document reference
- PCC-DEMO-****-2048
- Consent reference
- CNS-PCC-DEMO-2048
- Timestamp
- 24 May 2026, 11:14 IST
Certificate numberExtracted
Issuing authorityReturned for review
Issue dateWithin fixture window
Sensitivity noteMinimal disclosure
Sample sandbox report — no real PII. PCC verification provides certificate signals and does not claim direct police-source clearance.
Risk and limitation signals
Clear flags for what needs review.
Expired or old PCC
Old certificates may not reflect current context and should be reviewed.
Issuer mismatch
Unexpected authority, jurisdiction, or formatting needs manual review.
Tampered certificate
Edited or inconsistent certificate imagery should not be auto-approved.
Pricing and CTA
Run one consented PCC document review.
Use PCC verification as a high-sensitivity document workflow with manual-review guidance.
Single live verification
₹99
- Certificate extraction
- Issuer/date consistency
- Minimal disclosure
- Manual-review note
Enterprise and API
PCC workflows for sensitive workforce decisions
Integrate certificate-signal review into HR, facility, contractor, and background-document queues.
Purpose limitation
Audit export
Role-based review
Sensitive-data handling
Related verification documents
Explore all checksCombine this check with the right adjacent signals.
Aadhaar
Household help, driver, tutor — the default identity rail in India.
PAN
Tenant, vendor, employee — anyone receiving payment in India.
Passport
Most senior hires, mid-management vendors, NRIs returning.
Driving Licence
Drivers, delivery workers, fleet operators — DL is the implicit job-credential.
Degree Certificate
Mid-to-senior hires, tutors, professional services contractors.
Electricity Bill
Tenant verification, household help address proof, vendor verification.
FAQ
Police Clearance Certificate verification questions.
Can PRAMAAN run a PCC check without consent?
No. Live checks require explicit consent from the data principal before processing begins.
Can I test this without real personal data?
Yes. The sandbox demo uses fixture data only and does not require real PII.
What happens on a mismatch?
PRAMAAN surfaces the mismatch as a verification signal and recommends manual review where the evidence is incomplete, stale, or inconsistent.
Is the report a legal conclusion?
No. Reports provide verification signals and consent evidence for reviewer decision support. They should not be treated as a guaranteed legal outcome.
Does this query a police source directly?
No. This page frames PCC verification as document and certificate-signal review unless a direct-source workflow is explicitly configured.
Does PRAMAAN say someone has no criminal record?
No. PRAMAAN should only surface what the certificate and configured workflow support, with manual review for sensitive decisions.
Consent-first verification
Start a PCC verification with PRAMAAN.
Use sandbox fixture data first, then run a live ₹99 verification when the requester, purpose, and consent path are ready.