Subprocessors
Updated October 2026
The approved third parties to whom we may pass your data as part of operating the product. Each is bound by a Data Processing Agreement (DPA) or the provider's data-protection terms, and committed to a protection level equivalent to what is described in our privacy policy and privacy posture. We notify customers of new subprocessors at least 30 days in advance via the email registered with their account. Add this page to your procurement team's watch-list if you need formal tracking.
A note on Amargi Workspace
Reach and every other Amargi product use a shared identity provider called Amargi Workspace for sign-in. Workspace is an internal authentication service operated by Amargi Creative, same legal entity, same hosting, same compliance perimeter, and therefore NOT a subprocessor. Workspace does not store any WhatsApp message content, contact lists, or any data governed by Meta's BSP terms. Full breakdown in our privacy posture.
Hostinger International Ltd
Purpose: Primary hosting, compute, the PostgreSQL databases, object storage, outbound SMTP email relay, and DNS. This is where customer data lives at rest. Location: Germany (Frankfurt), EU. Engagement: Always engaged, the platform host for every tenant; data (including backups) resides in the EU (Frankfurt). DPA: https://www.hostinger.com/privacy-policy
Meta Platforms, Inc. / Meta Platforms Ireland Ltd.
Purpose: WhatsApp Business Platform (Cloud API), Messenger Platform, Instagram Graph API. The channel provider for messages our customers send and receive through Meta-owned surfaces. Location: Ireland (EU customers) + United States. Engagement: Engaged when the customer connects a WABA, a Facebook Page, or an Instagram Business account. DPA: https://www.whatsapp.com/legal/business-data-transfer-addendum
OpenAI, L.L.C.
Purpose: Large-language-model inference for Amargi Agents and AI replies, when a tenant runs AI on the OpenAI provider. By default it also computes the search embeddings for Amargi Agents knowledge, whichever chat provider the tenant uses. OpenAI does not train on data submitted through its API. Location: United States. Engagement: When an Agent run or an AI reply fires on the OpenAI provider, and when files or web pages are added to Agents knowledge or that knowledge is searched. DPA: https://openai.com/policies/data-processing-addendum
Anthropic PBC
Purpose: Large-language-model inference (Claude) for Amargi Agents and AI replies, when a tenant runs AI on the Anthropic provider. Anthropic does not train on data submitted through its API (Commercial Terms). Location: United States. Engagement: Only when an Agent run or an AI reply fires on the Anthropic provider. DPA: https://www.anthropic.com/legal/commercial-terms
Google LLC (Gemini API)
Purpose: Large-language-model inference (Gemini) for Amargi Agents and AI replies, when a tenant runs AI on the Google provider. Amargi is provider-agnostic, you choose which model processes your prompts. Location: United States. Engagement: Only when an Agent run or an AI reply fires on the Google (Gemini) provider. DPA: https://cloud.google.com/terms/data-processing-addendum
Expo (650 Industries, Inc.)
Purpose: Push-notification delivery for the Amargi Workspace mobile app. Expo receives the device's push token and each notification, and hands it to Apple Push Notification service (iPhone) or Google Firebase Cloud Messaging (Android) for delivery to the device. Expo stores the push token; it handles each notification only while sending it and does not store it. Location: United States. Engagement: Only when a user allows notifications in the mobile app. Data-protection terms: Expo's Terms of Service, section 3.2, which make Expo our processor for the personal data in what we send it and apply the EU Standard Contractual Clauses (Module 2), and make Expo a controller only for that data in aggregated or de-identified form, used to improve its services (Module 1); Expo is also certified under the EU-U.S. Data Privacy Framework. https://expo.dev/terms
Apple Inc. (Apple Push Notification service)
Purpose: Final delivery of Amargi Workspace mobile app push notifications to iPhones, as handed over by Expo. Location: United States. Engagement: Only when a user allows notifications in the mobile app on an iPhone. Terms: Apple Developer Program License Agreement.
Google LLC (Firebase Cloud Messaging)
Purpose: Final delivery of Amargi Workspace mobile app push notifications to Android devices, as handed over by Expo. Location: United States. Engagement: Only when a user allows notifications in the mobile app on an Android device. Terms: Firebase Data Processing and Security Terms.
Jina AI GmbH, part of Elastic (Reader)
Purpose: Fetching a web page that a tenant adds to Amargi Agents knowledge by its address. Jina receives the page's address, fetches the page and returns its text, which we then index, and may keep a cached copy of the fetched page. Jina does not train its models on these requests. Location: Jina AI GmbH is based in Berlin, Germany, and has been part of Elastic N.V. since October 2025. Its Reader service and its cache run on Google Cloud and MongoDB in the United States and Belgium, behind Cloudflare's global network. Engagement: Only when a web page is added to Agents knowledge by its address. Data-protection terms: Jina AI's legal page names the Elastic Customer DPA as the applicable data processing agreement, and section 11.2 of its terms of service incorporates Elastic's data processing addendum by reference: https://www.elastic.co/pdf/v100623-0-elastic-customer-dpa.pdf
Amargi Agents and AI provider choice
Amargi Agents is provider-agnostic: you choose which AI provider (OpenAI, Anthropic, or Google Gemini) processes your prompts, or none at all. The search embeddings for Agents knowledge use OpenAI by default, whichever provider you choose for chat. Amargi is also developing its own LLM, planned for a future release; once available it will run on Amargi's own infrastructure, so AI can be served with no third-party AI subprocessor at all.
Cross-border transfers
Hosting (Hostinger) is in the EU (Frankfurt). The AI providers (OpenAI, Anthropic, and Google) are in the United States, Meta is in Ireland/US, and the mobile app's push-notification services (Expo, Apple, and Google Firebase Cloud Messaging on Android) are in the United States. Jina AI is based in Germany and is part of Elastic; its Reader service runs in the United States and Belgium. For transfers outside the EEA we rely on the EU Standard Contractual Clauses (2021 issue) and equivalent transfer mechanisms (UK IDTA, etc.). AI is optional, if you don't run it, no data leaves the EU for inference.
Contact
Questions about this list, or subprocessor-change notifications: contact@amargicreative.com