Skip to main content

Sub-processors (draft list)

Updated October 10, 2026

Draft — pending legal review; not yet in effect

This document is a working draft prepared for counsel. It may change before launch and is not yet in effect.

Draft for legal review — not in effect.

This list is derived from the adapters that exist in the code (packages/providers, packages/config/providers/*.json, packages/social, packages/config/platforms/*.json, packages/billing, packages/commerce/src/registry.ts, packages/intelligence, packages/storage, packages/auth) and from docs/PROVIDER_CATALOG.md. A provider named in the catalog but with no adapter in the code is not listed. "Mode today" describes the staging environment (influencebot.ai, ADR-145), where AI providers and billing run in Mock and email sending is disabled.

[COUNSEL: decide which entries are sub-processors (process customer personal data on our behalf) and which are third parties the customer directs (social networks, commerce tools, the customer's own AI keys); add each vendor's legal entity, location and transfer mechanism.]

1. Infrastructure

Vendor Purpose Data Status / mode today
Google Cloud (Cloud SQL for MySQL, Compute Engine) Database and application hosting All workspace and account data Live. [Founder: confirm regions]
Google Cloud Storage Media and document storage Uploaded and generated assets Adapter exists; staging uses local disk until a bucket is set up (launch checklist 1.5)
Redis (self-hosted on the same VM) Queues, rate limits, caches Job payloads, counters Self-hosted; not a third party
FFmpeg (self-hosted) Video rendering Media Self-hosted; no media leaves our infrastructure

2. AI providers

Live use of any provider is blocked by the router until its commercial terms are reviewed and recorded in the registry.

Vendor Used for Terms reviewed Modes supported Mode today
Google — Gemini API Text, structured output Yes (commercial use approved 2026-09-29) Mock, Sandbox, Live Mock on staging; Live approved in the dev preview
Google — Veo (Gemini API) Video generation Yes (2026-09-29); outputs carry an invisible watermark Mock, Live Mock on staging
OpenAI Text, embeddings; customer keys (BYOK) No — Live blocked Mock, Sandbox, Live Mock
Anthropic Text No — Live blocked Mock, Sandbox, Live Mock
fal.ai Image and video models No — Live blocked Mock, Live Mock
ElevenLabs Voice, audio and transcription; voice cloning disabled until consent gate No — Live blocked; zero-retention mode not used by default Mock, Live Mock
HeyGen Avatar video No — Live blocked Mock, Live Mock

Data sent: prompts, workspace content needed for the task (brand knowledge excerpts, scripts, product images, persona reference images, voice settings). Outputs are copied into workspace storage; vendor URLs are not exposed. [COUNSEL: each vendor's data-retention and training terms].

Customer keys (BYOK): when a platform operator enables BYOK for a workspace, calls run on the customer's own provider account (OpenAI today, text only). The provider is then the customer's processor, not ours. [COUNSEL: confirm].

3. Payments

Vendor Purpose Data Mode today
Stripe (Billing, Checkout, Customer Portal, Tax) Subscriptions, credit packs, seats, service payments Billing email, customer id, payment method (held by Stripe), tax details Mock on staging ("Mock billing"); test mode in the dev preview; Live needs the founder's Stripe account (launch checklist 5.3)

4. Social networks and publishing

Customer-directed: the customer connects their own accounts. Content, captions and metrics flow to and from the network.

Network / service Status Modes Notes
Sandbox network (built-in) Available Mock Simulated; nothing is posted
YouTube / Shorts Beta Mock, Sandbox Needs Google app verification and quota
TikTok Beta Mock, Sandbox Unaudited API clients post privately only
Instagram (Meta) Beta Mock, Sandbox Needs Meta app review
LinkedIn Beta Mock, Sandbox Needs API access approval
Ayrshare (unified social API) Adapter in code — No contract signed; not enabled

5. Commerce, lists and payouts

All run in Mock only until a real adapter and credentials exist.

Vendor Status Mode
Shopify (read-only products and orders) Coming soon Mock
WooCommerce (read-only) Coming soon Mock
Stripe Payment Links Beta Mock
External checkout URL Available Live (a plain link; no data exchange)
Klaviyo, Mailchimp (lead list sync) Coming soon Mock
Twilio SMS Coming soon Mock
Stripe Connect Standard (payouts) Coming soon Mock

6. Intelligence data sources

Source Status
Mock listening, competitor and trend connectors Available (Mock, labelled)
YouTube Data API (search, channel, most popular), Meta Ad Library, approved Google Trends provider, news API Coming soon (no runnable mode)

7. Email

  • No email delivery provider is integrated. The code has only development transports and a "disabled" mode; staging runs disabled, so magic links, verification and invitation emails are not sent. A transactional email vendor will become a sub-processor when one is added (launch checklist 5.1). [COUNSEL: add when chosen].

8. Identity

  • Enterprise SSO connects to the customer's own identity provider (OIDC or SAML) — customer-directed.
  • Google and Microsoft OAuth sign-in are supported by the authentication backend when configured, but not offered on the sign-in page today.

9. Change notification

  • [COUNSEL: how customers are notified of new sub-processors and the objection period].

More in Legal