Subprocessors

Know where a request can go.

Transparency about the infrastructure, payment, communication, model, and research services that may help Cuebloom deliver a feature.

Last updated July 30, 2026

Feature-dependent

A service receives data only when the feature, model, or integration requires it.

Purpose-limited

We aim to send only the content and settings needed to perform the request.

Enterprise controls

Provider allowlists and contractual retention terms are available through scoped agreements.

What this list means

A subprocessor is a service provider that may process personal data or customer content for Cuebloom. Not every service receives data from every customer. AI and research services are used only when the selected feature, model, routing, or connected service calls for them.

Cuebloom’s policy is to send a service 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 service categories

ServicePurposeData involved
VercelApplication hosting and content deliveryRequests, technical data, and content served through the application
SupabaseAuthentication, database, and media storageAccount, workspace, project, and stored media data
StripePayments, subscriptions, invoices, and fraud preventionBilling contact, transaction, and payment data
ResendTransactional and product email deliveryEmail address and message-delivery metadata
AI model servicesLanguage, image, video, audio, transcription, and agent featuresPrompts, instructions, generation settings, relevant context, references, and source media required for the selected feature
TelegramOptional remote agent controls when connected by a userTelegram identifiers, commands, and approval messages
ScrapeCreatorsOptional public advertising research featuresResearch queries and identifiers for public ad sources

Processing choices and enterprise terms

Model availability and routing can change as services evolve. Where Cuebloom exposes a model selection, choosing it directs us to process the relevant request with that model family. Some agent and workflow features may choose an internal service based on capability, availability, policy, or configured routing.

Customers that require an allowlist, service 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 service categories materially change. If a signed agreement requires advance notice or an objection process, the notice terms in that agreement control. Questions about a service or data flow can be sent to admin@cuebloom.ai.

Questions or requests

We would rather answer a direct question than hide an important detail in fine print. Email admin@cuebloom.ai with the name and email associated with your workspace.