Zero Friction uses carefully selected subprocessors to provide its platform in a secure, reliable, and functional manner.
In this article, we provide transparency on:
which subprocessors we use;
for what purpose they are engaged;
where data is processed (data residency);
how these subprocessors are categorized.
This information is part of the Zero Friction Trust Center and supports customers in meeting their own compliance and due-diligence obligations (such as GDPR).
Categorization
Zero Friction distinguishes between three categories of subprocessors:
Essential for hosting, monitoring, and the technical operation of the platform.
Required for core Zero Friction functionalities such as communication, payments, and reporting.
Optional integrations that are only used when a customer enables the relevant functionality.
Each category is described separately below and presented in its own table.
Infrastructure Subprocessors
Infrastructure subprocessors support the technical foundation of the Zero Friction platform, including cloud hosting, monitoring, and platform stability.
Name | Purpose | Data Residency |
Microsoft Azure | Hosting of cloud infrastructure for storage and processing of application data | Western Europe (Amsterdam); management may be US-based |
Datadog | Collection of metrics, logs, and traces for monitoring and alerting of platform and application health | EEA |
Core Functionality Subprocessors
These subprocessors are required for essential platform functionalities that are a standard part of Zero Friction.
Name | Purpose | Data Residency |
SendGrid | Sending emails and processing inbound webhooks | United States |
Intercom | In-app chat, user identification, and conversation routing | United States |
Power BI | Data streams to report ready datasets and reports embedded in Zero Friction platform | EEA |
Optional Subprocessors
Optional subprocessors are only engaged when a specific integration or functionality is activated by the customer.
Name | Purpose | Data Residency |
Berger Levrault | Integration with the e-SedIt accounting platform | EEA |
Recommand | Peppol access point for sending electronic invoices | EEA |
TKB Trust | Sending invoices to the TKB Trust debt collection platform | EEA |
Payt | Sending invoices to the Payt debt collection platform | EEA |
Piste | API integration layer for Chorus Pro | EEA |
Exact Online (BE) | Synchronization of invoices and accounting data | United Kingdom, Ireland, Netherlands |
Chorus Pro | Sending invoices to Chorus Pro and retrieving invoice statuses | EEA |
Twilio | Sending SMS messages and service updates | United States (EU-US Data Privacy Framework) |
Stripe | Online payment processing | United States (EU-US DPF & Standard Contractual Clauses) |
Freshdesk | Customer support tooling and customer context linking | EEA or other (depending on configuration) |
Zendesk | Agents can identify customers, view balance and invoice context in tickets, and deep-link into Zero Friction. | US, AU, JP & EEA (EU-US Data Privacy Framework, international transfer possible) |
AFAS | Export of billing data with reconciliation and error handling | EEA (Netherlands) |
TwiKey | Creation and management of SEPA mandates and payment links / QR codes | EEA |
Pingen | Send print jobs with address data and PDFs for remote printing & postal delivery. | EU |
Changes and Updates
This list is periodically reviewed and updated at least annually.
The date of the most recent review for each subprocessor is recorded internally.
Customers are informed of additions or changes to subprocessors in accordance with contractual and legal requirements.