[Enforcement library](/enforcement)

# FedEx: a cookie toggle that leaves ad trackers running is not a CCPA opt-out

The California Privacy Protection Agency Board adopted a stipulated final order fining Federal Express Corporation USD 2,975,000. The Enforcement Division found that fedex.com shared visitor identifiers with Meta, LinkedIn, Google, Adobe and other ad tech companies for cross-context behavioral advertising while the privacy policy said FedEx did not sell or share, that the site did not honor Global Privacy Control, that its CCPA webform excluded tracking technologies, and that toggling off cookies in its Cookie Preferences window did not stop all sharing. FedEx neither admitted nor denied the findings.

## Key facts

- **Regulator or court:** California Privacy Protection Agency
- **Jurisdiction:** California, US
- **Framework:** CCPA (Civil Code §§ 1798.120, 1798.130, 1798.135; Cal. Code Regs. tit. 11, §§ 7011, 7013, 7025, 7026)
- **Record date:** 2026-11-06
- **Procedural status:** Stipulated final order adopted by the Board; effective immediately; FedEx waived appeal

FedEx's privacy policy said it did not sell or share personal information, while ad trackers on fedex.com did exactly that. Global Privacy Control was ignored, and switching off cookies in the preferences window did not stop every tracker. The CalPrivacy Board fined FedEx USD 2,975,000.

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

- **Regulator**: California Privacy Protection Agency (CalPrivacy) Board; Enforcement Division as complainant
- **Case number**: ENF25-073-TS-FE
- **Respondent**: Federal Express Corporation
- **Law**: California Consumer Privacy Act and its regulations
- **Period reviewed**: 1 July 2023 to 27 October 2025, unless otherwise stated
- **Stage**: Order of decision adopting the stipulated final order, 6 November 2026; effective immediately; announced 10 November 2026
- **Amount**: USD 2,975,000 administrative fine
- **Source review**: 11 November 2026

## The problem

FedEx placed cookies and pixels from Meta, LinkedIn, Google, Adobe and other ad tech companies on fedex.com. According to the stipulated final order, these trackers made unique device and user identifiers available to those companies for purposes that included targeted advertising, which the CCPA treats as sharing for cross-context behavioral advertising. Some of the companies also synced cookies with each other ([stipulated final order](https://privacy.ca.gov/wp-content/uploads/sites/357/2026/11/FedEx_Decision-and-Stipulated-Final-Order.pdf), paragraphs 26 to 35).

At the same time, FedEx's privacy policy said: "We do not 'sell' or 'share' your Personal Information ... and have not done so in the previous twelve months." The site had a "Cookie Consent" footer link but no "Do Not Sell or Share My Personal Information" or "Your Privacy Choices" link, and the policy did not explain how opt-out preference signals were processed (paragraphs 39 to 42).

The order also rejects the idea that business-to-business visits fall outside the CCPA: people use the same devices for work and personal browsing, so identifiers collected on a shipping site can feed a broader advertising profile (paragraph 33).

## What the regulator found

| Finding | What the order says |
| --- | --- |
| Misleading disclosures | The privacy policy said FedEx did not sell or share personal information while its trackers shared it for cross-context behavioral advertising (Civil Code § 1798.130; Regs. §§ 7011, 7013) |
| No opt-out link | Only a "Cookie Consent" link; no Do Not Sell or Share or Your Privacy Choices link |
| Opt-out preference signals ignored | The site was not configured to detect and honor Global Privacy Control, so sharing with multiple ad tech companies continued (Civil Code § 1798.120(d); Regs. §§ 7025(c)(1), 7026(f)) |
| Webform excluded trackers | The CCPA request form said: "This form does not opt you out of cookies or tracking technologies" and pointed to the Cookie Consent link |
| Cookie controls did not work | After toggling off "Analytical" and "Tracking" cookies, FedEx still made some visitors' personal information available to some ad tech companies |
| Cookie controls did not address sale or sharing | A cookie tool can only serve as an opt-out method if it says how it applies to sale and sharing (Regs. § 7026(a)(4)) |

Source: [stipulated final order](https://privacy.ca.gov/wp-content/uploads/sites/357/2026/11/FedEx_Decision-and-Stipulated-Final-Order.pdf), paragraphs 36 to 56. FedEx admitted only the jurisdictional facts in paragraphs 1 to 5 and otherwise neither admitted nor denied the findings (paragraph 75).

## Technical issue

- **Data:** unique device and user identifiers collected by third-party cookies and pixels on fedex.com. The order says shipping data was not included.
- **Path:** Meta, LinkedIn, Google, Adobe and other ad tech tags on the site, plus cookie syncing between ad tech companies.
- **Signal:** the GPC header and the `navigator.globalPrivacyControl` property were not used to stop those tags.
- **Control:** the Cookie Preferences toggles for "Analytical" and "Tracking" did not block every vendor.

**Inth's technical interpretation:** each opt-out route has to reach the same switch. A GPC signal, a Do Not Sell or Share request and a Reject or toggle-off in the cookie tool should all mark the visitor as opted out of sale and sharing, and every advertising tag should check that state before it loads. Test it with real network traffic, not only the banner settings.

Sample:

```ts
// Cookie toggle only removes some tags; GPC never checked
if (prefs.tracking) loadTag('linkedin');
loadTag('meta'); loadTag('adobe');

// One opt-out state for GPC, the opt-out link and cookie toggles
const optedOut = navigator.globalPrivacyControl === true
  || consent.optedOut('sale-sharing');
if (!optedOut) ['meta', 'linkedin', 'google', 'adobe'].forEach(loadTag);
```

## Timeline

| Date | Event |
| --- | --- |
| 1 July 2023 to 27 October 2025 | Period covered by the factual findings, unless otherwise stated |
| September 2025 | Date of the Cookie Preferences window screenshot included in the order (Figure 2) |
| 1 November 2026 | FedEx signs the stipulated final order |
| 2 November 2026 | CalPrivacy Enforcement Division signs |
| 6 November 2026 | The Board adopts the stipulated final order as its decision, effective immediately |
| 10 November 2026 | CalPrivacy announces the decision |
| About 6 December 2026 | Fine due within 30 days of the decision's effective date (paragraph 61) |
| About 4 June 2027 | Conduct changes to be implemented within 210 days (paragraph 71); the practices review is due within 180 days (paragraph 68) |

## Outcome

FedEx agreed to the order and waived any hearing, reconsideration or appeal (paragraph 78), so the decision is final. The conduct terms last three years from the decision (paragraph 70). They require FedEx to scan its sites at least quarterly for trackers that sell or share personal information, keep CCPA-compliant contracts with those third parties, configure its sites to honor opt-out requests made through GPC or another required method, test those configurations in staging and production at least quarterly and whenever a tracker is added, offer a Do Not Sell or Share or Your Privacy Choices link without unnecessary friction, make any cookie control used for opt-outs say how it applies to sale and sharing, link cookie notices to the place where the choice can be made, and post annual CCPA request metrics ([stipulated final order](https://privacy.ca.gov/wp-content/uploads/sites/357/2026/11/FedEx_Decision-and-Stipulated-Final-Order.pdf), paragraphs 62 to 69; [CalPrivacy announcement](https://privacy.ca.gov/2026/11/federal-express-to-change-practices-and-pay-close-to-3-million-fine-over-ccpa-privacy-violations/)).

## What it cost

| Item | Amount | Source |
| --- | --- | --- |
| Administrative fine | USD 2,975,000 | [stipulated final order](https://privacy.ca.gov/wp-content/uploads/sites/357/2026/11/FedEx_Decision-and-Stipulated-Final-Order.pdf), paragraph 61 |
| Attorneys' fees and costs | Each party bears its own | [stipulated final order](https://privacy.ca.gov/wp-content/uploads/sites/357/2026/11/FedEx_Decision-and-Stipulated-Final-Order.pdf), paragraph 72 |

## Why it matters

- **A cookie toggle is only an opt-out if it works for every vendor.** Some ad tech companies kept receiving data after visitors switched cookies off.
- **GPC is not optional.** CalPrivacy said the duty to honor opt-out preference signals has been in place since 2020; the order requires testing it every quarter.
- **B2B sites are in scope.** Visits to a business shipping site can still feed consumer advertising profiles.
- **Say what you do.** A policy that denies selling or sharing while ad pixels run was itself a violation. Compare [PlayOn Sports](/enforcement/playon-sports), [Tractor Supply](/enforcement/tractor-supply) and [Honda](/enforcement/honda).

Related pages: [Ignored opt-out signals](/enforcement/issues/ignored-opt-out-signals), [Failed opt-out controls](/enforcement/issues/failed-opt-out-controls), [Notice, consent scope and assent](/enforcement/issues/notice-consent-scope-and-assent), [CCPA](/enforcement/laws/ccpa).

## How Inth catches this

- **Consent banner**: Can apply GPC, the opt-out link and Reject or toggle-off choices as one sale and sharing opt-out, and hold Meta, LinkedIn, Google and Adobe tags until that state allows them.
- **Website audit**: Loads pages with GPC on, and again after Reject, and records which ad tech requests still fire and which identifiers they carry.

### Out of reach

- Inth cannot fix a privacy policy that misdescribes selling or sharing, and it does not see server-side or cookie-sync traffic between ad tech companies after the browser request.

Consent records with the exact wording shown, choice, purpose, GPC state, country and policy version.

[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 tag that can share identifiers for advertising and confirm each one checks a single sale and sharing opt-out state.
- [ ] Confirm the code reads the GPC signal and treats it as an opt-out before tags load.

### In the browser and network

- [ ] Visit with GPC enabled in a clean profile and record every ad tech request.
- [ ] Turn off each cookie category in your preferences tool and confirm the related vendors stop receiving requests.
- [ ] Check that the footer shows a Do Not Sell or Share or Your Privacy Choices link that works.

### With the people responsible

- [ ] Compare the privacy policy's statements on selling and sharing with the tags actually running.
- [ ] Agree who runs a quarterly opt-out test and who approves new trackers before launch.

## Sources and limits

- [CalPrivacy order of decision and stipulated final order, Case No. ENF25-073-TS-FE](https://privacy.ca.gov/wp-content/uploads/sites/357/2026/11/FedEx_Decision-and-Stipulated-Final-Order.pdf) (opened 11 November 2026)
- [CalPrivacy announcement, 10 November 2026](https://privacy.ca.gov/2026/11/federal-express-to-change-practices-and-pay-close-to-3-million-fine-over-ccpa-privacy-violations/) (opened 11 November 2026)

Facts come from the stipulated final order, which FedEx neither admitted nor denied beyond paragraphs 1 to 5. The order does not name every ad tech company involved or say how many Californians were affected. The payment and implementation dates above are calculated from the 6 November 2026 effective date and are approximate.

Source review: 11 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)