Privacy Policy

CanWeChat (canwechat.dev) operates this Service. Privacy and data requests: hello@canwechat.dev. Security issues: security@canwechat.dev.

Roles: For account, billing, and service analytics data, CanWeChat acts as an independent controller (or “business”). For visitor conversation content processed on behalf of a customer workspace, CanWeChat acts as a processor / service provider under the customer’s instructions — see the DPA.

Account and workspace

• Email address, display name (optional), avatar URL (optional).
• Session/login data for Better Auth email OTP.
• Workspace settings, teammate invites/roles, site public key, allowed domains.

Visitor and conversation data (customer content)

• Message bodies and conversation metadata (timestamps, status, assignment, tags).
• Optional visitor identity traits you pass (name, email, user id, custom traits).
• Page URL, referrer, coarse browser/OS hints, Cloudflare country code when available.
• Attachments you or visitors upload (images/PDFs within product limits).

Billing

• Customer and subscription identifiers from Dodo Payments; we do not store full card numbers.

Integrations and operations

• Integration metadata (channel ids, health). Secrets are encrypted at rest and not returned after save.
• Webhook delivery logs (status, bounded response snippets).
• Abuse/rate-limit signals and request diagnostics needed to operate the Service.

Not stored (by design)

• Raw visitor IP addresses are not persisted as a product feature.
• Raw visitor tokens are hashed; we do not store recoverable raw tokens.

• You and your teammates when creating accounts and configuring the workspace.
• Your websites running the CanWeChat widget.
• Visitors who send messages through your widget.
• Providers you enable (Slack, Discord, Telegram) and Dodo Payments.

• Provide chat, route replies, and operate the dashboard.
• Authenticate users and secure the Service (rate limits, domain lock, abuse prevention).
• Bill subscriptions and prevent entitlement fraud.
• Provide support and improve reliability.
• Comply with law and enforce Terms.

Where those laws apply, we rely on:

• Contract — to provide the Service you request.
• Legitimate interests — security, abuse prevention, product reliability (balanced against your rights).
• Consent — where your configuration or local law requires it (e.g., certain marketing uses you enable on your own site).
• Legal obligation — where we must retain or disclose information.

Customers using the widget on their sites are responsible for their own legal bases and notices to visitors.

We share data with:

• Subprocessors needed to host and operate the Service (e.g., Cloudflare, Dodo Payments, email delivery).
• Destinations you configure: Slack, Discord, Telegram, or your webhook URL.
• Authorities when required by law, or to protect rights, safety, and security.

We do not sell personal information as “sale” is commonly understood for advertising. We do not use visitor chat content to train third-party foundation models.

• Active workspace conversations: until you delete them or close the workspace.
• Deleted conversation records: removed from primary stores promptly; backups/logs may lag for a limited period.
• Billing records: retained as required for tax and accounting.
• Webhook delivery history: short operational window for debugging.
• Security logs: retained only as long as needed for abuse investigation and reliability.

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority. California residents may have additional rights under the CCPA/CPRA, including non-discrimination for exercising rights.

Self-serve: export conversations (JSON/CSV) and delete conversation history from Settings → Data. For account or workspace deletion and other requests, email hello@canwechat.dev. We may verify your identity before fulfilling a request.

The Service runs primarily on Cloudflare’s global network. Data may be processed in regions where Cloudflare and other subprocessors operate. Where required, we rely on appropriate transfer mechanisms provided by those vendors (such as Standard Contractual Clauses).

The Service is not directed to children under 16, and we do not knowingly collect account data from children. If you believe a child created an account, contact us to delete it.

• Account session cookies on canwechat.dev are HTTP-only and used to keep you signed in.
• Visitor token uses first-party localStorage on your website so the widget can resume a visitor session.
• We do not currently load third-party advertising cookies on canwechat.dev marketing pages.

Customers should disclose the widget in their own privacy/cookie notices where required.

We use TLS in transit, encrypt integration secrets at rest (AES-GCM), hash visitor tokens, scope data by workspace, sign outbound webhooks (HMAC-SHA256), and apply rate limits. Details: Security. No security program is perfect; report issues to security@canwechat.dev.

• Mention CanWeChat in your privacy notice if you collect chat or identity data.
• Obtain consent where your laws require it before collecting personal data via chat.
• Avoid sending sensitive categories of data unless you have a lawful basis and safeguards.
• Lock allowed domains before production traffic.
• Verify webhook signatures on your receivers.

We may update this Policy by posting a new version with a revised effective date. Material changes will be communicated when practical via email or in-product notice.