Ecommerce Privacy and Cookie Consent: How to Handle Customer Data Responsibly, Including in India
Ecommerce privacy and cookie consent: data mapping, consent, notices, rights and retention, plus what Indian stores should implement for the DPDP Act and Rules.
Quick answer
Handle customer data responsibly by first mapping it: what you collect, why, where it goes, who sees it and how long you keep it. Collect only what you need for clear purposes, get consent where the law requires it (commonly for non-essential cookies and some marketing), explain processing in a clear privacy notice, honour customer rights requests across every tool, vet vendors, set retention periods and secure the data. Obligations vary by jurisdiction and change over time, so take legal advice; this article is orientation, not legal advice.
Why Privacy Is an Ecommerce Design Problem
Customer data runs through every part of a store: accounts, checkout, email marketing, analytics, advertising pixels, reviews, support, loyalty, fulfilment and increasingly AI tools. Each adds a data flow and often a vendor. Privacy problems usually come from flows nobody documented, not from the platform itself.
Handled well, privacy builds trust and keeps data useful. Clear consent choices, honest notices and prompt responses to requests are part of the customer experience. For the security side, see ecommerce security; for mobile apps, see mobile app data privacy.
Step 1: Map Your Data
Start with a data map. For each category of personal data, record the source, purpose, legal basis or justification where the law requires one, systems where it's stored, vendors it's shared with, access and retention period.
| Data | Purpose | Where it goes | Retention (example to decide) |
|---|---|---|---|
| Name, email, address | Fulfil orders, service | Platform, fulfilment, support desk | Per tax and service needs |
| Order history | Service, analytics | Platform, warehouse, CRM | Defined period |
| Marketing email and SMS consent | Marketing | Email/SMS platform | Until withdrawn, plus records |
| Browsing and ad data | Analytics, advertising | Analytics and ad platforms | Tool settings |
| Support conversations | Service | Help desk, AI tools | Defined period |
| Sizes, preferences | Personalization | Platform, personalization tools | While account active |
Step 2: Purpose and Minimization
Collect data for specific purposes and no more than needed. Checkout needs an address; it doesn't need a date of birth unless you sell age-restricted goods. Personalization may need sizes; it doesn't need inferred sensitive characteristics. Minimization reduces risk, simplifies compliance and makes breaches less damaging. Review forms, apps and pixels for data they collect that you don't use.
Step 3: Consent and Cookies
Several laws regulate cookies and similar tracking, and some require consent for non-essential uses such as analytics and advertising. In the EU and UK, for example, consent is generally required before setting non-essential cookies. In some US states, laws give consumers rights to opt out of the sale or sharing of personal data and of targeted advertising, and some require honouring browser opt-out signals. Configure your consent tool to your markets, block tags until consent where required, record consent, and make it as easy to withdraw as to give.
On Shopify, the Customer Privacy API lets themes and apps read a visitor's consent choices, and Shopify offers cookie banner and privacy settings. Advertising platforms have their own consent mechanisms, such as Google's consent mode. Server-side tracking doesn't remove consent obligations.
- Consent banner configured per market
- Non-essential tags blocked until consent where required
- Consent state passed to analytics and ad tools
- Opt-out signals honoured where required
- Consent records kept
- Withdrawal as easy as giving consent
Not sure where your customer data goes?
ZSpace Labs maps ecommerce data flows, configures consent across tools and cleans up tracking you don't need.
What Indian Online Stores Should Implement
India's Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 apply to the personal data an Indian online store collects. The Rules come into force in stages: the provisions on consent managers apply from 13 November 2026, and the notice, security, breach, retention and children's data provisions from 13 May 2027. This section describes technical implementation, not legal advice; confirm what applies to your business with a lawyer.
Consent. Where you rely on consent, the Act requires it to be free, specific, informed, unconditional and unambiguous, given with a clear affirmative action (section 6). In practice that means unticked boxes, separate choices for separate purposes (order updates are not the same as marketing), and a way to withdraw that is as easy as giving consent.
Notice. The consent request must be accompanied or preceded by a notice describing the personal data and the purpose, how to withdraw consent and how to complain to the Data Protection Board (section 5). Customers must be able to read it in English or any of the languages in the Eighth Schedule to the Constitution.
Cookies. Neither the Act nor the Rules mention cookies specifically. Cookies and similar technologies fall within the law where they process personal data, which most analytics, advertising and personalisation tags do. A banner that loads tags before the visitor chooses, or offers only "Accept", does not meet the consent standard above. On Shopify, the built-in cookie banner shows to UK and EEA visitors by default, but you can choose to show it in any region, including India, and the Customer Privacy API lets apps and tags respect the choice.
Breaches. From May 2027, a personal data breach must be reported to affected customers without delay and to the Data Protection Board, with a detailed report within 72 hours. Separately, CERT-In's 2022 directions already require cyber security incidents to be reported within six hours.
Children. Processing a child's data (under 18 in the Act) needs verifiable parental consent. Stores selling toys, school supplies or teen products should design account creation with this in mind.
Retention. The Rules set specific erasure periods for some large platforms, including e-commerce entities with at least two crore registered users in India; smaller stores still need a retention policy based on purpose. Processing logs must be kept for at least one year.
| What to build | Why |
|---|---|
| Separate, unticked consent choices at signup and checkout | Specific, affirmative consent per purpose |
| Notice in plain language, available in English and relevant Indian languages | Notice requirement and language option |
| Tags blocked until consent; consent state passed to analytics and ad tools | Cookies that process personal data need valid consent |
| Self-service withdrawal and preference centre | Withdrawal as easy as giving consent |
| Consent records with time, source and notice version | Evidence if challenged |
| Breach runbook covering CERT-In (6 hours) and DPDP notices | Two different reporting regimes |
| Retention schedule and deletion jobs | Purpose limitation and Rule-based erasure |
Worth noting
Consent screens are also covered by India's consumer protection rules on dark patterns. The CCPA's 2023 guidelines list patterns such as interface interference and nagging, and the Consumer Protection (E-Commerce) (Amendment) Rules, 2026, in force from 1 January 2027, require a yearly self-audit for dark patterns and a displayed certificate of compliance. A banner that hides the reject option or keeps asking fails on both counts.
Step 4: Notices
Your privacy notice should explain, in plain language, what data you collect, why, who you share it with, how long you keep it, what rights customers have and how to exercise them. It must match reality: if you add an AI chat tool or a new ad pixel, update the notice. Some laws require specific content. Link to it from checkout, account creation and forms.
Step 5: Customer Rights Requests
Depending on the law, customers may request access to, correction of, deletion of or a copy of their data, or opt out of certain processing. Handle requests through a documented process: verify identity, find the data in every system on your data map (platform, email, support, warehouse, apps), respond within the legal deadline, and keep records. Deletion must reach third-party tools too, subject to data you're legally required to keep, such as tax records.
| Request | Where to act |
|---|---|
| Access | Platform, email, support, warehouse, apps |
| Deletion | Same, plus backups per policy; retain what law requires |
| Correction | Source systems; sync downstream |
| Opt-out of marketing or targeted ads | Email/SMS tools, ad audiences, consent state |
| Portability | Export in a usable format |
Step 6: Vendors and Transfers
Every app and tool that receives customer data is a vendor relationship. Check what data it receives, its security practices, where it processes data, and that appropriate contracts (such as data processing agreements) are in place. International data transfers may need additional safeguards under some laws. Remove apps you don't use; they often keep data access.
Step 7: Retention and Deletion
Set retention periods per data type based on purpose and legal requirements, and implement them: automatic deletion or anonymization where tools support it, scheduled clean-ups where they don't. Old exports, abandoned tools and inactive accounts are common places where data outlives its purpose.
Security of Personal Data
Privacy laws typically require appropriate security for personal data. Apply least-privilege access, MFA, encryption where you control storage, secure exports, vendor review and incident response, including breach notification processes where laws require them. See ecommerce security audit.
Analytics, Personalization and AI
Analytics, personalization and AI features are where privacy questions multiply. Use aggregated or pseudonymized data where possible, respect consent in every tool, avoid sensitive inferences, be transparent about personalization, and check AI providers' data terms before sending customer data. Some laws regulate profiling and automated decisions with significant effects; assess before building. See customer analytics and AI customer support.
Privacy in Checkout and Forms
Checkout and signup forms are where most customer data is collected, so they're where privacy design matters most. Separate marketing consent from purchase (not pre-ticked where consent is required), explain why optional fields are requested, avoid collecting data you don't use, and link to the privacy notice. Offer guest checkout and create accounts after purchase with clear choice. See checkout UX.
- Marketing consent separate and not pre-ticked where consent is required
- Optional fields marked and justified
- No unused fields
- Privacy notice linked at collection points
- Guest checkout available
Privacy for Marketing Data
Email, SMS and advertising audiences use customer data in ways many laws specifically regulate. Keep consent records for email and SMS, honour unsubscribes quickly across tools, check rules for uploading customer lists to ad platforms and for retargeting in each market, and make sure opt-outs from targeted advertising propagate. Build suppression lists that sync between tools.
Privacy Governance
Assign someone to own privacy: maintain the data map, review new tools and features, handle requests and track legal changes with advisers. Add a privacy check to the process for adding apps, pixels, AI tools and new data fields, and review the data map at least annually. Some laws require formal roles or assessments for certain processing; take advice.
| Trigger | Privacy check |
|---|---|
| New app or pixel | Data received, vendor terms, consent handling, notice update |
| New market | Local privacy and cookie rules |
| New AI feature | Data sent, provider terms, profiling risks |
| New data field | Purpose, necessity, retention |
| Annual review | Data map, notice, retention, vendors |
Common Mistakes
- No data map, so rights requests miss systems
- Tags firing before consent where it's required
- Privacy notice out of date with actual tools
- Apps with data access never reviewed or removed
- No retention periods
- Treating server-side tracking as consent-free
- Sending customer data to AI tools without checking terms
Ready to get customer data under control?
Talk to ZSpace Labs about privacy-aware tracking and data flows, Shopify consent configuration and analytics audits.
Conclusion
Responsible data handling starts with a data map, then minimization, consent where required, accurate notices, rights handled across all tools, vendor review, retention and security. Take legal advice for your jurisdictions. Related: ecommerce compliance and ecommerce data warehouse.
Common questions.
India's DPDP Act and Rules do not mention cookies by name, but cookies and tags that process personal data are covered, and consent must be free, specific, informed and given with a clear affirmative action. In practice most stores using analytics, advertising or personalisation tags need a consent mechanism that blocks those tags until the visitor chooses. Shopify's cookie banner can be enabled for India. Get legal advice for your specific setup.
In stages. The consent manager provisions apply from 13 November 2026, and the main obligations, including notices, security safeguards, breach reporting, retention and children's data, from 13 May 2027.
Names, emails, phone numbers, addresses, order history, payment tokens (not card numbers when using a payment provider), account data, browsing and marketing data, support conversations and sometimes sizes or preferences.
It depends on where you're established, where your customers are and what you do with data. Examples include the EU GDPR, the UK GDPR, California's CCPA as amended by the CPRA, other US state laws and national laws elsewhere. Get legal advice for your situation.
In some jurisdictions, such as the EU and UK, consent is generally required for non-essential cookies and similar tracking. Elsewhere, rules differ. Configure your consent tool to match the rules for your markets.
Documenting what personal data you collect, why, where it's stored, who can access it, which vendors receive it and how long it's kept. It's the foundation for privacy notices, rights requests and security.
Depending on the law, rights can include access, correction, deletion, portability, objecting to or opting out of certain processing, such as sale, sharing or targeted advertising, and withdrawing consent.
Shopify provides tools such as a customer privacy settings area, a consent banner option, the Customer Privacy API for apps and themes, and processes for handling data requests. You still need to configure them for your markets and handle data in other tools.
No. Moving tracking to the server changes where data is sent, not whether you're allowed to collect and use it.
Only as long as needed for the purposes you've stated and any legal requirements, such as tax records. Set retention periods per data type and delete or anonymize afterwards.
Sending customer data to AI services is processing like any other. Check the provider's terms, minimize data, update notices and assess risks, especially for profiling or automated decisions.
No. It's a practical orientation. Privacy law varies by jurisdiction and changes; consult qualified counsel.