Sub-processors

The services this demo deployment is configured with, and what each one sees. The list is rendered from the deployment's own configuration at build, so it cannot quietly go stale.

The list

• your identity provider — identity provider, when an operator brings their own. It sees whatever the provider an operator configured sees. Kanban Toolkit asks it for an address and a name, and receives nothing else.
• the machine this runs on — hosting. It sees everything the database holds: accounts, workspaces, cards and the audit trail. On the demo instance that is a Cloudflare Worker with a D1 database; a self-hoster's is their own server.
• the error log — diagnostics. It sees a message, a stack trace, the path of the page, the build and the browser — never a query string and never an IP address, which are not collected.

A provider that is not configured is not listed, because it is not running. The privacy notice reads the same file, and a test fails when the code knows a provider this list does not.

If you run your own

This list is not yours. A self-hosted instance's processors are the ones its operator chose — the machine, the identity provider they configured, the database file, their own error log — and the operator is the controller of that data. The table above is the shape to copy, not a relationship to inherit.

There is no data processing agreement to sign with this project, because there is no processing: it ships software, and you run it. If you process somebody else's data on an instance you operate, your own agreement is the one that matters.

Changes

When this deployment adds or removes a processor, the release note for the tag says so. A self-hosted instance changes when its operator changes it, and nobody here can promise them notice.