Fundle.ai: DPDP Compliant Loyalty Analytics in India: Technology and Best Practices

Technical Requirements for DPDP Compliant Analytics Platforms

A loyalty analytics platform that claims DPDP compliance cannot bolt it on as a feature. Compliance must be structural — baked into the data model, the processing pipeline, and the API layer from the ground up. Here is what retail technology buyers need to audit before signing any loyalty platform contract.

First, consent state must be a first-class data entity. Every customer record must carry a consent object — not a boolean flag buried in a profile table, but a structured record that captures: the specific purpose for which consent was granted (e.g., 'marketing communications', 'personalised offers', 'third-party brand partners'), the timestamp and channel of consent capture, the version of the consent notice shown, and the current revocation status. When a Manyavar customer walks into a Select CITYWALK store and joins the loyalty program on a kiosk, the platform must record all of that in real time and propagate it to every downstream system — the CDP, the campaign engine, the analytics warehouse — before any processing begins.

Second, data minimisation and purpose limitation must be enforced at the pipeline level. The DPDP Act is explicit: you may only process personal data for the purpose for which consent was given. If a customer at a Cafe Coffee Day outlet consents to 'loyalty points tracking' but not 'personalised marketing', the analytics platform must ensure that customer's purchase data feeds the points ledger and nothing else. This requires attribute-level consent tagging — a capability that most legacy CRM platforms, including point solutions used widely in Indian retail, simply do not have. Vendors like Capillary Technologies and EasyRewardz have begun adding consent fields, but their data models were not designed for attribute-level purpose enforcement.

Third, the platform must support the Data Principal's rights under DPDP: the right to access their data, the right to correction, the right to erasure, and the right to grievance redressal — all within defined timescales. For a retail chain with 5 million loyalty members, managing those requests manually is impossible. The platform must expose self-service portals and automated fulfilment workflows. Finally, data residency matters: DPDP requires that certain categories of sensitive data be stored within India's borders. Any SaaS platform with cloud infrastructure hosted exclusively outside India is immediately non-compliant for sensitive personal data categories.

Best Practices in Consent Gathering and Data Usage

Consent collection in Indian retail is almost universally broken. The standard playbook — 'give us your mobile number to earn points, and by doing so you agree to our privacy policy' — violates the DPDP Act's requirement for freely given, specific, informed, and unambiguous consent on at least three of those four dimensions simultaneously. Here is what good looks like.

Purpose granularity is non-negotiable. Instead of one blanket consent, present members with distinct, plain-language purposes: 'We will use your purchase history to calculate and credit loyalty points'; 'We would like to send you personalised offers via WhatsApp'; 'We will share your anonymised shopping behaviour with our brand partners to improve recommendations'. Each purpose should carry a separate toggle, and the member must be able to opt into some and not others without losing core loyalty program benefits. Apollo Pharmacy already applies a version of this for their health data processing — the model is proven and commercially viable.

Consent must be layered and contextual. At POS enrollment, capture minimal consent — mobile number for points, basic marketing opt-in — and defer enrichment to a second interaction. When the customer is browsing the app, prompt them to complete their profile with declared preferences (cuisine, fashion category, occasion type) and explain exactly what personalisation they will receive in return. Reliance Trends' app does a reasonable job of this progressive profiling; DPDP now makes it mandatory rather than optional.

Refusal must carry no penalty. Under DPDP, a customer who refuses to consent to marketing communications cannot be denied the core benefit of the loyalty program — points earning and redemption. Platforms that gate points issuance behind marketing opt-in are already non-compliant. Redesign your enrollment flow so that the minimum viable consent bundle covers only what is strictly necessary for program operation.

For data usage, implement purpose-bound data segmentation. A customer who consented to 'personalised offers' can receive AI-generated product recommendations. A customer who consented to 'loyalty tracking only' should be served only transactional communications — points balance updates, expiry reminders. Your campaign engine must be able to filter audiences by consent purpose at query time, not as a post-processing exclusion list. The difference is architectural: exclusion lists lag; consent-filtered queries are real-time and audit-safe.

Role of Modern Consent Management Platforms Like ConsentFirst

A Consent Management Platform (CMP) is the operational layer that sits between your customer touchpoints — app, web, kiosk, store associate tablet, WhatsApp bot — and your loyalty analytics infrastructure. Its job is to serve the correct consent notice for each context, capture the member's choice in a legally admissible format, store it in a tamper-proof ledger, and expose APIs that allow every downstream system to query consent state before processing any data. Without a CMP, DPDP compliance is a documentation exercise rather than a technical reality.

In the Indian market, the CMP landscape is nascent. Global players like OneTrust and Cookiebot were built for web cookie consent under GDPR and are poorly suited to the offline-first, multi-channel reality of Indian retail loyalty — where a member might enroll on a store kiosk, update preferences on a mall app, and interact via a WhatsApp chatbot in the same week. Indian-market CMPs need to handle SMS and WhatsApp consent flows, integrate with POS middleware from vendors like GoFrugal and POSist, and support regional language consent notices for members who do not read English — a non-trivial engineering challenge.

Fundle's ConsentFirst module was designed specifically for this environment. It operates as a consent orchestration layer within the Fundle Loyalty Platform, serving consent notices in 11 Indian languages, capturing explicit purpose-specific consent at every touchpoint, and writing every consent event to an immutable ledger that is queryable by the campaign engine, the analytics platform, and any Data Protection Board audit process. Fundle's ConsentFirst and AI analytics platform deliver DPDP compliance across 123+ malls in India — a deployment footprint that has surfaced every edge case the Indian retail environment can produce, from rural kiosk enrollments with feature phones to luxury mall members with complex cross-brand data sharing preferences.

The commercial case for a dedicated CMP is straightforward. Brands that use ConsentFirst-style purpose-specific consent collection report opt-in rates that are 3.2× higher than brands using generic T&C acceptance — because members who understand what they are consenting to are significantly more willing to share. Higher opt-in rates mean larger addressable audiences for AI-driven campaigns, which means better ROAS on loyalty spend. Compliance and commercial performance are not in tension; they are aligned when the consent architecture is right.

Security and Data Governance Frameworks for Loyalty Analytics

DPDP compliance does not end at consent collection. The Act places significant obligations on how personal data is stored, transmitted, and protected once it is inside your analytics infrastructure. For retail loyalty platforms handling tens of millions of member records, the security and governance requirements are substantial.

Data encryption must be end-to-end. Member personal data — mobile numbers, purchase histories, location signals — must be encrypted at rest and in transit using current standards (AES-256 at rest, TLS 1.3 in transit). Encryption keys must be managed within India using a key management service that does not give foreign cloud providers access to unencrypted data. Pseudonymisation — replacing direct identifiers with tokens for analytics processing — should be applied wherever the analytics use case does not require direct identification, which is the vast majority of segmentation and propensity modelling work.

Role-based access control must be strict and audited. A Pantaloons store manager should have read access to their store's transaction aggregates, not to individual member mobile numbers. A campaign analyst at Lifestyle's head office should be able to build audience segments but not export raw PII to spreadsheets. Every access event must be logged, and logs must be reviewed regularly. Most Indian retail IT teams currently have no formal access review cadence for their loyalty platforms — DPDP makes this a compliance gap rather than just a best practice.

Data retention policies must be defined and enforced programmatically. DPDP requires that personal data not be retained beyond the period necessary for the stated purpose. For loyalty analytics, this means defining retention windows by data category — transaction records (typically 3 years for accounting purposes), behavioural event logs (12 months for personalisation models), and identity data (duration of active membership plus a defined post-exit window). These retention rules must be enforced by automated deletion jobs, not by manual processes that get deferred indefinitely.

Vendor risk management is a new compliance dimension that most Indian retail CMOs have not engaged with seriously. Under DPDP, you are responsible for how your data processors — your analytics vendor, your campaign platform, your cloud provider — handle your members' data. Contracts must include specific data processing agreements, audit rights, and breach notification timescales. If your current loyalty platform vendor cannot produce a signed Data Processing Agreement within 30 days of request, that is a significant compliance risk signal.

How Fundle solves this

Vineet Narang's founding thesis for Fundle was simple but radical for Indian retail: that loyalty should be built on earned trust, not accumulated data exhaust. That philosophy is now encoded into every layer of the Fundle AI Platform — from the ConsentFirst CMP module to the AI analytics engine that powers personalised offers across malls, brands, and channels.

Fundle Loyalty Platform is architected as a consent-first system from the database schema upward. Every member record in Fundle carries a structured consent object — purpose-tagged, timestamped, versioned, and propagated in real time to every downstream service via an event-driven consent bus. When a member at a Phoenix Marketcity outlet updates their WhatsApp consent preference at a kiosk, that change is reflected in the campaign engine, the AI segmentation layer, and the analytics warehouse within seconds — not in the next nightly batch. This is not a feature; it is a foundational architectural commitment.

Fundle Mall Loyalty and Fundle Brand Loyalty both inherit this consent infrastructure, which means a single deployment can handle the complex multi-tenancy of a mall environment — where Tanishq, Lenskart, and Cafe Coffee Day might each have their own brand-level consent preferences alongside the mall's umbrella program consent — without creating consent conflicts or data leakage between tenants. Fundle AI Agents handle member-facing interactions — WhatsApp flows, app nudges, kiosk dialogs — and are programmed to check consent state before executing any personalised communication, making DPDP compliance an autonomous, always-on operational capability rather than a periodic compliance review.

Fundle Agentic AI and Fundle AI Workflow take this further into the analytics layer. Propensity models, RFM segmentation, churn prediction, and next-best-offer engines all run inside a consent-filtered data environment. A member who has opted into 'personalised recommendations' but not 'third-party brand sharing' is automatically included in first-party AI models and excluded from co-marketing activations — without any manual intervention by the analytics team. For retail CMOs managing campaigns across 50+ stores and millions of members, this automation is the difference between DPDP compliance being theoretically possible and being operationally real. Fundle's ConsentFirst and AI analytics platform deliver DPDP compliance across 123+ malls in India, giving Indian retail operators the most battle-tested DPDP-native loyalty infrastructure available in the market today.