Under Processors on Agency (/agency/<your-agency>/processors) you see who processes personal data, in which layer and under which agreement. The screen is for the owner and administrators and is read-only; the platform changes it.
Three layers
- The client and the agency. The client is the controller, the agency a processor.
- The agency and Denkploeg. Denkploeg is a sub-processor of the agency.
- Denkploeg and its suppliers. Such as hosting, DNS, sending mail and bookkeeping. Denkploeg's suppliers are sub-processors of the agency. What the client arranges itself, such as its own AI key or its own WhatsApp account, is listed too, with who arranges it.
Per party you see what they do, which data, where it is, under which agreement and who arranges it.
The status of an agreement
- To be reviewed: we think it is right, but the lawyer has not seen it.
- Missing: there is no agreement yet.
- Recorded: the lawyer has seen it, with the date.
- Client arranges and Not needed: for what the client agrees itself with a provider, and for a source without personal data.
Nothing is on Recorded until the lawyer has seen it. What is here is what we know; it has not been legally reviewed. The hash of an email address (later the sign-in pointer of an agency) counts as personal data and belongs to Denkploeg's data.
For the lawyer
The platform can download the overview as csv for the lawyer. Every change of a status is in the audit trail. Drafting a processing agreement itself is for the lawyer, not this screen.
Update 22 October 2026
The agency and public legal pages share the technical supplier register. Platform credit and BYOK routes are distinguished. A technical entry does not confirm a contract, role or region. Recorded agreements require an existing platform evidence file.