Consumer privacy rules that shape FMCG data collection
A shopper scans a QR code on a shampoo bottle to start a "hair quiz," then enters her email, her skin type and a photo of her scalp. That one interaction touches at least three legal regimes at once: GDPRGDPREU regulation governing how organizations collect, store and use personal data, with fines tied to global revenue for breaches.View full definition → in Europe, CCPA in California, and a cookie-consent rule if the quiz sits on a tracked webpage. If the brand gets any one of them wrong, its new "connected packaging" campaign becomes a regulatory liability instead of a data asset.
This lesson covers the rules that bind FMCG data teams (FMCG means fast-moving consumer goods: low-cost, frequently repurchased products like shampoo, snacks or detergent). It ends with the checks to run before launch.
Why FMCG is a special case
FMCG brands historically had almost no first-party datafirst-party dataData collected directly from your own customers and prospects through your own channels: your most reliable and privacy-compliant source.View full definition →. A shampoo brand sells through retailers like Walmart or Carrefour, and the retailer owns the checkout relationship, not the brand. Loyalty apps, sampling programs and smart packaging (QR codes, NFC chips) exist to close that gap by collecting data directly from consumers.
Privacy law scrutinizes this kind of direct collection hardest. The consumer starts the interaction, the data is often close to sensitive (skin conditions, allergies, family size), and it usually happens on mobile, where consent mechanics are stricter.
The three regimes, defined
GDPR (General Data Protection Regulation): EU law in force since 2018. National Data Protection Authorities (DPAs) enforce it, for example France's CNIL and Ireland's DPC. It applies to any company processing EU residents' personal data, wherever the company is based. The core requirement is a valid "legal basis" before processing, usually consent or "legitimate interest."
CCPA (California Consumer Privacy Act, amended by the CPRA, California Privacy Rights Act, effective 2023): gives California residents the right to know about, delete, and opt out of the "sale or sharing" of their personal information. The California Privacy Protection Agency (CPPA) enforces it. Unlike GDPR, it is opt-out by default for most data uses, not opt-in.
Cookie-consent rules: in the EU these come from the ePrivacy Directive (sometimes called the "cookie law"). It requires prior consent before placing non-essential cookies or trackers, on top of GDPR. The US has no single federal cookie law. A growing number of state laws (California, Colorado, Connecticut, Texas and others) require businesses to honor browser-level opt-out signals like Global Privacy Control (GPC).
What this means for a shampoo brand, concretely
Loyalty apps. Under GDPR, a "join our haircare club" sign-up needs a clear, unticked consent checkbox for marketing emails, separate from the terms-of-service checkbox. Under CCPA, the brand must post a "Do Not Sell or Share My Personal Information" link if it shares loyalty data with ad networks. It must also honor GPC signals automatically.
Sampling programs. Collecting a name and address to mail a free conditioner sample is generally low-risk, because the data is needed to fulfill the request. If the sampling form also asks "how often do you color your hair" and feeds the answer into a marketing segmentationsegmentationDividing a market into distinct groups of customers who share similar needs, characteristics or behaviours, so each group can be served with a tailored approach.View full definition → model, that is a secondary use. Under GDPR it needs its own legal basis.
Connected packaging. A QR code linking to a personalization quiz often lands on a third-party web platform running tracking pixels (Meta Pixel, Google Tag). If EU users arrive there, the ePrivacy rule requires consent before any pixel fires. Many brands fail this by loading the pixel on page load and showing the consent banner a second later.
Building a compliant first-party data asset
"First-party data" is data you collect directly from consumers. "Third-party dataThird-party dataData purchased from external aggregators, collected from audiences you don't own. It is bought or licensed rather than gathered through your own direct relationships.View full definition →" is data bought from data brokers. Third-party data is getting weaker for several reasons:
- Safari and Firefox already block third-party cookies by default.
- Regulators keep fining brokers and ad-tech firms.
- US states keep adding opt-out rights.
Chrome is the exception. Google abandoned its plan to remove third-party cookies in 2024 and confirmed in 2025 that Chrome will keep them. Even so, legal pressure and signal loss make first-party data FMCG's main growth lever.
Collecting it compliantly means four things:
- Purpose limitation. State exactly why you collect each field ("email for order confirmation," not "email for future use"). GDPR requires this explicitly, and it is good practice everywhere.
- Data minimization. Don't ask for a scalp photo if a text-based quiz answers the same question. Every unnecessary field is unnecessary legal exposure.
- Consent logging. For every opt-in, store the timestamp, the version of the consent text and the channel. If a DPA or the CPPA asks you to prove a user consented, you need a record, not a memory.
- Retention limits. Loyalty data for a discontinued shampoo line shouldn't sit in your CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → for five years "just in case." GDPR requires a defined retention period tied to the purpose.
A simple internal audit script can flag stale or unjustified data:
# Flag loyalty records with no activity and no documented retention reason
import pandas as pd
df = pd.read_csv("loyalty_members.csv")
cutoff = pd.Timestamp.now() - pd.DateOffset(years=2)
stale = df[
(pd.to_datetime(df["last_activity"]) < cutoff) &
(df["retention_justification"].isna())
]
print(f"{len(stale)} records flagged for deletion review")Run this kind of check every quarter, not once at launch.
Knowledge check
1. Why do FMCG brands invest heavily in loyalty apps, sampling programs, and smart packaging like QR codes?
2. Why does a QR-code-based 'hair quiz' that collects email, skin type, and a scalp photo draw especially heavy privacy scrutiny?
3. Under GDPR, what must a company establish before it processes an EU resident's personal data?
4. A US-based FMCG brand runs a scalp-photo quiz on a website that EU visitors can access. Why would GDPR still apply to this brand?
5. Select ALL correct answers about why a single 'hair quiz' interaction can touch multiple legal regimes at once.
Select all the correct answers.
6. Select ALL correct answers about rights CCPA/CPRA grants to California residents regarding their personal information.
Select all the correct answers.
Practical checks and audits to run
Before any campaign involving a loyalty app, sample form or QR-linked landing pagelanding pageA standalone web page built for a single campaign goal, designed to maximise conversions by removing distractions and focusing visitors on one action.View full definition →, run these checks:
- Consent audit: does the consent flow separate "necessary" processing from "marketing" and "analytics"? Is it opt-in where GDPR requires it, and does it honor opt-out signals like GPC in US states?
- Data mapping: trace every field collected to a named purpose and to the named system it flows into (CRM, ad platform, analytics tool). Unmapped fields are the most common audit failure.
- Vendor check: if a third-party agency runs your sampling site, confirm that a Data Processing Agreement is signed. This is a GDPR-required contract governing how processors handle data on your behalf. Note that "DPA" here means the contract, not the regulator.
- Cross-border transfer check: if EU consumer data flows to a US-based marketing cloud, confirm a valid transfer mechanism is in place. Options are Standard Contractual Clauses, or the EU-US Data Privacy Framework, adopted in 2023 and upheld by the EU General Court in September 2025.
- Children's data flag: family-size or "products for kids" campaigns must screen out children's data, which needs parental consent. In the US the cutoff is under 13 (COPPA, the Children's Online Privacy Protection Act). Under GDPR the default is under 16, though some EU states set 13.
For a practical starting reference, the UK Information Commissioner's Office publishes a clear, free guide to consent under GDPR. It is useful well beyond the UK.
Key Takeaways
- GDPR (EU) is opt-in by default and CCPA/CPRA (California) is opt-out by default. Design consent flows for the stricter one, GDPR, to stay safe globally.
- Cookie-consent rules (the EU ePrivacy Directive, US state GPC requirements) govern trackers separately from the main privacy law. They are the piece most often mis-implemented on QR-code landing pages.
- Loyalty apps, sampling forms and connected packaging are FMCG's main first-party data channels. Each carries its own legal-basis and minimization obligations.
- Run recurring audits, not one-time launch checks. Consent logs, data maps, vendor contracts and cross-border transfer mechanisms all need periodic review.
- Chrome kept third-party cookies, but privacy law, other browsers and enforcement keep shrinking the value of third-party data. Compliant first-party data is still the durable asset for FMCG brands.