DPA · ANNEX
Sub-processors
Convenience translation. The German version prevails. German version
This page is the public annex to the data processing agreement (DPA) for the SlimCore application (Art. 28 (2) and (4) GDPR). It lists the sub-processors that digiFORMER GmbH uses by default. The version is increased on material changes.
Last updated: 16 November 2026 · Version 1.0
1. Services in use
IONOS SE
Germany · Sub-processor
Hosting of application, database and files (Berlin); database backups (Frankfurt); hosting of our own geo service.
Transfer: No third-country transfer.
Brevo SAS (Sendinblue)
France · Sub-processor
Sending of system emails: invitations (first administrator, team members) and password reset.
Transfer: No third-country transfer.
Hetzner Online GmbH
Germany · Sub-processor
DNS resolution for website and application.
Transfer: No third-country transfer.
Anthropic
USA · Sub-processor
AI-assisted analysis of product feedback that users send to digiFORMER.
Transfer: Standard contractual clauses (SCC) from the Anthropic DPA.
Under Anthropic’s Commercial Terms the data is not used to train models.
Mistral AI SAS
France · Sub-processor
AI-assisted review of support and product feedback that users send to digiFORMER through the feedback function (message text).
Transfer: Established in the EU (France). Any third-country transfers are governed by the Mistral DPA.
The data is not used to train models (opt-out under the Mistral DPA) and is not stored after processing (zero data retention). Only reports that users actively submit through the feedback function are processed.
Firebase Cloud Messaging (Google LLC)
USA · Sub-processor
Delivery of push notifications (push token, notification content).
Transfer: EU-US Data Privacy Framework (Google LLC) and standard contractual clauses; Firebase data processing terms.
On iOS the notification is additionally delivered through Apple’s push service (APNs). Apple acts as platform operator and is not a sub-processor; see the application’s privacy notice.
Microsoft 365 (Microsoft Corporation)
USA · Sub-processor
Connection of the customer’s team email mailbox (sending and receiving emails).
Transfer: Transfer to the USA; transfer mechanism as per Microsoft’s terms.
Only if enabled by the customer (team email). Sign-in uses a system-wide OAuth client operated by digiFORMER; the mailbox belongs to the customer.
2. Customer-enabled integrations
Data is transmitted on the customer’s instruction. Where the “Account” line names a customer account, the customer has its own contract with the provider; there the provider is not a sub-processor of digiFORMER. Depending on the provider it is the customer’s processor or an independent controller (e.g. PayPal). For integrations that run through an account or key held by digiFORMER (noted per entry), the legal classification is still pending and will be updated following management’s decision.
- PayPal · USA
If the customer enables PayPal as a payment method.
Account: Account and credentials of the customer.
- Mollie · Netherlands
If the customer enables Mollie.
Account: Account and credentials of the customer.
- DHL · Germany
If the customer sets up DHL as shipping carrier.
Account: Account and credentials of the customer.
- DPD · Germany
If the customer sets up DPD as shipping carrier.
Account: Account and credentials of the customer (own DPD contract); credentials are currently stored on the operator side for the tenant.
- WooCommerce · Depends on shop operator
If the customer connects their shop.
Account: Shop and credentials of the customer.
- Webhooks · Depends on recipient
If the customer sets up webhooks to their own targets.
Account: Target URL, headers and payload are set by the customer; no digiFORMER credentials are used.
- Customer’s IMAP mail server · Depends on the customer’s mail server
If the customer connects their own IMAP mail server.
Account: Server, port and credentials are set by the customer; no digiFORMER credentials are used.
- Email delivery using the customer’s own account (currently Brevo) · France
If the customer sets up their own sending service under Settings → Email (off by default).
Account: API key and sender of the customer; Brevo acts on behalf of the customer, who concludes the data processing agreement with Brevo themselves.
3. Further information
Privacy on slimcore.io: Privacy notice. Questions: hallo@slimcore.io.