Sub-processors
Last updated: October 30, 2026
1. Current sub-processors
| Sub-processor | Purpose | Location | Binding terms |
|---|---|---|---|
| Railway (infrastructure + Postgres) | Application hosting, database | US | DPA + SCCs where applicable |
| Whop Payments | Payment processing (processor path), card vaulting | US | PCI DSS Level 1 service provider |
| Stripe | Payment processing (processor path), card vaulting | US | PCI DSS Level 1 service provider |
| NMI | Payment gateway for merchant-gateway connections, Customer Vault | US | PCI DSS Level 1 service provider |
| Shopify | Order mirroring / fulfillment for connected stores | US / Canada | Shopify DPA |
| Resend | Transactional email delivery | US | DPA |
| Zoho ZeptoMail | Transactional email delivery (alternative) | US / India | DPA |
| Cloudflare | DNS, DDoS protection | US | DPA |
| Meta Platforms (Conversions API, pixels) | Ad tracking only where merchant connects | US | DPA / SCCs |
| TikTok (Events API, pixels) | Ad tracking only where merchant connects | US | DPA / SCCs |
| Google (Ads / Analytics, AI features) | Ad tracking and AI store generation where used | US | DPA / SCCs |
| OpenAI | AI store generation where used | US | DPA |
| Anthropic | AI store generation where used | US | DPA |
| Namecheap | Domain registration for merchant domains | US | DPA |
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.