Skip to content
HeloFlow
All resources
Compliance

Opt-in, the 24-hour window and the DPDP Act

Three rules every Indian business on WhatsApp has to follow: WhatsApp's opt-in policy, the 24-hour window, and the Digital Personal Data Protection Act. What each one asks, and how they fit together.

HeloFlow team · 14 November 2026 · 10 min read

If you sell to customers in India over WhatsApp, three sets of rules apply to you at the same time. Two come from Meta: the opt-in requirement and the 24-hour window. The third comes from Indian law: the Digital Personal Data Protection Act, 2023, usually called the DPDP Act.

They are often mixed up, because they all touch the same moment: a customer giving you their number. But they answer different questions. Once you see which rule answers which question, they become much easier to follow.

This is general information, not legal advice. Laws and platform rules change, and how they apply depends on your business. If you are unsure about your own situation, speak to a lawyer.

Three rules, three questions

  • WhatsApp opt-in answers: may I message this person on WhatsApp at all?
  • The 24-hour window answers: what kind of message can I send them right now?
  • The DPDP Act answers: how must I collect, use, protect and delete this person's data?

A business can follow one and break another. A customer can opt in to WhatsApp messages, and you can still mishandle their data. A customer can be inside an open window, and you can still have no permission to send them offers. You need all three.

Rule 1: WhatsApp opt-in

The WhatsApp Business Messaging Policy requires a person's opt-in before you message them. In practice, three points matter.

  • The opt-in must say the business will message them on WhatsApp. A general "I agree to receive updates" that never mentions WhatsApp does not meet the bar.
  • Opt-out requests must be honoured. When someone asks you to stop, you stop.
  • It affects your number, not just your conscience. People who never agreed block and report. That lowers your quality rating (green, yellow or red), and a low rating can restrict your number.

We cover collecting opt-in in detail in Opt-in is not a checkbox.

Rule 2: The 24-hour window

When a customer messages you, a customer service window opens for 24 hours from their last message. Inside it, you can send any kind of message. Outside it, you can only send an approved template.

Two points connect the window to the other rules.

  • An open window is not consent to marketing. A customer who asked about a delivery yesterday has started a conversation. They have not agreed to receive your offers. Answer their question; ask before adding them to promotions.
  • Templates are where Meta charges. Meta charges for each delivered template message, by category and country, and marketing costs the most. Rates change at the start of each quarter, so check Meta's current rate card.

Our guide to the 24-hour window explains how to plan quotes and follow-ups around it.

Rule 3: The DPDP Act

The DPDP Act is India's general law on digital personal data. A customer's name, phone number, chat history, order details and payment status are all personal data, so a business that keeps them in a WhatsApp tool is covered.

The Act uses its own vocabulary. The person whose data it is is the data principal. Here is what it asks, in plain English.

Who is responsible: fiduciary and processor

The data fiduciary decides why and how personal data is used. When you collect customers' numbers and message them about your products, that is your business.

A data processor handles personal data on the fiduciary's behalf. When you use HeloFlow to store contacts and send messages, HeloFlow is processing that data for you.

This matters because the Act puts responsibility on the fiduciary. You remain responsible for your customers' data even when a processor handles it, and you should have a proper contract with that processor. That is what a data processing agreement is for.

Where you rely on consent, the Act says it must be:

  • Free: not pressured.
  • Specific: for a stated purpose, not "anything we like".
  • Informed: the person knows what they are agreeing to.
  • Unconditional: not forced as the price of something unrelated.
  • Unambiguous: given through a clear affirmative action, like ticking an unticked box or replying YES.

Consent should also be limited to the data you actually need for that purpose.

This lines up closely with WhatsApp's opt-in rule. A pre-ticked box fails both. Silence fails both. A box that bundles order updates, offers and "sharing with partners" into one tick is hard to call specific.

The Act also describes some legitimate uses where consent is not required, for example in certain cases where a person has voluntarily shared their data for a specific purpose. These are narrow. For marketing messages, plan on consent.

Notice

When you ask for consent, you also need to give a notice. It should describe the personal data you are collecting and the purpose you will use it for. It should also tell people how to exercise their rights and how to complain.

The notice does not need to be long. A short line next to the opt-in, linking to your privacy policy, is a common way to do it, as long as the policy actually covers WhatsApp messaging and the data you keep.

People must be able to withdraw consent as easily as they gave it. If they opted in with one tap or a one-word reply, leaving should take one tap or a one-word reply too. "Email our head office with your request in writing" does not match a one-tap opt-in.

On WhatsApp, the natural way to do this is a line in your marketing messages like "Reply STOP to stop offers", and a process that marks the contact as opted out the same day.

Once someone withdraws consent, you should stop processing their data for that purpose. Withdrawal does not undo what you lawfully did before it.

The rights of the people whose data you hold

The Act gives data principals rights you must be able to respond to.

  • Access: to get a summary of the personal data you hold about them and what you do with it.
  • Correction: to have wrong or incomplete data corrected or updated.
  • Erasure: to have their data deleted when it is no longer needed for the purpose, unless you are required to keep it.
  • Grievance redressal: to complain to you, and get a response, before going to the Data Protection Board of India.

For a small business, this mostly means knowing where your customer data lives, being able to export or delete one person's data, and naming someone who handles complaints.

Security and breaches

A data fiduciary must take reasonable security safeguards to prevent a personal data breach. For most small businesses, that starts with basics:

  • Give each team member their own login, not a shared password.
  • Remove access when someone leaves.
  • Do not keep customer lists in spreadsheets passed around on WhatsApp groups.
  • Choose tools that encrypt data and keep access logs.

If a breach does happen, the Act requires you to notify the Data Protection Board and each affected person. Have a plan for who does what before you need it.

Keeping data only as long as you need it

The Act expects you to delete personal data once the purpose is served or consent is withdrawn, unless the law requires you to keep it. A lead from three years ago who never bought and never replied is worth reviewing.

Where the DPDP Rules stand

The Act sets out the principles. The DPDP Rules, which fill in the practical detail, were notified in November 2025. Their obligations are being phased in over the following months, so check the current status before you rely on any particular date.

Even before every part applies, the direction is clear. Building the habits now is far easier than retrofitting them later.

How the three fit together

The good news is that one well-designed moment can satisfy most of all three.

One opt-in that does three jobs

Take a coaching institute with an enquiry form on its website. Next to the phone number field, it adds an unticked box:

Send me class updates and offers from Bright Minds Academy on WhatsApp. I can reply STOP at any time. How we use my data: Privacy policy.

That single tick:

  • Meets WhatsApp's opt-in rule, because it names the business and says WhatsApp.
  • Is a clear affirmative action under the DPDP Act, with a specific purpose and a notice linked.
  • Shows how to withdraw, as easily as it was given.

If the institute also sends fee receipts and class timings, it can offer those as a separate choice. That keeps each consent specific, and a student who declines offers can still get their timetable.

A lead's journey, start to finish

  1. A parent fills in the form and ticks the box. You record when, where, and the exact wording they saw.
  2. They message you with a question. A 24-hour window opens. You answer and send the brochure as normal messages.
  3. Three days later you want to follow up. The window has closed, so you send an approved template.
  4. The parent replies "please stop". You mark them as opted out the same day, confirm once, and they drop out of every future broadcast.
  5. A month later they ask what data you hold. You export their record and send it to them. If they ask you to delete it, you do, unless you must keep something by law.

Every step follows all three rules, and none of it is complicated.

What about the customers you already have?

Most businesses start with an existing list: numbers in the shop phone, an old spreadsheet, past orders. It is tempting to import them all and send a broadcast. Resist that.

If you cannot show that these people agreed to hear from you on WhatsApp, you do not have opt-in, and you may not have the consent the DPDP Act expects for marketing either. Messaging them asking them to opt in is still messaging them without opt-in.

Instead, collect it as they come back to you. Ask when they next message you, at checkout, at the counter, or in your next order confirmation. The list grows more slowly, but every number on it is one you can stand behind.

A practical checklist

  • Use an unticked opt-in that names your business and says WhatsApp.
  • Separate order updates from offers.
  • Link a privacy policy that covers WhatsApp messaging.
  • Record when, where and how each contact opted in.
  • Honour "stop" and its variations the same day.
  • Do not treat an open 24-hour window as permission to market.
  • Send messages outside the window only as approved templates.
  • Know how to export, correct and delete one person's data.
  • Name a person who handles complaints, and make their contact easy to find.
  • Give every team member their own login and remove leavers promptly.
  • Have a written plan for what you would do after a data breach.
  • Check the current status of the DPDP Rules every few months.

How HeloFlow helps

In HeloFlow, every contact carries an opt-in status, a reply of STOP or UNSUBSCRIBE marks the contact as opted out automatically, and broadcasts always skip contacts who opted out. The shared inbox shows the countdown on every chat's 24-hour window, and templates are submitted to Meta from inside HeloFlow. Owners and admins can export the workspace's data and request deletion under Settings → Data & privacy. HeloFlow processes your customers' data on your behalf: our privacy policy and data processing agreement explain what we store and how, and you can reach our Grievance Officer on the contact page. If you have a question about any of this, the help centre is a good place to start.

Once again: this article is general information, not legal advice. For decisions about your own business, speak to a qualified lawyer.

ShareLinkedInXWhatsApp

Related articles

  • Compliance

    Opt-in is not a checkbox. It is your delivery rate.

    6 min read

  • Compliance

    WhatsApp message templates: categories, approval rules, and examples that pass

    8 min read

  • Guides

    Connect your WhatsApp number to HeloFlow: the complete setup guide

    8 min read

Start confirming conversations today

Connect your WhatsApp Business number, add your content and go live — 7-day free trial, no credit card.

Questions first? Read the FAQ