Sub-processors

Every third party that processes data on our behalf. We update this page before adding a new sub-processor.

Services that may touch customer data

Sub-processor	Purpose	Data touched	Terms
Anthropic	LLM API for the Recon research agent	Research queries + tool outputs, in transit only — Zero Data Retention: nothing retained, no training on inputs	SOC 2 Type II · ZDR agreement
Supabase	Managed Postgres + authentication (platform identity, tenant data, and the vendor-run OFAC reference plane)	Account emails, tenant records, audit logs; the reference plane holds public Treasury data only	SOC 2 Type II
Vercel	Web application hosting + TLS termination	Transient request/response processing	SOC 2 Type II
Railway	Container hosting for the Recon service	Transient request/response processing — stateless, read-only filesystem, no customer text at rest	SOC 2 Type II
Stripe	Subscription billing and payments	Billing contact, payment method, subscription state — card data never touches our systems	PCI DSS Level 1 · SOC 2

Public reference-data sources (no customer data)

These integrations read public datasets or receive only the entity name being researched — never account data. The optional ones are off by default and activate only when a customer supplies their own API key.

Sub-processor	Purpose	Data touched	Terms
U.S. Treasury (OFAC)	SDN + Consolidated list and General License ingestion	Outbound HTTP to public government datasets only	U.S. government public data
OpenSanctions (optional)	PEP screening in Recon — off until a customer supplies a key	Outbound entity-name lookups; nothing retained vendor-side	Customer-keyed, opt-in
Lloyd's List Intelligence (optional)	Vessel intelligence in Recon — off until a customer supplies a key	Outbound vessel IMO lookups; nothing retained vendor-side	Customer-keyed, opt-in
UK Companies House / OpenCorporates	Corporate-registry lookups in Recon	Outbound entity-name lookups; nothing retained vendor-side	Public / provider ToS
Tavily / Brave / GDELT	Web search + news aggregation in Recon	Outbound search queries; nothing retained vendor-side	Provider ToS

Notes for reviewers

Recon’s LLM degradation path stays inside the same Anthropic organization, so the Zero Data Retention agreement covers it unchanged — no additional sub-processor.
Customer-installed chat surfaces (Slack, Microsoft Teams) store messages in the customer’s own workspace under the customer’s existing agreements — they are not vendor sub-processors.
Full engineering register, data-flow detail, and the stateless-architecture attestation are available in the vendor pack: request it.