Live Agent Pro Sub-Processors
Last Updated: November 6, 2026
What a "sub-processor" is
A sub-processor is a third party we engage to process personal information in order to operate the Service — for example, to host data, process payments, deliver messages, or monitor errors. We remain responsible to you for the services these vendors perform on our behalf.
Current sub-processors
| Sub-processor | Service provided | Categories of data processed | Primary location |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Core cloud infrastructure: application hosting and load balancing (EC2 / Application Load Balancer), databases (via our managed database stack), caching and queues (ElastiCache), file and media storage (S3, with access controls), outbound email (Amazon SES), DNS (Route 53), and secrets management (AWS Secrets Manager). A separate AWS region hosts our inbound-email receiving pipeline (SES receiving), where replies to managed email addresses land before being processed. | Account data; Agency and Host contact records (including names, contact details, dates of birth, CPF, PIX keys, and payout addresses); custom field values and notes; message content (WhatsApp and email, both directions, including inbound email from third parties); performance stats and monthly statements; uploaded documents and media; session and log data. | United States (primary region); a second US data location — a separate AWS region — hosts inbound-email receiving. |
| Stripe, Inc. | Payment processing and subscription billing for Agencies. | Agency billing name and address, payment card details (held by Stripe under PCI standards; we store only card brand and last four digits), transaction and subscription data. | United States. |
| Meta Platforms, Inc. | WhatsApp Business messaging via the WhatsApp Cloud API, sent using the Agency's own WhatsApp Business credentials. | Host and recipient phone numbers; full WhatsApp message content, both directions (outbound sends and inbound replies), including media attachments; delivery and read status. | United States (global platform). |
| TikTok (TikTok Pte. Ltd. / affiliated entities) | TikTok Open API integration, authorized per-Host via OAuth, used to sync each Host's platform stats. | TikTok OAuth tokens; profile data received from TikTok (display name, bio, avatar) and stats data (follower, following, likes, and video counts). | United States / Singapore (global platform). |
| Sentry (Functional Software, Inc.) | Application error and performance monitoring. | Diagnostic/error data, which may incidentally include request data such as IP address or other request details. | United States. |
| Expo (650 Industries, Inc.) and/or Google (Firebase Cloud Messaging) | Delivery of push notifications to the host mobile app. Notifications are routed through Expo's push service and/or Firebase Cloud Messaging depending on configuration. | Device push tokens, device platform (iOS/Android), and notification payloads (which may include message previews and alert content). | United States. |
Notes
- Agency-directed email providers are not our sub-processors. An Agency may configure its own outbound email provider (for example, Resend, Postmark, Mailgun, or its own SMTP server) using its own account and API key. Those providers are engaged by the Agency, act under the Agency's own agreement with them, and are the Agency's responsibility — they are not Pelton Solutions sub-processors. Email sent through our managed sending option is delivered by Amazon SES and covered by the AWS row above.
- Tools an Agency connects are not our sub-processors. An Agency may connect its own application or AI assistant to the Service using an API key or a connector authorization that we issue to it. That tool is chosen and engaged by the Agency, reads and, as the Service makes it available, creates, changes, or deletes data at the Agency's direction under the Agency's own agreement with its provider, and is the Agency's responsibility — it is not a Pelton Solutions sub-processor.
- Slack is used only for Pelton Solutions' internal operational notifications (for example, system alerts to our own staff). It does not routinely process Agency or Host personal data and is not engaged as a sub-processor of Customer data.
- No third-party advertising or cross-site tracking vendors are used in the application.
Changes to this list
We will keep this page current. Where the Data Processing Addendum applies, we will provide advance notice of new sub-processors as that addendum specifies, giving Agencies an opportunity to object.
Questions: hello@liveagentpro.com