Sub-processors
Who may process service data
Core providers are separated from optional integrations so the list does not imply that every customer's data is sent to every vendor. This overview is not a readout of a tenant's live configuration. Request the current hosting provider, region and applicable provider details before relying on a residency requirement.
Last updated 2026-10-19
Service providers
| Provider | When used | Purpose | Data |
|---|---|---|---|
| Cloudflare | Domain services | Domain name services, and Turnstile bot checks on signup and public forms. | DNS query and domain-administration metadata; browser signals and IP address for Turnstile checks. |
| Microsoft 365 (Graph) | Active platform email | Account, verification, billing and notification email sent by Zubby AI. | Recipient address, subject, message body, and delivery metadata. |
| GitHub | Live source control | Private source control and release transport for the application. | Application source and release metadata; production credentials and customer databases are excluded. |
AI model routing
Only the provider selected by the platform configuration receives a given model request.
| Provider | When used | Purpose | Data |
|---|---|---|---|
| Microsoft - Azure OpenAI | Active model provider | Chat generation and embeddings. | Prompt text and the retrieved store context needed for the request. |
| OpenAI | Optional; only when enabled | Alternate model routing. | Prompt text and retrieved context for the selected route. |
| Anthropic | Optional; only when enabled | Alternate model routing. | Prompt text and retrieved context for the selected route. |
| Google - Gemini | Optional; only when enabled | Alternate model routing. | Prompt text and retrieved context for the selected route. |
Communications
| Provider | When used | Purpose | Data |
|---|---|---|---|
| Resend | Conditional; fallback email only when configured | Backup delivery for platform and merchant email. | Recipient and sender addresses, subject, message body, and delivery metadata. |
| Browser push services (Google, Mozilla, Apple) | Conditional; only when a merchant turns on web push | Delivering merchant dashboard notifications to their browser. | Encrypted notification payload and the browser's push endpoint. |
| Merchant SMTP | Conditional; only when configured by a merchant | Store-specific or fallback email delivery. | Recipient and sender addresses, subject, message body, and delivery metadata. |
| Twilio; Meta (WhatsApp, Facebook and Instagram) | Conditional; only for merchant-enabled channels | SMS, WhatsApp, Facebook, or Instagram messaging selected by a merchant. | Channel identifiers, message content, and delivery or conversation metadata. |
Commerce, billing, and diagnostics
| Provider | When used | Purpose | Data |
|---|---|---|---|
| Shopify; merchant-hosted WooCommerce | Chosen by each merchant | Connected-store catalog, order, customer, and webhook operations. | The store records and actions authorized by the merchant's granted scopes. |
| Merchant-connected apps (Gmail, Microsoft 365, Klaviyo, Mailchimp, HubSpot, Zendesk, Segment, TikTok) | Chosen by each merchant | Syncing contacts, events, tickets or email through accounts the merchant connects. | Only the records the merchant's connection sends, such as contact, order or ticket data. |
| Amazon S3 or Cloudflare R2 | Conditional; only when media storage is configured | Storing images a merchant uploads for social posts. | Uploaded media files and their metadata. |
| Freemius | Conditional; web billing when enabled | Embedded checkout, subscription billing, receipts, and invoices for WooCommerce and Custom API stores. | Billing contact, license, payment, and subscription identifiers; payment details are handled by Freemius checkout. |
| Stripe | Legacy billing only; previously connected accounts | Existing legacy subscriptions and their lifecycle events. | Billing contact, customer and subscription identifiers; card data is handled by Stripe, not Zubby AI. |
| Sentry | Conditional; only when a DSN is configured | Error and performance monitoring. | Diagnostics and request metadata subject to application-side filtering. |
Configuration-specific review
Need the providers used for your tenant?
Ask for a configuration-specific list before onboarding regulated or residency-sensitive data.