Subprocessors and external service providers.
Lumenoeva keeps external providers behind a controlled operating layer. The core register names fixed framework-level providers that can be identified accurately; customer-specific providers are defined by the workflow, approved architecture, data requirements and client systems.
Workflow-specific provider disclosure.
Additional AI models, enrichment services, client systems and operational providers are introduced only when the defined workflow requires them. Where a provider acts as a subprocessor of customer personal data, the applicable disclosure, authorisation and contractual requirements are established before that provider is introduced into the production workflow.
AI model providers
Approved models used for extraction, classification, research, preparation or other defined execution steps.
Data / enrichment providers
Approved services used where a workflow requires external business data or validation.
Client-system integrations
CRM, email, document, database or other systems used to receive or deliver the agreed outcome.
Infrastructure services
Hosting, logging, communications and other technical services required to operate the workflow.
The provider chain should not change invisibly.
Customer-specific subprocessor commitments are governed by the applicable contract and processing documentation. Where notification or authorisation is required, the customer arrangement defines how material provider changes are communicated and handled.
This public register is intentionally limited to providers Lumenoeva can identify accurately at framework level; it does not guess at customer-specific vendors or processing regions.