Skip to content
Opens the cited record in a new tab

Healthline: an opt-out must stop the tags, and article titles can reveal a diagnosis

Check two things in every ad request: that it does not fire after an opt-out, and that its page title or URL does not say something sensitive about the reader. California's Healthline case alleged both failures, and ended with what the Attorney General called a "novel term": a ban on sharing certain article titles with an identifier.

Civil penalty
USD1,550,000
Regulator
California DOJ
Law
CCPA
Stage
Settlement announced. Announced

Healthline stipulated without admitting liability and without any adjudication of fact or law (Judgment, pp. 1–2).

The problem

About 6.5 million Californians a month read Healthline.com without logging in (Complaint, ¶ 8). The Attorney General alleged that after a reader opted out by every available route, ad trackers kept sending their identifier together with titles such as "Newly Diagnosed with HIV? Important Things to Know" to advertising companies. About 65,000 Californians had opted out, mostly through Global Privacy Control (Complaint, ¶¶ 1, 14, 21).

What the regulator alleged

ClaimWhat the law requiresFacts allegedResult
Selling and sharing after opt-outStop selling and sharing once a consumer opts out, including by GPC (Civ. Code §§ 1798.120, 1798.135)After a "triple opt-out" (webform, GPC and unticking advertising cookies), investigators found 118 third-party advertising cookies, 82 ad tags on one page, a cookie-sync pixel and a universal ID in local storage (Complaint, ¶¶ 14–18)Settled; not decided
Purpose limitationUse data only for purposes consistent with the consumer's reasonable expectations (Civ. Code § 1798.100(c); 11 CCR § 7002)Article titles suggesting a current diagnosis went to advertisers; the privacy policy never mentioned sharing titles (Complaint, ¶¶ 21–23)Settled; not decided
Missing contract termsContracts with recipients must list limited, specified purposes (Civ. Code § 1798.100(d))Several recipients had not signed the industry framework Healthline relied on; some contracts allowed use for "any business purpose" (Complaint, ¶¶ 24–25)Settled; not decided
Deceptive banner (UCL)No misleading practicesThe cookie banner let readers untick advertising cookies, but did not disable them (Complaint, ¶¶ 13, 33)Settled; not decided

The complaint also argued Healthline could not use the CCPA safe harbour for passing on opt-outs. It sent the US Privacy String in some traffic, but its contracts did not oblige recipients to honor it (Complaint, ¶¶ 26–27).

What the judgment requires

Paragraphs are from the signed judgment.

  • Process GPC and other opt-out preference signals (¶ 17).
  • No diagnosis titles. Healthline "shall not SELL or SHARE PERSONAL INFORMATION combined with information that allows the recipient to determine that the CONSUMER is viewing a specific DIAGNOSED MEDICAL CONDITION ARTICLE, such as by including the title or URL" (¶ 18). Paragraph 6 lists 11 example articles and excludes general health articles.
  • Sensitive data: notice and a right to limit if sensitive personal information is ever used for ads (¶¶ 19–20).
  • Opt-out testing program: for three years, with an annual report explaining the testing done and any errors found and fixed (¶ 21).
  • Annual recipient review: list every third party and service provider receiving data through tracking technology, keep audit records of contract terms, verify that opted-out readers' data is not sold or shared, document any "service provider mode" signal, and recheck framework signatory lists each year (¶ 22).

Technical issue

  • Tools or vendors: unnamed ad-tech companies; a cookie-sync pixel; a universal identifier in local storage; the US Privacy String; a "privacy compliance vendor" (Complaint, ¶¶ 17–18, 26, 28).
  • Where: public article pages.
  • What data: cookie identifiers with the article title and URL.
  • When: after opt-out by form, GPC and cookie banner.
  • How it came to light: the Attorney General's own browser testing in autumn 2023 (Complaint, ¶ 2).

Healthline told the Attorney General that one opt-out mechanism was misconfigured, that ad vendors had installed some of the tags, and that its privacy compliance vendor "may not have properly identified and blocked all relevant online trackers" after detecting an opt-out. It now disables trackers directly (Complaint, ¶ 28).

Inth's technical interpretation: two separate faults. First, the opt-out was a signal passed along (the privacy string) rather than a gate: tags still loaded and decided for themselves. Second, the bid request carried document.title and the full URL by default, so the page's subject travelled with the reader's ID. Ad tags that load other tags make the first fault worse, because the blocking list never sees them.

Illustrative pattern, not the defendant's code.
// Bad: tags load after opt-out and carry the article title with the ID
loadAdTags();
requestAds({
  uid: readCookie("uid"),
  page_title: document.title, // "Newly diagnosed with ..."
  page_url: location.href,
  us_privacy: optedOut ? "1YYN" : "1YNN", // a signal, not a block
});

Timeline

DateEvent
Autumn 2023Attorney General tests Healthline's opt-outs (Complaint, ¶ 2)
1 July 2025Complaint filed; settlement announced (Announcement)
28 July 2025Judge Wong signs final judgment; filed the same day (Judgment, pp. 1, 8)

Outcome

Healthline pays USD 1,550,000 within 30 days after it is served with notice of entry, into the Consumer Privacy Fund (¶¶ 3, 24–25). Each side bears its own fees (¶ 26). The testing program and recipient reviews start within 180 days and run for three years, with confidential annual reports (¶¶ 21–23). The release is broad: all civil privacy and consumer protection claims about data from readers' use of Healthline's sites and apps, including for advertising and analytics (¶ 27). Nothing in the judgment is a finding.

What it cost

ItemAmount or term
Civil penaltyUSD 1,550,000 (¶ 24)
Attorney General's feesNone; each side bears its own (¶ 26)
Opt-out testing programThree years, annual reports (¶ 21)
Recipient and contract reviewThree years, annual reports (¶ 22)

Why it matters

The Attorney General billed it as the "Largest CCPA Settlement to Date" and the title ban as "a novel term" (Announcement); Disney and General Motors have since passed it. It is also an early CCPA case pleaded on purpose limitation: the claim is that the use itself, not only the missing opt-out, was unlawful. Two lessons for engineering teams: a consent vendor's blocking list is only as good as its coverage, and a contract framework counts only for recipients who actually signed it. See sensitive context in event data and CCPA.

How Inth catches this

  • Code audit

    Traces the article title from the page template into the ad request, and flags a pull request that adds an ad tag outside the consent check.

  • Website audit

    With an opt-out or GPC in place, records each request to an advertising domain, and each script injected by another script, with the page, time, region and consent state.

  • Consent banner

    In California, Global Privacy Control counts as an opt-out of sale and sharing, so marketing and analytics stay off for that visitor. Inth's default California policy is opt-out, so tags run until the visitor opts out; after an opt-out the Consent banner sends it to each integration and stops loading tags that have not loaded yet. It holds back only the tags it manages; tags an ad vendor injects need Website audit to surface.

Out of reach

  • None of this checks contract terms or what a recipient did with a privacy string.

The consent record (choice, country, policy) beside the runtime observation of what loaded.

Start a free scan

Checks for your own systems

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

0 of 8 done

In the repository

0 of 3 done

In the browser and network

0 of 3 done

With the people responsible

0 of 2 done

Sources and limits

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