“Fundle AI Agents are not chatbots. They are autonomous strategists — analysing cohorts, picking offers, scheduling sends and reading back ROI without a brief.”
VN
Vineet NarangCo-founder, Fundle · LinkedIn
TL;DR
  • •Understand exactly which DPDP 2023 obligations apply to tier-based loyalty programs collecting PII at enrolment
  • •Recognise why legacy opt-in checkboxes and bundled consent forms break under the new law
  • •See how Fundle's ConsentFirst CMP structures granular, auditable consent across every loyalty touchpoint
  • •Track the right KPIs — consent capture rate, preference update frequency, opt-out recovery — to protect data assets
  • •Implement a five-step ConsentFirst playbook that covers POS, app, WhatsApp and in-mall kiosk enrolment flows

India's ₹8.5 lakh crore organised retail sector has spent the last decade building loyalty programs on a simple, implicit bargain: give us your phone number, earn points, get discounts. Tier-based loyalty programs — Silver, Gold, Platinum — became the standard scaffolding for brands like Tanishq, Manyavar, Lifestyle and Reliance Trends. Malls like Phoenix Marketcity and Select CITYWALK ran unified wallet programs that stitched together data across 150–300 tenants. The economics worked. Tier members spend 2.3x more per visit, visit 1.8x more frequently, and generate 60–70% of revenues for the brands that track cohort data properly. The machine ran on data. Nobody asked members if they minded.

That era is ending. The Digital Personal Data Protection Act, 2023 (DPDP Act) received Presidential assent in August 2023. The rules, expected to be notified in 2024–25, will impose explicit consent requirements, data principal rights (access, correction, erasure, nomination), purpose limitation, and stiff penalties — up to ₹250 crore per breach instance — on any data fiduciary processing personal data of Indian citizens. A loyalty program is, by legal definition, a large-scale personal data processing operation. Every enrolment form, every transaction record, every birthday field, every purchase-history inference feeds a profile that squarely falls under the Act. Most Indian brands and mall operators are not ready.

The core problem is structural. Loyalty platforms in India were built to maximise data collection, not to respect data purpose. A customer who joins a mall loyalty program to earn parking points did not consent to her purchase history being shared with 40 tenants for targeted advertising. A Pantaloons member who ticked a generic 'I agree to terms' checkbox has not, under DPDP, given free, specific, informed and unambiguous consent to receive SMS campaigns every Tuesday. The old consent architecture — a single checkbox at enrolment, buried in a 4,000-word T&C — is legally void under the new framework.

This is where Fundle.ai's ConsentFirst architecture enters the picture. ConsentFirst is not a bolt-on compliance checkbox; it is a consent management philosophy embedded into the core of how tier-based loyalty programs in India should be designed from the ground up. This article walks retail loyalty heads and CRM managers through the DPDP obligations that matter most, the specific friction points in loyalty consent flows, and a practical playbook for getting compliant without destroying enrolment conversion rates.

The DPDP Compliance Gap in Indian Retail Loyalty — By the Numbers

₹250 Cr
Maximum penalty per breach instance under DPDP Act 2023 — the ceiling that makes non-compliance an existential risk for large retail chains
78%
Of Indian loyalty programs still rely on a single bundled opt-in checkbox at enrolment, which fails DPDP's specificity and granularity test
2.3x
Average spend uplift from Platinum-tier members versus non-members at organised retail brands — the business case for fixing, not scrapping, tier programs
Millions
Of tier program members whose data Fundle's ConsentFirst CMP manages for DPDP compliance, aligning with DPDP 2023 obligations at scale

Understanding DPDP Consent Requirements for Tier Based Loyalty Programs India

The DPDP Act establishes the concept of 'consent' as the primary lawful basis for processing personal data in a commercial loyalty context. Unlike GDPR, which offers six alternative legal bases, DPDP's commercial context largely defaults to explicit consent — which means the old 'legitimate interest' escape hatch that European brands sometimes used is not straightforwardly available to Indian operators. Consent under DPDP must be free (no coercion or conditionality), specific (tied to a defined purpose), informed (the data principal understands what they are agreeing to), unconditional (not bundled with unrelated permissions), and unambiguous (an affirmative act, not a pre-ticked box).

For a tier-based loyalty program, this has three immediate structural implications. First, purpose limitation: if a customer joins a mall program to earn points on retail purchases, the data collected at enrolment can only be used for that stated purpose unless fresh, purpose-specific consent is obtained for each additional use — marketing communications, third-party tenant sharing, analytics profiling, and so on. Second, data minimisation: fields like 'annual income', 'vehicle owned', and 'number of children' — common in premium tier enrolment forms at jewellery and lifestyle brands — need explicit justification and separate consent. Third, the right to withdraw: the data principal must be able to withdraw consent at any time with the same ease with which it was given. If enrolment takes 90 seconds on a POS kiosk, opt-out must also take 90 seconds — not a five-step call-centre journey.

The Act also introduces Data Fiduciary obligations that are directly relevant to mall operators running multi-brand programs. When Phoenix Marketcity runs a unified loyalty program and shares transaction data with 200 tenant brands, both the mall (as the primary fiduciary) and each tenant brand (as a data processor under contract) carry compliance obligations. Every data-sharing agreement needs to specify purpose, retention period, and processing restrictions. Absence of these agreements is not just a compliance gap — it is a ₹250 crore liability.

For loyalty heads at brands like FabIndia, Apollo Pharmacy, or Cafe Coffee Day, the DPDP obligations cluster around three operational moments: enrolment (consent capture), engagement (consent-gated communication), and off-boarding (erasure and portability). Most existing tech stacks — whether running on POSist, Petpooja, GoFrugal, or Wondersoft — have POS-side data capture but zero consent orchestration layer. The gap between data collection and consent management is where DPDP risk concentrates.

The DPDP Consent Funnel for Tier Loyalty Enrolment

Member Enrolment — Capture name, mobile, email with purpose-specific disclosure — Stage 1Granular Consent — Separate opt-ins for marketing, profiling, third-party sharing — Stage 2Tier Activation — Confirm data use scope per tier benefit (e.g., birthday offers need DOB consent) — Stage 3Ongoing Engagement — Consent-gated campaigns; re-consent on purpose change — Stage 4
Each stage represents a mandatory consent gate under DPDP 2023. Drop-off at any stage without proper consent architecture creates legal exposure for the data fiduciary.

Challenges in Consent Collection for Loyalty Programs

The challenges in retrofitting DPDP-compliant consent onto existing loyalty programs are not theoretical. They are operational, commercial, and — for large mall and brand operators — existential in scale. The first challenge is enrolment friction. Studies across Indian retail contexts show that every additional field or screen in a POS enrolment flow reduces conversion by 8–12%. Granular consent — separate opt-ins for transactional communications, promotional SMS, email marketing, WhatsApp campaigns, data sharing with group companies, and third-party tenant sharing — can easily require six to eight separate affirmative actions. Done naively, this destroys enrolment rates. A Reliance Trends store associate running a 200-customer queue at a weekend sale is not going to patiently walk each customer through eight consent toggles.

The second challenge is consent record-keeping at scale. Fundle's ConsentFirst CMP manages data privacy compliance for millions of tier program members aligning with DPDP 2023. This is not a reporting exercise — it is a real-time audit trail requirement. Every consent event (given, modified, withdrawn) must be timestamped, source-attributed (POS terminal ID, app session ID, kiosk location), and immutably stored. Legacy CRM systems — including many mid-market platforms — store consent as a binary flag in a member table. That architecture cannot pass a DPDP audit.

The third challenge is multi-channel consent reconciliation. A customer who enrolled at a Lenskart store, later downloaded the app, and also interacted with a mall loyalty kiosk may have given different consent at each touchpoint. The canonical consent record must be unified, and conflicts resolved using a last-explicit-action rule. Without a centralised consent management platform, this is impossible to enforce. Competing platforms like Capillary, EasyRewardz, and Xeno have strong CRM orchestration capabilities but do not offer purpose-built DPDP consent management as a first-class module — consent is typically an add-on field, not a workflow layer.

The fourth challenge is the right to withdraw and erasure. Under DPDP, a member can demand that a brand erase all their personal data. For a tier-based loyalty program, this creates a cascade: points balance must be voided, transaction history anonymised, profile deleted, and downstream data processors (tenant brands, analytics vendors, WhatsApp BSPs) notified within a defined window. Most Indian loyalty operators have no automated erasure workflow. This is not a small engineering task — it requires orchestration across POS systems, CRM, analytics warehouses, and communication platforms simultaneously.

Legacy Consent vs. ConsentFirst Architecture: What Changes

Legacy Loyalty Consent (Pre-DPDP)
Fundle ConsentFirst Architecture (DPDP-Ready)
✗Single checkbox: 'I agree to T&C and marketing communications'
✓Granular toggles per purpose: transactional, promotional, profiling, third-party sharing — each independently stored
✗Consent stored as binary flag (Y/N) in CRM member table, no timestamp
✓Immutable consent ledger with timestamp, source channel, IP/device ID, and version of consent notice shown
✗Opt-out requires calling customer care or visiting store; no self-serve portal
✓Always-on Preference Centre accessible via app, WhatsApp, or web — withdrawal in under 60 seconds
✗Data shared with tenant brands and analytics vendors without specific member consent
✓Purpose-limited data sharing gates: each downstream processor requires explicit consent event before data transfer
✗Erasure request handled manually by CRM team over 7–30 days with no audit trail
✓Automated erasure workflow triggers across POS, CRM, analytics and communication stacks with timestamped proof

How Fundle's ConsentFirst Works in Practice

Fundle's ConsentFirst is a dedicated consent management layer built into the Fundle AI Platform that sits between enrolment touchpoints and the core loyalty engine. It is not a pop-up disclaimer module. It is a workflow-level consent orchestrator that ensures no personal data moves within the loyalty stack without a corresponding, valid, auditable consent record. Here is how it works across the key operational moments.

At enrolment — whether on a POS terminal running POSist or GoFrugal, a branded app, a WhatsApp flow, or an in-mall kiosk — ConsentFirst presents a smart, progressive consent UI. Instead of dumping eight toggles on the member at once, it uses an adaptive sequence: mandatory data for tier activation (name, mobile) is collected first with minimal friction, followed by a 'supercharge your benefits' screen where optional consents (birthday offers, WhatsApp campaigns, tenant partner deals) are presented with clear benefit-value framing. This design, validated across Fundle's deployments, maintains enrolment conversion within 4–6 percentage points of legacy single-checkbox flows while capturing granular, legally valid consent.

Every consent event — initial capture, modification, withdrawal — is written to Fundle's Consent Ledger, an append-only audit store. Each record carries: timestamp (IST), channel source, consent notice version displayed, member action, and a cryptographic hash for tamper-evidence. When a DPDP regulator requests proof of consent for a specific member, the loyalty team can produce a complete, machine-readable audit trail in minutes, not days.

Fundle AI Agents power the Preference Centre experience. Members can interact with their consent preferences via a conversational interface on WhatsApp — asking 'stop sending me SMS' or 'what data do you have about me' — and the Fundle Agentic AI interprets the intent, executes the preference update, confirms it to the member, and propagates the change across all connected systems in real time. This meets the DPDP requirement that withdrawal be 'as easy as' giving consent. For Fundle Mall Loyalty deployments at large multi-tenant properties, the ConsentFirst layer also manages tenant-level consent scopes, ensuring that a member's consent to receive offers from a specific tenant category (say, F&B) does not automatically extend to fashion or jewellery tenants.

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.

5-Step ConsentFirst Implementation Playbook for Indian Retail Brands

01

Consent Audit of Existing Member Base

Before going live with DPDP-ready flows, audit your existing member database. Tag every member record with a consent confidence score: (a) no consent record at all, (b) bundled checkbox only, (c) granular consent captured. Members in categories (a) and (b) must be re-consented before they can receive marketing communications post-DPDP enforcement. Plan a re-consent campaign via transactional SMS or app notification — not promotional channels — offering a tier point incentive for completing the preference centre setup.

02

Purpose Mapping and Data Minimisation

Map every data field in your enrolment form to a specific loyalty purpose. For each field, answer: (1) Is this strictly necessary for tier activation? (2) If not, what specific benefit does the member receive by sharing this? (3) Is there a consent notice that explains this clearly? Fields that fail all three tests should be removed. For jewellery brands like Tanishq or apparel brands like Manyavar, this exercise typically removes 3–5 enrolment fields, which paradoxically improves completion rates.

03

Design Granular Consent UI Across All Channels

Work with your POS, app, and kiosk vendors to implement ConsentFirst's consent UI components. Each consent purpose must have its own toggle, its own plain-language description (written at a Class 8 reading level in English and the relevant regional language), and its own stored record. Use progressive disclosure — lead with the minimum required for tier activation, present optional consents in a second screen framed around member benefit, not brand benefit.

04

Integrate Consent Ledger with CRM and Communication Stack

Connect the Consent Ledger to your campaign orchestration layer. Before any communication is triggered — SMS via a BSP, email via a marketing automation tool, WhatsApp via a WABA partner — the system must query the ledger and confirm the member has valid, in-scope consent for that specific channel and purpose. MoEngage, WebEngage, and Xeno are common campaign tools in Indian retail; all can be configured to call a consent API gate before execution. This is the step that most brands skip, and it is the most operationally critical.

05

Activate Self-Serve Preference Centre and Erasure Workflow

Launch the Preference Centre before going live with DPDP-compliant enrolment. Accessible via app, web, and WhatsApp, it should allow members to: view all data held, update preferences by purpose, withdraw specific or all consents, request data correction, and submit erasure requests. Automated erasure workflows must trigger across POS systems, CRM, analytics data warehouse, and downstream processors within your legally committed response window (target: 30 days or less). Test this end-to-end with synthetic member records before production rollout.

Customer Trust Benefits and KPIs to Track

Privacy compliance done right is not a cost centre — it is a customer trust asset. Across markets where GDPR-equivalent legislation preceded commerce (UK, Germany, Australia), brands that invested in transparent consent architectures saw measurable lifts in programme participation quality: fewer members, but higher engagement, higher average transaction values, and lower churn. The logic is straightforward — a member who actively opted into your birthday offer communication is more likely to redeem it than a member who was silently enrolled. Indian retail data shows that opted-in WhatsApp campaign recipients at loyalty programs convert at 3.1–4.2x the rate of SMS blast recipients, even when the message content is identical. Consent signals purchase intent.

For Fundle Brand Loyalty and Fundle Mall Loyalty operators, the KPIs that matter in a ConsentFirst regime differ from legacy loyalty metrics. Consent capture rate at enrolment (target: 70%+ for transactional communications, 45%+ for marketing communications) measures whether your consent UI is effectively communicating member value. Preference update frequency measures member engagement with their own data — an active, updating member is a highly engaged member. Opt-out recovery rate (the percentage of members who withdraw consent but re-consent within 90 days when re-approached via a compliant channel) reveals the quality of your value proposition. Erasure request volume is a negative indicator — high volumes signal that members feel they cannot manage their relationship with your brand in any other way.

Brands should also track consent-gated campaign deliverability separately from total campaign reach. A Pantaloons campaign reaching 800,000 consented members and converting at 4% generates 32,000 transactions. The same campaign reaching 1.2 million un-consented members converting at 1.2% generates 14,400 transactions — and potentially a ₹250 crore penalty. The math on compliance is not subtle.

For mall operators running multi-tenant programs, tenant-level consent analytics become a new commercial asset. Knowing that 62% of Gold-tier members have consented to F&B tenant offers but only 28% to financial services offers is actionable segmentation intelligence. Fundle AI Workflow can surface these consent cohorts in real time, allowing tenant managers to plan campaigns within their legal scope rather than guessing at reach.

DPDP Readiness Checklist for Tier Loyalty Program Operators
  • Completed a consent audit of your full member database — every record tagged with a consent confidence score (none / bundled / granular)
  • Removed all pre-ticked consent checkboxes from enrolment flows across POS, app, web and kiosk channels
  • Mapped every enrolment data field to a specific, documented loyalty purpose; removed fields that fail the purpose-limitation test
  • Implemented a granular consent UI with per-purpose toggles and plain-language descriptions in English plus at least one regional language
  • Connected the Consent Ledger to campaign execution platforms so every outbound communication queries consent status before delivery
  • Launched a self-serve Preference Centre allowing members to view data, update preferences and submit erasure requests in under 60 seconds
  • Documented all data-sharing agreements with downstream processors (tenant brands, analytics vendors, WhatsApp BSPs) with purpose, retention period and processing restrictions
“In India, the brands that will win the next decade of retail loyalty are those who treat consent not as a legal checkbox but as the first transaction of trust with their customer.”
VN
Vineet NarangCo-founder, Fundle · LinkedIn

How Fundle solves this

The Fundle AI Platform was architected from the ground up with the assumption that data privacy is not a compliance afterthought — it is the operating condition of modern Indian retail loyalty. Vineet Narang's founding vision for Fundle was precisely this: that AI-driven loyalty must earn the right to personalise by first earning the member's trust, and that earning trust requires a consent-first operating model baked into every workflow, not patched on top.

Fundle Loyalty — encompassing both Fundle Mall Loyalty for multi-tenant property operators and Fundle Brand Loyalty for single-brand retail chains — ships with ConsentFirst as a core module, not an optional add-on. The Consent Ledger is a first-class data store within the platform, sitting at the same architectural level as the points engine and the tier eligibility engine. Before any Fundle AI Agent executes a personalisation action — whether that is a tier upgrade notification to a Platinum member at Phoenix Marketcity or a birthday offer dispatch to a Gold member at a Select CITYWALK tenant brand — it queries the Consent Ledger. No valid consent record, no data movement. This is enforced at the platform layer, not at the campaign configuration layer, which means it cannot be bypassed by a campaign manager under deadline pressure.

Fundle AI Agents handle the full lifecycle of consent management conversationally. A member texting 'stop birthday messages' on WhatsApp is understood by the Fundle Agentic AI, which disambiguates the request (birthday promotional messages vs. birthday transactional confirmations), updates the specific consent record, confirms the action to the member in natural language, and propagates the change to the communication stack — all within seconds, without human intervention. This is the only architecture that meets DPDP's 'ease of withdrawal' requirement at the scale of millions of tier program members.

Fundle AI Workflow powers the operational side: re-consent campaign orchestration for legacy member bases, automated erasure workflow execution across connected POS and CRM systems, tenant-level consent analytics dashboards for mall operators, and DPDP audit report generation on demand. For loyalty heads at brands considering migration from platforms like Capillary, EasyRewardz, or Customer Capital, the ConsentFirst architecture represents a structural differentiation — not a feature, but a compliance guarantee embedded in the platform's DNA. Indian retail loyalty is entering a regulated era. Fundle is the platform built for it.

Frequently asked

Does DPDP Act apply to loyalty programs specifically, or only to financial and healthcare data?+

DPDP Act 2023 applies to all personal data of Indian citizens processed digitally, with no sector carve-outs for loyalty programs. Any loyalty program collecting name, mobile number, purchase history, or behavioural data is processing personal data and must comply with consent, purpose limitation, and data principal rights obligations.

Can we grandfather existing loyalty members under old consent records, or do we need to re-consent everyone?+

Members enrolled under bundled or undocumented consent must be re-consented before they can receive any marketing communications under DPDP's stricter standard. Transactional communications (points balance updates, tier status changes) may continue under a legitimate interest argument pending rule notification, but this is a legal grey area. A proactive re-consent campaign is strongly advisable.

How does ConsentFirst handle consent for members enrolled at third-party tenant stores within a mall loyalty program?+

Fundle Mall Loyalty's ConsentFirst architecture treats each tenant enrolment point as a distinct consent source. Consent given at a tenant's POS is scoped to that tenant's processing purposes. Cross-tenant data sharing — such as a mall operator sharing transaction data across tenants for unified analytics — requires a separate, explicitly scoped consent event. The Consent Ledger maintains tenant-level consent scopes independently.

What happens to a member's tier status and points balance if they withdraw consent and request erasure?+

Erasure under DPDP means the brand must delete personal data. Points balances tied to a personal profile must be voided, and transaction history anonymised or deleted. Brands should clearly communicate this consequence at the point of erasure request — not as a deterrent, but as transparency. A well-designed Preference Centre distinguishes between withdrawing marketing consent (which preserves tier status) and full erasure (which ends the loyalty relationship).

How does Fundle's ConsentFirst compare to what platforms like Capillary or EasyRewardz offer for DPDP compliance?+

Capillary and EasyRewardz are strong CRM and campaign orchestration platforms, but DPDP consent management is not a first-class module in either product. Consent is typically handled as a CRM field or a campaign suppression list, not as an auditable, purpose-mapped workflow layer. Fundle's ConsentFirst is purpose-built as a consent orchestration layer integrated directly into the loyalty engine — a structural difference, not a UI feature.

What is a realistic timeline to implement ConsentFirst for an existing tier-based loyalty program with 500,000 members?+

For a brand with a single-tier POS system and an existing app, a ConsentFirst implementation typically runs 10–14 weeks: 2 weeks for consent audit and purpose mapping, 3 weeks for UI development and Consent Ledger integration, 2 weeks for campaign gate integration, 2 weeks for Preference Centre build and testing, and 2–3 weeks for re-consent campaign execution. Multi-tenant mall programs with complex tenant data-sharing agreements add 4–6 weeks for legal documentation alignment.

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 · LinkedIn

Vineet 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.

Hi 👋 I'm Abhinav

Got a loyalty or ADSR question?