dx0

Legal

dx0 Sub-processors

Third-party vendors that process personal data on behalf of our customers

Last updated: July 7, 2026

dx0 (HappySoup Limited) uses the sub-processors listed below to provide the Service. This page constitutes the current list of approved Sub-processors under Section 5 of the dx0 Data Processing Addendum ("DPA"). By accepting the DPA, Customer provides general written authorisation for dx0 to engage these sub-processors, in accordance with Section 5 of the DPA. dx0 will notify Customers of any additions or replacements to this list at least 14 days before the change takes effect, in accordance with Section 6.3 of the DPA, via email or by updating this page.

For questions about this list, contact us at help@happysoup.io.

Core Infrastructure

Sub-processorPurposeLocationPersonal Data Processed
MongoDB Atlas (AWS eu-west-1)Primary databaseEU — IrelandAccount data, session records, AI conversation history, workspace configuration, application logs.
AWS S3 (eu-north-1)Object storage for metadata index and audit logsEU — StockholmEncrypted Salesforce metadata index; encrypted audit logs.
AWS KMS (eu-north-1)Encryption key managementEU — StockholmEncryption/decryption requests only; no customer content.
RenderCompute — API server and background workerEUApplication runtime; logs.

AI Processing

Sub-processorPurposeLocationPersonal Data Processed
OpenAI, Inc.AI-powered analysis and explanationsUnited StatesTargeted Salesforce metadata snippets; user query content; prior conversation turns. Not the full metadata index, not credentials.

Transfer mechanism for OpenAI: Standard Contractual Clauses (EU Commission Decision 2021/914), Controller-to-Processor (Module 2).

Customer Communication

Sub-processorPurposeLocationPersonal Data Processed
CrispIn-product support messagingNetherlands / Germany, EUEmail address and name, captured when support chat is used.
ResendTransactional and product communication emailsUnited StatesEmail addresses of dx0 users.

Changes to This List

dx0 will notify Customers of any additions or replacements to this list at least 14 days before the change takes effect, via email or by updating this page.