“Most platforms automate marketing. Fundle automates outcomes — incremental revenue, retention lift, attributed footfall. The number is the product.”
- •Understand why India's Digital Personal Data Protection Act 2023 rewrites the loyalty data rulebook
- •Design consent experiences that feel like value exchange, not legal fine print
- •Implement data minimisation so your loyalty stack collects only what actually drives revenue
- •Measure trust as a KPI alongside redemption rate and NPS
- •Deploy Fundle AI Platform's privacy-safe architecture to stay compliant without sacrificing personalisation
India's loyalty industry is sitting on a powder keg of its own making. Brands have spent the last decade vacuuming up consumer data — mobile numbers, purchase histories, location pings, browsing trails — under the assumption that more data always means better personalisation. The bill has arrived. India's Digital Personal Data Protection Act 2023 (DPDP Act) passed by Parliament in August 2023 fundamentally reframes the relationship between a brand and the consumer data it holds. For retail CMOs and CIOs running loyalty programmes at scale — whether for a Phoenix Marketcity, a Tanishq, a Reliance Trends, or a Lifestyle — the question is no longer whether to comply, but how to compete on consent.
The numbers clarify the stakes immediately. A 2023 LocalCircles survey found that 78% of Indian internet users felt brands were collecting more data than necessary, and 61% said they would switch to an alternative brand or service if given clearer privacy controls. In a market where a loyalty programme's primary currency is trust, that is an existential signal. The Indian consumer is not a passive data subject waiting to be monetised — she is increasingly aware, increasingly mobile-first, and now, increasingly protected by law. A privacy first loyalty platform India-wide is no longer a differentiator; it is the price of entry.
The irony is that the loyalty platforms most likely to win the next decade are those that treat consent as a product feature, not a compliance checkbox. When a member at Select CITYWALK opts in to location-based offers because she genuinely believes it benefits her, the quality of that first-party signal is orders of magnitude higher than a passive data trail collected without explicit awareness. Consent-based loyalty data management is, in practice, a data quality strategy. Brands running on platforms that default to opt-out or bundle consent into 47-clause privacy policies are not just legally exposed — they are sitting on noisy, low-intent data that produces mediocre CRM outcomes.
Fundle was built on the premise that privacy and personalisation are not in tension — they are compounding forces when the architecture is right. This article is a field guide for the Indian retail CMO or CIO who needs to redesign loyalty infrastructure before the DPDP Rules land, without sacrificing the engagement metrics their board is watching. We will walk through the legal landscape, the consumer psychology, the system design choices, and the KPIs that distinguish a trust-led loyalty programme from a compliance-lite one.
The Privacy-Loyalty Gap in Indian Retail: By the Numbers
Understanding Indian Consumer Privacy Expectations
The Indian consumer's relationship with data privacy is often mischaracterised as apathetic. The empirical record says otherwise. A 2022 IAMAI-Kantar study found that 74% of Indian smartphone users had deliberately withheld personal information from an app or brand at least once in the prior six months. Among urban millennials — the core loyalty programme demographic for brands like FabIndia, Manyavar, and Cafe Coffee Day — that figure rose to 83%. This is not apathy; it is strategic withholding driven by a rational cost-benefit calculation that brands have consistently lost.
The calculation works like this: the consumer asks herself, 'What tangible benefit do I receive in exchange for sharing this specific piece of information?' If the answer is unclear — which it usually is when a mall loyalty app asks for date of birth, residential pincode, income bracket, and purchase category preferences at the point of registration — the consumer either abandons registration or provides false data. Loyalty programmes in India routinely report 20–35% dirty data rates in their member databases, a direct consequence of this friction. A Capillary Technologies benchmark from 2022 estimated that Indian retailers lose approximately ₹180 per member per year in misallocated marketing spend because of poor data quality — a problem that consent-first design solves at the root.
There is also a generational shift underway. Gen Z consumers entering the spending funnel today have grown up with GDPR headlines, WhatsApp privacy update controversies, and Aadhaar data breach news cycles. They are sceptical by default. When Pantaloons or Apollo Pharmacy enrolls a 22-year-old into a loyalty programme, that member's willingness to share rich behavioural data is directly proportional to how transparent and controllable the data experience feels. Programmes that lead with clear value propositions — 'Share your purchase preferences and we will personalise your reward calendar' — consistently outperform programmes that bury data uses in a terms-of-service link.
Finally, trust asymmetry matters enormously in the Indian context. Unlike Western markets where brand trust is often mediated by regulatory certainty, Indian consumers place enormous weight on relational trust — the sense that a brand genuinely acts in their interest. When a loyalty programme operator respects a member's stated preferences, honours opt-out requests promptly, and sends communications that feel relevant rather than intrusive, that relational trust translates directly into higher active member rates, larger basket sizes, and lower churn. Building a privacy first loyalty platform India consumers believe in is therefore both an ethical obligation and a measurable revenue strategy.
The Consent-Quality Funnel: From Registration to Revenue
Legal Frameworks Protecting Consumer Privacy in India
The DPDP Act 2023 is the centrepiece of India's data privacy architecture, but it sits within a broader legal ecosystem that retail loyalty operators must map with precision. The Act establishes seven core principles: lawfulness and consent; purpose limitation; data minimisation; accuracy; storage limitation; security; and accountability. Every one of these principles has direct design implications for how a loyalty platform collects, stores, and activates member data. The consent requirement alone — explicit, informed, granular, and revocable — dismantles the legacy model of bundled consent that most Indian loyalty programmes currently operate on.
Under the DPDP Act, a Data Fiduciary (the brand or mall operator running the loyalty programme) must obtain consent through a 'consent notice' that is clear, standalone, and not bundled with terms and conditions. Critically, consent must be specific to the purpose of data processing. This means a Phoenix Marketcity loyalty programme cannot use a single consent checkbox to cover purchase tracking, location-based marketing, third-party brand partner data sharing, and behavioural profiling simultaneously. Each processing purpose requires a separate, freely given consent signal. For large mall loyalty programmes managing data across 150–200 brand tenants, this is an architectural redesign challenge, not merely a legal one.
The Information Technology (Amendment) Rules 2023 and the proposed DPDP Rules (expected to be notified in 2024–25) add further granularity. The Rules are expected to mandate that Data Fiduciaries provide a 'Data Principal Dashboard' — effectively a self-service privacy control centre — to every registered user. For CIOs at organisations like Reliance Retail or Lifestyle Stores, this means loyalty platform infrastructure must expose APIs that allow members to view what data is held, correct inaccuracies, restrict processing categories, and trigger erasure requests, all within defined SLA windows. The penalty framework — up to ₹250 crore per breach instance, with a total cap of ₹500 crore per organisation — concentrates minds at the board level.
Beyond the DPDP Act, the RBI's guidelines on consent for payment data, TRAI's regulations on unsolicited commercial communications, and SEBI's forthcoming data governance norms for listed entities all intersect with how loyalty platforms handle the transaction-level data that powers points accrual, cashback, and reward redemption. A CIO designing loyalty infrastructure in 2024 cannot treat compliance as a single-team problem — it requires integration between legal, technology, marketing operations, and the loyalty platform vendor. The platforms that have built consent management and data rights into their core data models (rather than bolting on a consent widget) are the ones that will scale without accumulating regulatory liability.
Consent-Bundled Loyalty vs. Consent-Granular Loyalty: What Changes
Designing User-Friendly Consent Experiences for Loyalty
The most common mistake Indian loyalty operators make in privacy redesign is treating consent as a legal event rather than a product moment. When Lenskart or Manyavar asks a new member to agree to data terms, that interaction is simultaneously a trust signal, a data quality gate, and a brand experience moment. Designing it as a dense privacy notice with a single 'I agree' button is a failure on all three dimensions. The alternative — progressive consent design, where data permissions are requested contextually as benefits are unlocked — dramatically improves both compliance quality and member experience.
Progressive consent works as follows. At registration, the platform collects only the minimum data required to activate a member account: mobile number (for authentication), first name (for personalisation), and a single broad consent to loyalty programme participation. No income brackets. No household size. No date of birth unless the programme offers a birthday reward — and even then, the request is deferred until the member has had at least one positive engagement with the programme. This approach reduces registration drop-off by an estimated 28–34% compared with front-loaded data collection, based on benchmarks from loyalty programme redesigns in the Indian quick service restaurant and fashion segments.
The consent UX must also make the value exchange explicit in real time. When Tanishq's loyalty platform asks for purchase category preferences, the ask should be accompanied by a concrete benefit statement: 'Share your jewellery preferences and we will notify you 48 hours before a private preview sale — no general marketing unless you want it.' This transforms the consent moment from a compliance formality into a value negotiation that the member wins. Programmes that run controlled A/B tests on consent copy — comparing generic privacy language against benefit-led framing — consistently see 40–55% higher consent completion rates with the benefit-led variant.
For mall loyalty operators running programmes across multiple brand tenants — the typical structure at DLF Mall of India, Nexus Select Trust properties, or Phoenix Marketcity — consent architecture must handle data federation carefully. A member might consent to FabIndia accessing their fashion purchase history but explicitly decline to share that data with a co-tenanted consumer electronics brand. The loyalty platform's consent engine must enforce these member-level permissions at the API layer, not merely at the CRM campaign layer. Platforms like Fundle AI Platform that model consent as a first-class data entity — with versioning, audit trails, and real-time enforcement — make this technically tractable. Platforms that store consent as a binary flag in a CRM contact record do not.
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 Playbook: Redesigning Your Loyalty Programme for Privacy-First Data Collection
Audit Your Current Data Inventory
Map every data attribute your loyalty platform collects against the DPDP Act's purpose limitation principle. For each attribute, document: what business decision it informs, which team uses it, how frequently it is accessed, and whether the member explicitly consented to that specific use. In a typical Indian retail loyalty programme, 30–45% of collected attributes will fail this test immediately.
Redesign Consent Architecture at the Data Model Level
Work with your loyalty platform vendor to model consent as a versioned, member-level entity — not a checkbox field on the contact record. Each consent grant must carry: timestamp, consent version, channel of capture (app, POS, web, WhatsApp), purpose category, and expiry logic. This is the foundation that makes DPDP compliance operationally sustainable rather than a monthly fire drill.
Implement Progressive Consent UX Across All Touchpoints
Redesign registration and data enrichment flows to request permissions contextually and incrementally. Prioritise mobile-first consent interfaces given that 74% of Indian loyalty programme interactions happen on a smartphone. Test benefit-led consent copy against generic privacy language. Deploy consent preference centres that are accessible within two taps from any loyalty communication.
Build a Data Principal Dashboard into the Member Portal
This is not optional post-DPDP Rules notification. Every loyalty member must be able to view what data you hold, see a log of how it has been used, correct inaccuracies, restrict processing categories, and trigger erasure. For mall loyalty programmes, this dashboard must aggregate data across all brand tenant APIs in a unified member view — a significant integration challenge that must be scoped into platform architecture now.
Instrument Privacy KPIs into Your Loyalty Analytics Stack
Add consent completion rate, data accuracy rate, opt-out rate by channel, erasure request volume and SLA compliance, and data minimisation ratio (attributes collected vs. attributes actively used in the last 90 days) to your standard loyalty dashboard. These metrics should sit alongside redemption rate, active member rate, and NPS as first-class programme health indicators.
Ensuring Data Minimisation and Security in Loyalty Infrastructure
Data minimisation is the principle that loyalty platforms find most culturally difficult to embrace. The product instinct — hardwired into most loyalty platform vendors and the CRM teams that operate them — is to collect everything and figure out how to use it later. The DPDP Act's purpose limitation and data minimisation principles make this approach both legally untenable and, increasingly, commercially counterproductive. There is a direct correlation between the volume of data a loyalty programme collects at registration and its drop-off rate: every additional mandatory field reduces completion by approximately 7–12% in the Indian mobile-first context.
The commercial argument for minimisation is straightforward. A loyalty member at Cafe Coffee Day who provides verified purchase frequency data and a confirmed city of residence is a higher-value data asset than a member who has filled in 14 profile fields, half of which are inaccurate because they were mandatory at registration with no visible benefit attached. First-party data platform for loyalty India strategies that invert the traditional data collection sequence — earning data trust through repeated positive interactions before asking for richer profile information — consistently produce cleaner, more predictive data assets at lower regulatory risk.
On the security side, the DPDP Act mandates 'reasonable security safeguards' without prescribing specific standards — a deliberate flexibility that will likely be filled by the forthcoming DPDP Rules referencing existing frameworks like IS/ISO 27001, PCI-DSS (relevant for payment-linked loyalty programmes), and RBI's Master Directions on data governance. For loyalty CIOs, the practical checklist includes: encryption at rest and in transit for all member PII; role-based access controls that prevent marketing analysts from accessing raw mobile number databases; tokenisation of loyalty IDs so that analytical workloads never touch raw identifiers; and data residency compliance ensuring member data is stored on infrastructure located in India.
Vendor due diligence is equally critical. Many Indian loyalty programmes run on infrastructure that was originally built for a different regulatory context — platforms like EasyRewardz, Capillary, or WebEngage have varying degrees of built-in consent management maturity. When evaluating any loyalty platform vendor, the CIO must assess: whether consent is modelled as a first-class entity or a flag; whether the platform provides a member-accessible data dashboard out of the box; whether erasure workflows are automated or manual; and whether the vendor's own data processing agreements are DPDP-compliant. Outsourcing the loyalty platform does not outsource the regulatory liability — the brand remains the Data Fiduciary.
- Consent is modelled as a versioned, purpose-specific, member-level entity in the loyalty data model — not a single boolean flag
- Progressive consent UX is live: registration collects only authentication data; enrichment is deferred to contextual, benefit-led moments
- Data Principal Dashboard is accessible within two taps from the loyalty app home screen, showing full data inventory and consent log
- Automated erasure workflow is configured to complete within DPDP-mandated SLA; manual override is audited and exception-logged
- Data minimisation audit completed: every collected attribute is mapped to an active business decision made in the last 90 days
- Privacy KPIs (consent completion rate, opt-out rate, erasure SLA compliance, data accuracy rate) are included in the standard loyalty programme dashboard
- Vendor data processing agreements with all loyalty platform partners, analytics vendors, and brand tenant API consumers are reviewed and updated for DPDP compliance
“In Indian retail, the brand that earns the right to know its customer — through transparency, through value, through control given back to the member — will own the most predictive first-party data asset in the market. Privacy is not a cost; it is a competitive moat.”
How Fundle solves this
Fundle was purpose-built for the Indian market's specific complexity: multi-brand mall environments, high mobile-first usage, intense price sensitivity, and now a rapidly tightening regulatory environment. The Fundle AI Platform treats consent as a first-class data entity from the ground up. Every member record in the Fundle Loyalty engine carries a consent object with full versioning, purpose mapping, channel of capture, and expiry logic. When a brand tenant at a Phoenix Marketcity property sends a personalised offer through the Fundle Mall Loyalty programme, the platform's consent enforcement layer checks member-level permissions at the API call — not at the campaign scheduler. The result is that no communication is sent, and no data is shared, without a valid, purpose-specific consent signal on file.
Fundle Brand Loyalty takes this architecture downstream to individual retail brands — whether a fashion chain like Manyavar running its own loyalty programme or a pharmacy network like Apollo Pharmacy integrating loyalty with prescription data. For these operators, the consent architecture supports the DPDP Act's requirement for separate consent per processing purpose without forcing the member through a friction-heavy experience. Fundle's progressive consent UX — tested across Indian mobile-first member populations — serves consent requests at the moment of maximum perceived value, reducing the cognitive load while maximising the quality of the consent signal. This is why Fundle's loyalty platform is trusted by 1.33 crore members for privacy-safe engagement: members stay because the data relationship feels fair.
Fundle AI Agents add an operational layer that most loyalty platforms cannot offer: automated privacy workflow execution. When a member triggers an erasure request through the Data Principal Dashboard, a Fundle Agentic AI workflow initiates the multi-system deletion sequence — loyalty database, campaign history, analytics warehouse, and brand tenant API consumers — logging each step with a timestamp for regulatory audit. The same Fundle AI Workflow engine manages consent refresh campaigns: when a consent version is superseded (because the programme adds a new data processing purpose), the system automatically identifies affected members, pauses communications to those members, sends a consent refresh request with benefit-led framing, and resumes the communication stream only after a new valid consent is recorded. No manual intervention. No compliance gap.
Vineet Narang's founding vision for Fundle was that the loyalty industry's obsession with data volume was solving the wrong problem. The right problem is data quality and data trust — and those two properties are maximised when the member is in control, not when the brand is. The Fundle AI Platform's privacy architecture is the operational expression of that vision: a consent-based loyalty data management system that makes compliance the path of least resistance for every brand operator, and makes data dignity the default experience for every Indian consumer.
Frequently asked
What does the DPDP Act 2023 mean specifically for retail loyalty programmes in India?+
The DPDP Act requires loyalty programme operators (classified as Data Fiduciaries) to collect explicit, purpose-specific, and revocable consent for each category of data processing. Legacy practices like bundled consent checkboxes, default opt-in to partner data sharing, and indefinite data retention are all non-compliant. Brands must also provide members with a self-service dashboard to view, correct, restrict, and erase their data within defined SLA windows.
How does consent-based loyalty data management actually improve marketing performance?+
Consent-based data is higher intent and higher accuracy than passively collected data. Members who have actively chosen to share purchase preferences or location data produce 2.3–3.1x higher campaign response rates than members in the same programme whose data was collected by default. Consent-first design also reduces dirty data rates — the 20–35% inaccuracy problem common in Indian loyalty databases — which directly improves segmentation quality and reduces wasted campaign spend.
What is progressive consent and how should it be implemented in a loyalty app?+
Progressive consent defers data permission requests until the moment a specific benefit associated with that data type is being offered. At registration, collect only what is needed to activate the account. When introducing a birthday reward feature, request date of birth at that moment with the benefit made explicit. When launching location-based offers, request location permission at the point of first offer delivery. This approach reduces registration drop-off and produces higher-quality, higher-intent consent signals than front-loaded data collection.
How should a mall loyalty programme manage consent across multiple brand tenants?+
Mall loyalty programmes must model consent at the member-tenant level, not just the member-programme level. A member may consent to their fashion purchase data being shared with apparel brands but decline sharing with electronics or food and beverage tenants. The loyalty platform must enforce these granular permissions at the API layer in real time. Platforms like Fundle Mall Loyalty are architecturally designed for this multi-tenant consent enforcement challenge.
What KPIs should a CMO or CIO track to measure privacy programme health?+
Beyond standard loyalty metrics (active member rate, redemption rate, NPS), privacy-first programmes should track: consent completion rate at registration; consent completion rate at each progressive enrichment step; opt-out rate by channel and communication type; erasure request volume and SLA compliance rate; data accuracy rate (verified vs. total attributes); and data minimisation ratio (attributes actively used in decisions in the last 90 days vs. total attributes collected). These metrics should be reviewed monthly alongside commercial KPIs.
How does Fundle.ai handle data erasure requests under the DPDP Act?+
The Fundle AI Workflow engine automates the full erasure sequence when a member submits a deletion request through the Data Principal Dashboard. The Fundle Agentic AI identifies all systems holding that member's data — loyalty database, campaign history, analytics warehouse, and connected brand tenant APIs — and executes a time-stamped deletion workflow across all of them. Each step is logged in an immutable audit trail. The entire process is designed to complete within DPDP-mandated SLA windows without manual intervention from the brand's CRM or compliance team.
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 1.33Cr+ Indian retail members, 123+ malls and 270+ 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.