₹99
Published entry path
Shown only where the public pricing source supports it.
R3 personal-use consent playbook
Verify personal trust without secret checks
PRAMAAN supports limited-scope identity, address, and configured background-document signals for tenants, flatmates, and high-trust introductions only after the person sees the purpose and consents.
R3 sensitive segmentStarts at ₹99Consent requiredLimited-scope signalsNo secret verificationAbuse reporting
Sample preview — no real PII
Limited-scope consent report
Purpose
Flatmate verification
Shown before consentSubject
A*** R.
Masked sampleSignals shared
Identity/address status
No raw IDConsent ref
CONS-REL-26-9xx
CapturedNo secret checks, stalking use, or private-life intrusion.
R3 sensitive
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Personal-use checks require explicit purpose, consent, and support routes.
Audience stakes
Personal verification can become invasive quickly; PRAMAAN must make consent, minimization, refusal, and abuse boundaries impossible to miss.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Personal trust is high stakes
Tenant, flatmate, and introduction decisions affect housing, dignity, safety, and reputation.
Secret checks create harm
The subject must see the purpose and decide before any PRAMAAN processing starts.
Sensitive results need limits
Signals should be bounded, reviewable, and never used for stalking, coercion, or discriminatory decisions.
Specialized module
Relationship consent boundary
R3 personal-use playbook for tenants, flatmates, matrimonial introductions, and other high-trust decisions with explicit consent and abuse guardrails.
Relationships teams
Operations owners
Compliance reviewers
People being verified
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.
Requester
Can I ask responsibly before a high-trust decision?
PRAMAAN view: Purpose, consent state, permitted status, expiry, and refund-policy route.
Person being verified
What is being checked and who sees it?
PRAMAAN view: Purpose notice, report visibility, correction, DSR, support, and abuse-reporting routes.
Reviewer or support
Is this safe and lawful to process?
PRAMAAN view: Misuse cues, refusal state, escalation, and sensitive-signal boundaries.
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.
- Purpose1
Requester states a narrow purpose
Tenant, flatmate, or introduction use must be explicit before the subject is asked.
- Consent2
Subject sees and decides
The person can consent, decline, ask for support, or report coercion before processing.
- Signal3
Requester sees permitted status
The result uses bounded status and masked signals, not raw document forwarding or private-life exposure.
- Rights4
Correction and abuse routes stay attached
Support, correction, DSR, grievance, and abuse-reporting paths remain visible after the result.
Capabilities
Built around the segment's daily operating model.
Capabilities are useful only when the live/planned/target boundary is visible.
Tenant and flatmate purpose
Use a stated housing or co-living purpose before requesting verification.
Limited-scope signal sharing
Identity, address, and configured background-document signals remain bounded to what the flow supports.
Subject report visibility
The person being verified keeps visibility, correction, DSR, and support routes.
Refusal respected
No secret PRAMAAN check runs when consent is declined or incomplete.
Abuse reporting
Stalking, coercion, harassment, and discriminatory use are not supported and need escalation.
No partner-app claim
Dating, matrimony, broker, and property integrations are by agreement only.
Consent and DPDP
Consent and DPDP-native workflow
Each page keeps consent, purpose, minimization, DSR, support, and grievance paths visible.
Explicit consent before checks
Purpose shown before processing
Operational views prefer signals over raw documents
DSR, correction, support, and grievance routes visible
Sample preview
Limited-scope consent report
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Limited-scope consent report
Purpose
Flatmate verification
Shown before consentSubject
A*** R.
Masked sampleSignals shared
Identity/address status
No raw IDConsent ref
CONS-REL-26-9xx
CapturedNo secret checks, stalking use, or private-life intrusion.
Use cases
Specific workflows a buyer can recognize.
Primary workflow
Use PRAMAAN for the highest-frequency verification path.
Less document forwarding and clearer consent.
Exception review
Route amber, incomplete, or disputed signals to a human reviewer.
Better decisions without automatic rejection.
Renewal or expiry
Refresh signals when a badge, pass, or role context becomes stale.
No reliance on old screenshots.
Responsible use
Responsible personal-use boundaries
PRAMAAN must not be used for stalking, coercion, harassment, doxxing, public shaming, or discriminatory decisions.
No secret checks
Consent refusal must be respected
No income, marital-status, caste, religion, or private-life intrusion claim
Do not share reports publicly
Escalate coercion or abuse
Personal-use pricing
Starts at ₹99
Use the public ₹99 check path only where the selected personal-use flow supports it. Payment and refund handling follows the published policy and gateway state.
- No instant refund promise
- No sensitive-signal guarantee
- No partner-app bundle claim
Personal-use playbook
R3 sensitive
Relationship and tenant verification copy is intentionally cautious. Partner apps, outcome claims, and sensitive-signal coverage are not published without approval.
Integration and operations
Personal-use operating model
Keep self-serve checks, support escalation, and partner integrations separate.
Self-serve consent link
Supported
Tenant / flatmate purpose
Supported
Matrimonial introduction purpose
Planned
Dating-app integration
By agreement
Broker / property integration
By agreement
Proof and pilot clarity
Personal-use rollout clarity
Relationships copy is R3 and sensitive. Partner apps, named brokers, matrimony outcomes, safety metrics, and sensitive-signal coverage are not published without approval.
FAQ
Relationships verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Request a consent-first personal-use check
Use limited-scope signals for a stated purpose, and respect refusal when consent is not given.