Source-backed category hub
How do people opt out of advertising, device, location, or audience data flows while distinguishing collection from broker publication? This category hub contains 141 catalog profiles. Each profile records what the current snapshot supports about the provider route, workflow, sources, and evidence limits; category membership does not establish that a particular person appears in a provider database.
Catalog snapshot: 2026-09-25. Read the evidence methodology before relying on a route.
141
Profiles
catalog records
83
Direct routes
records with an attached URL
116
Registry context
matched public context
141
Evidence gaps
records with tracked gaps
Name the category or identifier only when the provider or official source states it, such as device, location, audience, or contact data. A general privacy policy should not be narrowed into a more specific individual finding without supporting text.
Sources:
Identify whether the page provides a provider-specific rights route, an industry choice tool, a device control, or explanatory context. These mechanisms can coexist and should not be presented as interchangeable deletion channels.
Sources:
The answer depends on the provider, browser signal, jurisdiction, and the source describing how the signal is honored. Treat a GPC statement as provider-specific evidence and do not generalize one implementation to all advertising or data-broker flows.
Sources:
Check the page language, form or submission controls, host relationship, and request type. A policy or choices page can explain rights without being the page where a request is submitted.
Sources:
A browser, operating-system, platform, or advertising-choice control can address a different collection or delivery point than a broker request. Document the separate control and its scope instead of claiming that one opt-out stops every downstream flow.
Sources:
Source requirements: provider privacy choices or request route; official regulator or recognized framework source; explicit distinction between provider statements and OfflistMe observations. Do not infer: claiming an opt-out stops all tracking; inferring data sharing from a reachable endpoint; presenting industry-choice tools as universal deletion.
Open a profile to review the current route, workflow fields, source ledger, freshness, and unknowns.
This category groups provider profiles that the current catalog classifies as advertising & adtech. It is a research and routing index, not proof that every provider has data about a particular person or that category members share one ownership or suppression route.
The current catalog contains 141 advertising & adtech profile records. The category count is derived from the catalog snapshot dated 2026-09-25; it is not a count of every provider operating in the market.
No. A source-backed profile records provider material, official registry context, workflow fields, or bounded read-only observations. Users still review, send or submit, save confirmation, re-check the listing, and follow up themselves.
Name the category or identifier only when the provider or official source states it, such as device, location, audience, or contact data. A general privacy policy should not be narrowed into a more specific individual finding without supporting text.
Identify whether the page provides a provider-specific rights route, an industry choice tool, a device control, or explanatory context. These mechanisms can coexist and should not be presented as interchangeable deletion channels.
The answer depends on the provider, browser signal, jurisdiction, and the source describing how the signal is honored. Treat a GPC statement as provider-specific evidence and do not generalize one implementation to all advertising or data-broker flows.
Check the page language, form or submission controls, host relationship, and request type. A policy or choices page can explain rights without being the page where a request is submitted.
A browser, operating-system, platform, or advertising-choice control can address a different collection or delivery point than a broker request. Document the separate control and its scope instead of claiming that one opt-out stops every downstream flow.