What this list means
A subprocessor is a service provider that may process personal data or customer content for Cuebloom. Not every provider receives data from every customer. AI and research providers are used only when the selected feature, model, routing, or connected service calls for them.
Cuebloom’s policy is to send a provider only the content and configuration reasonably needed to perform the requested function. Our commitment not to use customer work for generalized Cuebloom model training is described in the Privacy Policy.
Current providers
| Provider | Purpose | Data involved |
|---|---|---|
| Vercel | Application hosting and content delivery | Requests, technical data, and content served through the application |
| Supabase | Authentication, database, and media storage | Account, workspace, project, and stored media data |
| Stripe | Payments, subscriptions, invoices, and fraud prevention | Billing contact, transaction, and payment data |
| Resend | Transactional and product email delivery | Email address and message-delivery metadata |
| OpenAI | Language, image, transcription, and agent features when selected | Prompts, instructions, and source media required for the selected feature |
| Anthropic | Language and agent features when selected | Prompts, instructions, and relevant workspace context |
| fal.ai | Image, video, and media processing when selected | Prompts, generation settings, references, and source media |
| Replicate | Model inference when selected | Prompts, generation settings, references, and source media |
| WaveSpeedAI | Image and video generation when selected | Prompts, generation settings, references, and source media |
| AtlasCloud | Model inference and agent services when selected | Prompts, generation settings, relevant context, references, and source media |
| Telegram | Optional remote agent controls when connected by a user | Telegram identifiers, commands, and approval messages |
| ScrapeCreators | Optional public advertising research features | Research queries and identifiers for public ad sources |
Provider choice and enterprise terms
Model availability and routing can change as providers update services. Where Cuebloom exposes a provider or model selection, choosing it directs us to send the relevant request to that provider. Some agent and workflow features may choose a provider based on capability, availability, policy, or configured routing.
Customers that require an allowlist, provider exclusion, zero-retention commitment, data residency, additional audit rights, or advance notice should document that requirement in a signed enterprise agreement. Public website language alone does not create a customer-specific deployment commitment.
Changes to the list
We update this page when our provider set materially changes. If a signed agreement requires advance notice or an objection process, the notice terms in that agreement control. Questions about a provider or data flow can be sent to rakeen@cuebloom.ai.
Questions or requests
We would rather answer a direct question than hide an important detail in fine print. Email rakeen@cuebloom.ai with the name and email associated with your workspace.