AxoDesk Legal

Third-Party Services and Subprocessors Notice

Effective: June 2, 2026 | Last updated: June 2, 2026

AxoDesk relies on vendors and customer-directed integrations. This notice explains the categories visible in the platform and how to request the production-specific list for your agreement.

Who this is for: Customers, procurement teams, privacy teams, and security reviewers.

1. Read this before relying on the list

The providers used for a specific customer can vary by production deployment, plan, region, enabled feature, and customer configuration. This public notice identifies provider categories and supported connections visible in the AxoDesk architecture. It is not a representation that every provider processes every customer's data. Enterprise customers should request the production-specific subprocessor schedule from sales@axodesk.io before contract signature.

2. AxoDesk-controlled vendor categories

CategoryPotential provider visible in the platformPurpose
Object storageCloudflare R2-compatible object storageFile and media storage or delivery.
Operational monitoringSentry, when configuredError diagnostics, logs, tracing, and operational monitoring.
PaymentsStripe and Razorpay, depending on billing flowSubscription, invoice, and payment processing.
Website analyticsGoogle Analytics, Google Tag Manager, Microsoft ClarityMarketing-site analytics after visitor consent.
Website supportTawkOptional marketing-site support chat after visitor consent.

3. Customer-directed channels and integrations

When a customer enables a connection, AxoDesk exchanges data with that provider on the customer's instructions. Depending on configuration, supported or referenced integrations include:

  • Meta services: WhatsApp Business Platform, Instagram, Facebook Messenger, Meta Ads, and Meta Conversions API.
  • Shopify for commerce synchronization and webhook-driven updates.
  • Google for OAuth-enabled account or channel flows.
  • Email delivery and ingestion services such as Mailgun.
  • SMS services such as MSG91.
  • Calling services such as Exotel.
  • Website chat and customer-configured webchat experiences.

These providers can act as independent controllers, processors, or subprocessor-like recipients depending on the integration and contract. Customers are responsible for reviewing their provider terms and configuration.

4. AI providers

Where a customer enables an AI feature, relevant instructions, knowledge content, and conversation context may be sent to the configured AI provider. Supported or referenced providers include OpenAI, Mistral AI, Cohere, Anthropic, and Google Gemini.

The production provider depends on customer configuration and deployment. Customers should request the applicable AI-provider terms, retention settings, and transfer details during enterprise review.

5. Changes and enterprise notices

AxoDesk may update providers as the platform evolves. Where a signed DPA requires advance notice or an objection process for new subprocessors, the signed DPA controls. Request the applicable schedule and notification channel from sales@axodesk.io.

This public legal center should be reviewed with AxoDesk sales for enterprise procurement and with your own counsel for your use case. A signed order form or enterprise agreement may include additional terms.