On this page

Meta's Business Tools Terms tell advertisers not to send Meta any data that "includes or is based on, directly or otherwise, health information," whether it goes through the Meta Pixel, the Conversions API or another Meta business tool. That rule is Section 1(h) of the Meta Business Tools Terms, which showed an effective date of November 3, 2025 when we checked the page on October 8, 2026. Meta does not sign a BAA (Meta in the BAA Directory). Curve Compliance sends Meta only a fixed list of fields from its own servers and flags PHI-like data before it reaches Meta. Curve signs a BAA on every plan.

Book a call. Curve's team will go through what your site sends Meta today and set up server-side conversion tracking, with a BAA signed on every plan. Book a call with Curve.

Already restricted? If Meta has limited your purchase or lead events, see Meta restricted purchase events for health and wellness. If Events Manager says data sharing restrictions were applied, see what Meta's data sharing restrictions mean. If your account status changed in Business Support Home, see what Meta Business Support Home is telling you.

Checked November 15, 2026. We re-read the seven Meta Business Help Center pages this guide cites. None has changed since this guide was published on October 8. Meta's Business Tools Terms still say you will not share data that "includes or is based on, directly or otherwise, health information".

The clause, quoted

Section 1 of the terms defines two kinds of "Business Tool Data": "Contact Information," such as names, email addresses and phone numbers, and "Event Data," information "about people and the actions that they take on your websites and apps or in your shops." Section 1(h) limits both. This is the text on Meta's page today:

"You represent and warrant that you will not share Business Tool Data with us that (i) you know or reasonably should know is from or about children under the age of 13, (ii) includes Contact Information not hashed in accordance with Section 1.a.i, (iii) includes identifiers we do not permit, such as social security or credit card numbers, or (iv) includes or is based on, directly or otherwise, health information, financial information, consumer report information, or other categories of sensitive information (including any information defined as sensitive under applicable laws, regulations and applicable industry guidelines). The names you choose and criteria you establish for your events, conversions, and any custom audiences you create must not reflect, imply or be based on any category of information described in this Section 1.h."

The terms call it both "Section 1.h" and "Section 1(h)". Section 2 says, twice, "The custom audiences you create must comply with Section 1(h)." The terms also say Meta "may use Event Data to personalize the features and content (including ads and recommendations) that we show people," and "may retain the Event Data for a maximum of two years." What an event carries can be used and kept.

What each part of Section 1(h) means

  • "Health information" is not defined. The clause points to information "defined as sensitive under applicable laws, regulations and applicable industry guidelines." Meta's prohibited information article gives examples such as "Diseases, medical conditions and injuries," "Medical procedures, treatments and testing" and "Physical locations that identify a health condition, or places of treatment and counseling," and says the list "is not exhaustive."
  • "Directly or otherwise." The data does not have to state a diagnosis. Names and criteria "must not reflect, imply or be based on" health information, so an event that implies a condition through its page or its name is covered.
  • No "should know" test for health. "You know or reasonably should know" qualifies prong (i), data about children under 13. Prong (iv), health information, has no qualifier.
  • Hashing is a separate rule. Prong (ii) requires hashed Contact Information, and Meta's prohibited information article says "Meta requires the hash method to be SHA-256." Hashing satisfies prong (ii), not prong (iv).
  • It is your warranty. Section 1(h) is a promise you make to Meta. Section 1 adds that if you share data "on behalf of or together with a third party," you warrant that you can bind that third party to the terms. That is the position an agency running a clinic's pixel is in.

Sensitive information beyond health

Prong (iv) also covers "financial information, consumer report information, or other categories of sensitive information." Meta's data source categories reflect that. Besides Health and wellness, the categories that may carry restrictions include Financial service, Sexuality and Gender Identity, Religion and Personal hardship. Events Manager shows which categories, if any, apply to your data source.

What the clause covers in practice

Meta's help pages turn Section 1(h) into a checklist. Prohibited information "should not be shared in Meta Business Tools data such as URL parameters, custom audiences, custom conversions, custom event names, and custom data" (Meta). Meta's troubleshooting article says to check URL strings, "parameter names and values you are sharing, and the names you have chosen for custom events." Here is where health information tends to hide.

Where it shows upWhat Meta saysOn a clinic site
Event names"The names you choose and criteria you establish for your events, conversions and custom audiences must not reflect, imply or be based on any prohibited information about people."A custom event or custom conversion named after a treatment.
Page URLsCheck pages with the Meta Pixel and "assess whether those pages, including the URL, contain information that may be considered prohibited data".A path or query string that names a condition.
UTM parameters"UTM parameters in a URL string may contain prohibited data from the landing pages viewed."A campaign named after a condition, carried in utm_campaign.
Custom parametersCheck "the data you send with events, such as product IDs, content names, custom properties and URL parameters".A content name filled in from the treatment menu.
Form answers"Analyze data fields, such as forms, on your webpages".Symptoms or intake answers picked up from a form.
Logged-in pages"You shouldn't send information about people from web pages where visitors may log in and provide potentially sensitive information, such as patient portals."A pixel still running on the patient portal.

Meta adds that "you are ultimately responsible for the data you share with Meta" and that "Meta's systems are not a substitute for your own compliance mechanisms."

What Meta does when it detects health data

Meta says its systems "are designed to block and remove potentially prohibited information they detect," and that you may then get a notice by email, in Events Manager or in Ads Manager (Meta). Failing to comply can also lead to consequences "such as performance issues, data restrictions, or suspension or termination of your use of our products and services, including the Meta Business Tools." The terms reserve the right "to monitor or audit your compliance." Day to day, it shows up as one of these notices.

What you seeWhat Meta has doneRead next
"Potentially prohibited information was removed from the data you're sharing"Filters removed data. Diagnostics show "which parameters, from which pages, had information removed," not the data, and Meta says never to re-send it (Meta).Prohibited information removed
Event parameters blockedParameters are blocked. Repeat notices can put the tool in core setup "for at least 90 days" (Meta).Event parameters blocked
Data sharing restrictions appliedThe site or app is in a restricted data source category: core setup, restricted standard events, or full restrictions (Meta).Data sharing restrictions applied
Core setupCustom parameters and "anything in a URL following the domain" are restricted (Meta).What still works under core setup
Custom events waiting for reviewWith any data restriction, custom events "are automatically blocked until you review and confirm them" (Meta).Custom events blocked for review
A category you think is wrongMeta-assigned categories can't be edited, but you can request a review.Requesting a category review

The Health and wellness category covers a data source that "Is associated with medical conditions or specific health statuses, provider/patient relationships, services for accessing personal health information, or health-related products and services," with examples including "a patient portal, wellness tracker, telemedicine platform, pharmacy, health insurance marketplace, or condition-specific support group." Meta assigns categories "based on the topics related to the data source and the products and/or services provided," so a category describes the business, not one parameter.

Book a call. Not sure whether your site sends Meta anything health-related? Curve detects PHI-like patterns, such as condition names or emails in URLs, before data reaches an ad platform and flags them so they can be stopped at the source. Book a call with Curve.

Does the Conversions API change anything?

No. The terms open by listing the products they cover: "Meta Pixel, Conversions API, Facebook SDK for App Events, Offline Conversions and App Events API." Section 1(h) applies to data from all of them, so a server event is held to the same clause as a browser event.

The FTC's complaint against Hims & Hers names both tools. Filed on July 29, 2026, it alleges that health information was shared through "the Meta Pixel and Conversions API business tools." It says the Conversions API "serves the same purpose of allowing Meta to automatically track Events" and "creates a direct connection between the advertiser's server, website, app or other internal software and Meta's systems" (complaint, paragraph 70). These are allegations, not findings. Our guide to the Hims & Hers complaint covers them.

Update, November 2026: on November 10, 2026 the FTC said it filed an amended complaint that "now includes Arizona, Florida, Nebraska, Ohio and Wisconsin in addition to Utah and California, by and through Los Angeles County Counsel," and that it alleges violations of those five states' consumer protection laws as well (FTC). As the FTC notes, "The case will be decided by the court."

What server-side sending changes is control. On a server, you decide field by field what leaves. But the same URL, event name or parameter breaks Section 1(h) whichever route it takes, and Meta forbids re-sending data it has removed. See why server-side tracking does not get around a restriction. Meta signs no BAA for either path (BAA Directory).

For how Curve sends Meta conversions server-side with a fixed list of fields, see HIPAA-compliant Meta conversion tracking.

Consent sits elsewhere in the terms, under "Special Provisions Concerning the Use of Certain Business Tools." You warrant "robust and sufficiently prominent notice" to users, which on websites means "a clear and prominent notice on each web page where our pixels are used" with a way to opt out. Where the law requires "informed consent for storing and accessing cookies or other information on an end user's device," as in the European Union, you must get it "in a verifiable manner" before Meta Business Tools store or access Meta cookies.

None of that is an exception to Section 1(h). The clause has no consent carve-out, so a consent banner does not make health information something you may send Meta. For how HIPAA, state health privacy laws and patient authorizations apply to your own site, talk to your counsel. Curve Compliance includes consent management alongside its tracking.

How Curve Compliance handles it

With Curve Compliance, what reaches Meta is set before anything is sent, not left to Meta's filters.

  • Server-side, from Curve's servers. One script replaces the browser ad pixels, and conversions go from Curve's servers to Meta Conversions API, Google Ads, TikTok, Microsoft Advertising and LinkedIn.
  • A fixed list of fields. Each platform receives only its own list. For Meta, the page address is cut to the site address, without the page path or query string. Page titles, free text and form answers are never sent.
  • Neutral event names that don't reveal a condition or a treatment.
  • Contact identifiers off by default, and hashed with SHA-256 when switched on.
  • PHI-like pattern detection. Condition names, form answers and emails in URLs are flagged before data reaches Meta, so they can be stopped at the source.

Curve signs a BAA on every plan. Like every BAA, it covers the data Curve handles for you. Curve's team does the setup, typically in about a week; it varies case by case. To see which pixels your site loads today, run the free website scan, or read why healthcare sites remove the Meta pixel.

Book a call. Curve's team will map which events and fields your site sends Meta, Google and TikTok, show what is likely to trigger a flag, and set up server-side tracking under a BAA signed on every plan. Book a call with Curve.

Sources, checked October 8, 2026 (Meta's Commercial Terms date re-checked October 25, 2026): Meta Business Tools Terms (the same text is at facebook.com/legal/businesstech); Meta Commercial Terms and the updated Commercial Terms; Meta Business Help Center: About prohibited information, Troubleshoot prohibited information notifications, Understand data sharing restrictions, About data source categories, About core setup, How to review custom events and How to review blocked parameters; and the FTC complaint against Hims & Hers.

Frequently Asked Questions

What do Meta's Business Tools Terms say about health information?

Section 1(h) says you will not share Business Tool Data that "includes or is based on, directly or otherwise, health information," and that names and criteria for your events, conversions and custom audiences "must not reflect, imply or be based on" it.

Does Meta sign a BAA?

No. Meta's terms rule health information out instead, as the BAA Directory entry for Meta shows. Curve Compliance signs a BAA on every plan for the conversion tracking it runs for you.

Did Meta's Business Tools Terms change in 2026?

On October 8, 2026, the Business Tools Terms page showed "Effective date: November 3, 2025" and no 2026 date. Meta's Commercial Terms, which the Business Tools Terms supplement, say updates "will go into effect on October 30, 2026." Update, checked October 25, 2026: Meta has since moved that date. Its Commercial Terms page now says the updates "will go into effect on November 20, 2026." In the updated version, the health wording of the Data Restrictions clause is unchanged apart from "Meta Products" becoming "Meta Company Products," and the Business Tools Terms are listed among the incorporated supplemental terms. Meta "may update these Business Tools Terms from time to time," so check the page itself.

Update, November 2026: Meta has put its updated Commercial Terms on hold. Its Commercial Terms page, checked November 15, 2026, says "We recently shared a preview of updated Commercial Terms. These updates are on hold. The existing Commercial Terms remain in effect until further notice." The terms in effect, dated March 6, 2024, still say you may not use Meta Products "to collect from people" information that "includes health, financial, biometrics, or other categories of similarly sensitive information" (Meta Commercial Terms). Meta's preview page is no longer available; an archived copy shows what it proposed.

The Business Tools Terms page carries no such notice, and the Section 1(h) wording quoted above is unchanged (checked November 15, 2026).

Do Meta's Business Tools Terms apply to the Conversions API?

Yes. The terms list the Meta Pixel, Conversions API, Facebook SDK for App Events, Offline Conversions and App Events API among the products they cover. Sending from a server does not change what Section 1(h) allows.

What counts as health information under Meta's terms?

The terms don't define it. Meta's help center gives examples such as diseases and medical conditions, mental health, sexual and reproductive health, procedures, treatments and testing, prescription medications, and places of treatment and counseling, and says the list is not exhaustive.

Does hashing make health data acceptable to Meta?

No. Hashing meets the separate rule that Contact Information be hashed with SHA-256. The health prong of Section 1(h) still applies to the event the hashed identifier travels with.

They require prominent notice on pages where Meta pixels run and, where the law requires it, verifiable consent before Meta cookies are stored or accessed. Neither is an exception to Section 1(h).

What happens if you send Meta health information?

Meta's systems are designed to block and remove it. Meta may also block parameters or custom events, or put the dataset in core setup after repeat notices. Its help center also lists suspension or termination of the Business Tools as possible consequences.

Is Meta's November 20, 2026 Commercial Terms update still happening?

No. Meta had announced updated Commercial Terms for November 20, 2026, but its Commercial Terms page now says "These updates are on hold. The existing Commercial Terms remain in effect until further notice" (Meta, checked November 15, 2026). The paused version would have let Meta "use automated software (such as web scrapers, bots, robots, spiders, crawlers, and user agents) and create test credentials" to reach advertisers' pages (archived preview). Under the terms in effect and the paused version alike, the Data Restrictions clause bars health information.