Subprocessor list

Adsidian uses the following subprocessors to deliver the platform and Prism. We will update this page when the list changes; direct questions to [email protected].

Last updated: July 16, 2026

Infrastructure

Subprocessor	Purpose	Data	Location
Supabase	Database & authentication	All platform data, incl. CRM contacts and Prism events	United States
Cloudflare	Hosting, CDN, Prism edge network (Workers/KV)	Prism event traffic, cached identity hashes	Global edge (US-controlled)
Fly.io	API hosting	Data in transit through the API	United States
Stripe	Payments	Billing details	United States

AI providers

Subprocessor	Purpose	Data	Location
Anthropic	AI assistant & campaign strategy	Prompts, conversation context (may include CRM contact details surfaced by tools)	United States
OpenRouter	AI model routing (legacy agent path)	Prompts, campaign context	United States
Groq / OpenAI	Voice dictation transcription	Dictation audio (not stored)	United States
Google (ImageFX), Runway, Higgsfield, fal.ai	Creative generation	Creative prompts and generated assets (no end-user personal data)	United States

Connected platforms (at the customer's direction)

These receive data only when a customer connects them, acting on the customer's instructions:

Platform	Purpose	Data
Meta	Campaign management, Conversions API delivery	Campaign data; consented conversion events with hashed identifiers
Google	Google Ads management and conversion delivery	Campaign data; consented conversions (gclid, hashed email/phone)
LinkedIn	Campaign management	Campaign data
GoHighLevel	CRM sync	Contact records (bidirectional, customer's own CRM)
Resend	Lead email notifications	Lead contact details, to the customer's configured inbox

International transfers

Data is processed in the United States. For personal data originating in the EEA, UK, or Switzerland, we rely on each subprocessor's Standard Contractual Clauses and/or EU–US Data Privacy Framework participation. See the Data Processing Agreement.