EllichEllich legal
Subprocessor List
Providers Ellich may use to operate the core service or an optional feature. Optional providers process data only when the corresponding integration or communication channel is enabled.
Effective and last updated: July 25, 2026
Current providers
| Provider | Purpose | Data categories | Applies when |
|---|---|---|---|
| Vercel | Application hosting, edge delivery, runtime logs, and security controls | Account, request, tenant-routing, device, and diagnostic data | Core service |
| Neon | Managed PostgreSQL database infrastructure and recovery | Tenant application records stored by Ellich | Core service |
| Stripe | Subscription billing, connected merchant payments, payouts, disputes, and risk checks | Business, representative, transaction, payout, and payment-provider identifiers | When billing or Stripe payments are enabled |
| Amazon Web Services (SES) | Transactional and tenant-configured email delivery | Sender, recipient, message, delivery, bounce, and complaint metadata | When Ellich Managed Email is enabled |
| Google account authentication and enabled Google integrations | Account identifiers, email, profile, authentication, and integration data | When Google login or an integration is enabled | |
| Twilio | SMS and communications delivery | Phone numbers, message content, consent, and delivery metadata | When SMS features are enabled |
Changes and questions
Ellich may replace or add a provider as the service changes. When the Data Processing Addendum or applicable law requires notice of a material new subprocessor, Ellich will provide notice through an account, service, or email channel before the provider begins the relevant processing when reasonably practicable.
Questions or legally required objections may be sent to privacy@ellich.com. An objection should identify the Customer, the provider, and the specific data-protection concern.