01.Current Subprocessors
TODO before launch
Every row below is a placeholder. Replace with the actual vendors, links, and regions — and keep this page current — before launch. Material changes should be notified to customers per the DPA.
| Vendor | Purpose | Data processed | Privacy policy | Region |
|---|---|---|---|---|
| [Cloud infrastructure provider] EXAMPLE — replace | Hosting & compute | All service data | Privacy policy | [Region] |
| [Database / storage provider] EXAMPLE — replace | Managed data storage & backups | Customer content, account data | Privacy policy | [Region] |
| [Payment processor] EXAMPLE — replace | Subscription billing (hosted checkout) | Billing contact, payment status | Privacy policy | [Region] |
| [AI model provider(s)] EXAMPLE — replace | Content generation & analysis | Connected business data submitted for processing | Privacy policy | [Region] |
| [Call tracking provider] EXAMPLE — replace | Call tracking & lead scoring | Caller phone numbers, call metadata/recordings where enabled | Privacy policy | [Region] |
| [Email provider] EXAMPLE — replace | Transactional email & reports | Names, email addresses | Privacy policy | [Region] |
| [Analytics provider] EXAMPLE — replace | Product & website analytics | Usage data | Privacy policy | [Region] |
02.Change Notifications
We update this page when we add or replace a subprocessor. Customers with a signed DPA may subscribe to change notifications by emailing legal@redpalm.ai, and may object on reasonable data-protection grounds as described in the DPA.
03.Vendor Due Diligence
Before engaging a subprocessor we review its security posture, privacy terms, and data handling. Subprocessors are bound by written agreements imposing data-protection obligations no less protective than those in our DPA.