Your Privacy Promise Is a Spec Your Tags Have to Meet
November 17, 2026
November 2026
/
The Hims & Hers case is a warning for every healthcare marketer. Regulators are no longer only asking whether your tracking code was legal. They are reading what your marketing promised, then checking it against what your tags actually sent. Where the two do not match, each gap becomes a potential count. Your privacy promise has become a specification your analytics setup has to meet.
What the complaint alleges, and what it does not
On November 10, 2026, five more states, Arizona, Florida, Nebraska, Ohio and Wisconsin, joined the Federal Trade Commission's case against Hims & Hers, standing alongside Utah and California in an amended complaint in the U.S. District Court for the Northern District of California.
Read it closely and notice what it does not say. It does not argue that the Meta pixel, or tracking code in general, is illegal on its own. It argues that Hims told customers their health information would stay private, then, by the complaint's account, shared sensitive data with advertising platforms including Meta and Snap. The reported specifics are the uncomfortable part: registration and purchase events passed to those platforms, roughly 8 million of them tied to treatment types, and about 14 million email addresses uploaded for ad matching. Hims has said it will vigorously defend itself, and no court has ruled.
The legal theory is what matters for everyone else. The problem the government describes is not that a pixel exists. It is the distance between a promise and a data flow.
How a lawsuit about pixels becomes one about what you promised
A privacy lawsuit used to live in the network tab, a question of which scripts fired and what they carried. This one lives in the copy. The evidence a regulator reaches for includes the reassuring line in your FAQ, the discretion promised in an ad, the script an influencer read. Each becomes a benchmark. If the site says information stays private and the tags say otherwise, the marketing is not just off message. It is the measure the conduct is judged against.
That redraws the compliance map. It is no longer only legal reviewing a privacy policy in isolation. The copywriter who promised discretion, the media buyer who added a Conversions API, and the developer who passed a product name into an event parameter are now authors of the same risk.
Where health data leaks without anyone noticing
Most of these exposures are not malicious. They are the defaults. Three places account for most of it.
- Custom event parameters. A developer names an event for the product or plan a customer selected, and a treatment category rides along into the analytics or ad platform without anyone deciding it should.
- The Conversions API. Server-side event forwarding was adopted to recover signal lost to browser restrictions. It also moves data the browser never would have sent, often with less visibility into exactly what leaves.
- Customer list matching. Uploading an email list for ad targeting feels like a marketing task. When the list is a list of patients, it is a disclosure of who sought care.
A claim-to-tag audit
The fix is not to rip out analytics. It is to make the promise and the plumbing agree. We run a claim-to-tag audit on every healthcare build, and the method is simple enough to adopt.
- Inventory every privacy claim. Pull each statement about privacy, security and discretion from the FAQ, the policy, the ads and any influencer or affiliate scripts.
- Map each claim to the data flows that could break it. For every promise, list the tags, parameters and integrations that touch the data the promise covers.
- Inspect what actually fires. Load the site and read the network requests and server-side events against that map, before consent and after, to see what is really sent.
- Close each gap. Where a tag contradicts a claim, change the tag, the parameter or the claim until they agree.
Who signs off on what
Shared risk needs shared sign-off. Four roles, one checkpoint before launch.
- Copy owns every privacy and discretion claim, and flags any new one for review.
- Media owns Conversions API configuration and every list upload, and treats a patient list as regulated data.
- Development owns event parameters, and clears anything that could name a condition or treatment.
- Counsel owns the reconciliation, confirming the claims and the data flows line up before the campaign goes live.
Before the next campaign launches
A short checklist for any telehealth or direct-to-consumer launch.
- Every privacy claim in marketing copy is mapped to the tag that could break it.
- No event parameter names a condition, treatment or plan that implies one.
- The Conversions API payload has been read field by field, not assumed.
- Every customer list upload has been reviewed as a data disclosure.
- Copy, media, development and counsel have signed off together, not in sequence.
The question to ask your team is small and revealing. When did marketing last read the tag manager? In the gap between what your site promises and what it sends, that is where the next complaint is written.
Sources: FTC, Five States Join FTC Lawsuit Alleging Hims & Hers Engaged in Deceptive and Unlawful Privacy Practices (Nov 10, 2026); PPC Land (Nov 11, 2026); Insurance Journal (Nov 12, 2026).
Ready to start a conversation about digital transformation?
Speak with our team and discuss your digital transformation.
Learn How our Pathfinder™ process Can improve your website
Schedule a meeting with our strategy team and we’ll show you how Pathfinder™ leads to project success.
Learn more about our fractional growth offering
Connect with our team to explore how a Fractional Growth Team can accelerate your marketing, UX, and digital execution, without the delays or costs of traditional models.
Curious how your site stacks up?
We’ll show you what’s working, what’s not, and where you’re leaving opportunities on the table.
Turn AI Search Into a Competitive Advantage.
See how your site can be structured to earn visibility in generative results and convert high-intent traffic into action.
Episode details
The Hims & Hers case is a warning for every healthcare marketer. Regulators are no longer only asking whether your tracking code was legal. They are reading what your marketing promised, then checking it against what your tags actually sent. Where the two do not match, each gap becomes a potential count. Your privacy promise has become a specification your analytics setup has to meet.
What the complaint alleges, and what it does not
On November 10, 2026, five more states, Arizona, Florida, Nebraska, Ohio and Wisconsin, joined the Federal Trade Commission's case against Hims & Hers, standing alongside Utah and California in an amended complaint in the U.S. District Court for the Northern District of California.
Read it closely and notice what it does not say. It does not argue that the Meta pixel, or tracking code in general, is illegal on its own. It argues that Hims told customers their health information would stay private, then, by the complaint's account, shared sensitive data with advertising platforms including Meta and Snap. The reported specifics are the uncomfortable part: registration and purchase events passed to those platforms, roughly 8 million of them tied to treatment types, and about 14 million email addresses uploaded for ad matching. Hims has said it will vigorously defend itself, and no court has ruled.
The legal theory is what matters for everyone else. The problem the government describes is not that a pixel exists. It is the distance between a promise and a data flow.
How a lawsuit about pixels becomes one about what you promised
A privacy lawsuit used to live in the network tab, a question of which scripts fired and what they carried. This one lives in the copy. The evidence a regulator reaches for includes the reassuring line in your FAQ, the discretion promised in an ad, the script an influencer read. Each becomes a benchmark. If the site says information stays private and the tags say otherwise, the marketing is not just off message. It is the measure the conduct is judged against.
That redraws the compliance map. It is no longer only legal reviewing a privacy policy in isolation. The copywriter who promised discretion, the media buyer who added a Conversions API, and the developer who passed a product name into an event parameter are now authors of the same risk.
Where health data leaks without anyone noticing
Most of these exposures are not malicious. They are the defaults. Three places account for most of it.
- Custom event parameters. A developer names an event for the product or plan a customer selected, and a treatment category rides along into the analytics or ad platform without anyone deciding it should.
- The Conversions API. Server-side event forwarding was adopted to recover signal lost to browser restrictions. It also moves data the browser never would have sent, often with less visibility into exactly what leaves.
- Customer list matching. Uploading an email list for ad targeting feels like a marketing task. When the list is a list of patients, it is a disclosure of who sought care.
A claim-to-tag audit
The fix is not to rip out analytics. It is to make the promise and the plumbing agree. We run a claim-to-tag audit on every healthcare build, and the method is simple enough to adopt.
- Inventory every privacy claim. Pull each statement about privacy, security and discretion from the FAQ, the policy, the ads and any influencer or affiliate scripts.
- Map each claim to the data flows that could break it. For every promise, list the tags, parameters and integrations that touch the data the promise covers.
- Inspect what actually fires. Load the site and read the network requests and server-side events against that map, before consent and after, to see what is really sent.
- Close each gap. Where a tag contradicts a claim, change the tag, the parameter or the claim until they agree.
Who signs off on what
Shared risk needs shared sign-off. Four roles, one checkpoint before launch.
- Copy owns every privacy and discretion claim, and flags any new one for review.
- Media owns Conversions API configuration and every list upload, and treats a patient list as regulated data.
- Development owns event parameters, and clears anything that could name a condition or treatment.
- Counsel owns the reconciliation, confirming the claims and the data flows line up before the campaign goes live.
Before the next campaign launches
A short checklist for any telehealth or direct-to-consumer launch.
- Every privacy claim in marketing copy is mapped to the tag that could break it.
- No event parameter names a condition, treatment or plan that implies one.
- The Conversions API payload has been read field by field, not assumed.
- Every customer list upload has been reviewed as a data disclosure.
- Copy, media, development and counsel have signed off together, not in sequence.
The question to ask your team is small and revealing. When did marketing last read the tag manager? In the gap between what your site promises and what it sends, that is where the next complaint is written.
Sources: FTC, Five States Join FTC Lawsuit Alleging Hims & Hers Engaged in Deceptive and Unlawful Privacy Practices (Nov 10, 2026); PPC Land (Nov 11, 2026); Insurance Journal (Nov 12, 2026).