Fundle.ai: How DPDP Shapes Consent Based Loyalty Data Management

Consent Requirements Under DPDP for Loyalty Programmes

The DPDP Act establishes a clear, non-negotiable framework for consent. Section 6 of the Act requires that consent must be free, specific, informed, unconditional, and unambiguous — expressed through a clear affirmative action. For a loyalty programme, this means a pre-ticked checkbox saying 'I agree to receive personalised offers' is not valid consent. Neither is burying data usage terms in a 4,000-word terms-and-conditions document that members click through during a two-minute store enrolment on a Saturday afternoon.

The 'specific' requirement is particularly disruptive for loyalty operators. It means consent must be sought separately for each distinct purpose: earning and redeeming points is one purpose; sharing data with mall tenants for targeted campaigns is a second purpose; using purchase history to train AI recommendation models is a third. A single omnibus consent tick cannot cover all three. This has immediate implications for how brands like Manyavar, FabIndia, or Apollo Pharmacy structure their enrolment flows. Each of these brands collects data for multiple downstream purposes — their consent architecture must reflect that granularity.

The 'informed' requirement mandates a consent notice that is clear, plain-language, and available in all 22 scheduled languages on request. For a brand like Tanishq operating across Tier 1 and Tier 2 India, this is a non-trivial localisation challenge. The notice must identify the Data Fiduciary (the brand), the categories of personal data being collected, the specific purposes for processing, and the member's rights including the right to withdraw consent at any time. Loyalty platforms that currently store consent as a binary flag in a database field are architecturally unfit for this standard.

Perhaps the most operationally demanding DPDP requirement is the consent renewal obligation. If a loyalty programme changes its data usage purpose — say, it integrates a new AI-driven personalisation engine, or it begins sharing anonymised cohort data with a third-party analytics provider — it must obtain fresh, specific consent from existing members before processing their data for the new purpose. For a programme with 3 million members across 200+ stores, this is a consent campaign at scale. Without automated consent lifecycle tooling, this is practically impossible to execute correctly.

Best Practices in Consent Management for Loyalty

The gap between minimum legal compliance and genuinely privacy-first loyalty design is where commercial advantage is won or lost. Brands that treat DPDP as a box-ticking exercise will implement the minimum — a consent checkbox at enrolment and a buried 'unsubscribe' link in emails. Brands that treat it as a trust-building opportunity will implement a consent architecture that actively improves member engagement metrics.

The first best practice is consent granularity by channel and purpose. Rather than a single 'I accept' moment, leading programmes are moving to a tiered enrolment flow: a fast track where the member consents only to core loyalty mechanics (earn/redeem), and an enrichment track where additional consents unlock richer personalisation and exclusive benefits. Lenskart's loyalty enrolment, for instance, can productively separate consent for 'eye health reminders' from consent for 'personalised frame recommendations' from consent for 'sharing your purchase history with our partner eyewear brands.' Each tier has a clear value exchange that makes consent feel like a choice, not a formality.

The second best practice is a persistent, accessible preference centre. DPDP requires that withdrawal of consent be as easy as giving it. In practice, this means your loyalty app or member portal must have a clearly labelled 'My Data & Privacy' section where any individual consent can be toggled off in under three taps, and where the downstream effect (e.g., 'switching this off means you will no longer receive personalised birthday offers') is clearly explained. Platforms like MoEngage and WebEngage have preference centre modules, but they are typically channel-preference tools (email, SMS, push), not purpose-consent tools. The distinction matters enormously under DPDP.

Third, consent versioning and audit trails are non-negotiable. When the Data Protection Board of India or a court asks you to prove that member ID 9,847,221 gave valid consent on 14 March 2024 for purpose category 'AI-driven cross-sell recommendations,' you need an immutable, timestamped record that includes the exact text of the consent notice presented, the channel, the member's affirmative action, and any subsequent modifications. This is a data engineering problem as much as a legal one. Most mall loyalty programmes running on older stacks — whether built in-house or on legacy platforms — store consent as a single boolean column in a member master table. That is not an audit trail. That is a liability.

Fourth, purpose-change re-consent automation is a competitive differentiator. When you add a new AI personalisation vendor, integrate a new data clean room partner, or start using behavioural signals from your mall's Wi-Fi analytics provider, DPDP requires fresh consent from existing members for those new purposes. Brands that have built this into their consent workflow as an automated campaign — triggered by a configuration change in the platform — will execute this in hours. Brands that rely on manual processes will face weeks of legal review, IT tickets, and campaign coordination before they can go live.

Technological Tools to Support DPDP Compliance in Loyalty

The Indian market has several categories of technology that touch consent management for loyalty programmes, and understanding which layer does what is essential before any CIO begins a compliance architecture review. The categories are: Customer Data Platforms (CDPs), Loyalty Management Platforms, Consent Management Platforms (CMPs), and CRM and Marketing Automation tools. Each plays a role; none individually solves the full DPDP consent lifecycle for loyalty without significant integration work.

CDPs like Segment or Adobe Real-Time CDP can unify member profiles and tag consent attributes to individual records, but they are not natively designed for Indian regulatory requirements or for the specific consent semantics of DPDP — they do not understand 'purpose limitation' in the DPDP sense, and they do not have pre-built re-consent workflow engines. Loyalty platforms like Capillary or EasyRewardz handle points mechanics and campaign management well, but their consent frameworks were designed for GDPR at best, and several Indian deployments of these platforms have consent stored as campaign subscription flags rather than DPDP-grade purpose consents. Antavo, a global loyalty platform, has strong programme logic but no India-specific DPDP tooling whatsoever.

Standalone CMPs like OneTrust or Cookiebot handle web cookie consent effectively but were not designed for loyalty programme enrolment flows, in-store kiosk consent, or the post-enrolment consent lifecycle that DPDP mandates. They also do not integrate natively with the POS systems used across Indian retail — Petpooja, POSist, GoFrugal, Wondersoft — where the majority of loyalty enrolments actually happen in India's store-first retail environment.

Marketing automation tools like Xeno, WebEngage, MoEngage, or Customer Capital are excellent at campaign execution and customer journey orchestration, but they sit downstream of the consent layer. They consume consent signals; they do not manage the consent lifecycle. A brand using Xeno for WhatsApp loyalty campaigns still needs a separate, upstream consent management system to determine whether any given member has consented to WhatsApp marketing for purpose X versus purpose Y.

The CIO's practical conclusion: a DPDP-compliant loyalty data platform for India requires either assembling a four-layer tech stack and integrating it carefully, or adopting a purpose-built platform that natively handles consent lifecycle within the loyalty context from enrolment to erasure. This is the gap that Fundle AI Platform was architected to fill — an integrated loyalty and consent management stack where DPDP compliance is not a plugin but a foundational design principle.

Consumer Rights and Revocation Procedures Under DPDP

DPDP grants Indian data principals — your loyalty members — a set of enforceable rights that are materially stronger than what existed under IT Act rules. For loyalty operators, four rights have the highest operational impact: the right to access, the right to correction, the right to erasure, and the right to grievance redressal. Understanding the operational implications of each is essential before a CMO or CIO signs off on their compliance posture.

The right to access means any loyalty member can request a complete, machine-readable copy of all personal data you hold about them, the purposes for which it is being processed, and the entities with whom it has been shared. For a mall loyalty programme like the one operating at Select CITYWALK, this includes transaction history, dwell-time data from Wi-Fi analytics, AI-inferred persona labels, campaign interaction history, and any data shared with anchor tenants. Fulfilling this request manually, within the timeframe the rules will specify, is operationally impossible at scale without a data subject access request (DSAR) automation layer built into the loyalty platform.

The right to erasure — or the right to be forgotten in common parlance — is the most commercially disruptive. When a member withdraws consent and requests erasure, DPDP requires deletion of their personal data from all processing systems, not just the marketing database. This means the deletion must cascade to your CDP, your data warehouse, your AI training datasets, your BI dashboards, and any third-party data processors you have shared the data with — including analytics vendors, clean room partners, and mall Wi-Fi providers. Brands that have shared member data with external processors without adequate data processing agreements will find erasure requests extremely difficult and potentially legally exposing to fulfil.

The right to correction sounds straightforward but creates operational complexity when member data exists in multiple systems. A member who updates their mobile number or date of birth in the loyalty app must see that correction propagate consistently across every system that holds their data. In most retail tech stacks, this requires either a golden record architecture in a CDP or a manual reconciliation process. DPDP effectively mandates the former.

Grievance redressal is an often-overlooked obligation. DPDP requires every Data Fiduciary to designate a contact point for privacy complaints and to resolve them within a specified period. For loyalty programmes, this means member-facing communication must include a clear privacy contact — not a generic customer care email — and there must be an internal workflow for logging, escalating, and resolving data-related complaints within the regulatory window. Brands like Apollo Pharmacy or Reliance Trends, which run large loyalty programmes with millions of enrolled members, need ticketing and workflow systems purpose-built for DPDP grievance management, not generic customer service platforms.

KPIs to Track for DPDP-Compliant Loyalty Data Management

Compliance is not a binary state — it is a continuous operational posture that requires active measurement. For Indian retail CMOs and CIOs, the key performance indicators for consent based loyalty data management fall into three clusters: consent health metrics, rights fulfilment metrics, and commercial impact metrics.

Consent health metrics tell you whether your consent architecture is functioning correctly. Track consent capture rate at enrolment (what percentage of new members complete granular consent, not just a blanket checkbox), consent completeness score (what percentage of active members have valid, purpose-specific consent records for every active processing purpose), and consent decay rate (what percentage of consents are being withdrawn per month, and for which purposes — this is a leading indicator of trust erosion). A healthy loyalty programme should have a consent completeness score above 95% for core loyalty purposes and should be monitoring withdrawal rates by purpose category to identify pain points before they become regulatory issues.

Rights fulfilment metrics track your operational performance against DPDP obligations. Measure average DSAR response time (target: well within the regulatory window, likely 30-72 hours for digital-first programmes), erasure cascade completion rate (what percentage of erasure requests result in confirmed deletion across all connected systems within the required timeframe), and grievance resolution time. For large programmes at brands like Lifestyle or Pantaloons, these metrics need to be reviewed weekly, not quarterly.

Commercial impact metrics close the loop between compliance investment and business outcome. The hypothesis — supported by PwC India CX data — is that transparent, member-controlled consent architecture improves trust, and improved trust improves engagement and lifetime value. Track consent opt-in rates for enrichment purposes (personalisation, AI recommendations, partner offers) as a proxy for trust levels. Track campaign engagement rates segmented by consent tier — members who have given broad consent should show meaningfully higher engagement than minimum-consent members. Track churn rates among members who have withdrawn specific consents to understand whether the programme is offering sufficient value exchange to retain privacy-conscious members.

Finally, track programme-level compliance posture: number of open DPDP grievances, number of regulatory inquiries received, and completion status of annual consent architecture reviews. These are board-level risk metrics for any large retail operator and should be reported alongside financial loyalty programme KPIs in CMO and CIO dashboards.

How Fundle solves this

Fundle was designed from the ground up as a privacy-first loyalty platform for the Indian market — not retrofitted for DPDP after the fact, but architected with consent lifecycle management as a core product primitive. The Fundle AI Platform integrates loyalty programme mechanics, first-party data management, and DPDP-grade consent infrastructure into a single operational layer, eliminating the need for Indian retail operators to assemble and integrate four separate technology categories to achieve compliance.

At the consent capture layer, Fundle Loyalty delivers granular, purpose-specific consent flows that can be deployed across in-store POS integrations (including Petpooja, POSist, GoFrugal, and Wondersoft), the Fundle-powered loyalty app, and web enrolment. Every consent event is written to an immutable audit log with full metadata — member ID, consent text version, channel, timestamp, and affirmative action — that is accessible for regulatory inspection. The Fundle Mall Loyalty product extends this to multi-brand mall environments, managing consent across anchor tenants and specialty retailers within a single programme structure, with purpose-level consent tracked per brand and per data use case.

Fundle Brand Loyalty handles post-enrolment consent lifecycle for standalone retail brands: automated re-consent campaigns triggered by purpose changes, consent renewal workflows for programmes with time-bound consent architecture, and a member-facing preference centre where any consent granule can be viewed or withdrawn in real time. The preference centre is natively integrated into the loyalty member portal and app — it is not a separate CMP bolted on top, but a first-class feature of the member experience.

Fundle AI Agents and Fundle Agentic AI power the operational automation layer. When a new data processing purpose is added to a brand's programme configuration, Fundle Agentic AI automatically generates a re-consent campaign brief, routes it through the brand's preferred approval workflow, and schedules deployment across opted-in channels (WhatsApp, app push, SMS, email) — all without manual intervention from the compliance or CRM team. Fundle AI Workflow manages DSAR fulfilment: receiving a member's erasure or access request, generating the complete data export or executing the deletion cascade, and logging the fulfilment event for audit purposes.

Fundle manages consent lifecycle for 270+ brands ensuring DPDP alignment — a scale that has given the platform battle-tested architecture across the full range of Indian retail contexts, from single-brand D2C programmes to complex multi-tenant mall loyalty deployments. Vineet Narang's founding vision for Fundle was explicit: that the right to data privacy and the commercial value of personalised loyalty are not in tension — they are mutually reinforcing when consent is treated as a product feature rather than a compliance obligation. Every feature in the Fundle AI Platform reflects that conviction.