Subprocessors and connected services
This list identifies third parties that may process customer data for the hosted Umwise service. Optional channel and CRM providers process data only when a workspace administrator connects them. The exact deployment and enabled providers are confirmed during onboarding.
Core hosted service
DigitalOcean — cloud infrastructure and encrypted storage for the hosted application and database. Processing location depends on the selected deployment region.
Cloudflare — DNS, TLS edge delivery and network security. Cloudflare may process connection metadata at its global network edge.
OpenRouter — structured language-model routing when model assistance is enabled. Umwise requests providers that deny data collection and, by default, advertise zero data retention; OpenRouter may retain operational request metadata.
ElevenLabs — optional web and telephone voice agent, transcription and signed post-call delivery. Provider recording is disabled for the Umwise agent and provider conversation retention is configured for no more than seven days.
Zadarma — optional telephone carrier, virtual number, PBX, SIP routing and signed call-event metadata. Umwise does not request or download Zadarma call recordings.
Customer-enabled services
Meta Platforms / WhatsApp Business — inbound and outbound customer messaging for a connected business account.
Telegram — inbound and outbound messaging for a connected bot.
HubSpot and Kommo — CRM synchronization for connected accounts.
Twilio — optional organization/account OAuth status and telephone-number connectivity. OAuth client credentials remain in the protected Umwise server environment and are exchanged for short-lived access tokens that are not persisted; status checks retain only context, authorization booleans and aggregate number counts. When an existing Twilio number is imported into ElevenLabs, the separately supplied Account SID and Auth Token are transmitted to ElevenLabs once and are not stored by Umwise.
Resend — transactional workspace-invitation email when the deployment owner configures a verified sending domain. Without it, invitations remain available as one-time links for secure manual sharing.
Customer inventory provider — a workspace-selected HTTPS endpoint supplying availability and price facts under the validated Umwise inventory contract.
Customer booking and payment providers — workspace-selected systems that send signed reservation, checkout and payment lifecycle events under the Umwise adapter contract.
Model providers
The selected OpenRouter model determines an additional model provider. Administrators can choose the primary and fallback models, and the resulting provider list is documented for a production onboarding. Umwise sends only the current message and limited structured request memory needed for extraction.
Changes and questions
Material changes to subprocessors are reflected on this page. Contractual notice periods and objection rights are defined in the customer agreement or data-processing addendum. Contact [email protected] for the current deployment details or a data-processing addendum.