Consent Management in Automated Loyalty Campaigns India

Overview of Consent Regulations Including DPDP 2023

India's data privacy journey has been long and tortured. The Supreme Court's 2017 Puttaswamy judgment established privacy as a fundamental right. Years of drafts, committees, and withdrawn bills later, the DPDP Act 2023 is the law of the land. For loyalty programme operators, the four provisions that matter most are: first, the requirement for free, specific, informed, and unambiguous consent before processing personal data for any purpose; second, the right of a Data Principal (your loyalty member) to withdraw consent at any time with effect as easy as giving it; third, the obligation to maintain a verifiable consent record; and fourth, the requirement to process data only for the purposes explicitly consented to — using birthday data to send a birthday offer is fine, using it to infer household income for credit scoring is not.

The TRAI's DLT (Distributed Ledger Technology) framework for commercial communications, already operational, adds a second compliance layer specific to SMS and voice. Every template, every sender ID, every promotional campaign must be pre-registered and matched to a consented preference. When Reliance Trends fires a Diwali offer SMS to 50 lakh members, each message must pass a DLT scrub before it exits the platform. Platforms like Capillary and EasyRewardz have added DLT connectors, but the consent logic governing which members are even eligible for that send often lives outside the campaign tool — in a separate CRM, sometimes in a spreadsheet — creating dangerous synchronisation gaps.

The upcoming DPDP Rules are expected to introduce consent manager intermediaries: regulated entities that sit between the Data Fiduciary and the Data Principal to facilitate granular consent across multiple platforms. This is not a distant theoretical construct. The Meity consultation papers suggest timelines within 2025. Loyalty heads who wait for the Rules to be finalised before re-architecting their consent infrastructure will find themselves scrambling to retrofit compliance into campaign workflows that were never designed for it.

For mall operators specifically, the complexity multiplies. A Select CITYWALK loyalty member interacts with 30+ brand tenants. Each brand may have its own communications preference, its own promotional cadence, its own CRM. The mall's data sharing agreements with tenants are now squarely in DPDP territory — passing member mobile numbers to a new F&B tenant for an opening offer is a secondary processing activity that requires explicit consent from the member. Getting that consent architecture right, and automating it at scale, is the defining CRM challenge of the next two years for any serious mall operator in India.

Risks of Ignoring Consent in Loyalty Campaigns

The risk calculus for ignoring consent in automated loyalty campaigns has changed fundamentally. Until 2023, the practical downside was mostly reputational: a complaint on Twitter, a churn spike after an aggressive SMS blitz, maybe a TRAI complaint. Under DPDP, the downside includes regulatory enforcement with teeth. The Data Protection Board can impose penalties that, for large retail chains and mall operators, are material. A programme operating 50 lakh members without a verifiable consent record is not running a loyalty programme — it is running a liability.

Beyond regulatory penalties, there is a campaign effectiveness argument that is equally compelling. Un-consented campaigns perform badly. A member who receives a WhatsApp message from a brand they do not recall opting into does not convert — they block. In a platform like Manyavar or FabIndia where the brand relationship is deeply personal and values-driven, a WhatsApp blast to a member who gave only email consent is not just a compliance breach; it is a brand equity erosion event. The 3.2x conversion premium cited above for explicit-consent campaigns is not accidental — when a member has consciously opted in for a specific type of communication, their intent and receptivity are categorically higher.

For mall operators, the inter-brand data sharing risk is particularly acute. If Phoenix Marketcity shares a member's purchase history with a new jewellery anchor tenant to seed their opening campaign, and that member never consented to data sharing with third-party tenants, the mall — as Data Fiduciary — is in violation, not the tenant. The contractual indemnity clauses that most mall data sharing agreements currently contain are not a substitute for consent. They redistribute liability; they do not eliminate it.

Operational risk is the third dimension. Loyalty programmes that run consent logic manually — through suppression lists exported weekly, or through a CRM filter applied at campaign build time — are one system lag away from a violation. A member who withdraws consent on Monday will still receive the Tuesday drip campaign if the suppression list runs weekly. Automated workflow engines like those in Capillary Loyalty+, WebEngage, or MoEngage can fire thousands of messages per hour. Without real-time consent propagation baked into the workflow engine itself, the speed of automation becomes the speed of potential violation. This is not a theoretical scenario — it is a routine operational gap in the majority of Indian loyalty stacks today.

Tools for Automating Consent Capture and Management

Automating consent management in a loyalty context requires capability across four distinct layers: capture, storage, propagation, and governance. Most Indian loyalty operators have partial solutions at one or two layers but lack an integrated architecture that connects all four.

At the capture layer, the gold standard is a dynamic consent widget — a mobile-first UI component that presents consent choices in plain, DPDP-compliant language at enrolment, at every subsequent channel opt-in, and whenever the programme's data processing purposes change. The language must meet the Act's 'clear and plain language' standard, which effectively means no legalese. Platforms like Wondersoft and GoFrugal handle billing and POS but have no native consent capture widget. POSist and Petpooja are kitchen and operations platforms — consent is entirely outside their scope. The loyalty-specific players — EasyRewardz, Almonds.ai, Xeno — have opt-in fields but few have built a fully DPDP-compliant dynamic consent UI as of mid-2024.

At the storage layer, consent must be maintained as a structured data object: member ID, purpose, channel, consent status, timestamp, version, and the exact consent text the member agreed to. This is not a Boolean flag in a CRM field. It is a multi-dimensional record that needs its own data model. Xeno and Customer Capital store basic opt-in status, but neither publicly documents a versioned consent ledger architecture. MoEngage and WebEngage, primarily engagement platforms rather than loyalty platforms, have consent preference centres but are not built to handle the loyalty-specific complexity of tiered rewards, tenant data sharing, and mall-level member identity.

At the propagation layer, the hard problem is ensuring that a consent change made by a member — via USSD, WhatsApp, the mall app, or a POS terminal — propagates instantly to every active automated workflow. This requires an event-driven architecture where a consent withdrawal fires a webhook that immediately pauses or re-routes every in-flight campaign that touches that member. Very few Indian loyalty platforms have this capability natively today.

At the governance layer, programme operators need dashboards showing consent coverage rates by channel, consent withdrawal trends by campaign type, and exception reports for any automated send that bypassed consent logic. This is the audit infrastructure that the DPDP Board will ask for in an investigation. Building it after the fact is expensive and often incomplete.

KPIs to Track Consent Health Across Your Loyalty Programme

Consent management is not a one-time compliance project — it is an ongoing operational discipline that needs its own set of performance indicators. Loyalty heads who embed consent health metrics into their monthly review cadence will catch problems early; those who treat consent as an IT project to be signed off and forgotten will face enforcement scenarios they cannot explain to their boards.

The primary KPI is Consented Campaign Coverage Rate: the percentage of your total active loyalty base that has valid, purpose-specific, DPDP-compliant consent for your primary campaign channels. For a mall programme, track this separately for SMS, WhatsApp, push notifications, and email. A programme with 10 lakh members but only 6 lakh with documented WhatsApp consent should be sending WhatsApp campaigns to 6 lakh members, not 10 lakh. The gap between your total base and your consented base is your compliance exposure.

The second KPI is Consent Withdrawal Rate by Campaign Type. If your weekly flash sale SMS is generating a 3% withdrawal rate and your personalised anniversary email is generating 0.2%, the data is telling you something important: the flash sale SMS is perceived as intrusive. This is simultaneously a compliance signal and a campaign quality signal. High withdrawal rates should trigger a campaign design review, not just a suppression list update.

Third, track Consent Propagation Latency — the time between a member withdrawing consent and that withdrawal being reflected across all active automated workflows. The target is under two minutes. If your current stack takes 24 hours or more, you are running a structural compliance risk at the speed of your automation engine.

Fourth, monitor the Consent Record Completeness Score: what percentage of your member records have a fully populated consent data model (purpose, channel, version, timestamp, text) versus members with only a legacy opt-in Boolean. This metric tells you how far through your DPDP readiness journey you actually are. Cafe Coffee Day, for example, has one of India's largest loyalty databases — but the consent infrastructure underneath it was built for a pre-DPDP world and is likely to require significant remediation.

Finally, track Consent-Driven Segment Shrinkage Against Campaign Performance. As you tighten consent logic, your campaign audiences will shrink. Track whether the resulting campaigns deliver higher per-member revenue — the hypothesis is that a smaller, fully consented audience converts better than a larger, poorly consented one. If the data confirms this, you have a business case for consent-native automation that goes well beyond compliance.

How Fundle solves this

Vineet Narang built Fundle on a specific thesis: that the next generation of Indian retail loyalty would be won or lost on data trust, not discount depth. That thesis has aged well. The Fundle AI Platform is architecturally consent-native — consent is not a module bolted on for compliance, it is the data layer that every campaign workflow reads before it executes. Fundle's ConsentFirst CMP automates compliance and consent management for 1.33 crore+ loyalty members in India, making it the largest consent-managed loyalty infrastructure in the country's organised retail sector.

For mall operators, Fundle Mall Loyalty treats the mall as a data fiduciary and each brand tenant as a downstream data processor, with consent flags governing exactly what each tenant can access and what automated communications they can trigger against any given member. When a new anchor tenant joins a mall on the Fundle platform, they do not receive a member data dump — they receive access to a consent-gated API that returns only records where the member has explicitly opted in to communications from 'new brand partners at this mall.' This is not just DPDP compliance; it is a commercially differentiated tenant proposition that makes the mall's data ecosystem genuinely valuable and trustworthy.

For enterprise retail brands, Fundle Brand Loyalty integrates with existing POS environments — including Wondersoft, GoFrugal, POSist, and Petpooja — and captures consent at the transaction moment, not as a separate process. The Fundle AI Agents handle the consent re-enrolment journey autonomously: an AI agent identifies members with incomplete consent records, designs a personalised re-consent offer based on that member's tier and purchase history, and executes the outreach through the member's last-verified channel — all without a human campaign manager having to build a suppression list or run a manual query.

Fundle Agentic AI and Fundle AI Workflow bring consent management into the campaign automation layer in a way that no incumbent Indian loyalty platform currently matches. Every workflow node has a consent check as a first-class condition — not a filter applied at send time, but a real-time gate that reads the Fundle consent ledger and routes, pauses, or escalates based on what it finds. If a member's WhatsApp consent is withdrawn mid-journey, the Fundle AI Workflow automatically re-routes that member's remaining journey nodes to email, logs the routing decision with a timestamp, and flags the workflow exception in the governance dashboard — all without human intervention. This is what consent-native campaign automation actually looks like in production, as opposed to what most loyalty platforms describe in their sales decks.