Sub-processors

This page explains how third-party service providers may be used to support ZENIA Assistant.

ZENIA is designed as an agnostic SaaS product for website and document-based AI assistants. Some parts of the service may rely on external providers for hosting, data storage, AI inference and embeddings, email delivery, monitoring, support, or payment processing.

Paid plans are being prepared for launch through Paddle. Until checkout is enabled, paid access may be unavailable or limited to approved early-access users. This page may be updated as providers are confirmed, added, removed, or replaced.

ZENIA may use managed cloud infrastructure to host the public website, dashboard, API, widget delivery, uploaded files, indexed content, logs, and related platform services.

Infrastructure providers may process technical and operational data required to operate the service, such as IP addresses, request metadata, service logs, application assets, uploaded files, and indexed knowledge content, depending on the deployment environment.

Provider names and processing regions should be listed here only when confirmed for the production environment. Do not infer production providers from development, local, or test tooling.

ZENIA may use external AI inference and embedding providers to generate chatbot responses and create vector representations of indexed knowledge content.

When a chatbot response is generated, the minimum necessary prompt, conversation context, and relevant knowledge snippets may be transmitted to the AI provider for processing. This may include end-user messages and selected passages from website content, uploaded documents, or manual knowledge entries.

ZENIA does not use customer knowledge content to train its own general-purpose AI model. Provider-side handling is governed by the applicable provider terms and should be reflected in this page once the production AI provider list is confirmed.

ZENIA stores account, workspace, domain, knowledge, conversation, file, usage, and operational data in systems used to operate the platform.

Database or storage providers may process account information, workspace configuration, crawled content, uploaded-file metadata, indexed knowledge chunks, conversation records, usage limits, and operational metadata.

A database technology or internal library is not automatically a sub-processor. A provider should be listed as a sub-processor only where a third-party service provider processes personal data for ZENIA in the production environment.

ZENIA may use an email delivery provider for account notifications, password reset messages, service alerts, billing-related notices, and support communications.

Email providers may process limited contact data such as email address, display name, account identifier, message content, and support metadata.

Nodemailer is an internal software library used for sending email and is not itself a sub-processor. The actual email delivery provider, if any, should be listed here only after it is confirmed for production use.

Paid subscriptions are being prepared for launch through Paddle. If Paddle checkout is enabled, Paddle may process buyer, payment, subscription, tax, invoice, receipt, refund, cancellation, renewal, and chargeback information on its own systems.

ZENIA will not store full card numbers, CVV codes, or complete payment credentials. The platform may store only the information necessary to manage access and subscription state, such as selected plan, billing status, customer identifiers, transaction identifiers, subscription identifiers, and payment or cancellation status returned by Paddle.

Paddle is not expected to process customer knowledge-base content, uploaded files, indexed snippets, or chatbot conversation content for ZENIA.

ZENIA may use internal or third-party tools to monitor availability, diagnose errors, understand product usage, and improve platform reliability.

Monitoring and analytics data may include operational logs, error metadata, feature usage events, timestamps, request metadata, and limited account or workspace identifiers where necessary for troubleshooting.

Optional analytics that require consent should be handled through the Cookie Policy and cookie preference controls. Marketing tracking should not be listed here unless it is actually implemented and disclosed.

The provider categories described on this page may change as ZENIA evolves.

Where a named production provider processes personal data for ZENIA as a third-party service provider, this page should be updated to include the provider name, purpose, categories of data, processing region where known, status, and a link to the provider privacy or data-processing information.

Customers should review this page periodically. Where required by applicable law or contract, material sub-processor changes may also be communicated through the product website, account email, or related legal documents.