₹99
Published entry path
Shown only where the public pricing source supports it.
Customer Zero R2 Bengaluru
Verify household help without secret checks
A household-safe flow for maids, cooks, drivers, nannies, tutors, caregivers, and home-service workers: purpose first, worker consent, masked signals, and clear limits.
Starts at ₹99Customer Zero R2Consent-firstWorker sees their own reportAddress/identity signalsNo secret checks
Sample preview — no real PII
Household verification report
Person
S*** K. · Cook · Bengaluru
Masked sampleConsent ref
CONS-HH-26-4xx
Captured before checksIdentity signal
Name and phone aligned
Signal onlyAddress signal
Current address needs review
Manual reviewDoes not guarantee future behaviour and does not replace statutory police/legal requirements.
R2 Bengaluru
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Worker report visibility and consent remain central.
Audience stakes
Households need confidence before someone enters the home, but the flow must not become secret checking, class bias, or raw document circulation.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Many roles enter the home
Maid, cook, driver, nanny, caregiver, tutor, part-time worker, and maintenance worker each need a clear purpose.
Consent must be visible
The worker receives the purpose and can consent or decline before checks run.
Families need signals, not raw IDs
Households receive readable status and masked report context instead of circulating documents.
Customer Zero R2 Bengaluru
A household playbook that is firm without being secretive.
Customer Zero R2 Bengaluru playbook for consent-first domestic worker, driver, nanny, tutor, caregiver, and home-service verification.
Safe request script
- 1I want to verify you through PRAMAAN before starting work at my home.
- 2You will see the purpose before anything runs.
- 3You can consent, decline, or ask for help.
- 4I will see only the permitted result, not a pile of raw documents.
Maid or cook
Confirm identity and current-contact signals before home access.
Do not ask neighbours or building chats to forward raw documents.
Driver
Use the role purpose before requesting driver-specific evidence.
PRAMAAN does not replace any statutory police or transport requirement.
Nanny, tutor, or caregiver
Keep the request narrow because the role is sensitive and family-adjacent.
A green signal is not a guarantee of future behaviour.
Home-service vendor
Use one consent-backed check for recurring plumbers, electricians, cleaners, and repair staff.
Manual fallback stays available if the person declines.
Who this is for
Role-based trust, not one generic buyer.
Each stakeholder gets the decision surface they need while the person being verified keeps consent and rights visible.
Household requester
Can I make a responsible decision quickly?
PRAMAAN view: Identity/address signals, consent reference, and review state.
Worker
Will I know what is checked?
PRAMAAN view: Purpose notice, own report visibility, support and DSR routes.
Family member
Can we store and share safely?
PRAMAAN view: Responsible-use guidance and masked sample report.
Workflow
Request, consent, signal, review, and audit stay connected.
The person being verified sees the purpose before checks run; the operator receives a decision-support signal and escalation path.
- Enter1
Enter role and contact details
The requester chooses the purpose and sends a consent link.
- Consent2
Worker receives the request
The worker sees who is asking, why, and what result may be shared.
- Review3
Household sees permitted signals
The result shows status, consent reference, and whether manual review is needed.
Capabilities
Built around the segment's daily operating model.
Capabilities are useful only when the live/planned/target boundary is visible.
Responsible household verification
Get consent, explain purpose, avoid discriminatory questions, store reports safely, and avoid forwarding documents in WhatsApp groups.
Role-specific check depth
Households can match the verification purpose to the role without overcollecting data.
Worker report visibility
The worker can see their own report and use support, correction, DSR, or grievance routes.
Manual review label
Insufficient or mismatched data is shown as review-needed, not as an automatic rejection.
No secret checks
If consent is refused, the check does not run.
Police/legal boundary
PRAMAAN does not replace applicable police or legal requirements.
Consent and DPDP
Consent-first household flow
The worker sees the purpose before checks. No consent means no PRAMAAN check.
Purpose shown before request
Worker consents or declines
Worker can see their own report
Support, correction, DSR, and grievance routes visible
Sample preview
Household verification report
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Household verification report
Person
S*** K. · Cook · Bengaluru
Masked sampleConsent ref
CONS-HH-26-4xx
Captured before checksIdentity signal
Name and phone aligned
Signal onlyAddress signal
Current address needs review
Manual reviewDoes not guarantee future behaviour and does not replace statutory police/legal requirements.
Use cases
Specific workflows a buyer can recognize.
New maid or cook
Send a consent link before the first day.
Household sees masked identity/address signals.
Driver or nanny
Use a careful role purpose and avoid sharing raw documents.
Family decision is informed and consent-backed.
Caregiver or tutor
Run purpose-limited checks and retain only what is needed.
Sensitive home roles get a cleaner trust trail.
Responsible use
What PRAMAAN does not prove
Verification is a decision-support signal, not a guarantee about future conduct.
Not a guarantee of future behaviour
Not a replacement for police verification where legally required
Do not use for harassment or discrimination
Do not circulate raw documents in groups
Household pricing
Starts at ₹99
Use the public single-check path where the subject is ready to consent.
- Refund policy lives at /pricing/refund-policy
- No secret checks
- Report visibility is purpose-limited
Household self-serve
R2 Bengaluru
The public ₹99 verification path is preserved for household checks. Verification is a decision-support signal, not a guarantee of future behaviour.
Integration and operations
Operational model
Self-serve household flow first; society or worker badge workflows can extend the same consent language.
Single check
Supported
Sandbox demo
Supported
Society rollout
Supported
Worker badge
Supported
Proof and pilot clarity
Household rollout clarity
Customer Zero R2 is the Bengaluru focus for this household page. It uses the public pricing path and avoids fake society names, invented customer counts, or unsupported outcome claims.
FAQ
Household verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Verify household help responsibly
Start only when the worker is ready to see the purpose and consent.