“We don't sell AI Agents. We sell business outcomes — increase repeat rate, reduce churn, raise basket size. The AI Agents are how Fundle gets there.”
- •Understand what India's DPDP Act 2023 actually demands from your POS-to-loyalty data pipeline
- •Distinguish between genuine consent-led data collection and dark patterns that will attract DPDP penalties
- •Audit your current POS integration for data minimisation, purpose limitation and storage controls
- •Implement a Consent Management Platform (CMP) at the point of enrolment — not as an afterthought
- •Track five measurable KPIs that prove your loyalty programme is DPDP-ready to your board and auditors
Every mall CMO in India has a version of the same story. A major fashion anchor — say a Lifestyle or Pantaloons — rolls out a new loyalty programme. Footfall data, transaction records, mobile numbers, and purchase categories start flowing from eight POS terminals per floor into a central CRM. Twelve months later, the loyalty database has 4 lakh members, the campaign open rates look good, and the IT head is sleeping well. Then August 2023 happens. The Digital Personal Data Protection Act is notified, and suddenly that same database is a liability as much as it is an asset.
The DPDP Act 2023 is not a distant compliance checkbox. The rules on consent, purpose limitation, data localisation, and grievance redressal are moving from gazette to enforcement at a pace that has caught many retail operators off-guard. For a mall operator running 200+ brand partners across three properties, or a retail chain operating 500 POS nodes on GoFrugal or POSist or Wondersoft, the compliance surface area is enormous. Every swipe, every loyalty enrolment, every cross-brand data share is a potential point of non-compliance.
The challenge is structural. POS integration for loyalty platform India setups were designed for speed, not for privacy. Most integrations pipe raw transaction data — item-level SKU, price, time, location, member ID — directly into a loyalty engine via API or flat-file batch. Consent was an afterthought: a checkbox on a paper form at the customer service desk, or a pre-ticked field in the app. Under DPDP, that model is broken. Consent must be free, specific, informed, and unambiguous. It must be as easy to withdraw as to give. And the data fiduciary — the mall or the brand — must be able to prove all of this on demand.
This is precisely the gap that Fundle was built to close. The Fundle AI Platform sits at the intersection of loyalty intelligence and privacy engineering, giving mall operators and retail brands a single system of record for both customer engagement and consent governance. This article walks CMOs and IT heads through what DPDP actually requires of your POS-loyalty stack, what good looks like, and how to build a compliant, commercially effective programme that does not treat privacy and personalisation as opposites.
The DPDP Compliance Gap in Indian Retail Loyalty — By the Numbers
Understanding DPDP Requirements for Retail Data
The Digital Personal Data Protection Act 2023 introduces a consent-first, purpose-bound framework for all personal data processing in India. For retail operators, three provisions matter most: Section 6 (valid consent), Section 8 (obligations of data fiduciaries), and Section 9 (children's data). Each of these directly intersects with how POS integration loyalty platform India setups collect, store, and use customer data.
Section 6 defines valid consent as a specific, informed, unconditional, and unambiguous indication of a data principal's wishes — communicated through a clear affirmative action. This immediately invalidates the most common loyalty enrolment pattern in Indian malls: the SMS OTP flow where a member is enrolled into a programme and simultaneously opted into marketing communications without a separate, explicit consent step. Enrolling a customer in a loyalty programme is a distinct processing purpose from sending them promotional WhatsApp messages about Tanishq's Akshaya Tritiya sale or Manyavar's Navratri collection. These require separate consent notices.
Section 8 places the burden of proof on the data fiduciary — the mall or the brand, not the technology vendor. This means your IT head cannot simply point to a clause in the Capillary or EasyRewardz contract and call it done. The operator must maintain a consent artefact: a timestamped, versioned, member-linked record of what was consented to, when, via which channel, and what the processing purposes were at that time. If a member enrolled in 2022 on a paper form and you have now migrated to a digital programme, you need re-consent before processing their data under the new regime.
Section 9 is particularly relevant for mall-based programmes that operate entertainment zones, gaming arcades, or youth-oriented brand activations. Any data principal under 18 requires verifiable parental consent before their data can be processed. This is not a theoretical risk: a significant share of loyalty enrolments at food courts and entertainment floors in malls like Phoenix Marketcity or Select CITYWALK involve teenagers transacting on family accounts or their own devices. The technical controls to flag and gate these enrolments must live in your POS integration layer, not just in a policy document.
The DPDP Consent Funnel: From POS Swipe to Compliant Loyalty Member
How POS and Loyalty Platforms Handle Consent and Data Privacy
Most Indian retail POS software — whether it is GoFrugal, POSist, Petpooja, or Wondersoft — was built to solve a billing and inventory problem, not a privacy problem. The loyalty integration is typically a bolt-on: a middleware API that ships transaction data to a loyalty engine like Capillary, EasyRewardz, or Xeno in near-real-time. The consent layer, if it exists at all, sits in the loyalty engine's CRM as a boolean flag. That architecture is no longer adequate.
Under DPDP, the consent artefact must be granular by purpose. A customer may consent to earning and redeeming points (core loyalty transaction processing) without consenting to behavioural profiling for personalised offers, or to their data being shared with co-located brands in the mall ecosystem. These are distinct processing purposes, and each requires its own consent record. A flat boolean field in a CRM does not capture this granularity. You need a Consent Management Platform (CMP) that sits as a discrete layer between the POS event and the loyalty engine, intercepting the data flow, checking consent status by purpose, and either passing or blocking the data accordingly.
The Indian retail competitive set has been slow to build this. MoEngage and WebEngage are strong on marketing automation but their consent management is oriented toward cookie consent for web — not transactional consent for offline POS-triggered loyalty events. Almonds.ai focuses on hyperlocal retail activation but does not operate a purpose-built DPDP CMP. Customer Capital has strong RFM analytics but consent governance is not a native capability. This leaves a significant gap in the market for operators who need a single platform that handles both the loyalty intelligence and the consent infrastructure.
The data minimisation principle is also frequently violated in standard POS-loyalty integrations. A typical integration sends the full transaction record — including item-level SKU data, discount applied, cashier ID, terminal ID, and exact timestamp — to the loyalty engine. For the purpose of calculating and awarding points, you need: member ID, transaction value, store ID, and date. Item-level data is only required if you are running category-specific earn rules or personalised offers — and that requires a separate, explicit consent for behavioural processing. Most operators are over-collecting by default, which is a DPDP violation before a single marketing message is sent.
DPDP-Compliant vs. Legacy POS-Loyalty Integration Architecture
Fundle's ConsentFirst: India's DPDP-Compliant CMP Solution for POS Integration Loyalty Platform India
Fundle's ConsentFirst CMP was built from the ground up for the Indian retail consent problem — offline-first, POS-native, and purpose-granular. It is not a web cookie banner retrofitted for retail. It operates as a middleware consent authority between your POS terminals and the Fundle Loyalty engine, and it is the infrastructure behind the fact that Fundle's ConsentFirst CMP ensures DPDP compliance for 1.33Cr+ loyalty members across mall and brand loyalty programmes in India today.
Here is how ConsentFirst works in practice. When a customer is invited to enrol at a POS terminal — whether on a cashier-facing screen, a customer-facing display, or an SMS/WhatsApp onboarding flow — ConsentFirst presents a structured notice that separates four processing purposes: core loyalty (earn/redeem), personalised marketing communications, behavioural analytics and profiling, and cross-brand data sharing within the mall ecosystem. The customer makes an affirmative selection for each. This is not a default opt-in. Each purpose requires a deliberate tap or confirmation. The consent record — including member ID, timestamp, channel, IP or device fingerprint, and the exact version of the consent notice displayed — is written to an immutable consent ledger within the Fundle AI Platform.
At the data pipeline level, Fundle AI Workflow intercepts every POS transaction event before it reaches the loyalty engine. The workflow checks the member's consent record in real time: if behavioural profiling consent has not been given, item-level SKU data is stripped from the event payload before it enters the Fundle Loyalty data store. If cross-brand sharing consent has not been given, that member's profile is excluded from any audience segments shared with co-tenants. The enforcement is automated, not policy-dependent. You do not need your IT team to manually filter records every campaign cycle.
The withdrawal mechanism is equally important under DPDP. A member must be able to withdraw any specific consent as easily as they gave it — without it affecting their ability to participate in the core loyalty programme. Fundle Brand Loyalty's member portal and WhatsApp bot both surface a real-time consent dashboard where members can toggle individual purposes on or off. A withdrawal event triggers an immediate update to the consent ledger and a cascading data suppression across all active campaign audiences. This is what genuine DPDP compliance looks like operationally — not a notice buried in a terms page, but a live, auditable, member-controlled privacy interface.
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.
Best Practices for Secure POS-to-Loyalty Data Flows: A 5-Step Implementation Playbook
Map Your Data Flows Before You Touch Any Code
Document every POS terminal, middleware, API endpoint, and data store in your current loyalty stack. For each data element — name, mobile, email, transaction value, SKU, location — tag the processing purpose, the legal basis under DPDP, and the current retention period. Most mall operators doing this exercise for the first time discover 3-5 data flows they had forgotten about: a BI dashboard feed, a third-party analytics integration, or a legacy batch export to an email vendor. You cannot govern what you have not mapped.
Deploy a Purpose-Granular CMP at the Enrolment Layer
Implement a Consent Management Platform that presents separate, affirmative consent notices for each distinct processing purpose at the moment of loyalty enrolment — whether that enrolment happens at the POS counter, on a branded app, or via an SMS link. The CMP must write a timestamped, versioned consent artefact to an immutable log for every consent action, including withdrawals. Avoid pre-ticked boxes, bundled consents, or consent notices buried in terms and conditions. Under DPDP Section 6, these are dark patterns and will not constitute valid consent.
Enforce Data Minimisation at the API Gateway
Configure your POS-to-loyalty API integration to apply field-level filtering based on the member's active consent record before any data enters the loyalty engine. For members who have consented only to core loyalty processing, the payload should contain: member ID, store ID, transaction total, and date. Item-level SKU, exact timestamp, cashier ID, and discount details should only flow through for members who have explicitly consented to behavioural profiling. This is a technical control, not a policy — it must be enforced in code at the middleware layer.
Implement Section 9 Age Verification at POS Enrolment
Add an age verification step to your POS enrolment flow for all new loyalty members. For members who indicate or are identified as under 18, trigger a parental consent workflow before any data processing begins. This workflow should send a verifiable consent request to a parent or guardian's mobile number, collect an OTP-confirmed approval, and store the parental consent artefact alongside the minor's loyalty member record. Until parental consent is confirmed, the minor's account should be in a restricted state with no data processing beyond the consent collection itself.
Set Automated Retention Schedules and Deletion Workflows
Define a retention period for each data category in your loyalty programme — transaction records, behavioural profiles, communication logs, consent artefacts — based on the processing purpose and applicable statutory requirements. Build automated workflows that either anonymise or delete data when the retention period expires, or when a member withdraws consent or closes their account. Retention schedules must be disclosed in the consent notice at enrolment. Indefinite retention of loyalty member data is a DPDP violation regardless of consent status for the original collection.
Auditing and Maintaining Compliance in POS Integrations
DPDP compliance is not a one-time implementation project. It is an ongoing operational discipline, and the audit function is where most retail operators will fail. A consent notice that was DPDP-compliant in January 2024 may become non-compliant if you change your data processing practices — say, you add a new AI-powered personalisation engine, share data with a new analytics vendor, or integrate a new brand into your mall loyalty ecosystem. Every material change to your data processing must be reflected in an updated consent notice, and existing members must be re-consented for the new purposes before their data is used.
The audit trail for POS-loyalty integrations has three dimensions. First, consent audit: can you produce, for any given member at any point in time, an exact record of what consents they gave, when, and via which channel? Second, data flow audit: can you demonstrate that no data was processed for a purpose beyond what the member consented to — including in third-party integrations with vendors like MoEngage for push notifications or Xeno for SMS campaigns? Third, breach audit: do you have incident response procedures and notification timelines in place for a data breach event, as required under DPDP Section 8(6)?
For mall operators, the complexity multiplies because the data fiduciary relationship is layered. The mall is a data fiduciary for the mall loyalty programme. Each brand anchor is a separate data fiduciary for its own loyalty programme. When these programmes share data — when a Phoenix Marketcity loyalty member's transaction at an Apollo Pharmacy in the mall is used to personalise an offer from a co-tenant — you have a data sharing arrangement that requires explicit consent from the member and a Data Processing Agreement between the two data fiduciaries. These agreements need to be in place before the data sharing begins, not after.
The KPIs to track for ongoing compliance health in your POS-loyalty integration include: consent capture rate at enrolment (target above 85% to maintain a commercially useful database), consent withdrawal rate (a spike indicates a trust problem or a dark pattern complaint), data breach incident response time (DPDP requires notification to the Data Protection Board within a timeframe to be specified in rules), percentage of member records with expired retention that have been deleted or anonymised on schedule, and the time-to-update for consent notices following any material change in data processing practices.
- Data flow map completed: every POS terminal, API endpoint, middleware, and third-party vendor receiving loyalty member data is documented with processing purpose and legal basis
- Purpose-granular consent notices implemented at all enrolment touchpoints (POS counter, app, SMS/WhatsApp) — no bundled or pre-ticked consents
- Timestamped, versioned consent artefacts stored in an immutable log and linked to each loyalty member ID
- Field-level data minimisation enforced at the POS-to-loyalty API gateway — only consent-permitted data fields pass to the loyalty engine
- Section 9 age verification gate active at POS enrolment; parental consent workflow triggered and logged for all under-18 members
- Consent withdrawal mechanism available to members in real time via app, WhatsApp bot, or customer service — withdrawal triggers immediate data suppression across all active campaign audiences
- Automated retention schedules and deletion/anonymisation workflows configured for all data categories; retention periods disclosed in consent notices
“In Indian retail, the brands that will win the next decade are the ones that treat consent as a trust product — not a legal hurdle. First-party data built on genuine permission is worth ten times more than a database built on dark patterns.”
How Fundle solves this
The Fundle AI Platform is the only loyalty and customer engagement platform in India that was architected with DPDP compliance as a native capability, not a retrofit. Vineet Narang's founding thesis was that the Indian retail loyalty market needed a platform that could simultaneously drive commercial outcomes — higher repeat visit rates, larger basket sizes, lower churn — and operate as a genuine steward of customer data. Those two goals are not in tension; they reinforce each other. Members who trust a loyalty programme share more data, engage more deeply, and generate higher lifetime value.
Fundle Loyalty — available in both Fundle Mall Loyalty and Fundle Brand Loyalty configurations — ships with ConsentFirst CMP as a standard component, not a paid add-on. Every POS integration built on the Fundle AI Platform enforces purpose-granular consent at the API gateway layer, runs data minimisation checks on every transaction event, and maintains a real-time, member-linked consent ledger that is audit-ready for the Data Protection Board of India. Mall operators on the platform get a compliance dashboard that shows consent capture rates, withdrawal rates, retention schedule adherence, and data sharing audit logs across all brand partners in the ecosystem — in a single view.
Fundle AI Agents bring intelligent automation to the compliance workflow. When a member withdraws consent for behavioural profiling, an AI Agent automatically removes that member from all active personalisation workflows in Fundle AI Workflow, updates the audience segments in connected marketing tools, and generates a suppression confirmation artefact for the compliance log — without any manual intervention from the IT team. When a new brand is onboarded to a mall loyalty ecosystem, Fundle Agentic AI triggers a guided Data Processing Agreement workflow, checks that the new brand's consent notice is compatible with the mall's master consent framework, and flags any purpose mismatches before the data sharing integration goes live.
For retail IT heads evaluating Indian retail POS loyalty software options, the Fundle integration model supports GoFrugal, POSist, Petpooja, and Wondersoft out of the box, with a certified REST API connector and a Fundle-managed middleware layer that handles consent enforcement, data minimisation, and event routing without requiring modifications to the POS software itself. The implementation timeline for a standard mall property with 80-120 brand partners is 8-12 weeks from contract to go-live, including consent notice design, CMP configuration, and staff training at POS counters. DPDP compliance and loyalty performance are not a choice — with the Fundle AI Platform, you get both.
Frequently asked
What does DPDP compliance mean specifically for a POS integration loyalty platform India setup?+
Under India's DPDP Act 2023, any personal data collected at a POS terminal and processed by a loyalty platform must have a valid, purpose-specific consent from the customer. This means your POS-to-loyalty integration must: present a clear consent notice at enrolment, capture separate consents for distinct processing purposes (earning points vs. receiving marketing vs. behavioural profiling), store timestamped consent artefacts, and enforce data minimisation so only consent-permitted fields flow to the loyalty engine. The mall or brand operating the programme is the data fiduciary and bears full compliance responsibility.
Can I use my existing paper-based or checkbox loyalty enrolment forms after DPDP?+
No. Paper forms and pre-ticked digital checkboxes do not meet the DPDP standard for valid consent under Section 6, which requires a specific, informed, unconditional, and unambiguous affirmative action. If your current loyalty database was built on paper forms or bundled consents, you will need to run a re-consent campaign to bring existing members into compliance before processing their data under the new regime. Fundle's ConsentFirst CMP includes a re-consent workflow for exactly this scenario.
What is the penalty for non-compliance with DPDP in a retail loyalty context?+
The DPDP Act 2023 sets penalties of up to ₹250 crore per violation instance for data fiduciaries who fail to meet their obligations. For a mall operator or retail chain, a single breach event or a finding of systematic non-compliant consent collection could trigger penalties at this scale. Beyond the financial penalty, the reputational damage of a Data Protection Board enforcement action — which is likely to be public — is a significant commercial risk for any brand with a large loyalty member base.
How does Fundle's ConsentFirst CMP handle consent withdrawal in a POS loyalty context?+
Fundle's ConsentFirst CMP gives loyalty members a real-time consent dashboard accessible via the Fundle member app, WhatsApp bot, or customer service portal. When a member withdraws consent for a specific processing purpose — say, behavioural profiling — the withdrawal event is written to the consent ledger immediately. Fundle AI Agents then automatically suppress the member from all relevant data flows and campaign audiences within the Fundle AI Platform. The entire withdrawal-to-suppression cycle is logged and auditable. Withdrawal of marketing consent does not affect the member's core loyalty account or point balance.
How does DPDP Section 9 (children's data) affect mall loyalty programmes?+
DPDP Section 9 prohibits processing personal data of children (under 18) without verifiable parental consent. For mall loyalty programmes, this is operationally significant because a meaningful share of enrolments at entertainment zones, food courts, and youth retail anchors involve minors. Your POS enrolment flow must include an age verification step, and any under-18 identification must trigger a parental consent workflow before data processing begins. Fundle Loyalty includes a native Section 9 compliance gate in its POS enrolment module.
Does Fundle support integration with GoFrugal, POSist, Petpooja, and Wondersoft POS systems?+
Yes. The Fundle AI Platform supports certified integrations with GoFrugal, POSist, Petpooja, and Wondersoft — the four most widely deployed POS systems in organised Indian retail and mall environments. Fundle's middleware layer handles consent enforcement, data minimisation, and DPDP-compliant event routing between the POS and the Fundle Loyalty engine without requiring modifications to the POS software. The standard integration goes live in 8-12 weeks for a typical mall property. Custom POS systems can be connected via Fundle's documented REST API.
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.