Zero Friction uses carefully selected subprocessors to ensure its platform is safe, reliable, and functional.
In this article we provide insight into:
which subprocessors we use;
for what purpose they are used;
where data is processed (data residency);
how these subprocessors are categorized.
This information forms part of our Trust Center and supports customers in their own compliance and due diligence obligations (such as GDPR).
Categorization
Zero Friction distinguishes three categories of subprocessors:
Infrastructure Subprocessors
Essential for hosting, monitoring and technical operation of the platform.
Core Functionality Subprocessors
Required for core Zero Friction functionalities such as communication, payments, and reporting.
Optional Subprocessors
Optional integrations that are only used when a customer activates this functionality.
Each category is explained separately below and shown in its own table.
Infrastructure Subprocessors
Infrastructure subprocessors support the technical foundation of the Zero Friction platform, such as cloud hosting, monitoring, and platform stability.
Name | Goal | Data Residency |
Microsoft Azure | Hosting of cloud infrastructure for storage and processing of application data | Western Europe (Amsterdam); management may be US-based |
Datadog | Data flows to report ready-made datasets and reports embedded in the Zero Friction platform | HONOR |
Core Functionality Subprocessors
These subprocessors are necessary for essential platform functionalities that are standard part of Zero Friction.
Name | Goal | Data Residency |
SendGrid | Sending emails and processing inbound webhooks | United States |
Intercom | In-app chat, user identification, and conversation management | United States |
Power BI | Embedded reporting within the Zero Friction platform | HONOR |
Optional Subprocessors
Optional subprocessors are only deployed when a specific integration or functionality is activated by the customer.
Name | Goal | Data Residency |
Berger Levrault | Integration with e-SedIt accounting platform | HONOR |
Recommend | Peppol access point for sending e-invoices | HONOR |
TKB Trust | Sending invoices to the TKB Trust collection platform | HONOR |
Payt | Sending invoices to the collection platform Payt | HONOR |
Track | API integration layer for Chorus Pro | HONOR |
Exact Online (BE) | Synchronization of invoices and accounting data | UK, Ireland, Netherlands |
Chorus Pro | Sending invoices and retrieving statuses | HONOR |
Twilio | Sending SMS messages and service updates | USA (EU-US Data Privacy Framework) |
Stripe | Online payment processing | US (EU-US DPF & SCCs) |
Freshdesk | Customer service support and context linking | EER or other (depending on configuration) |
Zendesk | Agents can identify customers, view balance and billing context in tickets, and deep-link to 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 | SEPA mandates and payment links/QR codes | HONOR |
Print Street (Pingen) | Printing and mailing of documents | EU |
Changes and updates
This list is evaluated periodically and revised at least annually.
The date of last assessment per subprocessor is recorded internally.
When adding or changing subprocessors, customers will be informed in accordance with contractual and legal obligations.