Sub-processors
This page lists the companies that process personal data on SolveBotic's behalf (“sub-processors”), what each one receives, and where it is processed. It is the current list referred to in our Privacy Policy.
It covers both kinds of data we handle: merchant account data, which we control, and the end-customer data we process for merchants through the chat widget. See Section 1 of the Privacy Policy for the difference.
Current sub-processors
Anthropic, PBC
- What it does
- AI processing. Reads each message sent through the chat widget, works out what the customer needs, and drafts the reply.
- Data it receives
- The end-customer's message and the earlier messages in the same conversation (whatever the customer typed, plus our earlier replies, which can mention an order's status or tracking), the merchant's brand name, and the merchant's FAQ / knowledge-base text. Order records are not sent from our database directly.
- Where
- Stored in the United States. Under Anthropic's default routing, the model may run in data centers outside the United States.
- Its own sub-processors
- anthropic.com/subprocessors
Supabase
- What it does
- Database and merchant sign-in.
- Data it receives
- Everything SolveBotic stores: merchant accounts and settings, including the store credentials a merchant connects (Shopify access tokens, and WooCommerce consumer keys, consumer secrets and webhook secrets — all stored encrypted, and never shown to other accounts), synced order details (order number, customer name and email, shipping city, state, postal code and country, totals, payment and fulfillment status, tracking), chat conversations, return requests, and error logs (with email addresses and card numbers removed).
- Where
- United States (Amazon Web Services, us-east-1, Northern Virginia).
- Its own sub-processors
- supabase.com/legal/customer-resources/subprocessor-list
Vercel Inc.
- What it does
- Hosting. Runs the SolveBotic app and serves the chat widget.
- Data it receives
- Every request to the app and the widget passes through Vercel, including chat messages on their way to us. Our server logs record IDs, store domains, and yes/no flags, not message text.
- Where
- Our application servers run in the United States (Washington, D.C. area). Requests first reach Vercel's global edge network at the location nearest the visitor.
- Its own sub-processors
- security.vercel.com
Resend (Plus Five Five, Inc.)
- What it does
- Transactional email.
- Data it receives
- Sign-in emails to merchants (the merchant's own email address and a one-time sign-in link), escalation emails to the merchant (the end-customer's email address, a summary of the conversation, and the order number), return-request emails to the merchant (email address, order number, return category, and reason), alerts to SolveBotic about Shopify customer data requests (the end-customer's email address and Shopify order IDs), and alerts to SolveBotic about service errors.
- Where
- United States (Amazon Web Services, us-east-1).
- Its own sub-processors
- resend.com/legal/subprocessors
Stripe, LLC
- What it does
- Merchant billing.
- Data it receives
- Merchant billing details only: name, email address, payment card (entered directly with Stripe), and subscription. No end-customer data.
- Where
- United States, and Stripe's affiliates and service providers in other countries.
- Its own sub-processors
- stripe.com/legal/service-providers
Zoho Corporation
- What it does
- SolveBotic's business email.
- Data it receives
- Alerts about Shopify privacy requests (which include the end-customer's email address and Shopify order IDs), and messages sent to our support, privacy, billing, and general addresses.
- Where
- United States (Zoho's US data center).
- Its own sub-processors
- zoho.com/privacy/sub-processors.html
Not sub-processors
Shopify and WooCommerce. These are the merchant's own store platforms. SolveBotic reads order data from them using credentials the merchant provides; they are where the data comes from, not companies processing it for us.
Slack. A merchant can choose to send escalation and return alerts to their own Slack workspace. That destination, and the relationship with Slack, belong to the merchant.
How we tell you about changes
Notice. At least thirty (30) days before a new or replacement sub-processor starts receiving personal data, we will add a dated entry to the changelog below and email the account owner of every active or trialing merchant account.
Objections. Within fifteen (15) days of that notice, a merchant may object on reasonable data-protection grounds by emailing privacy@solvebotic.com. We will discuss the concern in good faith and work toward a resolution. If it can't be resolved, you may close your account.
Urgent replacements. If we have to replace a sub-processor quickly — for a security issue, a prolonged outage, or because the provider stops offering its service — we may do so with shorter notice. We will tell merchants as soon as we can, and the same right to object applies.
Scope. This list covers the companies SolveBotic works with directly. Each of them uses its own sub-processors, listed at the links above.
Changelog
- October 29, 2026 — Updated the Resend entry. Sign-in emails to merchants now go through Resend, so it receives the merchant's own email address. Alerts about Shopify requests to erase data no longer include the end-customer's details. No new sub-processor.
- October 12, 2026 — Updated the Supabase entry. WooCommerce consumer keys and webhook secrets are now stored encrypted, so every store credential a merchant connects is encrypted where we store it. No change to who processes data or what they receive.
- October 8, 2026 — Corrected the Supabase entry. It said store API credentials are encrypted; that is true for Shopify access tokens and WooCommerce consumer secrets, but WooCommerce consumer keys and webhook secrets are stored unencrypted. No change to who processes data or what they receive.
- October 6, 2026 — First version of this page. Zoho Corporation is listed for the first time: it was already in use for SolveBotic's business email but was missing from earlier versions of our Privacy Policy.
Contact
Questions about this list: privacy@solvebotic.com.