Transparency list
Subprocessors and Service Providers
1. Scope of this list
The providers below may be used depending on Customer’s plan, integrations, channels and enabled features. Not every provider is used for every Customer. Providers marked “Web/CRM” primarily process visitor, lead or account-relationship data for which Pushouse acts as controller; “Service” providers may process Customer Personal Data as subprocessors.
The actual production region depends on Customer and provider account configuration. This list is not a representation of an unverified data location or certification.
2. Provider list
| Provider / category | Purpose | Scope |
|---|---|---|
| Amazon Web Services (AWS) | Cloud infrastructure, object storage, files, queues and, where enabled, managed database services | Service; account and production-configuration dependent |
| MongoDB Atlas and infrastructure-hosted PostgreSQL/Redis deployments | Application database, job queue and cache | Service; actual host and region are verified per account |
| Cloudflare | DNS, proxy/CDN, network security, performance and caching | Service / web |
| Meta Platforms / WhatsApp | WhatsApp Business messaging channel and platform functions | Customer-enabled channel |
| Gupshup | WhatsApp templates, transmission and message status services | Only for accounts using this channel provider |
| Connexease | WhatsApp message delivery and channel integration | Only for accounts using this channel provider |
| 360dialog | WhatsApp Business channel integration and account management | Only for existing/eligible accounts |
| OpenAI | AI-commerce, content, product/review analysis, support, voice and transcription features | Only where the relevant AI feature is enabled |
| fal.ai | Customer-initiated AI image and video generation | Only where the relevant generation feature is enabled |
| Bunny.net / Bunny Stream | Media upload, video processing, delivery, CDN and statistics | Only where the relevant media/video feature is enabled |
| Stripe | Subscription payment and billing infrastructure | Account/billing; card data remains with the payment provider |
| PayTR | Payment and subscription infrastructure for existing/eligible accounts | Account/billing; only in the relevant payment flow |
| Vercel | Landing hosting, performance and analytics | Website visitor data |
| Google services | Gmail contact infrastructure, tag management, fonts and user-opened YouTube content | Web/CRM; feature- and consent-dependent |
| Brevo | Newsletter, permission-based marketing and unsubscribe | Web/CRM; subscriber data only |
| Odoo | Sales lead and customer relationship management | Web/CRM |
| Cal.com | Meeting scheduling | Web/CRM; user initiated |
| Commerce integrations (Shopify, ikas, Ticimax and other Customer-connected platforms) | Store, product, order and customer integration | Customer-enabled integration |
3. Changes and objections
If Pushouse plans to add or replace a subprocessor that will access Customer Personal Data, the DPA’s advance-notice and objection process applies to each such addition or replacement.
You may request the providers and data-region details applicable to your account at [email protected]. Planned subprocessor additions and replacements are announced through the notice process in the Data Processing Addendum.
4. Contact
Questions about this list or subprocessor notices may be sent to [email protected].
This page covers both subprocessor transparency and website service providers; each provider’s legal role depends on the actual data flow.