Skip to main content

Source-backed category hub

Top German Data brokers

Which German or EU privacy route applies to a broker record, and what should a person verify before sending? This category hub contains 9 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-10-23. Read the evidence methodology before relying on a route.

9

Profiles

catalog records

2

Direct routes

records with an attached URL

1

Registry context

matched public context

9

Evidence gaps

records with tracked gaps

Opt-Out Burden Score by broker category

Median score across 1,034 catalog brokers is 28 of 100. 341 Light, 673 Moderate, 18 Heavy, 2 Severe.

  • Median Opt-Out Burden
  • Median Exposure Reach
Social, Marketplaces & Platforms33 burden
10 reach
Marketing & Audience Data28 burden
13 reach
Credit, Risk & Identity28 burden
13 reach
B2B & Sales Intelligence27 burden
18 reach
Advertising & Adtech26 burden
16 reach
People Search & Public Records26 burden
38 reach

Chart by OfflistMe · offlist.me

Burden weights: catalog difficulty 45, government ID 15, sensitive identifiers (SSN, date of birth, ID numbers) 10, confirmation loop 5, email-only route 10, noindex on the opt-out page 15. Categories with fewer than 20 brokers are omitted. OBS v1 (2026-10-31); ERS v1 (2026-10-31). Full method

Show the data as a table
Opt-Out Burden Score by broker category data table
CategoryBrokersMedian burdenMedian reachHeavy or Severe burden
Social, Marketplaces & Platforms6633100%
Marketing & Audience Data35228131%
Credit, Risk & Identity23528136%
B2B & Sales Intelligence14827181%
Advertising & Adtech14126160%
People Search & Public Records9226382%

Sources: OfflistMe broker directory · Removal friction benchmark (CSV) · State data broker registry crosswalk · Corporate ownership graph · Opt-out page noindex scan · Checked catalog snapshot at build

Questions this category should answer

Does GDPR erasure, objection, or another right fit the request?

The relevant right depends on the processing purpose, legal basis, data, controller, and applicable exceptions. Explain the distinction using the official rights source and regulation text rather than treating every request as automatic erasure.

Sources:

What response window and complaint authority apply?

Use the current controller instructions and the applicable supervisory-authority guidance for the request. The knowledge base should preserve the source and jurisdiction instead of inventing a deadline from a generic privacy page.

Sources:

What identity information is proportionate to provide?

Provide only what the controller reasonably needs to identify the requester or record, following its current instructions. The GDPR principles and rights context support minimisation, but the exact verification step remains provider- and request-specific.

Sources:

Source requirements: provider controller or rights page; GDPR/BDSG or relevant supervisory-authority source; country-specific registry or official record where applicable. Do not infer: turning GDPR into an automatic deletion guarantee; assuming one EU route covers every affiliated controller; requesting unnecessary identity documents.

Direct source library

Top German Data broker profiles

Open a profile to review the current route, workflow fields, source ledger, freshness, and unknowns.

Browse all profiles →

Category FAQ

What are top german data brokers?

This category groups provider profiles that the current catalog classifies as top german data brokers. 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.

How many top german data broker profiles are in the catalog?

The current catalog contains 9 top german data broker profiles. The category count is derived from the catalog snapshot dated 2026-10-23; it is not a count of every provider operating in the market.

Does a source-backed profile prove that a broker removed my data?

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.

Is the controller identified and in the EEA?

Start with the provider controller, legal name, contact, and jurisdiction stated in the provider source. A German-language domain or a European customer does not by itself prove the controller location or applicable scope.

Does GDPR erasure, objection, or another right fit the request?

The relevant right depends on the processing purpose, legal basis, data, controller, and applicable exceptions. Explain the distinction using the official rights source and regulation text rather than treating every request as automatic erasure.

What response window and complaint authority apply?

Use the current controller instructions and the applicable supervisory-authority guidance for the request. The knowledge base should preserve the source and jurisdiction instead of inventing a deadline from a generic privacy page.

Is the record sourced from a public register or commercial data?

Name the source type and link the relevant official record or provider statement. Public availability does not by itself remove data-protection obligations or prove that a particular broker record is lawful or unlawful.

What identity information is proportionate to provide?

Provide only what the controller reasonably needs to identify the requester or record, following its current instructions. The GDPR principles and rights context support minimisation, but the exact verification step remains provider- and request-specific.

Explore Other Data Broker Categories