Stravax Group LLC uses a small set of infrastructure subprocessors to operate Stravax Engage. This page lists each one, what it does for the service, and whether it sits in the path of customer personal data. The processing commitments around this list are in the Merchant Terms and DPA, section 5.
| Subprocessor | What it does for the service | Customer personal data |
|---|---|---|
| Cloudflare | Hosting, database, object storage, queues, security and transactional email delivery | Yes: storage and processing infrastructure for all platform data |
| Meta Platforms (WhatsApp Business Platform) | Delivers WhatsApp messages; recipient phone numbers and message content pass through delivery | Yes: delivery path |
| Stripe | Subscription billing and prepaid wallet top-ups | Merchant billing data only, no customer message data |
| Anthropic | The optional AI conversation qualifier; processes WhatsApp conversation text only for workspaces that enable it | Only when you enable the AI qualifier |
| Google Ads, Meta Ads, TikTok Ads | Receive conversion events for workspaces that enable Ad Sync | Only when you enable Ad Sync, limited to conversion-event data |
| Shopify | Source of checkout and order webhooks for merchants who connect a store | Source of data, not a recipient |
For the Shopify integration specifically, only Cloudflare (storage) and Meta/WhatsApp (delivery) are in the path of the customer name and phone number fields. The Privacy Policy, section 6, carries the same table scoped to that data path.
We give merchants notice of any new subprocessor that would process customer names or phone numbers before it takes effect, per the DPA, section 5.
Questions about this list: privacy@stravax.ai.