# Entea service-provider and subprocessor register

Last updated: 18 September 2026  
Status: Published technical inventory; contractual review pending

The list distinguishes Entea-operated dependencies from services a customer chooses and controls. Final processor classification, processing locations, and transfer terms must be confirmed in the executed Data Processing Addendum.

## Entea-operated service providers

| Provider | Purpose | Data categories | Current status |
| --- | --- | --- | --- |
| Cloudflare | DNS, reverse proxy/CDN, TLS edge, and transactional authentication email | Network metadata; authentication email address and email content when mail is sent | In use |
| GitHub | Entea source control and deployment automation | Entea product source, commit metadata, and deployment workflow logs | In use |
| Production infrastructure provider | Hosts the Entea website and control plane | Account, organization, operational, and encrypted control-plane data | Provider identity and region disclosure pending before external production data is accepted |
| Stripe | Subscription and payment workflow when configured | Customer and billing identifiers; payment information is handled by Stripe | Optional; billing integration present |

## Customer-directed providers

Customers may connect OpenAI, Azure OpenAI, Responses-compatible model services, Microsoft Azure, Amazon Web Services, Google Cloud, databases, object stores, SaaS systems, and other connectors. These services process data only when selected and configured for a workflow. They may be independent processors or customer subprocessors depending on the account and contract; they are not represented as always-on Entea subprocessors.

## Changes

Material subprocessor changes should be published here before they affect production customer data. A contractual notice period has not yet been approved. Customers requiring advance notice or objection rights must include them in the signed agreement.

Questions can be sent through https://entea.in/support.