Last Updated: June 5, 2026
This page lists the third-party subprocessors that Netpeak LTD ("eniq.ai") uses to deliver the Service and process personal data on behalf of its customers. It is incorporated by reference into our Privacy Policy and our Data Processing Addendum.
We engage each subprocessor under a written agreement that imposes data-protection obligations substantially similar to those we accept toward our customers, including obligations of confidentiality, security, and limited processing on documented instructions. Where a subprocessor is located outside the European Economic Area ("EEA"), the United Kingdom, or a country that benefits from an adequacy decision, transfers are governed by the 2021 EU Standard Contractual Clauses ("SCCs") and, where relevant, the UK International Data Transfer Addendum, supplemented by the technical and organizational measures described in the DPA.
1. Active Subprocessors
1.1 Infrastructure and Storage
| Subprocessor | Purpose | Data involved | Location of processing |
|---|---|---|---|
| Google LLC (Google Cloud Platform — Google Cloud Storage, Compute, related infrastructure services) | Primary hosting and object storage for the Service and for recordings, transcripts, chat/message content, and application data | All Customer Data and Account Data | EU region(s) as configured; US for some global control-plane services |
| Cloudflare, Inc. | DNS, CDN, TLS termination, DDoS protection (as applicable to our public-facing domains) | Network metadata (IP, headers, request metadata) | EU / global edge |
1.2 Payments
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Stripe, Inc. / Stripe Payments Europe, Ltd. | Payment processing, subscription management, invoicing, tax calculation, fraud prevention | Customer billing contact, billing address, payment-method metadata (card brand, last four, expiry), transaction history. Full card numbers are handled directly by Stripe and never reach our systems. | IE / US |
1.3 AI / Model Providers
We use third-party foundation-model providers to generate transcriptions, summaries, scores, sentiment analyses, and other AI outputs. Where a provider offers a zero-retention or no-training configuration, we use it by default.
| Subprocessor | Purpose | Data involved | Location | Retention / training |
|---|---|---|---|---|
| Anthropic, PBC (Claude) | AI analysis (default provider) | Prompts and transcripts derived from Customer Data | US / EU per endpoint | Zero-retention API; no training on API inputs by default |
| OpenAI, L.L.C. | AI analysis and speech-to-text (optional, when selected) | Prompts, transcripts, audio snippets | US | API inputs not used for training; default 30-day zero-retention on enterprise/API tier |
| Google LLC (Gemini API, Speech-to-Text) | AI analysis and speech-to-text (optional) | Prompts, transcripts, audio | EU / US | Not used for training on paid Gemini API tier |
| xAI Corp. (Grok) | AI analysis (optional) | Prompts and transcripts | US | Per xAI API terms |
| Groq, Inc. | Low-latency AI inference (optional) | Prompts and transcripts | US / CA | Per Groq API terms |
1.4 Communication and Ingestion Platforms (activated per customer)
We do not connect to these providers on our own initiative. A customer activates a connector in project settings (or pushes data through our generic API); the provider then becomes a subprocessor for that specific data flow.
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Zoom Video Communications, Inc. | Meeting bot joining and streaming for Zoom meetings | Meeting audio/video/metadata | US / EU |
| Google LLC (Google Meet, Google Workspace APIs) | Meeting bot joining and streaming for Google Meet | Meeting audio/video/metadata | EU / US |
| Microsoft Corporation (Microsoft Teams, where connected) | Meeting integration (optional) | Meeting audio/video/metadata | EU / US |
| Cisco Systems, Inc. (Webex, where connected) | Meeting integration (optional) | Meeting audio/video/metadata | EU / US |
| Telephony, PBX, and contact-center providers you connect (including VoIP gateways and third-party call-tracking services) | Call audio and metadata | Call audio, CDRs, caller/callee identifiers | Provider-specific |
| Chat and messaging platforms you connect (WhatsApp Business API via Meta Platforms Ireland Ltd., Telegram FZ-LLC, Viber Media S.à r.l., Messenger/Instagram Direct via Meta, SMS/MMS gateway providers, live-chat widget vendors, email providers) | Message ingestion | Message content, participant identifiers, metadata | Provider-specific |
1.5 CRM Integrations (activated per customer)
A customer activates a CRM connector in project settings. The CRM vendor becomes a subprocessor only for data flowing through that integration.
| Subprocessor | Purpose |
|---|---|
| Zoho Corporation Pvt. Ltd. (Zoho CRM) | Bidirectional sync with Zoho CRM |
| HubSpot, Inc. | Bidirectional sync with HubSpot CRM |
| Pipedrive OÜ | Bidirectional sync with Pipedrive |
| Salesforce, Inc. | Bidirectional sync with Salesforce |
| Creatio, Inc. | Bidirectional sync with Creatio |
| Any other CRM, helpdesk, or sales-engagement platform you connect through our generic API | As configured by you |
1.6 Product, Security, and Support Tooling
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Functional Software, Inc. (Sentry) | Application error and performance monitoring | Stack traces, request metadata, user ID, IP | US / EU |
| Intercom R&D Unlimited Company | In-product messaging, customer support chat, and knowledge base | Support conversations, Account identifiers | EU / US |
| Cybot A/S (Cookiebot) | Cookie-consent management on our public website and app | Truncated IP, consent records | EU |
| Google LLC (Google Analytics 4, Google Tag Manager) | Website and in-app analytics (loaded only after visitor consent) | Pseudonymous device and usage data | EU / US |
| Telegram FZ-LLC | Optional push notifications and admin alerts via Telegram bot | Notification content, Telegram user IDs | UAE / global |
| Google LLC (Google Workspace — Gmail, Calendar, Drive) | Business communications (inbound and outbound email to customers, scheduling, file sharing) | Correspondence with customers and prospects, email content, attachments, calendar data | EU / US |
| SMTP2GO, Inc. | Transactional and system email delivery (receipts, invoices, password reset, account notices, scheduled reports, alerts) | Recipient email address, subject, message body, delivery metadata | US / EU edge |
1.7 Vector Database
The Service uses a self-hosted Qdrant vector database running inside our Google Cloud environment. No Customer Data is sent to a third-party vector-database service.
2. Affiliates
We may share Customer Data with group companies under common control with Netpeak LTD for the purposes described in the Privacy Policy, subject to equivalent contractual safeguards. Current affiliates: NETPEAK EOOD (LTD) and other companies under common control within FRACTAL (ex-Netpeak Group).
3. Notification of Changes
We will update this page before engaging a new subprocessor that materially affects customers' use of the Service. Customers on paid plans can subscribe to change notifications by emailing [email protected] with the subject line "Subprocessor notifications". Where required by law or contract, we will give at least 30 days' prior notice, during which a customer may object in writing for legitimate data-protection reasons; if we cannot reasonably accommodate the objection, the customer may terminate the affected Subscription for convenience, pro-rated.
4. How to Contact Us
Questions about this list, international-transfer mechanisms, or a specific subprocessor's processing activities: [email protected].