MZX AI Subprocessors

Effective date: November 7, 2025
Applies to: All Services operated by Metrix Zenith X Artificial Intelligence (“MZX AI”).

This page identifies third parties engaged by MZX AI to process  personal data on behalf of customers (“Subprocessors”). Terms used but not defined here have the meanings in your agreement and DPA with MZX AI.

Our no-training commitment (LLM APIs)

We engage LLM/API providers only where the provider publicly states that API inputs/outputs are not used to train or improve foundation models  and we contractually prohibit training on Customer Content/Personal Data for our workloads. We do not enable provider settings that allow retention for training unless you explicitly opt in (per contract).


Current Subprocessors

Regions. Processing regions reflect service configuration and availability. Unless agreed otherwise, primary processing occurs in the
United States. EU/UK transfer safeguards (e.g., SCCs + UK Addendum) apply where required.

Vendor (legal entity)Service category & purposeTypes of data processedProcessing location(s)Transfer mechanism (if applicable)Enabled by default?Notes
Amazon Web Services, Inc. (AWS)Hosting & infrastructure (compute, storage, encryption/KMS);
networking; logging
Customer Content (files you upload and generated outputs), account
& ops metadata, telemetry/logs
USA (primary). Other regions may be available by agreementSCCs/UK Addendum, as neededYesS3, EC2/Lambda, KMS, CloudWatch, etc.
Amazon Simple Email Service (SES)Transactional email delivery (notifications, confirmations)Sender/recipient names & emails; message headers; message body
(transactional)
USA (primary)SCCs/UK Addendum, as neededYesUsed for outbound transactional email only.
Microsoft Corporation (Exchange Online / SMTP relay)Transactional email delivery (fallback/relay)Sender/recipient names & emails; message headers; message body
(transactional)
USA/EU (per Microsoft routing)SCCs/UK Addendum, as neededNo (fallback)Used only as configured for redundancy or routing constraints.
Stripe, Inc.Payments (subscription/usage billing)Billing contact details; transaction metadata; tokenized payment info
(no full card stored by MZX AI)
USA/EU (per Stripe)SCCs/UK Addendum, as neededNo (only if your plan includes payments)Customer’s billing contacts only.
Zoho Corporation Pvt. Ltd.Support/CRM (ticketing, support emails/attachments)Support requester contact data; ticket content; attachments provided
by you
USA/EU/IN (per Zoho service/tenant)SCCs/UK Addendum, as neededNo (enterprise support)Do not include special categories in tickets unless instructed and
safeguarded.
OpenAI, L.L.C.Optional model API (inference only; no training on API
I/O
)
Prompt/response text you submit for inference (if enabled); minimal
metadata
USA/EU (per provider offering)SCCs/UK Addendum, as neededNo (opt-in)Subject to no-training commitment and customer enablement.
Google Cloud (Vertex AI) – Google LLCOptional model API (inference only; no training on API
I/O
)
Prompt/response text (if enabled); minimal metadataUSA/EU (per provider offering)SCCs/UK Addendum, as neededNo (opt-in)Subject to no-training commitment and customer enablement.
Anthropic PBCOptional model API (inference only; no training on API
I/O
)
Prompt/response text (if enabled); minimal metadataUSA/EU (per provider offering)SCCs/UK Addendum, as neededNo (opt-in)Subject to no-training commitment and customer enablement.
Perplexity AI, Inc.Optional model API (inference only; no training on API
I/O
)
Prompt/response text (if enabled); minimal metadataUSA/EU (per provider offering)SCCs/UK Addendum, as neededNo (opt-in)Subject to no-training commitment and customer enablement.
Mistral AIOptional model API (inference only; no training on API
I/O
)
Prompt/response text (if enabled); minimal metadataEU (primarily), other as offeredSCCs (when applicable)No (opt-in)Subject to no-training commitment and customer enablement.

Data minimization. For optional model APIs, we send only the text necessary for the specific inference task and disable persistent retention where feasible.


Change management & objections

  • Advance notice. We will post updates to this page before adding or replacing a Subprocessor. If you have a DPA with notice rights, we will also provide email notice to your designated contact (if provided).
  • Objections. Customers with an active DPA may object to a new Subprocessor on reasonable privacy grounds within the time stated in the DPA (typically 10 days). If not resolved, you may terminate the impacted Services and receive a pro-rata refund of prepaid unused fees, as described in your DPA.
  • Emergency additions. In rare cases (e.g., incident response), we may engage a temporary Subprocessor to maintain service and security; we will update this page promptly thereafter.

Subscribe for updates or questions: privacy@mzx.ai


Customer-controlled deployments

Some customers may contract for private/VPC deployments. In such cases, Subprocessors and data flows may differ (e.g., Customer’s own cloud account, no shared email provider). The applicable Subprocessor set and regions will be defined in your order form/SOW.


Historical log

  • 2025-11-07: Initial publication of Subprocessors page; supersedes any legacy ‘Approved Subprocessors’ annex in prior documents.

Reminder: This page is for transparency and works together with your Agreement and DPA with MZX AI. If there is any inconsistency, the DPA governs processing of personal data.