MarketsEngine

Subprocessors and dependencies

This is Schedule C of the Terms and Conditions (version 1.1).

The subprocessors and dependencies below reflect the architecture MarketsEngine currently uses. MarketsEngine may maintain the authoritative current list at marketsengine.app/legal/subprocessors and update it under the DPA and these Terms.

PurposeProviderData categories / notes
Identity and sign-inWorkOSUser name, email, authentication metadata.
LinkedIn and mailbox integrationUnipileProspect profile data, message content, connected-mailbox content and metadata, account identifiers.
Social publishing / inboxZernioPost content, inbound message content, account identifiers.
AI generation and critiqueAnthropic; OpenAIPrompt content, Prospect research, message drafts, and Output. Available no-training / enterprise data-protection controls are applied.
Contact enrichment (website and company lookup)MarketsEngine (first-party service); Google (Gemini API)Company name, website, and description. Contact details are read from the company's public website by MarketsEngine; Google is used only to identify a company's website where one is not known. No message content is sent.
Brand-kit extraction and AI image generationPLEUTH brand and AI gateway (Supabase Edge Functions)Company website URL, brand information, prompts, and generated images.
Application hostingContabo (virtual private server)Application runtime and Workspace data in transit.
DatabaseSupabase (PostgreSQL)Workspace data.
Network, DNS, and web protectionCloudflareRequest metadata (such as IP address) for traffic to the Service.
Media storageCloudflare R2Images, video, and generated media.
Background jobsInngestJob metadata, identifiers, and execution state.
BillingStripeBilling contact and payment metadata; payment-card data is handled by Stripe and not stored directly by MarketsEngine.
Service email (sign-in codes, account notices)ResendRecipient email address and the content of service emails.
Contact de-duplicationGojiberry (selected Workspaces only)Prospect LinkedIn URLs or comparable identifiers.
Voice calling and speech processing, if enabledLiveKit (including speech-to-text, language-model, and text-to-speech providers accessed through LiveKit Inference); Twilio (telephony)Phone number, call audio, transcript, and related metadata.

Questions about our subprocessors can be sent to [email protected].