Subprocessors

These are the third-party services that process customer data on behalf of JCIL.AI. Every item lists what it does, what data it sees, and where the processing happens. We notify B2B customers 30 days before adding or removing a subprocessor that handles their data.

ServicePurposeData receivedRegionPolicy
OpenAILarge-language model inference, content moderation, chat, reasoning, document generation, code interpretation, native web search, and image generationUser messages, system prompts, attached files when passed to the modelUSView
SupabaseAuthentication, PostgreSQL database, file storageAll application data — profiles, conversations, messages, memories, API keys (hashed), billing transactions, uploaded filesUS (us-east-2)View
VercelApplication hosting, edge middleware, DNS, production deployment infrastructureAll request metadata (IP, user agent, path, timings); response bodies for cachingUS (primary iad1)View
StripePayment processing for credit purchases and subscriptionsName, email, payment method (card number never touches JCIL.AI servers)USView
ResendTransactional email delivery (welcome, receipts, digests, alerts)Email address, name, email contentUSView
UpstashRedis-backed rate limiting and ephemeral countersRate-limit buckets keyed by user ID or IP — counts only, no message contentUSView
E2BEphemeral sandbox execution for Playwright browser automation and Chromium-based PDF renderingDocuments and code snippets passed to the sandbox for the duration of a single requestUSView
Google CloudVideo generation and music generationUser prompts passed to generative modelsUSView
AtlasCloudSupplementary model inference for specific generation workloadsUser prompts passed through for generationUSView

Subscribe to subprocessor changes

B2B customers can request 30-day advance notice of any change to this list. Submit your company email through the compliance contact form with topic: subprocessor notifications.

Last updated: April 17, 2026.