DataInlet Subprocessor List
Legal document bodies are currently available in English only.
On this page
Last updated: September 3, 2026
This page lists third parties that DataInlet uses to process Customer Content on behalf of customers in the production Service.
It does not attempt to list every vendor used for DataInlet's own controller-side business operations. For example, a communications tool used only to receive a website contact inquiry is not listed here unless it also processes Customer Content on behalf of a customer.
Current subprocessors
| Subprocessor | Service | Purpose | Customer Content processed | Primary processing / storage location |
|---|---|---|---|---|
| Google Cloud | Google Cloud Platform (GCP) | Production hosting, compute, database infrastructure, object storage, networking, backup and related cloud operations | Source files, derived artifacts, runtime state, and related Customer Content | United States |
| OpenRouter, Inc. | OpenRouter API | AI request routing and gateway access to approved zero-retention inference endpoints | Prompts, relevant source/target context, files or extracted content supplied for inference, model responses, and request metadata needed to route and operate the service | United States; DataInlet configures production requests for zero-data-retention routing and does not enable prompt/response logging or data-use opt-ins for production Customer Content |
| OpenAI | OpenAI API | AI inference used for source understanding, target-system reasoning, and structured import decisions | Prompts, relevant source/target context, files or extracted content supplied for inference, and model responses | OpenAI-operated infrastructure; DataInlet uses OpenAI for production Customer Content only under an enabled zero-data-retention configuration |
| Gemini / Google AI inference services | AI inference used for source understanding, target-system reasoning, and structured import decisions | Prompts, relevant source/target context, files or extracted content supplied for inference, and model responses | Google-operated infrastructure; used for production Customer Content only through a service or endpoint that satisfies DataInlet's zero-data-retention and no-training requirements |
OpenRouter downstream inference providers
For requests routed through OpenRouter, OpenRouter may use third-party inference providers as its own downstream service providers. DataInlet does not permit unrestricted provider routing for production Customer Content. Production OpenRouter requests are configured to:
- require zero data retention;
- deny providers that collect request content for training or related data-use purposes; and
- disable provider fallbacks.
The specific downstream inference provider may vary by model and service availability, but only endpoints satisfying those routing requirements are eligible to receive production Customer Content.
AI data-use and zero-retention commitment
DataInlet does not use Customer Content to train or fine-tune general-purpose AI models.
DataInlet applies a zero-data-retention (ZDR) policy to third-party AI routing and inference used for production Customer Content. DataInlet does not intentionally enable prompt logging, feedback, dataset contribution, or similar optional settings that would retain Customer Content or use it for model or product improvement.
This AI-inference ZDR policy is separate from DataInlet's own storage of Customer Content. Customer Content stored by DataInlet remains subject to the Service's retention settings, deletion controls, backup rotation, and the Data Processing Addendum.
Changes to subprocessors
DataInlet may add or replace subprocessors as the Service evolves. Where applicable data-protection law or the Data Processing Addendum requires prior notice, DataInlet will provide notice through an update to this page, email, account notice, or another reasonable method before the new subprocessor begins processing Customer Content.
Questions or objections relating to subprocessors may be sent to contact@datainlet.com.