Sub-processors

Last updated: October 30, 2026

1. Current sub-processors

Sub-processorPurposeLocationBinding terms
Railway (infrastructure + Postgres)Application hosting, databaseUSDPA + SCCs where applicable
Whop PaymentsPayment processing (processor path), card vaultingUSPCI DSS Level 1 service provider
StripePayment processing (processor path), card vaultingUSPCI DSS Level 1 service provider
NMIPayment gateway for merchant-gateway connections, Customer VaultUSPCI DSS Level 1 service provider
ShopifyOrder mirroring / fulfillment for connected storesUS / CanadaShopify DPA
ResendTransactional email deliveryUSDPA
Zoho ZeptoMailTransactional email delivery (alternative)US / IndiaDPA
CloudflareDNS, DDoS protectionUSDPA
Meta Platforms (Conversions API, pixels)Ad tracking only where merchant connectsUSDPA / SCCs
TikTok (Events API, pixels)Ad tracking only where merchant connectsUSDPA / SCCs
Google (Ads / Analytics, AI features)Ad tracking and AI store generation where usedUSDPA / SCCs
OpenAIAI store generation where usedUSDPA
AnthropicAI store generation where usedUSDPA
NamecheapDomain registration for merchant domainsUSDPA

Marketing pixels and tracking connections are sub-processors only for the merchants that enable them. Card networks and issuing banks are not sub-processors (they are controllers or independent processors of transaction data under network rules).

2. Changes and objections

We give 30 days' advance notice of new sub-processors by email to the account owner. A merchant may object within that window; unresolved objections permit termination of the affected configuration (or the Service) without penalty, as set out in the Data Processing Addendum.