Subprocessors
Last updated: May 2026
Muxbe engages a small number of carefully selected third-party providers ("Sub-processors") to deliver the platform. This page describes the categories of Sub-processors we rely on, the purpose of each category, and the data involved. The named list of specific Sub-processors is provided privately to Customers under contract.
Categories of Sub-processors
| Category | Purpose | Data Processed | Processing Region |
|---|---|---|---|
| Cloud infrastructure & database | Hosting, database, file storage, authentication, serverless compute, scheduled tasks, secrets management, and logging | All platform data, including account information, business data, files, and authentication credentials | United States |
| AI services | AI-powered analysis: business assistant, retention campaign analysis, sports briefings, and content extraction from monitored web pages | User queries, conversation context, business data summaries, campaign metrics, sports event data, crawled website content | United States |
| Transactional email delivery | Delivery of invoice notifications, signal alerts, tenant invitations, and monitoring alerts | Recipient email addresses, notification content | United States |
| Frontend hosting & content delivery | Hosting and global delivery of the Muxbe web application and its static assets | Static application files; standard access logs (IP, user agent) | United States / Global CDN |
| Customer-configured platform integrations | Synchronization with the Customer's own affiliate management platform and marketing automation platforms, using the Customer's own credentials | Partner, player, commission, financial, and campaign data — as configured by the Customer | Determined by the Customer's chosen provider(s) |
Important Notes
Customer-Configured Integrations
Some integrations — including connections to the Customer's affiliate management platform and to marketing automation platforms — are set up by the Customer using the Customer's own API credentials. Muxbe processes data from these services on behalf of the Customer as a data processor; the Customer remains the data controller, and the Customer's relationship and contractual arrangements with each such platform are governed solely by the Customer's own agreement with that provider.
AI Processing
Muxbe's AI features use a third-party AI service provider's API. Muxbe uses that API under terms that do not permit Customer Data to be used to train models, and does not opt into any program that would allow such use. AI requests and responses are transmitted over encrypted channels.
Operational Service Providers
Muxbe additionally relies on a small number of operational service providers — for example, sports data providers, search engine results data providers, and proxy infrastructure used by the monitoring crawler — that do not process Customer Personal Data. These providers handle queries about publicly available information only (such as sports events, public search results, and public websites) and do not receive personal data relating to the Customer's employees, partners, players, or end-users. Because these providers do not process Customer Personal Data on behalf of the Customer, they are not Sub-processors within the meaning of Article 28 GDPR.
Requesting the Named List
Existing Customers, and Customers in the process of executing a DPA with Muxbe, may request the current named Sub-processor list — including provider names, processing locations, and links to each provider's data protection terms — at any time by emailing legal@muxbe.com.
Contact
If you have questions about our Sub-processors or data processing practices, contact us at legal@muxbe.com.