Source-backed category hub
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-08-14. Read the evidence methodology before relying on a route.
9
Profiles
catalog records
1
Direct routes
records with an attached URL
1
Registry context
matched public context
9
Evidence gaps
records with tracked gaps
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.
Sources:
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:
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:
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.
Sources:
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.
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 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.
The current catalog contains 9 top german data brokers profile records. The category count is derived from the catalog snapshot dated 2026-08-14; 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.
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.
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.
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.
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.
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.