BOTBENTO / POLICIES AND HELP

Service providers

Which services can handle information when you use BotBento. A listed integration is not a promise that it is enabled, available to everyone or approved by its provider.

Public website and correspondence

  • Hostinger: hosting and team email infrastructure; website technical requests and correspondence as needed to deliver those services.
  • Cloudflare: DNS, website protection and email routing; network and delivery information and forwarded correspondence.
  • Resend, or the configured SMTP email provider: mailing-list confirmations, updates and delivery/suppression records. Website newsletter open and click tracking are disabled.
  • Umami: optional self-hosted website analytics, loaded after your choice when configured. See Cookies and analytics.

App features and connections

  • WorkOS: account identity, sign-in and session-related information.
  • PowerSync: conversation and workspace synchronization where used.
  • OpenRouter, configured primary and fallback model providers, and Groq/OpenAI for supported voice features: prompts, selected conversation context, files, tool results or audio needed for the feature you use. The downstream provider depends on the chosen model, feature and fallback routing; translation can use a separately configured endpoint such as FreeLLMAPI.
  • Composio and a connected app’s provider: connection identity, authorization and tool requests/results for supported connections.
  • LiveKit: call signaling, audio/video transport and bot participation where enabled.
  • Expo and device push services such as Apple or Google: push tokens, notification titles/bodies and routing information where notifications are enabled. Notification previews may appear on your device’s lock screen according to its settings.
  • Sentry: error diagnostics and native crash/performance information when configured. BotBento’s reporting code removes selected sensitive fields; this does not mean every error is anonymous.

Services you choose

A connected Google, GitHub, calendar, email, storage or other account remains subject to that provider’s terms. A runtime, computer, model endpoint or API key you supply may send information to additional services you configure. Review those services before authorizing access. The app is not a blanket assurance that every provider has identical retention or model-training practices.

Payments and managed hosting

Stripe billing and managed-computer providers appear in development work. This page does not announce paid availability or authorize a charge. Before a live offer, the applicable seller, billing terms and relevant providers must be disclosed.

Locations, contracts and questions

Processing locations and contractual roles depend on the service, deployment and account arrangement; information may be handled outside your country. This is a feature-based transparency list, not an executed data-processing agreement or a certification of international-transfer safeguards. For the services relevant to your account, retention, transfer arrangements or business data-processing needs, contact us before sharing regulated information.

Questions about this page? Contact the team.