Insurance IRDAI · DPDP

Proof of notice for consent collected in person

An insurer whose agents collect health and family details face to face, with no record of the notice the customer actually saw.

Book a demo Last reviewed 18 September 2026

Illustrative scenario - not a named customer. Built from how Promiz works, to show the shape of a deployment.

What was the problem?

Most policies were sold by agents sitting across a table. Health history, family details and nominee information were written onto paper proposal forms and keyed in later by a back office. The consent line on the form was generic, the language was English regardless of the customer, and nothing recorded which version of the privacy notice had been in front of the person. If a customer later disputed what they had agreed to, the insurer had a signature and nothing else.

Quotes, claims and marketing also shared one consent. A person who asked for a quote and never bought a policy kept receiving renewal-style outreach, and there was no clock on when that enquiry data should go. Section 5 asks for a clear, itemised notice before processing, and Section 8(7) asks that data be erased when its purpose ends. Paper forms and a single checkbox could satisfy neither.

What was set up in Promiz?

  1. 01

    One notice, three modes

    The privacy notice was built once in Promiz and published in the cookie-banner, form and emailed-request modes. Agents no longer improvise wording; the binding text is versioned and fingerprinted.

  2. 02

    Single-use email links for offline customers

    After a face-to-face meeting, the agent sends the customer a single-use consent link by email. The customer reads the notice in their own language, chooses per purpose and confirms. The link expires once used.

  3. 03

    Separate purposes for quotes, claims and marketing

    A quote enquiry, a policy under claim and marketing outreach each got their own purpose with its own legal basis and retention period. Claims processing stays on for the life of the policy; a lapsed quote enquiry has a short retention clock.

  4. 04

    Snapshot of the exact notice on each record

    Every consent record carries the version and the rendered view of the notice the customer saw, in the language they saw it. Assisted withdrawal lets branch staff withdraw on a customer’s request, with a reason logged.

  5. 05

    Receipts in the customer’s language

    The customer receives a receipt listing each purpose and choice. The compliance team can pull the notice PDF and the chained record for any policy in one step.

What changed?

  • For every policy sold offline, the insurer can now show the exact notice the customer saw, in the language they saw it.
  • Quote enquiries that do not convert now run down a retention clock and are erased with a confirmed deletion, rather than living on in the outreach list.
  • Agents send a link instead of explaining a privacy notice from memory, so the wording is the same for every customer.
  • A dispute about "what did I agree to" is answered from the record, not from the agent’s recollection.

Outcomes are described qualitatively on purpose. Promiz does not publish figures from illustrative scenarios.

Bring one purpose. Leave with the proof.

A 30-minute session on your own use case.

  1. 5 min Find your DPDP gaps for that purpose
  2. 20 min Build the notice, collect consent, withdraw it, and close the task
  3. 5 min Download the receipt and verify the chain

Book your demo

Enter your website. We scan its cookies before the call and show you the results.

Reply within 1 business day