Draft — pending legal review. This page is a complete first draft written to match what VeloBot actually does, with a few placeholders (marked in brackets) that need your company's real details. Have a lawyer review it before relying on it.
Sub-processors
Last updated [DATE]
These are the third-party services VeloBot uses to operate the platform, each processing data only as needed to provide their part of the service and bound by their own data-processing agreements. We'll update this list before adding a new sub-processor that would materially change how your data is handled.
| Sub-processor | Purpose | Location |
|---|---|---|
| OpenAI | Generates chat responses; powers the optional intent/sentiment/entity extraction feature. | United States |
| Supabase | Primary database, authentication, file/attachment storage, and realtime messaging between the widget and agent inbox. | United States |
| Razorpay | Billing and payment processing. Card and payment details are handled directly by Razorpay and never touch VeloBot's servers. | India |
| Resend | Delivers transactional email (team invites, unassigned-conversation and offline-message notifications). | United States |
| Upstash | Rate limiting for the chat widget and the Developer API. | United States / global edge |
| Sentry | Error monitoring for the dashboard, inbox, and chat API — active only once an account admin configures it. | United States |
| PostHog | Product analytics (e.g. signup and checkout funnel) — active only once an account admin configures it. | United States / EU |
Questions about a specific sub-processor: [SUPPORT EMAIL].