LiveCRM Subprocessors
These are the companies that process customer data on LiveCRM's behalf. We update this page, and notify customers who have subscribed to notifications, at least 30 days before a new subprocessor begins processing customer data.
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Hosting, database, storage, secrets, queueing | United States (us-east-1) |
| Cloudflare | TLS termination and network edge for the API | Global edge network |
| Anthropic | AI model inference for Console requests, when you have not connected your own key, and when your own key is missing or rejected and you allow fallback | United States |
| Resend | Sign-in links, account email, and demo-request forms submitted on our website | United States |
| Sign-in, when you choose to sign in with Google | United States | |
| Slack | Delivery of alerts and notifications, including operational alerts about your connection, and LiveCRM's own operator workspace, which receives administrator email addresses, company names, CRM record IDs, and CRM error text when a write fails | United States |
Salesforce, HubSpot, and data providers you connect with your own credentials are your own third-party services, used under your agreements with them, and are not LiveCRM subprocessors. Where you connect your own Slack workspace, the notifications LiveCRM sends to it are delivered under your agreement with Slack.