NeuroCRMSub-processors
NeuroCRM engages the third-party sub-processors below to help provide the Service. Each is bound by contractual confidentiality and data-protection obligations consistent with our DPA. We give customers advance notice of changes as described there.
1. Current Sub-processors
| Sub-processor | Purpose | Location of processing | Applies to |
|---|---|---|---|
| Amazon Web Services, Inc. | Cloud hosting & infrastructure | United States | Worldwide tenants |
| Hetzner Online GmbH | Cloud hosting & infrastructure | Germany (EU) | Worldwide / EEA tenants |
| Google LLC | Content-delivery network (CDN); and, where you connect them, read-only analytics integrations | United States / global edge | Worldwide tenants |
| Beget LLC | Cloud hosting & infrastructure | Russian Federation | Russian tenants (data localisation) |
| Anthropic, PBC | AI model provider (assistant / generation features) | United States | Tenants using AI features |
| OpenAI, L.L.C. | AI model provider (where enabled) | United States | Tenants using AI features |
| Google (Gemini API) | AI model provider (where enabled) | United States | Tenants using AI features |
Integrations you choose to connect (for example Yandex, Telegram, telephony, or payment providers) process data at your direction under their own terms; they are engaged only when you enable them. This list may be updated as our infrastructure evolves.
2. Notice of Changes
Where required by our DPA, we will give at least 30 days’ advance notice before a new sub-processor begins processing Customer Content, and you may object on reasonable data-protection grounds. To receive change notifications, contact support@neurocrm.vip.
3. Data Segregation
NeuroCRM keeps the Russian data contour (Beget, Russia) segregated from the worldwide contour (AWS in the US and Hetzner in the EU). We do not mix these data flows; data of Russian individuals is recorded and stored in Russia.