Screening
External list, media and data providers vary by the screening configuration.
Sub-processors
The list depends on the modules you activate.
Last updated 31 July 2026
Screening requires more external providers. Other module connections are activated on demand.
Your deployment schedule names the providers that can process client data.
There is no universal list padded with services your deployment never uses.
Core infrastructure
Hosting and inference are selected separately. A deployment may split them.
| Provider | Purpose | Location |
|---|---|---|
| AWS Europe | Hosting, storage and inference when selected | SwitzerlandZurich, eu-central-2Inference boundary: Switzerland and EU |
| Infomaniak | Hosting, storage and inference when selected | SwitzerlandInference boundary: Switzerland only |
Module-specific scope
Only providers used by the licensed workflow enter that deployment's schedule.
Onboarding & KYC review
External document, identity or registry connections activate only when selected.
Corporate mapping
Registry and ownership-data providers depend on the jurisdictions selected.
KYC remediation
Uses the data connections selected for the underlying KYC workflow.
AML & transaction monitoring
Connections depend on the client systems and monitoring scope selected.
What appears in the register
A provider is listed when it can process client data for the selected workflow.
Public sources do not automatically become sub-processors.
The exact names, purposes, countries and boundaries are confirmed before activation.
Changes to the list
Commitment
Written notice before a client-data sub-processor changes.
30 days, with a right to object inside that window.
Changing an inference host also changes the deployment's data-location boundary.
Questions or notice-list requests: contact@complai.ch.
Scope
This page covers the platform. Website providers are listed in the privacy notice.
Back to Security and residency