NiseBookings subprocessors and suppliers
Draft, not yet legally reviewed. Version: draft 2026-11-05. This is a translation of the Dutch text. If the two differ, the Dutch text applies.
This list has two parts, because Nise has two roles.
A. Subprocessors: End customer data
Here the Customer is the controller and Nise the processor. This part is annex 2 of the processor agreement.
| Party | Purpose | Data | Region |
|---|---|---|---|
| Hetzner Online GmbH | Hosting of application, database, files and backups | All data in annex 1 | Nuremberg, Germany |
| Scaleway | Sending booking mails and authentication mails | Name, e-mail address, mail content, calendar file | Paris, France |
B. Nise’s own suppliers
Here Nise is itself the controller; see the privacy statement. Hetzner and Scaleway from part A also work on this. These parties receive no End customer data, unless stated.
| Party | Purpose | Data | Region |
|---|---|---|---|
| bunny.net | Marketing site and documentation | IP address and browser of visitors | Storage in Germany (measured), delivery worldwide through a CDN |
| Mollie | Subscription payments to Nise. Not active yet | Name, e-mail address and payment data of the account holder | Not set yet |
| GitHub | Source code, CI and images | No customer data; only developers’ data | Not set yet |
| UptimeRobot | Checking that the site is reachable | Nise’s alert address | Not set yet |
| MXroute | Mailbox info@nisebookings.com | Content of mail sent to Nise; this may include End customer data | US |
C. Recipients the Customer chooses
These are not Nise’s subprocessors. The Customer chooses them and is responsible for them.
| Recipient | What happens |
|---|---|
| Mollie (the Customer’s own account) | End customers pay on Mollie’s page. Nise sends the amount, a description with service and time, and a payment reference, no name or e-mail address. |
| Jitsi | For online appointments the Service creates a link. By default that is meet.jit.si; the Customer can set its own server. Nise sends no data to that server; the participant connects themselves |
| Webhook receivers | Receive ids and status fields at an address the Customer sets |
| API and MCP clients | Receive data with a key the Customer creates, also when that is an AI assistant |
| Calendar apps | Fetch a calendar feed through a link the staff member or Customer shares |
Changes
Nise reports changes to part A under article 4 of the processor agreement.