DRAFT. This list is under review and is not final.
Subprocessors
Last changed:
Milly Software uses the service providers below to run its apps and services. For each one, this page lists what it does for us, whether shopper data reaches it, and where it processes data. Our Privacy Policy explains what we collect and why.
Our subprocessors
These companies process data on our behalf to run Milly Software's apps and services.
| Vendor | Purpose | Shopper data | Location |
|---|---|---|---|
| Vercel | Hosts the Milly Chat service, the merchant dashboard and this website, and keeps their request logs. | Yes: chat requests, and request logs that can include what a shopper searched for (email addresses and phone numbers are masked). | To be confirmed |
| Supabase | Our Postgres database: store settings, product catalogues, conversations and analytics. | Yes: conversations, widget interactions and the order line items we keep. | United States (AWS us-east-1) |
| Anthropic | Writes the chat replies, and helps us review conversation quality. | Yes: shopper messages and the conversation around them. | To be confirmed |
| OpenAI | Search embeddings, follow-up question suggestions, tagging the intent of shopper questions, and a fallback for chat replies. | Yes: shopper questions and messages. | To be confirmed |
| Cloudflare | DNS, the network that delivers the chat widget, and R2 storage for logos and the private archive of expired conversations. | Yes: archived conversations, and the network's request logs. | To be confirmed |
| Sentry | Error reports from the Milly Chat service. | Possibly: the context of an error. Our own logs mask email addresses and phone numbers. | To be confirmed |
| Firebase Authentication (merchant sign-in), Google Workspace mail (staff invitations and billing email), Firestore (settings and records for our checkout and compliance apps), and Google Analytics on millysoftware.com. | Merchant staff accounts, yes. Shoppers only when they visit millysoftware.com itself. | To be confirmed | |
| Stripe | Billing for merchants who pay us through Stripe. | No. | To be confirmed |
| Shopify | The platform our apps run on: app installation and sign-in (OAuth), and Shopify Billing. | Yes: Shopify sends us the store's order webhooks. | To be confirmed |
| Milly Software (our own server) | Background jobs: catalogue sync, intent tagging, the retention purge and analytics rollups. | Yes: it reads stored conversations, and sends shopper questions to OpenAI for intent tagging. | To be confirmed |
Integrations a merchant turns on
Milly Chat sends data to these services only when a merchant turns the integration on for their own store, using the merchant's own account with that service.
| Vendor | Purpose | Shopper data | Location |
|---|---|---|---|
| Klaviyo | Email marketing: receives leads captured in chat. | Yes: the lead and its chat context. | Set by the merchant's account |
| Maestra | Marketing platform: receives leads and chat activity. | Yes: the lead, its chat context and Maestra's own device ID. | Set by the merchant's account |
| Zendesk | Help desk: receives leads and chat hand-offs. | Yes: the lead and its chat context. | Set by the merchant's account |
| Gorgias | Help desk: receives leads and chat hand-offs. | Yes: the lead and its chat context. | Set by the merchant's account |
| HubSpot | CRM: receives leads captured in chat. | Yes: the lead and its chat context. | Set by the merchant's account |
| Custom webhooks | Sends captured leads to an address the merchant chooses. | Yes: the lead and its chat context. | Set by the merchant's account |
| AI clients connected over MCP | Lets the merchant's own AI tools read their store's Milly Chat data. | Yes: whatever the merchant's AI tool asks for, conversations included. | Set by the merchant's account |
Notice of changes
We give at least 30 days' notice before we add or replace a subprocessor. Leave your email address to receive that notice.
See also our Privacy Policy.