[Enforcement library](/enforcement)

# In re Meta Android Privacy Litigation: the Meta Pixel passed browser IDs to Facebook and Instagram apps through localhost

Android users allege that from about September 2024 Meta modified its Pixel to send the _fbp cookie to a localhost port on the phone, where the Facebook and Instagram apps listened and linked it to the user's account, defeating Android sandboxing until researchers disclosed it in June 2025. On May 11, 2026 Judge Lin let intrusion, California Constitution, Wiretap Act, CIPA wiretap and eavesdropping, and CDAFA claims proceed against Meta and negligence proceed against Google, finding consent was not established on the pleadings. A second motion-to-dismiss order was entered on November 2, 2026; press reports say the wiretap and hacking claims survive and the pen register claim was dismissed.

## Key facts

- **Regulator or court:** US District Court, Northern District of California
- **Jurisdiction:** California, US
- **Framework:** Federal Wiretap Act; CIPA §§ 631, 632, 635 and 638.51; CDAFA; California Constitution; intrusion upon seclusion; negligence
- **Record date:** 2026-11-02
- **Procedural status:** Second motion to dismiss decided 2 November 2026 (Dkt. 159); core claims proceed per press reports

Android keeps apps sandboxed so a browser cannot hand data to another app. Plaintiffs say Meta's Pixel got around that by sending its browser cookie to a localhost port that the Facebook and Instagram apps were listening on, which tied logged-out web browsing to real accounts.

[Start a free scan](/run-free-codebase-scan)

- **Court**: US District Court, Northern District of California (Judge Rita F. Lin)
- **Case number**: 3:25-cv-04674-RFL (consolidated)
- **Parties**: Consolidated putative class actions by Android users against Meta Platforms, Inc., with negligence and negligent misrepresentation claims against Google LLC
- **Laws**: Federal Wiretap Act; CIPA §§ 631, 632, 635 and 638.51; CDAFA; California Constitution; intrusion upon seclusion; unjust enrichment; negligence and negligent misrepresentation (Google)
- **Stage**: First motions to dismiss granted in part and denied in part 11 May 2026 (Dkt. 120). Order on Meta's motion to dismiss the amended complaint entered 2 November 2026 (Dkt. 159)
- **Amount**: None
- **Source review**: 3 November 2026

## The problem

The Meta Pixel on third-party websites sends Meta the pages a visitor views, searches, actions and common form fields, along with cookies. When a user is logged in to Facebook or Instagram in the browser, a c\_user cookie identifies the account. On phones, most people use the apps instead, and Android's sandboxing is supposed to stop a browser and an app from sharing data. The Pixel's \_fbp cookie alone holds only a pseudonymous, usually site-specific identifier ([Order, Dkt. 120](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_25-cv-04674/pdf/USCOURTS-cand-3_25-cv-04674-2.pdf)).

Plaintiffs allege that around September 2024 Meta changed the Pixel to send the \_fbp cookie's contents to a designated localhost port, and changed the Facebook and Instagram Android apps to listen on that port, combine the value with account identifiers and send it to Meta's servers. Around November 2024 Meta allegedly switched from HTTP to WebSocket and to WebRTC with SDP munging, and in May 2025, within days of a Chrome beta mitigation, changed the Pixel again to get around it. Security researchers disclosed the technique on 3 June 2025; Google said it violated Play terms and Android users' privacy expectations, and Mozilla called it a severe violation of its anti-tracking policies ([Order, Dkt. 120](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_25-cv-04674/pdf/USCOURTS-cand-3_25-cv-04674-2.pdf)). Plaintiffs say iOS restrictions prevented the same technique on Apple devices.

## What the court found

| Issue | Holding |
| --- | --- |
| Consent (11 May 2026) | Not established on the pleadings. Meta's Privacy Policy mentions cookie data received through the Pixel, but consent is construed narrowly in scope, and users could plausibly have understood that Meta's matching would be imperfect, not that it would circumvent Android sandboxing |
| Intrusion upon seclusion and California Constitution | Plausibly alleged: a reasonable expectation of privacy and a highly offensive intrusion |
| Wiretap Act, CIPA § 631, §§ 632 and 635 | Claims stated |
| CIPA § 638.51 pen register | Dismissed with leave to amend in May 2026. In the 2 November 2026 order it was dismissed again; MLex reports the court relied on SB 690 removing the private right of action |
| CDAFA | Plausibly alleged that Meta knowingly acted without permission |
| Unjust enrichment | Dismissed with leave to amend (plaintiffs conceded) |
| Google: negligence | Survives. Plaintiffs plausibly alleged Android let apps listen on localhost ports without monitoring or user consent, against an industry custom shown by iOS |
| Google: negligent misrepresentation | Dismissed with leave to amend (Rule 9(b) applies) |
| 2 November 2026 order (Dkt. 159) | Per MLex and Law360, Meta again failed to dismiss: plaintiffs plausibly alleged Meta exceeded the scope of consent, and the wiretapping and hacking claims proceed |

Sources: [Order granting in part and denying in part motions to dismiss, Dkt. 120](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_25-cv-04674/pdf/USCOURTS-cand-3_25-cv-04674-2.pdf); [MLex, 2 November 2026](https://www.mlex.com/mlex/articles/2545363/meta-loses-bid-to-dismiss-android-browsing-privacy-lawsuit-in-us); [Law360, 2 November 2026](https://www.law360.com/articles/2545372/meta-can-t-shake-android-users-browsing-profile-claims).

## Technical issue

- **Data (alleged):** page URLs, searches, on-page actions and form-field contents collected by the Pixel, plus the \_fbp cookie value.
- **Path (alleged):** the browser sent the \_fbp value to a localhost port; the Facebook or Instagram app on the same phone read it, joined it to account identifiers and sent it to Meta.
- **Why it matters:** it linked browsing to an identified account even when the user was not logged in on the web.

**Inth's technical interpretation:** a site owner does not control what a vendor's script does after it loads. The only reliable control is not loading advertising pixels until the visitor has chosen, and watching for script behavior the vendor never disclosed, such as requests to 127.0.0.1 or localhost, WebSocket or WebRTC connections from tag code.

Sample:

```ts
// Ad pixel loads for every visitor, before any choice
loadScript('https://connect.facebook.net/en_US/fbevents.js');

// Ad pixel loads only after marketing consent
if (consent.has('marketing')) {
  loadScript('https://connect.facebook.net/en_US/fbevents.js');
}
```

## Timeline

| Date | Event |
| --- | --- |
| About September 2024 | Meta allegedly begins sending the \_fbp cookie to localhost ports on Android |
| About November 2024 | Meta allegedly moves to WebSocket and WebRTC with SDP munging |
| May 2025 | A Chrome beta mitigates SDP munging; Meta allegedly changes the Pixel within days |
| 3 June 2025 | Security researchers disclose the technique; first complaint filed in N.D. Cal. |
| 11 May 2026 | Order granting in part and denying in part motions to dismiss (Dkt. 120); amended complaint due 1 June 2026 |
| 2 November 2026 | Order on Meta's motion to dismiss the amended complaint (Dkt. 159) and a separate order (Dkt. 160) |

## Outcome

The case is in the pleadings stage. After the 11 May 2026 order, all claims except the pen register, unjust enrichment and negligent misrepresentation claims survived ([Order, Dkt. 120](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_25-cv-04674/pdf/USCOURTS-cand-3_25-cv-04674-2.pdf)). The 2 November 2026 order on the amended complaint reportedly keeps the wiretap and hacking claims in the case and dismisses the pen register claim ([MLex](https://www.mlex.com/mlex/articles/2545363/meta-loses-bid-to-dismiss-android-browsing-privacy-lawsuit-in-us); [Law360](https://www.law360.com/articles/2545372/meta-can-t-shake-android-users-browsing-profile-claims)). No class has been certified, no liability has been found and no money has been paid.

## What it cost

| Item | Amount | Source |
| --- | --- | --- |
| Damages or settlement | None so far | [Docket](https://casemagic.ai/case/cand/3-25-cv-04674) |
| Defense costs | Not stated in the cited record |  |

## Why it matters

- **A privacy policy that mentions the Pixel is not enough.** The court read consent narrowly: disclosing that Meta receives cookie data did not plausibly cover a technique built to get around operating-system protections.
- **Platform makers can be defendants too.** Google's negligence claim survived on the theory that Android let apps listen on localhost ports without user consent.
- **Pen register claims are fading.** The 2 November order reportedly dropped the CIPA § 638.51 claim because of SB 690, leaving wiretap, CDAFA and privacy claims as the main route. Compare [In re Meta Pixel Healthcare](/enforcement/in-re-meta-pixel-healthcare), [Frasco v. Meta](/enforcement/frasco-v-meta) and [Calhoun v. Google](/enforcement/calhoun-v-google).

Related pages: [Federal Wiretap Act](/enforcement/laws/federal-wiretap-act), [CIPA § 631](/enforcement/laws/cipa-631-wiretapping), [CIPA § 638.51 pen register](/enforcement/laws/cipa-638-51-pen-register), [IP addresses and device identifiers](/enforcement/issues/ip-addresses-and-device-identifiers), [Notice, consent scope and assent](/enforcement/issues/notice-consent-scope-and-assent).

## How Inth catches this

- **Consent banner**: Holds advertising pixels such as the Meta Pixel until the visitor grants marketing consent, so the script that did this never loads without a choice.
- **Website audit**: Loads pages in a clean profile and records every third-party script and request before and after a choice, including connections to localhost or 127.0.0.1.

### Out of reach

- Inth sees the browser side only. It cannot see what a native app on the same phone does with data it receives.

Consent records with choice, purpose, country and policy version, plus per-page network observations.

[Start a free scan](/run-free-codebase-scan)

## Checks for your own systems

Your ticks stay on this page. Inth does not save or send them.

### In the repository

- [ ] List every advertising pixel and the consent category that gates it.
- [ ] Check whether the Meta Pixel or any vendor script loads before a consent choice.

### In the browser and network

- [ ] On an Android device, load key pages and look for requests or WebSocket or WebRTC connections to localhost or 127.0.0.1 from tag code.
- [ ] Confirm no \_fbp or similar ad cookie is set before marketing consent.

### With the people responsible

- [ ] Ask each ad vendor in writing what its script does on mobile browsers beyond the documented requests.
- [ ] Decide who reviews vendor script changes and how quickly a tag can be pulled if a vendor's behavior is exposed.

## Sources and limits

- [Order granting in part and denying in part motions to dismiss, Dkt. 120](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_25-cv-04674/pdf/USCOURTS-cand-3_25-cv-04674-2.pdf), filed 11 May 2026
- [GovInfo case record](https://www.govinfo.gov/app/details/USCOURTS-cand-3_25-cv-04674)
- [Docket activity](https://casemagic.ai/case/cand/3-25-cv-04674) listing the 2 November 2026 Order on Motion to Dismiss (Dkt. 159) and Order (Dkt. 160)
- [MLex, "Meta loses bid to dismiss Android browsing privacy lawsuit in US"](https://www.mlex.com/mlex/articles/2545363/meta-loses-bid-to-dismiss-android-browsing-privacy-lawsuit-in-us), 2 November 2026
- [Law360, "Meta can't shake Android users' browsing profile claims"](https://www.law360.com/articles/2545372/meta-can-t-shake-android-users-browsing-profile-claims), 2 November 2026

The 11 May 2026 order was opened, and the facts and first-round holdings come from it. The 2 November 2026 order (Dkt. 159) was not yet available on GovInfo or Justia and was not opened; its holdings come only from MLex and Law360 summaries, which are paywalled and were read only as published summaries. Check the order before publishing, including whether any claim against Google was decided. The complaints and briefs were not opened.

Source review: 3 November 2026. This page describes the cited record and procedural stage. It does not audit the company's current systems. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.

## Related cases

[Every case in the Enforcement library](/enforcement)