Last updated: June 2026
Keply uses the third-party providers below to help deliver the Service. Each is engaged under data-protection terms and processes personal data only to provide its function. This list is part of our Data Processing Addendum; we update it when subprocessors change and notify customers of material changes.
| Provider | Purpose | Data | Region |
|---|---|---|---|
| Supabase | Database, authentication, storage, edge functions | All application & customer data | Configured region |
| Cloudflare | Frontend hosting, CDN, TLS, WAF | App delivery; request metadata | Global edge |
| Anthropic | AI model (Claude) for scoring & drafting — no training on your data | Account/CS context sent as prompts | United States |
| Merge.dev | Unified API for CRM/ticketing integrations | CRM accounts, contacts, tickets | United States |
| Stripe | Billing & payments | Billing contact, payment metadata | United States / Global |
| Gmail send, Calendar, Docs/Slides (when connected) | Email, calendar, contacts | Global | |
| Microsoft | Outlook/365 send & calendar (when connected) | Email, calendar | Global |
| Inngest | Background jobs & scheduled syncs | Job payloads (may reference records) | United States |
These process data only for customers who connect the corresponding source.
| Provider | Purpose | Data | Region |
|---|---|---|---|
| Pendo | Product-usage signals (only if you connect it) | Usage events of your end-users | United States |
| Delighted | NPS/survey signals (only if you connect it) | Survey responses & identifiers | United States |
We will provide advance notice of a new or replacement subprocessor (e.g. by email or in-app). Customers may object on reasonable data-protection grounds as described in the DPA. To receive change notices, contact [email protected].