Loading...
Loading...
Last updated: August 11, 2026
IngestX uses third-party providers selectively to operate and support its services.
The exact provider set can vary by product scope, deployment model, region, support arrangement, and customer-specific implementation.
For that reason, customer-facing subprocessor information is reviewed against the applicable service scope rather than represented as a one-size-fits-all universal list on every page of the website.
The following services are visible in the current platform configuration and may act as processors or subprocessors when the relevant feature is enabled. A customer’s actual provider set remains deployment-specific.
| Provider or service | Purpose and data | Region and use limits |
|---|---|---|
| Cloudflare | Website delivery, security, and human verification; network, device, and request data | Uses Cloudflare’s network. Any customer-specific region or transfer commitment must be recorded in the applicable agreement. |
| Google Analytics | Website analytics; cookie, device, and usage data | Used for the public website where enabled. Cookie details and available controls are described in the Cookie Policy. |
| Google services (OAuth or Gmail) | Customer-authorized sign-in or email-document ingestion; account identifiers, email metadata, and selected content | Used only when the customer enables the integration. Google’s processing terms and the deployment scope apply. |
| Groq or Replicate | Optional external AI or OCR inference; submitted Customer Content | Used only for deployments that approve the provider and processing region. Restricted data must not be sent unless the deployment’s transfer and residency controls allow it. |
| Resend | Optional transactional email delivery; recipient, routing, and message data | Used only when enabled. Exact transfer terms depend on the applicable service configuration. |
| Future payment provider | Billing and payment processing; billing contact and transaction data | No future online payment provider is represented as active by this register. The selected provider, processing scope, and location will be published or disclosed before activation. |
A provider’s presence in the codebase does not mean it is enabled for every customer. The order form or Data Processing Addendum controls where a customer-specific commitment is required.
Customers and prospective customers may request the current applicable vendor and subprocessor information during formal legal, procurement, or security review. A current list can be provided under NDA where appropriate, including:
For legal or procurement review, contact [email protected].
For security-focused diligence questions, contact [email protected].
Any commitment about prior approval, advance notice, region restrictions, or Indonesia-only processing should be confirmed in the applicable customer agreement, order form, or implementation scope.
