Adure BV — Sub-processors
Version 1.0, published at https://adure.io/sub-processors.
This list identifies the third parties Adure BV ("the Processor") engages to process Account Data — the names, business contact details and roles of a Controller's designated administrators, Users, billing or finance contacts, and authorised signatories — within Adure's own account, billing, support and contracting systems.
It applies to every Adure application and engagement. It is referenced by, and forms part of, each Adure Data Processing Agreement — the DPA (ISV) at https://adure.io/dpa-isv and the DPA (OEM) at https://adure.io/dpa-oem — and each Data Annex. Where the Standard Contractual Clauses apply, this list serves as Annex III (List of Sub-processors) to those Clauses.
Scope
This list covers the Sub-processors Adure engages to run its own business. They are the same for every Adure application.
Two other categories are recorded elsewhere:
- App-specific Sub-processors — third parties engaged to process data for one particular application, such as the platform, hosting and infrastructure providers on which an OEM application runs. These are listed in the Data Annex for that application.
- Customer Platforms — platforms the Controller licenses directly from the provider, such as its own Salesforce org or its own Zoho Sign account. Under Article 4 of the applicable DPA these are not Sub-processors of Adure. Adure's own separate accounts with those providers are listed below.
Additions and replacements are notified in accordance with Article 4 of the applicable DPA, which gives the Controller a period to object on reasonable data-protection grounds.
Current Sub-processors
Sub-processor | Service | Location | Transfer mechanism |
|---|---|---|---|
Salesforce, Inc. | Storage of Account Data in Adure's own CRM, used to administer Controller accounts. This is Adure's own Salesforce org — separate from the Controller's own Salesforce org, which is a Customer Platform and not a Sub-processor. | EEA — hosted on Salesforce EU infrastructure | N/A (EEA); Salesforce's own DPA |
Stripe (Stripe Payments Europe, Limited, and/or Stripe, Inc.) | Payment processing for Subscription Fees, including billing contact and payment details. | EEA (Stripe Payments Europe, Limited, Ireland), with underlying infrastructure that may involve processing in the United States | Stripe's own DPA |
Billit NV | Invoicing and accounting platform used to issue invoices and manage billing contact details. | Belgium (EEA) | N/A (EEA) |
Google Ireland Limited (Gmail / Google Workspace) | Business email and file storage used to communicate with the Controller's administrators, Users and billing contacts. | EEA (Google Ireland Limited), with underlying infrastructure that may involve processing outside the EEA | Google Workspace's own DPA |
Atlassian (Jira) | Issue and project tracking used to manage support requests and implementation work, which may contain the names and business contact details of a Controller's administrators and Users. | EEA, with underlying infrastructure that may involve processing outside the EEA | Atlassian's own DPA |
Zoho Corporation B.V. | Electronic signature of Adure's contract documents. | EEA — Adure's account is hosted in Zoho's EU data centre | N/A (EEA); Zoho's own DPA |
OVHcloud (OVH SAS) | Hosting of Adure's own servers, internal tools and automations, which may process Account Data in the course of account administration and support. | EEA (OVH SAS, France; EEA data centres) | N/A (EEA) |
Combell NV | Server and website hosting for Adure's own internal tools and automations, which may process Account Data in the course of account administration and support. | Belgium (EEA) | N/A (EEA) |
Version history
Version | Change |
|---|---|
1.0 | Initial published version |