Subprocessors
Third parties that may process customer data to help us deliver EzyConn.
⌘K
We update this list before engaging a new subprocessor that processes customer data. Questions? Email sales@ezyconn.com.
Infrastructure
| Provider | Purpose |
|---|---|
| Amazon Web Services (AWS) | Application hosting, compute, and managed database |
| Object storage | Uploaded documents, attachments, and training files |
| Redis | Caching, queues, rate limiting, and real-time delivery |
| Neo4j | Knowledge-graph storage |
| Sentry | Error monitoring and diagnostics |
AI / LLM providers
Process conversation content to generate AI responses. Customers may bring their own provider keys (BYOK).
| Provider | Purpose |
|---|---|
| OpenAI | LLM inference and embeddings |
| Anthropic | LLM inference (Claude) |
| Google (Gemini) | LLM inference |
Communication & channels
Engaged only when the corresponding channel is enabled by the customer.
| Provider | Purpose |
|---|---|
| Twilio | Voice, SMS, and WhatsApp messaging |
| Slack | Slack channel integration |
| Microsoft (Teams / Bot Framework) | Microsoft Teams channel integration |
| Telegram | Telegram bot channel |
| Zoom | Meeting scheduling for bookings |
| Resend | Transactional email |
Payments
Billing only. EzyConn does not store full card numbers.
| Provider | Purpose |
|---|---|
| Razorpay | Subscription billing and payments |
| Stripe | Subscription billing and payments |
Mobile
| Provider | Purpose |
|---|---|
| Google Firebase | Mobile app distribution and notifications |