Voor klanten
Sub-processors
Versie 1.0 · Laatst bijgewerkt 2026-09-19
User and End User data sub-processors
Controller agrees to the commissioning of the following Sub-Processors for hosting and operating the Application Services. They are the only Sub-Processors that process User and End User Personal Data originating from the Customer Application:
| Sub-processor | Purpose | Region | Engaged since | Status |
|---|---|---|---|---|
| Amazon Web Services | Hosting and storage | EU | 2023-11-01 | Active |
| Microsoft Inc. | Microsoft Azure cloud services | EU | 2023-11-01 | Active |
| Google Inc. | Google Cloud Platform | EU | 2025-04-01 | Active |
User data sub-processors
Controller agrees to the commissioning of the following Sub-Processors for the operation of the UNLESS dashboard and customer administration. UNLESS does not submit End User Personal Data to these Sub-Processors:
| Sub-processor | Purpose | Region | Engaged since | Status |
|---|---|---|---|---|
| Stripe, Inc. | Payment provider for customers only | US | 2023-11-01 | Active |
| Chargebee | Automated subscription billing for customers only | US | 2023-11-01 | Active |
| HubSpot | CRM system and customer messaging platform for customer support | EU | 2023-11-01 | Active |
Integrations with third-party business systems
UNLESS offers integration with some of your existing business systems. If you choose to enable such an integration to exchange data with UNLESS, you may need to have additional legal arrangements with either the source or the destination of such data.
Changes to this list
We announce additions, replacements, and changes of region or scope at least twenty (20) business days before they take effect. A planned sub-processor is added to the table above with status “Announced” and its future effective date in the “Engaged since” column, and the designated administrators of each customer account are notified by email on the same day. Customers may object within the notice period on reasonable grounds, as set out in the Data Processing Addendum. On the effective date the status changes to “Active”. Sub-processors we stop using are removed from the table on the date the engagement ends.
