DPDP consent for AI founder videos

If an AI video uses a real person’s face or voice, their consent matters — under both India’s data-protection expectations and the synthetic-media rules. For a founder using their own likeness, that means keeping a clear consent record on file.

Why consent is the sensitive part

A founder video built on your own face and voice is personal data being processed to create a likeness. India’s Digital Personal Data Protection framework expects that processing to rest on clear, informed consent — and the 2026 synthetic-media rules add labelling on top. The likeness is the asset; the consent is what makes reusing it clean.

What a consent record should capture

Who consented, to what use, for how long, and the ability to withdraw. For a founder that’s straightforward — you’re consenting to your own likeness — but if you later feature a colleague, a customer, or a spokesperson, each needs their own record.

The reuse problem nobody plans for

AI founder videos are valuable precisely because you can reuse the likeness across campaigns. That’s also where consent gets murky: a face captured for one video quietly reused everywhere. A consent receipt that travels with the project keeps every reuse accountable.

How MirrorProd’s founder lane handles it

The founder lane captures your likeness with explicit consent, uses it only per approval, and receipts every reuse — the consent artifact travels with the project as part of the Certificate of Provenance. Consent custody, not just a signed form in a drawer.

Rules status as of 13 Jul 2026 — labelling and provenance obligations effective 20 Feb 2026; final label-visibility norms still in consultation. This is a delivery standard, not legal advice.