Processors
This is the complete list. It stands on this page so that nobody has to ask for it, telephone for it or sign in to see it. The last column says whether the party is actually reached on this installation: a no means nothing is sent there while the matching setting stays empty.
The same list, machine readable: /processors.json
| Party | Capacity | What for | Where | Reached through | Active here |
|---|---|---|---|---|---|
| DeepL | Not established | Machine translation of the documentation vault and of the titles a federated search finds at a source, from Dutch into the reader's language. | European Economic Area | Loaded by this site | Yes |
| Matomo | Processor | Visitor statistics, and the tag container through which the other front-end services arrive. | Wherever the operator runs that endpoint. | Loaded by this site | No |
| CookieHub | Processor | Showing the consent dialogue and remembering the answer. | European Economic Area | Matomo | No |
| Crisp | Processor | The chat window for questions. | European Economic Area | Matomo | No |
| Inspectlet | Processor | Session recordings and heat maps. | Not stated by that service. | Matomo | No |
| Zoho | Independent controller | The extended feedback form, where it is switched on. | Not stated by that service. | Loaded by this site | No |
| Anthropic PBC | Not established | Answers the questions of the question facility. Receives the question as it was typed and the answer that follows from it. | United States | Loaded by this site | No |
| WhyDonate | Processor | The payment form for a donation, and the handling of that payment. | European Economic Area | Loaded by this site | No |
The configured failure endpoint
BesluitBron:ErrorHandling:PostUrl |
Not established | The same failure record that is stored here, including the network, the browser identification and, when signed in, the user name. | Wherever the operator runs that endpoint. | Called by the server | No |
Why one capacity is left open
For one party the capacity reads as not established. That is not sloppiness but the honest answer: whether a party is a processor or an independent controller is a legal qualification, and it belongs to whoever carries that responsibility rather than to whoever writes the software. A payment platform is the standing example: anti-money-laundering law commonly obliges such a party to process on its own account, and a processing agreement then does not describe the relationship. What IS established stands in the table: which data that party sees and what for.
Who arrives through whom
This site loads only one script of another party itself: the tag container of Matomo. Everything carrying that name in the Reached through column arrives through it, not because this site asks for it. That is the sub-processor chain which otherwise stays invisible: a flat list of names does not help somebody who wants to know who is in their browser when four of them are there because of a fifth.
What is not in it
The source platforms this service reads are not here. They receive nothing about a visitor: it is the server that asks them, not the browser. Nor are there advertising networks or social media platforms, because there are none.
When this list changes
Adding a party means updating this list, in the same change. That is not an intention but a check: an address this installation puts in a page while no row of this list claims it is reported at start-up and fails a test.