Fundle.ai: Building DPDP Compliant Loyalty Analytics That Actually Work

Key Features of DPDP Compliance for Loyalty Analytics

The DPDP Act introduces four structural obligations that directly collide with how most Indian loyalty programs are architected today. Understanding these obligations in operational terms — not legal abstractions — is the starting point for any CMO or loyalty manager trying to build a compliant analytics stack.

First, the notice-and-consent requirement mandates that data principals (your customers) receive a clear, plain-language notice before their personal data is collected, and that they provide free, specific, informed, and unambiguous consent. For a loyalty program, this means the POS associate's verbal nudge of 'give your number for points' is no longer sufficient. Consent must be captured digitally, timestamped, and linked to a specific processing purpose — whether that is points accrual, personalised offers, third-party partner sharing, or marketing communications. Brands like Reliance Trends and Pantaloons, which run high-volume, multi-city loyalty programs across POSist or Petpooja-integrated POS environments, need consent capture baked into the billing flow itself.

Second, the right to withdraw consent at any time, with withdrawal being as easy as giving consent, fundamentally challenges the 'enrol once, market forever' assumption that underlies most loyalty CRM stacks. When a Lenskart customer withdraws consent for personalised offers via WhatsApp, that signal must propagate in real time to the analytics warehouse, the campaign tool (whether MoEngage, WebEngage, or Xeno), and the AI segmentation engine. Broken propagation is not a technical inconvenience — it is a DPDP violation.

Third, purpose limitation means you cannot collect data for points accrual and then silently use it for mall-level footfall analytics or tenant revenue attribution without explicit consent for those secondary purposes. This is a critical issue for mall operators at properties like Phoenix Marketcity or Nexus Malls, where the same customer data is used both by the mall management entity and individual tenant brands. The data fiduciary hierarchy under DPDP needs to be contractually and technically established before analytics pipelines are built.

Fourth, the data retention and erasure obligations require that personal data is not held longer than necessary for the stated purpose, and that erasure requests are honoured within defined timelines. For loyalty analytics, this means anonymisation or deletion pipelines must be part of the data architecture from day one, not retrofitted after a customer complaint. AI models trained on loyalty data must be auditable to confirm they do not encode personal data of erased subjects in their weights — a technical requirement that most current vendor contracts do not address.

How ConsentFirst Enables Seamless Data Consent Management

The term 'consent management platform' has been diluted in the Indian market to mean little more than a cookie banner or a checkbox on a registration form. Fundle's ConsentFirst module is architecturally distinct from that minimal interpretation. It is a consent operating system embedded within the broader Fundle Loyalty platform, designed specifically for the multi-touchpoint, multi-brand complexity of Indian retail and mall environments.

At the point of enrolment — whether through a POS terminal running GoFrugal, Wondersoft, or POSist, a brand's mobile app, a WhatsApp onboarding flow, or a mall's self-service kiosk — ConsentFirst delivers a DPDP-compliant notice in the customer's preferred language. India's linguistic diversity is not an edge case; it is the default. ConsentFirst supports notice delivery in English, Hindi, Tamil, Telugu, Kannada, Marathi, Bengali, and Gujarati, ensuring that the 'informed' requirement of DPDP consent is genuinely met across Tier 1 and Tier 2 city deployments. Consent is captured with a digital signature event, timestamped at the server level, and stored in an immutable ledger that serves as the legal record for any Data Protection Board inquiry.

ConsentFirst operates at the level of individual processing purposes, not a single blanket opt-in. A customer enrolling in a Manyavar loyalty program, for instance, can consent to points accrual and transaction-based notifications while declining targeted marketing communications and third-party partner data sharing. The ConsentFirst schema stores each purpose-consent pair independently, with version numbers that update each time the customer modifies their preferences. This granularity is what transforms a legal compliance requirement into a commercial intelligence asset: you now know not just that a customer is in your database, but exactly what they want from you.

The withdrawal mechanism is built into every customer communication channel. A single opt-out signal from a WhatsApp message, an in-app preference centre, or a call to customer service triggers a ConsentFirst webhook that cascades the withdrawal to the Fundle AI Platform's analytics layer, the campaign execution engine, and any integrated third-party tools. The propagation latency is under 60 seconds in standard deployments, which is relevant because the DPDP Act does not specify a grace period for processing after withdrawal is received. ConsentFirst's real-time architecture is a risk mitigation measure as much as a technical feature. For mall operators running shared loyalty ecosystems across 40 to 80 tenant brands, the ability to manage consent at the ecosystem level — with tenant-specific overlays — is a capability that no point solution in the market currently matches.

Integrating ConsentFirst with AI Loyalty Analytics Workflows

The commercial fear that DPDP compliance will hollow out your loyalty analytics capability is understandable but misplaced. The transition from consent-blind analytics to consent-first analytics does reduce the raw volume of data available for processing — but it simultaneously improves the signal quality of that data in ways that produce better commercial outcomes. Customers who have actively consented to personalised offers are meaningfully more responsive than customers who have been silently opted into every communication bucket. The Fundle AI Platform is built on this premise.

Integrating ConsentFirst with the Fundle Agentic AI layer works through a consent-scope API that every analytics workflow must query before accessing personal data. When a loyalty manager at a Lifestyle or Pantaloons store cluster wants to build an RFM segment for a re-engagement campaign, the Fundle AI Workflow automatically cross-references the candidate customer list against the ConsentFirst ledger and removes any customers whose consent does not cover marketing communications. The resulting audience is smaller but legally clean and commercially warmer. This is not a manual compliance step imposed on top of the analytics process — it is a native architectural gate that runs automatically on every query.

For AI model training — whether for churn prediction, next-best-offer recommendation, or footfall attribution in a mall context — ConsentFirst feeds the model training pipeline with a consent-status flag at the record level. Records belonging to customers who have withdrawn consent or whose consent has expired are excluded from training datasets automatically. This ensures that the predictive models driving Fundle AI Agents' recommendations are not encoding data from individuals who have exercised their DPDP rights, a technical audit requirement that will become standard when the Data Protection Board begins enforcement reviews.

The integration layer also supports third-party tool connectivity. If a retail brand is running campaign execution through MoEngage or WebEngage alongside Fundle Loyalty analytics, the ConsentFirst webhook framework pushes consent-status updates to those platforms in real time. This eliminates the 'consent island' problem where a customer opts out in one channel but continues to receive communications from another because the systems are not synchronised. Brands like Cafe Coffee Day or Apollo Pharmacy, which operate across app, web, in-store, and partner channels simultaneously, face this fragmentation risk acutely. The Fundle AI Workflow's consent synchronisation capability closes that gap without requiring a full platform migration.

KPIs to Track DPDP Compliance and Commercial Performance Together

The strategic mistake most Indian retail operators make with DPDP compliance is treating it as a legal project with a binary pass/fail outcome. Compliance is not a state you arrive at — it is an operational condition you maintain. The KPIs that matter are therefore a blend of legal hygiene metrics and commercial performance indicators, because the two are not separable in a consent-first analytics architecture.

On the compliance side, track your Consent Coverage Rate: the percentage of active loyalty members with a DPDP-compliant consent record covering at least one processing purpose. At launch, expect this to be below 40% for most programs with legacy data. A 90-day remediation campaign should bring it to 65-75%. Sustainable ongoing operations should target 90%+. Track Withdrawal Propagation Latency as a technical SLA — any withdrawal that takes more than five minutes to cascade across all integrated systems is a compliance risk. Track your Records of Processing Activities completeness score monthly.

On the commercial side, track Consent-Segmented Campaign ROI: compare campaign conversion rates and revenue per communication for fully-consented audiences versus partially-consented or legacy audiences. Fundle Loyalty benchmarks consistently show a 1.8x to 2.3x improvement in campaign ROI for explicit-consent audiences. Track Re-Consent Campaign Conversion Rate as an indicator of loyalty program health — members who actively re-consent are your most engaged cohort and deserve priority treatment in your tier architecture.

For mall operators using Fundle Mall Loyalty, track Tenant Consent Attribution Clarity: what percentage of shared loyalty data used for tenant analytics has explicit cross-brand consent attached. This metric directly determines what analytics you can legally show to tenant brands in your monthly performance reporting. Malls that score above 80% on this metric are able to offer richer, more granular tenant analytics as a commercial service — turning a compliance investment into a revenue line from data services.

Finally, track your Data Protection Board Readiness Score on a quarterly basis — a structured internal audit against the DPDP Act's requirements across notice, consent, withdrawal, retention, erasure, and grievance redressal. This score should be owned by the CMO's office in partnership with legal, not delegated entirely to IT.

How Fundle solves this

Vineet Narang founded Fundle with a specific conviction: that Indian retail's data advantage would only compound if operators could collect and use data with the active trust of their customers, not despite their ignorance of how it was being used. The Fundle AI Platform is built end-to-end around this premise, and the ConsentFirst module is its most direct expression.

Fundle Loyalty — covering both Fundle Mall Loyalty for shopping centre operators and Fundle Brand Loyalty for individual retail chains — integrates ConsentFirst as a native architectural layer, not a third-party bolt-on. This means consent status is a first-class attribute in every customer record, every analytics query, every AI model training run, and every campaign audience build. There is no separate consent database that needs to be reconciled with the loyalty CRM — consent and loyalty data exist in a unified schema that the Fundle AI Workflow processes as a single coherent system.

The Fundle AI Agents layer — which powers next-best-offer recommendations, churn risk scoring, footfall prediction for mall operators, and RFM-based tier management — is consent-aware by design. Every inference the Fundle Agentic AI makes is scoped to the data the individual customer has consented to share for that specific purpose. This means a customer who has consented to transaction-based personalisation but not to third-party partner offers will receive precisely that distinction in their experience — and the AI model driving their recommendations will be trained only on data from customers whose consent covers the relevant use case.

For the competitive set — Capillary, EasyRewardz, Antavo, Customer Capital, Almonds.ai — DPDP compliance is increasingly a feature they are adding to existing architectures. For Fundle, it is the foundation the architecture was designed around. The difference shows in deployment timelines: a Fundle ConsentFirst implementation at a new mall or retail chain goes live in four to six weeks, because consent management is not a customisation project — it is a configuration exercise on a pre-built, pre-audited framework. For operators already running on integrated POS stacks like GoFrugal, Wondersoft, or POSist, the ConsentFirst connectors are pre-certified, reducing integration risk to near zero. The result is a DPDP compliant loyalty analytics capability that is commercially productive from week one, not a compliance project that costs money for two years before delivering any commercial value.