When you ask Indian companies how ‘consent-ready’ they are with the Digital Personal Data Protection (DPDP) Act 2023, many would respond something like this, “We already have a privacy policy and a sign-up form with a checkbox. What more do we need to do?”

 

It’s often not enough. The Act calls for free, specific, informed and unconditional consent. Furthermore, the burden is on the organization to prove that such consent was obtained. The Rules were notified on 13 November 2025, and the main responsibilities will commence on 13 May 2027. That gives an organization a window of about 6 months.

 

The challenges that are most commonly encountered, and ways to address them are as follows:

1. Not knowing where consent is collected

 

There are many places where consent may be collected. Examples include websites, mobile apps, stores, counters, call centers, events, WhatsApp, partners, etc.

 

What helps: Create a spreadsheet with all the different ways you collect personal data and consent.

Consent collection points map

2. Vague and bundled requests

 

Using phrases like, “by continuing, you agree to our terms and policies” is not specific and may include several agreements. Likewise, a large “I agree” to receive order notifications, marketing and other information, is also vague.

 

What helps: Make a list of all the different requests for consent. Focus on ways to improve the requests and the design to make them more clear. Use a conservative approach for the time being. For example, if you bundle different consents, consider giving users the ability to unbundle them.

 

What helps: Only ask for the purpose you need. Use everyday language. Give people the option to say no to marketing. Leave unchecked boxes. The Act expects a clear positive action.

3. Notices people can’t understand

 

Notices must tell the user what data is collected, the rationale, how to withdraw consent, and how to exercise their rights. The act also requires users to be able to file a complaint to the Data Protection Board. Most notices are long legal documents that are hidden in a footer. The Act also allows notices in English or in any other 22 languages listed in the Constitution that many businesses have not prepared for.

 

What helps: Explain the notice in simple terms the way you’d explain it to a friend. Offer it in the languages your users actually speak.

4. Old consents and old data

 

A majority of businesses have a lot of old customer data that was collected a really long time ago, and much of it has no record of consent at all. Some data has been collected for one purpose and has since been used for a different purpose.

 

What helps: For already existing customers send a notice to explain how you will be using their data. Look for old data and remove what you no longer need.

5. Purely paper-based withdrawal

 

Consent can be withdrawn as easily as it was given, but that is not always the case. Oftentimes a user clicks “unsubscribe” in one system, and all other systems and vendors remain unchanged.

Consent withdrawal across systems

 

What helps: Think of withdrawal as a series of connected steps, not as a single event. Once you make a change, check that the appropriate systems heard about it by regularly testing the procedure.

6. Vendors and Third Parties

 

In the real world, business rarely exists in a vacuum. Payment gateways, call centers, marketing agencies and cloud and analytics providers all touch your customers’ data. Under the Act, only vendors processing data on your behalf and under your direction can be engaged through a valid contract, and you will remain responsible for the outcome.

 

What helps: Maintain a list that details the vendor, the data processed and the reason. Regularly check your contracts to ensure they cover your consents and require vendors to cease processing at the time you instruct them to do so.

7. Children’s Data

 

The Act presumes all persons under 18 years of age as children and requires verifiable consent of a parent or guardian. The Act also prohibits behavioral tracking of children and serving children-directed advertising. There are limited exceptions to these prohibitions in the Rules. In the absence of an age verification mechanism for a user, services (primarily apps) to assess who is a child is virtually impossible.

 

What helps: Decide how you’ll verify a user’s age and how a parent will provide consent. Education, gaming and family services should assess this first.

8. Proving Consent during an Audit

 

According to Section 6 of the Act, if consent is challenged, the business must demonstrate that it provided notice and that the consent was properly given. “We always show the banner” does not show proof. Records are.

 

What helps: Maintain a record of consent granted, including who consented, to what, when, how, and what notice version they saw. Keep the history of changes instead of overwriting the record, and protect the record from casual changes.

9. Trackers and Cookies

 

The Act does not mention cookies specifically, but cookies that identify a person could qualify as personal data. Also, many websites embed analytics, advertisements and chat tools that set cookies before a visitor has made a choice.

 

What helps: Scan your site to identify every cookie and tracker. Keep essential cookies only and block the rest until a visitor gives consent, and give “Reject” the same or more prominence than “Accept.”

10. Confusion about When Consent is Needed

 

Not every use of personal data requires consent. For instance, voluntarily sharing data for a particular purpose. And, certain types of medical emergencies. Businesses tend to ask for consent in all cases or not ask for consent in cases where it is needed.

 

What helps: With the help of legal counsel, determine the right basis for each purpose and document that decision. Engineering and product teams can then build or design around it.

11. Ownership and awareness within the company

 

Legal, IT, marketing, product, HR and customer support all have a role to play in consent. When no one owns it, small decisions can create risk. For example, the addition of a tracking tool to a webpage or the launch of a new marketing campaign can raise legal risks if consents are not thoroughly considered.

 

What helps: Appoint a consent owner, provide training to front-line teams, ensure a simple review step is performed to ensure that there are sufficient consents prior to the collection of new data.

Where tools fit in

 

Many small and medium sized enterprises start off with a spreadsheet. If a business is operational in a few channels, the use of forms to gather consents and store them in a spreadsheet may suffice. However, as a business grows and operates in several channels and languages, the use of manual processes to gather consents quickly becomes unworkable. Many organizations turn to a DPDP consent management platform (CMP) to help them collect and store consents. The tool is integrated with other platforms and systems to help automate the flow of changes to consents. A CMP helps fill the gap in data and process automation to govern legal and compliance obligations.

Why it’s worth getting right

 

The Act allows penalties of up to ₹250 crore for not keeping reasonable security safeguards and up to ₹200 crore for not reporting breaches and/or for violation of children’s data protection rules. The bigger deterrent, however, is loss of confidence. People share more when they know they’re in control.

Final thoughts

 

None of these challenges is new, and none is impossible. Most come down to the same habits: know where you collect data, ask clearly, make withdrawal easy, keep proof and review often. With approximately six months to go, picking even two or three of the items above this week will put you way ahead of your competitors.

 

Disclaimer : This article is for general information and is not legal advice. Please consult a qualified professional for your specific situation.