Provision record
Meta · Meta Business Tools Terms · View original document ↗

Custom audience names must not reflect sensitive categories

Common · 238 of 343 platforms
Stay ahead of the changes
Track Meta and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Meta's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

Paramount+

Your User Submissions will not contain any: (a) swearing; (b) comments or actions which appear to be discriminatory...(c) comments or actions which promote bigotry, racism, hatred...(d) sexual innuendo...

Wealthfront

If you are under the age of 18, please do not submit any Personal Information to Wealthfront.

Pika

upload or make available (1) unsolicited advertising, promotional materials, or spam, (2) any personal, financial, or sensitive information (such as government IDs, social security numbers, or health data) without proper authorization

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
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.

Excerpt from Meta's Business Tools Terms

Provision details

Document information
Document
Meta Business Tools Terms
Entity
Meta
Date stated by the document
Nov. 3, 2025
As printed in Meta’s text (version CA-V-007551), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
May 20, 2026
Text quoted from version
CA-V-007278, captured Oct. 2, 2026
Record ID
CA-P-063760
Document ID
CA-D-000867
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007278)
fab3bb1b36b135b257cd4ce8f481b47c8c8d555dc8476edab63ee6b84e90afe7
Analysis generated
May 20, 2026 23:35 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-007278, captured Oct. 2, 2026 (checked Oct. 5, 2026)
Not the current version. The document's current version is CA-V-007551, captured Oct. 16, 2026; this clause has not been re-checked against it.
Citation Record
Entity: Meta
Document: Meta Business Tools Terms
Record ID: CA-P-063760
Version: CA-V-007278
Captured: 2026-10-02 00:13:05 UTC
SHA-256: fab3bb1b36b135b2…
URL: https://conductatlas.com/platform/meta/meta-business-tools-terms/provision/CA-P-063760/custom-audience-names-must-not-reflect-sensitive-categories/
Accessed: Oct. 25, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Meta's Custom audience names must not reflect sensitive categories clause do?

The clause states: “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.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 238 platforms. See the full comparison.

Is ConductAtlas affiliated with Meta?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.