Subprocessors and Service Providers
The current deployment-specific register of third-party services that may process visitor, customer, account or billing information.
Current deployment architecture
Not automatically active
Product analytics, error monitoring, transactional-email providers, and AI providers must not be listed as active subprocessors merely because the codebase or planning documents contemplate them. They belong on the production list only after the applicable integration is enabled and its data flow, region, retention, model-improvement posture, confidentiality terms, and contractual role are reviewed.
Customer-connected AI providers
AI Connections is currently gated OFF and METRAXIOM does not accept customer provider credentials through this path. A provider selected, contracted, and funded directly by a customer may not have the same legal role as a METRAXIOM-selected inference provider. The effective DPA/Terms must state whether METRAXIOM acts merely as a technical conduit, whether the provider is a customer-authorized third party, and which party controls retention, model-improvement settings, regional processing, and provider account administration.
Customer-authorized external AI clients
A customer may later connect a compatible ChatGPT/MCP or other approved external AI client through OAuth. That client is not automatically a METRAXIOM subprocessor merely because the customer authorizes it to receive read-only tool output. The applicable controller/processor/subprocessor role depends on which party selected the provider, whose account and contract govern the client, and the final customer/data-processing agreement. METRAXIOM therefore documents this path separately in AI & Data Use.
Customer content boundaries
Private source documents are intended to be stored through the controlled Supabase storage path. When paid billing is enabled, payment-card information entered on Stripe-hosted payment pages is handled by Stripe rather than stored directly by METRAXIOM. Application/provider secrets remain server-side and are not customer content. Customer-connected provider credentials must remain encrypted, tenant scoped, and excluded from ordinary logs, analytics, audit metadata, prompts, and browser storage after submission.
Production control
This register is reconciled to the current public-production evaluation profile. Before any held paid, private-workspace, AI, or customer-connected path is activated, its exact production account, region, contractual role, retention and model-improvement posture, transfer mechanism where applicable, and relationship to the effective Privacy Policy or DPA must be re-reconciled. Material changes must be versioned and communicated under the applicable customer agreement.