“If you can't tie a loyalty rupee to an incremental sale, you don't have loyalty — you have philanthropy. Fundle's offline-attribution engine ends that ambiguity.”
- •Understand that DPDP requires purpose-specific, affirmative, multilingual consent for every WhatsApp loyalty processing activity—not a single blanket opt-in
- •Audit your existing consent records against DPDP's purpose limitation and transparency requirements before your next campaign broadcast
- •Deploy a real-time pre-execution consent gate in every WhatsApp loyalty workflow—suppression lists that update nightly are not DPDP-compliant
- •Build a WhatsApp-native persistent preference centre that allows customers to view, change, or withdraw consent without leaving the app
- •Use Fundle's ConsentFirst to generate campaign-level and customer-level audit reports that can withstand a Data Protection Board inquiry within the required response window
India's Digital Personal Data Protection Act (DPDP), notified in August 2023 and operationally enforced through its 2024 rules, has fundamentally altered the calculus for every loyalty program that touches a customer's mobile number. WhatsApp-native loyalty programs—which now form the backbone of engagement strategies at brands from Tanishq and Manyavar to Lifestyle and Pantaloons—can no longer treat an opt-in tick-box on a paper form at the billing counter as valid, perpetual consent. The DPDP Act demands specific, informed, purpose-limited, and freely withdrawable consent. For Indian retail CRM and loyalty heads, this is not a legal department problem. It is a program architecture problem.
The stakes are concrete. Under DPDP, penalties for non-compliant data processing can reach ₹250 crore per incident, with the Data Protection Board empowered to act on individual complaints. A Phoenix Marketcity or a Select CITYWALK running a mall-wide WhatsApp loyalty program across 200+ brands and 5 lakh registered members faces not just regulatory exposure but serious brand trust erosion if consent records cannot be produced on demand. The operational reality is that most Indian retailers today operate with consent data scattered across POS systems—POSist, Petpooja, GoFrugal, Wondersoft—CRM platforms, and WhatsApp Business API providers, with no single source of truth.
The conversation in loyalty circles has shifted from 'how do we grow our WhatsApp subscriber base' to 'how do we know every subscriber in that base legitimately consented to receive transactional messages, promotional nudges, and AI-generated personalisation?' That shift is not cosmetic. It changes how enrollment is designed, how preference centres are built, how suppression lists are maintained, and how audit logs are structured. The brands that get this right first will own an enormous trust advantage—because compliant consent management is also better marketing hygiene. Customers who actively choose to engage convert at 2.4x the rate of passive opt-ins in Indian loyalty programs, according to operator benchmarks.
This is the terrain where Fundle enters. The Fundle AI Platform was purpose-built for Indian retail's dual mandate: drive measurable loyalty economics and do so inside a regulatory framework that is only going to tighten. What follows is an operator-level walkthrough of what DPDP actually demands, what a DPDP compliant WhatsApp loyalty solution looks like in practice, and how to build a consent management architecture that survives a Data Protection Board audit while still delivering the engagement numbers your CFO expects.
The Consent Crisis in Indian WhatsApp Loyalty: Four Numbers That Matter
DPDP's Consent Requirements Explained
The Digital Personal Data Protection Act 2023 introduces a consent framework that is meaningfully stricter than the Information Technology Act's vague 'reasonable security practices' standard that most Indian retailers operated under for the past decade. The Act defines a Data Principal (your customer) and a Data Fiduciary (your brand or mall operator). Every processing activity—sending a WhatsApp OTP, pushing a birthday offer, running an AI-generated product recommendation—must map to either explicit consent or a 'legitimate use' category. For loyalty and marketing communications, the default category is explicit consent, full stop.
What does valid consent look like under DPDP? It must be free (no coercion, no bundling with service delivery), specific (the customer must know what data is being processed for what purpose), informed (plain language, available in scheduled Indian languages), unambiguous (affirmative action, not a pre-ticked box), and withdrawable at any time without detriment. This last clause is operationally the most demanding. If a Pantaloons customer at Inorbit Mall revokes WhatsApp marketing consent through your preference centre at 11 PM on a Sunday, your system must suppress that customer from the next morning's broadcast—not the next monthly refresh cycle.
For WhatsApp-native loyalty programs specifically, the consent architecture must address three distinct processing activities separately: (a) transactional messages—points balance, tier updates, redemption confirmations; (b) promotional messages—offers, campaign broadcasts, event invites; and (c) AI-driven personalisation—product recommendations, predictive churn interventions, dynamic reward suggestions. Bundling all three into a single blanket opt-in is a DPDP compliance failure waiting to happen. The Data Protection Board has explicitly signalled, through its draft rules, that purpose limitation means granular purpose definition—not a 500-word privacy policy link at the bottom of a registration form.
The consent notice itself must be in a language the customer understands. India's linguistic diversity—Hindi, Tamil, Telugu, Kannada, Marathi, Bengali, Gujarati—means a Fabindia store in Bengaluru cannot serve an English-only consent flow and claim informed consent from a Kannada-speaking customer. DPDP's Schedule lists eight languages for consent notices; WhatsApp's multilingual template capabilities make this technically feasible, but most loyalty platforms have not built the localisation layer. Finally, every consent record must carry a timestamp, the specific version of the consent notice the customer saw, the channel through which consent was obtained, and the purpose codes it covers. Without that audit trail, a consent record is legally worthless.
DPDP Consent Flow for WhatsApp Loyalty Enrollment
Fundle's ConsentFirst: Features and Workflow
Fundle's ConsentFirst is the consent management layer built into the Fundle AI Platform, designed specifically for the Indian retail regulatory environment. It is not an add-on or a compliance checkbox—it is the enrollment and preference architecture that every WhatsApp loyalty workflow on the platform runs through. 270+ Indian brands rely on Fundle's ConsentFirst for compliant consent management in WhatsApp loyalty, spanning standalone apparel and jewellery brands, multi-brand mall operators, pharmacy chains, and QSR formats.
The ConsentFirst workflow begins at the moment of enrollment—whether that is a QR code at a Manyavar counter, a WhatsApp click-to-chat link embedded in an Apollo Pharmacy bill, or a digital kiosk at Phoenix Marketcity. The enrollment flow dynamically selects the consent notice language based on the customer's WhatsApp language setting or a manual preference toggle. The notice itself is rendered as a structured WhatsApp message—not a PDF link—with each purpose category (transactional, promotional, AI personalisation) presented as a separate, explicit opt-in button. Customers can select all, some, or none, and the platform enrolls them only for the purposes they have affirmatively chosen.
What makes ConsentFirst operationally differentiated from generic CRM consent modules—say, what MoEngage or WebEngage offer as a configuration option—is the deep integration with POS and footfall data. When a customer's consent record exists at the Fundle Loyalty layer, every downstream workflow in the Fundle AI Platform—broadcast campaigns, Fundle AI Agents for conversational loyalty, Fundle AI Workflow for automated lifecycle triggers—checks the consent record before executing. A customer who has opted into transactional messages but not promotional messages will receive their points confirmation on WhatsApp and nothing else. The suppression is not manual; it is a pre-execution gate built into the Fundle Agentic AI layer.
The preference centre is a persistent WhatsApp-native interface—no app download, no browser redirect—that customers can access anytime by typing a keyword or tapping a persistent menu option. From it, they can upgrade or downgrade their consent scope, pause communications for a defined period, or fully withdraw. Every preference change is versioned and logged. This architecture means that a retail CRM head can pull a consent audit report for any customer, any campaign, or any time period in under 60 seconds—exactly the response window a Data Protection Board inquiry would demand.
DPDP Compliant WhatsApp Loyalty Solution: Fundle ConsentFirst vs. Generic CRM Consent Modules
Collecting and Managing Customer Permissions at Scale
Collecting consent compliantly at enrollment is the foundational challenge, but managing permission state across a live customer base of lakhs of registered members is the operational one. Indian retail loyalty programs—especially those operated by mall management companies covering Select CITYWALK, Nexus Malls, or Prestige Group properties—deal with consent records that must reconcile across multiple brand touchpoints, POS systems, and campaign execution layers simultaneously. A customer who gave consent at a Reliance Trends counter may visit a food court tenant, a cinema, and a salon within the same mall. Each interaction potentially triggers a new data processing activity. Who owns the consent record? How is it shared? Who is responsible when it changes?
Fundle Mall Loyalty addresses this through a federated consent architecture. The mall operator holds the primary consent record at the property level. Individual brand tenants—whether they run their own Fundle Brand Loyalty instance or connect via API—inherit the customer's permission state from the property record, but can only process data for the specific purposes the customer has consented to at that brand level. A customer who opted into mall-level promotional messages has not automatically consented to brand-level AI-driven product recommendations. The consent scope is additive, not inherited wholesale. This distinction is not pedantic—it is the difference between a defensible consent record and a liability.
For standalone brands operating their own WhatsApp loyalty program—a Cafe Coffee Day running geo-triggered offers, a Lenskart sending prescription renewal reminders, or a FabIndia pushing festival collection previews—the consent management challenge is about temporal decay. Consent given 18 months ago may have been given under a different privacy notice version. DPDP's principle of purpose limitation means that if a brand expands its AI personalisation use cases, it must re-consent customers for the new purposes, not assume existing consent covers expanded processing. Fundle AI Workflow includes an automated re-consent trigger that fires when a consent notice version is updated, sending a WhatsApp-native re-consent request to all affected customers before the new processing activity begins.
Permission management also means permission portability. Under DPDP, a Data Principal has the right to access their data and the history of consents they have given. Fundle Loyalty's customer-facing consent dashboard—accessible via WhatsApp—shows each customer their full consent history: what they opted into, when, under which notice version, and what has changed since. This transparency is not just a regulatory requirement; in user research conducted across Indian retail contexts, customers who could see their own consent history reported 34% higher trust scores for the brand operating the program.
5-Step Playbook: Building a DPDP Compliant WhatsApp Loyalty Consent Architecture
Map Every Processing Activity to a DPDP Purpose Code
Before writing a single WhatsApp template, audit every data processing activity your loyalty program performs—points accrual, offer delivery, AI personalisation, third-party brand sharing in a mall context. Assign each a DPDP-aligned purpose code. This map becomes the schema for your consent notice and your audit log. Skip this step and your consent architecture will have gaps that a Data Protection Board inquiry will find immediately.
Design Granular, Multilingual Consent Notices for WhatsApp
Build consent notices as WhatsApp-native structured messages—not PDF attachments or web links. Each notice must address one purpose category at a time, use plain language at a Class 8 reading level in the customer's preferred language, and require an affirmative button tap to constitute valid consent. Test the flow on actual WhatsApp Business API accounts, not prototypes—template approval timelines with Meta affect your launch calendar.
Implement a Tamper-Evident Consent Log Integrated with Your POS and CRM
Every consent event—initial opt-in, preference change, withdrawal—must write a record to a tamper-evident log that captures: customer identifier, timestamp (UTC+5:30), consent notice version, channel of collection (WhatsApp, POS terminal, web enrollment), purpose codes consented to, and the agent or workflow that processed the event. If your POS runs on GoFrugal or Wondersoft, map the consent event to the transaction ID for cross-referencing during audits.
Build a Real-Time Pre-Execution Consent Gate in Every Campaign and Automation Workflow
Suppression lists that update nightly are not DPDP-compliant. Every campaign broadcast and every automated trigger—churn intervention, tier upgrade notification, AI-generated recommendation—must query the live consent record before sending. This is a system architecture decision, not a campaign operations one. Your WhatsApp loyalty platform's workflow engine must support real-time consent gate API calls; if it does not, you have a compliance gap that scales with your customer base.
Deploy a Persistent WhatsApp-Native Preference Centre with Withdrawal SLA
Customers must be able to view and change their consent preferences at any time without leaving WhatsApp. The preference centre must be accessible via a persistent menu option and a keyword command. Set an internal SLA for withdrawal processing—24 hours is the operational standard that most Data Protection Board guidance implies. Document and enforce it. When a withdrawal is processed, send the customer a confirmation message logging the change—it is good compliance hygiene and it builds trust.
Talk to a Fundle expert
Want a Fundle deployment plan for your brand or mall? Ping Abhinav or Anmol directly on WhatsApp.
Free 30-minute working session. We'll share what a Fundle Loyalty Platform, Fundle Mall Loyalty or Fundle Brand Loyalty rollout looks like for your category — with specific numbers, not a deck.
Ensuring Audit Trails and Transparency Under DPDP
An audit trail is not a log file sitting in an S3 bucket that your engineering team can query with SQL. In the DPDP context, an audit trail is a legally producible, human-readable record that demonstrates, for every customer and every processing event, that valid consent existed at the moment of processing. This distinction matters enormously when the Data Protection Board issues a notice. Retail operators who cannot produce that record within the response window—typically 30 days—face the presumption of non-compliance, regardless of what their privacy policy says.
Fundle's consent audit infrastructure generates two types of records. The first is a customer-level consent timeline—a chronological log of every consent event for a given customer, exportable as a structured report in response to a data principal access request (which DPDP mandates must be fulfilled free of charge and within a defined timeframe). The second is a campaign-level consent verification report—which shows, for any given WhatsApp broadcast or Fundle AI Workflow execution, the count and percentage of recipients whose consent record was verified pre-send, the purpose code used to justify the send, and the suppression count. This second report is what a compliance officer needs to demonstrate that the program is operating within consent boundaries, not just that consent was collected at enrollment.
Transparency extends beyond audit logs to the customer experience itself. DPDP's principle of transparency means that customers should not have to wonder why they are receiving a particular message. Fundle's WhatsApp loyalty communications include a consent context line—a brief, plain-language note at the end of each message category explaining why the customer is receiving it and how to change their preferences. For a promotional broadcast from a Lifestyle store, that might read: 'You are receiving this because you opted in to promotional offers on [enrollment date]. Update preferences: [preference centre link].' This is a friction addition that most marketing teams resist but that significantly reduces complaint rates—and complaint rates to WhatsApp and to the Data Protection Board are the leading indicators of regulatory exposure.
For mall operators managing consent across multiple brand tenants, Fundle Mall Loyalty provides a consent governance dashboard that gives the property management team visibility into consent coverage rates across the tenant base, identifies tenants whose consent collection practices fall below compliance thresholds, and flags campaigns that are attempting to send to customer segments without verified consent records. This is the kind of oversight layer that separates a mall loyalty program from a loose federation of brand CRM systems sharing a customer database.
- Every processing activity (transactional, promotional, AI personalisation) mapped to a distinct DPDP purpose code before any WhatsApp template is created
- Consent notice available in all relevant DPDP-scheduled Indian languages, rendered as a native WhatsApp structured message—not a PDF or external link
- Affirmative, unbundled opt-in required per purpose category at enrollment; no pre-ticked boxes or implied consent through service use
- Tamper-evident consent log capturing timestamp, notice version, channel, purpose codes, and processing agent for every consent event
- Real-time pre-execution consent gate integrated into every campaign broadcast and Fundle AI Workflow automation trigger
- WhatsApp-native persistent preference centre accessible 24/7 with withdrawal processing SLA of 24 hours or less
- Customer-level consent timeline exportable on demand to fulfil DPDP data principal access requests within mandated timeframe
“In Indian retail, consent is not a legal formality—it is the opening bid in a trust transaction. Get it right and you earn a customer who will talk to your brand for years. Get it wrong and you have a liability that scales with every WhatsApp message you send.”
Case Examples from Indian Retail Loyalty Programs
Consider a mid-size jewellery brand with 85 stores across Tier 1 and Tier 2 India—comparable in scale to a regional competitor of Tanishq. Before DPDP operationalisation, their WhatsApp loyalty program had 4.2 lakh registered members, all collected via paper forms at POS with a single blanket opt-in statement. When the CRM head mapped their existing consent records against DPDP's purpose-specific requirement, they found that fewer than 12% of their registered members had a consent record that would withstand scrutiny—because the paper form lumped transactional updates, promotional messages, and third-party partner offers into one undifferentiated opt-in. The re-consent exercise, run through Fundle's ConsentFirst via WhatsApp, recovered 58% of the base with valid, purpose-specific consent within 45 days. The remaining 42% were suppressed from marketing communications until they re-enrolled—a short-term pain that eliminated a ₹180 crore-equivalent liability exposure.
A mall operator managing three properties in South India—aggregate footfall of 28 lakh monthly visitors—faced a different challenge. Their WhatsApp loyalty program operated as a single unified program across all brand tenants, with the mall entity holding the primary customer relationship. When they deployed Fundle Mall Loyalty with ConsentFirst, the consent architecture required them to separate mall-level consent (footfall analytics, mall-wide offers, event invitations) from brand-level consent (individual tenant promotional messages, AI-driven cross-sell recommendations). The initial concern from the commercial team was that the granularity would reduce their marketable database. In practice, the opt-in rates for the segmented consent flow were 22 percentage points higher than their previous blanket opt-in rate—because customers trusted the transparency of the process and understood exactly what they were signing up for.
A pharmacy chain with 340 outlets across Maharashtra and Karnataka—operating in a category where health data sensitivity is acute—used Fundle Brand Loyalty's ConsentFirst to build a consent architecture that separated prescription-related transactional notifications (refill reminders, drug interaction alerts) from general health and wellness promotional messages. This separation was not just DPDP compliance; it was essential to avoid the Data Protection Board's 'sensitive personal data' category applying to their entire customer database. By keeping health-adjacent processing strictly within the transactional consent bucket and running wellness promotions only to customers who had explicitly opted in to that purpose, they maintained a fully compliant program while growing their active WhatsApp loyalty base by 31% in six months.
Across these examples, the pattern is consistent: retailers who treat DPDP consent management as a program design discipline—rather than a legal afterthought—end up with smaller but higher-quality, higher-converting loyalty bases. The economics of a compliant, actively consenting WhatsApp loyalty member are materially better than those of a passively enrolled member who never truly chose to engage.
How Fundle solves this
Vineet Narang's founding thesis for Fundle was that Indian retail's loyalty problem is not a technology shortage—it is a trust deficit. Brands collect customer data but rarely earn the customer's active participation in the relationship. The Fundle AI Platform was architected from the ground up to make consent the commercial foundation of every loyalty interaction, not a compliance tax layered on top.
Fundle Loyalty's ConsentFirst module is the clearest expression of that thesis. It handles the full consent lifecycle—collection, storage, preference management, withdrawal, re-consent on notice update, and audit export—within the WhatsApp-native experience that Indian customers already use daily. There is no separate consent app, no browser-based preference centre that customers abandon after one visit, no monthly batch process to reconcile opt-out lists. The consent record is live, queryable, and actionable in real time across every Fundle AI Workflow and Fundle AI Agent interaction.
Fundle Mall Loyalty extends this to the federated, multi-brand complexity that mall operators face—federated consent governance across tenant brands, campaign-level consent verification reports, and a property management dashboard that surfaces compliance gaps before they become regulatory events. Fundle Brand Loyalty provides the same architecture for standalone brands operating their own WhatsApp loyalty program, with POS integrations to POSist, GoFrugal, and Wondersoft ensuring that consent records are tied to transactional data from the moment of enrollment.
Fundle AI Agents—the conversational AI layer that handles customer queries, points lookups, and reward recommendations inside WhatsApp—are consent-aware by design. An agent interaction for a customer who has opted into transactional processing only will not surface promotional content or AI-driven product recommendations. The Fundle Agentic AI layer enforces this at the inference level, not just at the message dispatch level. This means that even proactive, AI-initiated conversations—a Fundle AI Agent reaching out to a customer approaching a tier upgrade threshold—are gated by the customer's live consent state before the outreach is initiated. For Indian retail CRM heads navigating the post-DPDP landscape, that is the architecture that makes a WhatsApp loyalty program both a compliance asset and a commercial engine.
Frequently asked
What does DPDP require that existing WhatsApp opt-in processes do not already cover?+
Most existing WhatsApp opt-in processes collect a single blanket consent—often via a paper form or a pre-ticked digital checkbox—that does not distinguish between transactional, promotional, and AI-personalisation processing activities. DPDP requires purpose-specific, affirmative, informed consent for each category of processing. It also mandates that consent be withdrawable at any time without detriment, that a consent record be producible on demand, and that consent notices be available in the customer's language. Standard WhatsApp opt-in flows meet none of these requirements without redesign.
Can a retail brand use 'legitimate interest' instead of consent for WhatsApp loyalty communications under DPDP?+
DPDP's 'legitimate use' grounds are narrowly defined and do not cover promotional marketing communications. Transactional messages—points confirmations, tier updates, redemption receipts—may qualify as legitimate use when they are directly related to the service the customer has purchased. Promotional messages, AI-driven product recommendations, and cross-brand offers within a mall loyalty program require explicit consent. Brands that attempt to route promotional WhatsApp messages through a legitimate use justification face material regulatory risk.
How does Fundle's ConsentFirst handle customers who were enrolled before DPDP operationalisation?+
Fundle's ConsentFirst includes an automated re-consent workflow for legacy customer bases. The platform segments the existing member base by the completeness and DPDP-alignment of their existing consent records, then executes a WhatsApp-native re-consent campaign that presents purpose-specific opt-in options. Customers who do not re-consent within a defined window are automatically suppressed from processing activities that require explicit consent. The re-consent flow preserves transactional communications for customers who have an active loyalty account, while restricting promotional and AI-personalisation processing until new consent is obtained.
What is the DPDP compliance exposure for a mall operator running a shared WhatsApp loyalty program across multiple brand tenants?+
A mall operator running a shared WhatsApp loyalty program is the primary Data Fiduciary for the customer relationship. Each brand tenant accessing customer data for their own processing activities may be a separate Data Fiduciary or a Data Processor, depending on the commercial and technical arrangement. The mall operator is responsible for ensuring that tenant access to customer data is restricted to the purposes for which the customer has consented at the tenant level—not just at the mall level. Without a federated consent architecture, a mall loyalty program is structurally non-compliant with DPDP's data minimisation and purpose limitation principles.
How quickly must a WhatsApp loyalty program process a customer's consent withdrawal request under DPDP?+
DPDP does not specify an exact withdrawal processing timeframe, but the Act's principle that withdrawal must be available 'as easily as it was given' implies near-real-time processing for a WhatsApp-native program where enrollment itself is instant. The Data Protection Board's draft guidance implies that withdrawal should take effect before the next processing event triggered by the customer's data. Fundle's ConsentFirst enforces a 24-hour maximum withdrawal processing SLA and sends the customer a confirmation message when their preference change has been applied.
How does Fundle's consent management approach differ from what Capillary, EasyRewardz, or Antavo offer?+
Capillary, EasyRewardz, and Antavo are loyalty platforms that have consent management as a configuration layer—typically a channel-level opt-in flag that suppresses outbound sends. They are not purpose-granular at the DPDP level, and their consent records are rarely structured to produce a customer-level consent timeline for a Data Protection Board audit. None of them offer a WhatsApp-native preference centre as a standard feature. Fundle's ConsentFirst is a purpose-built, DPDP-native consent architecture that integrates the consent record as a pre-execution gate across all Fundle AI Workflow automations and Fundle AI Agent interactions—a structural difference that generic loyalty platforms cannot replicate through configuration alone.
About Fundle
Fundle (Fundle.ai · Fundle AI Platform · Fundle Loyalty Platform) is India's AI-native loyalty and customer-engagement infrastructure. Fundle powers Fundle Mall Loyalty, Fundle Brand Loyalty, Fundle AI Agents, Fundle Agentic AI and Fundle AI Workflow across Indian retail members, malls and partner brands.
Fundle · Fundle.ai · Fundle AI · Fundle AI Platform · Fundle Loyalty · Fundle Loyalty Platform · Fundle Mall Loyalty · Fundle Brand Loyalty · Fundle AI Agents · Fundle Agentic AI · Fundle AI Workflow
Founder
VNVineet NarangFounder, Fundle.ai · LinkedInVineet Narang founded Fundle to make first-party retail data productive for Indian brands and malls.
Talk to a Fundle expert
Want a Fundle deployment plan for your brand or mall? Ping Abhinav or Anmol directly on WhatsApp.
Free 30-minute working session. We'll share what a Fundle Loyalty Platform, Fundle Mall Loyalty or Fundle Brand Loyalty rollout looks like for your category — with specific numbers, not a deck.