- PRAMAAN complements operations software; it does not replace it.
- Societies should use PRAMAAN for consented verification signals only.
- Do not use PRAMAAN as a resident-surveillance layer.
- Corrections, disputes, DSR, and grievances need formal routes.
Overview
PRAMAAN = verification layer
Use PRAMAAN for source-backed verification signals where consent and purpose are clear.
Society app = operations layer
Existing society apps can continue handling visitor logs, resident operations, and facility workflows.
Consent-first checks
Workers, vendors, residents, and subjects should see the purpose before checks run.
Purpose-specific workflows
Separate worker onboarding, vendor access, and resident requests by purpose.
No raw forwarding
Avoid forwarding Aadhaar, PAN, or documents in WhatsApp or committee groups.
No implied partnership
This is a coexistence guide, not a partnership or endorsement claim.
Coexistence model
- 1Society app handles resident, visitor, and gate operations.
- 2PRAMAAN handles consented verification signals.
- 3Admins review permitted source-backed signals.
- 4Workers or residents use correction, DSR, or grievance routes when needed.
What societies should use PRAMAAN for
- Worker onboarding.
- Vendor verification.
- Resident consent requests where appropriate.
- High-friction trust cases.
- Worker badge verification.
What societies should not use it for
- Resident surveillance.
- Secret checks.
- Discriminatory decisions.
- Free-text storage of identity documents.
- Committee WhatsApp document forwarding.
Frequently asked questions
Does PRAMAAN replace MyGate?›
No. PRAMAAN is a consent-first verification layer and should not be presented as a replacement for society operations software.
Can both systems coexist?›
Yes. Keep operations in the society app and use PRAMAAN where source-backed, consented verification signals are needed.
Can societies run checks without consent?›
No. PRAMAAN workflows are consent-first and purpose-specific.
Who can see raw documents?›
Public screens and badge views should avoid raw document exposure. Controlled review should happen only where the workflow supports it.
How should visitor logs be handled?›
Visitor logs need purpose, access limits, and retention discipline. They should not become informal surveillance records.
What if a worker changes societies?›
A worker-owned badge can travel with the worker, while each society should request only the fresh consented checks it needs.
Glossary terms
When to talk to a human
Use human handoff for society rollout, sensitive disputes, correction questions, or enterprise procurement.
Keep raw identity data out of chat
Do not paste Aadhaar, PAN, OTPs, raw documents, full passport numbers, or sensitive screenshots into chat or free-text support fields. Use guided verification, DSR, dashboard, or API flows instead.
Was this helpful?
Feedback helps PRAMAAN improve support answers without collecting raw identity data.
Move safely from answer to action
Use the route that matches the sensitivity of your case. Keep raw documents out of support messages unless a controlled workflow asks for them.