Legal
Subprocessors
Effective date: September 10, 2026. These pages describe the current CanWeChat service at canwechat.dev. They are not a substitute for legal advice. Contact hello@canwechat.dev for questions.
About this list
Current subprocessors
| Provider | Purpose | Typical data |
|---|---|---|
| Cloudflare, Inc. | Hosting, Workers, D1, Durable Objects, Queues, CDN, TLS, edge security | Service data, conversation content, account metadata as processed by the application |
| Dodo Payments | Checkout, subscriptions, customer portal, tax/payment processing | Billing identifiers, email, subscription status; card data handled by Dodo |
| Transactional email provider (configured for CanWeChat) | OTP login codes and transactional email | Account email, OTP content |
| Slack Technologies, LLC (optional) | Customer-selected reply destination | Message content and metadata Customer routes to Slack |
| Discord, Inc. (optional) | Customer-selected reply destination | Message content and metadata Customer routes to Discord |
| Telegram Messenger Inc. (optional) | Customer-selected reply destination | Message content and metadata Customer routes to Telegram |
Updates
We will update this page when subprocessors change. For advance notice requests, email hello@canwechat.dev.
Customer-controlled destinations
If you configure a webhook URL, that endpoint is operated by you (or your vendor), not by CanWeChat as a subprocessor. You are responsible for that receiver’s security and privacy practices.