An agent captures it. An underwriter relies on it. A TPA, a surveyor, a network hospital and a reinsurer all act on it — sometimes a decade later, at a claim. Consent Hub records that permission once, carries it to every party that needs it, withdraws it everywhere at once, and reproduces the exact words the policyholder saw when someone finally disputes them.
Built on the DPDP Act 2023 and the Rules notified in November 2025.
No other BFSI vertical hands personal data to as many independent parties as insurance does — and under the DPDP Act, every one of them is a processor acting on a permission the insurer is accountable for.
Individual agents, corporate agents, brokers, bancassurance desks, web aggregators, POSP.
Medical panels, diagnostic labs, tele-underwriting vendors, credit and fraud bureaux.
Third-party administrators, policy admin platforms, communication and payment vendors.
Surveyors, investigators, network hospitals, garages, repricing and adjudication partners.
Reinsurers and their analytics providers, often outside India.
Every capability below is live in the product today. The insurance framing is ours; the machinery underneath is the same ledger every Consent Hub deployment runs.
A governed dispatcher resolves who receives what by action and purpose, delivers over webhook, API or MCP, and records an append-only delivery with an acknowledgement. Withdrawal travels the same path as grant.
Processor Registry + Consent PropagationSection 14 nomination is built into the ledger, not bolted on — the one DPDP right that uses a word insurance has used for a century.
Right to NominateEach consent is frozen at capture with its exact text, signed as a tamper-evident artifact, hash-chained, and exportable as a court-ready pack with a verifier anyone can run without trusting us.
Consent Versioning · Cryptographic Artifact · Evidence PackagerOTP-verified consent over WhatsApp, SMS and email for agent-assisted journeys, and scanned-form upload for the proposal a policyholder signed on paper at a branch or a kitchen table.
Consent Channels · Manual / scanned captureSchedule 8 languages at capture, with the exact translated text stored against the record — so a Marathi proposal is defensible in Marathi, not reconstructed later from an English master.
22-Language Consent CaptureSection 9 verifiable parental consent for child plans, and automatic re-consent when the child reaches majority — the renewal nobody remembers to build.
Children / Minor Consent · Expiry & RenewalA retention engine that holds data for as long as the contract and the claim window require, then erases on schedule rather than on memory.
Retention EngineA processor register with risk tiering, contract references and cross-border posture — the evidence an IRDAI inspection or a DPDP inquiry asks for about every partner touching policyholder data.
Third-party Risk · ROPA BuilderConsent captured by whoever is holding the customer — agent, aggregator, bank desk — in their language, on their channel.
Purposes decomposed: underwriting, bureau checks, servicing, marketing. Nominee recorded. Text frozen and signed.
Every downstream processor holds a permission it can prove it was granted, and loses it the moment it is withdrawn.
The exact notice shown at onboarding, reproducible years later, with an audit trail a surveyor’s dispute cannot dent.
Consent expires with the policy, renews with it, and erases when the retention clock runs out.
Notice, consent, withdrawal, nomination, erasure — in force 13 May 2027.
Rule 3 notice content and comparable-ease withdrawal, notified 13 Nov 2025.
Policyholder protection, outsourcing and cyber governance expectations.
Verifiable parental consent for policies written on a minor.
TrustMark reads your live pages the way a regulator would — the form, the notice behind it, and the trackers that fire before anyone clicks anything — then scores them against the DPDP Act across twenty published rules.
See Consent Hub run against your own distribution chain — your agents, your TPAs, your claims partners — rather than a generic deck.