QR Lead Forms and Consent: What to Tell People Under India's DPDP Act

17.11.26 11:28:31

A visitor stops at your exhibition stall and scans the QR code on your standee. A short form opens. They type their name, mobile number, email, and company, and tap Submit. It takes twenty seconds.

In those twenty seconds you became responsible for a stranger's personal data. Under India's Digital Personal Data Protection Act, 2023 (the DPDP Act), the business that decides why and how that data is collected is called a Data Fiduciary, and it has duties about what it tells the person, how it asks for consent, and what it does with the data afterwards.

This guide explains what the law asks of a QR lead form: the dates that matter, the consent standard, what the notice must contain, a sample notice you can adapt, and the mistakes to avoid. It is general information, not legal advice, and you should have a lawyer review your final wording.


Why a QR Lead Form Falls Under the DPDP Act

The DPDP Act protects the digital personal data of individuals. A name, a mobile number, and an email address that identify a person are personal data, and a QR lead form collects exactly those, digitally.

Three points follow:

The Act does not carve out business contacts. The person scanning your code may be acting as a professional, but their details are still personal data. If you are unsure how this applies to your situation, that is a question for your lawyer.

You are the Data Fiduciary. You decide the purpose of the form and what happens to the answers, so the main duties fall on you.

The tool you use is a Data Processor. The platform that hosts your form and stores the submissions processes data on your behalf. That does not move your responsibility to the vendor. The Act expects a contract between you and any processor, and it expects you to choose a processor that protects the data properly.


The Dates to Know

The DPDP Rules, 2025 were published in November 2025 and switch on in stages, according to BRB Legal's timeline of what applies when:

DateWhat starts
November 2025The Data Protection Board is set up
13 November 2026Rules on Consent Managers begin
13 May 2027Notice and consent, security safeguards, breach reporting, rights, erasure, and children's data duties apply

For a QR lead form, the date that matters is 13 May 2027, when the notice and consent duties apply. Sources differ slightly on whether to call it 13 May or "mid-May", and the exact date is in the Gazette notification, so check it when you finalise your plans. One compliance guide suggests most organisations need six to twelve months to map data, rewrite notices, and change consent flows, which is a good reason to start now.


What the Law Says Consent Must Look Like

Section 6 of the Act sets the standard. As the Act's text at DPDP Rules puts it, consent must be free, specific, informed, unconditional, and unambiguous, given with a clear affirmative action, and limited to the personal data necessary for the specified purpose.

Here is what each part means on a QR lead form:

RequirementOn your QR lead form
Free and unconditionalDo not make something unrelated depend on agreeing to marketing. Optional consents must stay optional.
SpecificOne consent per purpose. "Contact me about this enquiry" is separate from "send me updates".
InformedShow the notice before or at the point the person submits.
Unambiguous, with a clear affirmative actionUse an unticked checkbox or an explicit "I agree" button. No pre-ticked boxes, and no "by submitting you agree" in small print.
Limited to necessary dataAsk only for what the purpose needs. A callback needs a name and a number, not a pincode and a landline.

The last row is the easiest to fix. Remove every field you do not use.


What the Notice Must Contain

The notice comes first. Rule 3 of the DPDP Rules, as summarised by Konfirmity's Rule 3 guide, asks for three things many notices lack: an itemised description of the data and purposes, standalone wording, and a way to withdraw that is as easy as giving consent.

What the notice must doWhat to put on the form
Stand on its own, in clear and plain languageA short notice on the form itself, not a link to a long privacy policy
Itemise the personal dataList each item: name, mobile number, email, company
State the specific purpose and what it enablesFor example, "to call you about the quote you asked for"
Explain how to withdraw consent, as easily as it was givenA link, email address, or WhatsApp number that works in one step
Explain how to exercise rights and complain to the BoardYour contact for requests, and a mention of the Data Protection Board of India
Be available in English or an Eighth Schedule languageA language switch on the form

On the last row: the Act says the notice and consent request must be available in English or any of the 22 languages in the Eighth Schedule to the Constitution, at the person's option, as this explainer of the Act notes. For a stall in Hyderabad, Chennai, or Pune, a Hindi, Telugu, or Tamil version is not decoration. Have native speakers check every translation.


A Sample Notice for a QR Lead Form

Adapt this to your own business, and have a lawyer review it before you use it. Replace the bracketed parts.

Before you submit

[Business name] will use the details below to [specific purpose, for example: call you about the enquiry you made and send the brochure you asked for].

What we collect: your name, mobile number, email address, and company name.

Why: only for the purpose above. We will ask you separately before using your details for anything else.

How long we keep it: [period, or "until we have answered your enquiry"], after which we delete it unless the law requires us to keep it.

Your choices: to withdraw your consent, see or correct your details, or ask us a question, [link, email, or WhatsApp number]. To complain, contact [grievance contact]. You can also approach the Data Protection Board of India.

Read this notice in: [English | Hindi | Telugu | Tamil | other languages you offer]

☐ Optional: send me occasional updates about [product or service] by [email or WhatsApp]. (Unticked by default.)

☐ I agree to the above. [Submit]


Three design notes on the sample:

  • The optional marketing consent is a separate box, so a person can submit the form without agreeing to marketing.
  • Both boxes start unticked. Consent must come from a clear affirmative action.
  • The withdrawal route is a single step. If giving consent took one tap, withdrawing should not take a form and a week.


A point to take advice on. Section 7 of the Act lists certain legitimate uses where consent is not the basis for processing, including data a person voluntarily gives for a specified purpose when they have not indicated that they do not consent to its use. Some practitioners read this as covering a simple "call me back" form. Whether it covers yours, and whether you still need a notice and a checkbox for the core request, is a legal judgment. The conservative design above, with a clear notice and an affirmative action, avoids relying on a narrow reading. Optional marketing is different: do not assume a person who asked for a callback agreed to a newsletter.


Keep a Record of Who Agreed to What

If a person or the Board questions you, it is on you to show that notice was given and consent was obtained. DPDP Rules' summary of Section 6 states that the Data Fiduciary must prove notice and consent if questioned.

For each submission, try to keep:

  • The person's details and the exact time they submitted
  • The version of the notice they saw
  • Which consent boxes they ticked
  • Which QR code, event, or placement the submission came from

A timestamp and an event tag are a useful start. Check that your form tool also stores the notice version and the checkbox choices, because many tools record only the answers.


Withdrawal, Deletion, and Retention

Under the Rules, personal data should be erased once its purpose is served or consent is withdrawn, unless the law requires it to be kept, according to BRB Legal. The same source notes that businesses must also keep personal data, traffic data, and logs for at least one year for the purposes the Rules specify.

Those two points pull in different directions, which is why a withdrawal flow that wipes everything the moment someone asks can create its own problem. Get advice on how long you must keep logs and what you should delete on request, and write that into your notice.


Children's Data

Before processing the personal data of anyone under 18, a business must obtain the verifiable consent of a parent, after checking that the person consenting is an identifiable adult. Most B2B lead forms are aimed at adults, so the practical step is to say so and not to collect from minors. If you exhibit at a college fair or an education expo, take particular care.


What the Penalties Are, and Where Consent Fits

The Schedule to the Act sets maximum penalties. Most sources agree on these ceilings, which the Board applies case by case:

FailureMaximum
Not taking reasonable security safeguards to prevent a breachUp to ₹250 crore
Not notifying the Board and affected people of a breachUp to ₹200 crore
Breaching the children's data obligationsUp to ₹200 crore
Breaching a Significant Data Fiduciary's obligationsUp to ₹150 crore
Breaching any other provision of the Act or RulesUp to ₹50 crore


Notice and consent do not have a band of their own, so as Konfirmity's penalty guide explains, they fall into the "any other provision" band of up to ₹50 crore. A defective notice carries a lower ceiling than a security failure. That does not make it safe to ignore, but it tells you where the largest exposure sits: protecting the data you collect and reporting a breach properly. Our guide to ISO and GDPR certification for digital visiting card platforms covers the security side.


A Design Checklist for Your QR Lead Form

  • [ ] Every field has a purpose you can state in a sentence
  • [ ] The notice appears on the form, in plain language
  • [ ] The notice lists each item of data and the specific purpose
  • [ ] Optional marketing sits in its own unticked box
  • [ ] The main consent is an unticked box or an explicit button
  • [ ] There is a one-step way to withdraw consent and to contact you
  • [ ] The notice shows who to complain to and mentions the Data Protection Board
  • [ ] The form offers English and the regional languages your audience uses
  • [ ] The form says it is for adults aged 18 and over
  • [ ] You keep a record of each submission, the notice version, and the choices made
  • [ ] You have a contract with your form or CRM vendor, and you know how it secures the data
  • [ ] You have a plan for retention and deletion that a lawyer has reviewed

Common Mistakes

"By scanning, you agree." Scanning a QR code is not an affirmative action that signifies agreement to anything. The person needs to be told what happens to their data and to tick or tap to agree.

Pre-ticked boxes. Consent has to come from a clear affirmative action, so a box that is already ticked does not count.

Bundling marketing into the main consent. If agreeing to marketing is required to get a brochure, the consent is not free.

Collecting more than you need. A twelve-field form for a simple callback breaks the rule that consent is limited to necessary data.

Linking only to a privacy policy. The notice must be understandable on its own and itemise the data and purpose.

English only, where your audience is not. Offer the languages your visitors use.

No way to withdraw. A notice that says "email us" with no working address is not a withdrawal route.

No record. If you cannot show what a person saw and agreed to, you cannot prove consent.

Forgetting the paper side. Forms filled in on paper at the stall carry the same duties, so give your team a consistent notice for those too.


Where a Lead Capture Platform Fits

A platform can help with the security side of your duties and make good form design easier. It cannot write your notice or make your consent valid, because those are yours as the business.

ConnectVith.Me's lead capture collects a prospect's details when they scan a card or code, tags each submission with the event and time, and sends the leads on to your CRM. The platform is ISO 27001, ISO 27701, and GDPR certified. When you use any lead capture tool, check that it lets you add your own notice text, an unticked consent box, a language option, and a record of the choices made. Our post on five questions to ask any vendor handling your data lists what to ask.

Explore ConnectVith.Me enterprise plans →Get your QR digital visiting card →


Frequently Asked Questions

Do I need consent to collect a business contact's details through a QR code? The Act covers personal data of individuals, including professional contacts. Either valid consent or a legitimate use, such as data voluntarily provided for a specified purpose, may apply. The safe design is a clear notice and an affirmative action. Take legal advice on your specific form.

Is a pre-ticked checkbox valid consent? No. Consent must be given by a clear affirmative action, so the person must tick or tap themselves.

Is a link to my privacy policy enough? No. The notice must stand on its own, in clear and plain language, with an itemised description of the data and purpose.

When do these duties apply? The notice and consent duties apply from 13 May 2027, with other parts starting earlier. Check the Gazette notification for the exact date.

Does the notice have to be in regional languages? It must be available in English or any of the 22 Eighth Schedule languages, at the person's option. Offer the languages your visitors use.

What about leads I collected before the duties apply? The Act deals with consent collected before it starts, and the details matter. Ask your adviser what to do about existing leads.

Does using a certified platform make me compliant? No. Certification helps with security, but the notice, consent wording, retention, and record-keeping are your duties as the Data Fiduciary.



Sindhura Deshpande