Skip to main content
CrowAgentSustainabilityIntelligenceBack to home

Sub-processors

Last updated: 24 April 2026

This page lists the sub-processors CrowAgent currently uses to deliver the platform. The list is part of our Data Processing Agreement and is updated here at least 30 days before any change takes effect. Customers may subscribe to updates at hello@crowagent.ai.

Current sub-processors

Sub-processorPurposeData processedRegionSince
Supabase (EU) GmbHHosted Postgres database, authentication, object storageAll application data (profiles, properties, contracts, reports)AWS eu-west-1 (Ireland)2025-09
Railway CorpBackend API compute (FastAPI)Request/response processing (no persistent storage)europe-west4 (Amsterdam)2025-09
Vercel Inc.Frontend hosting and edge functionsRequest routing, edge caching (no PII storage)Global edge; compute lhr1 (London)2025-09
Cloudflare, Inc.DNS, DDoS protection, WAFEdge request metadata only (IP, URL, headers)Global edge; no persistent storage of PII2025-09
Stripe Payments Europe, LtdBilling, payments, VAT handling, invoice deliveryBilling contact, VAT ID, payment method tokens, invoice historyEU (Dublin) with limited US fallback2025-09
Resend (Resend Inc. via Amazon SES)Transactional email deliveryRecipient email, email content, delivery eventseu-west-1 (Ireland)2025-09
Sentry GmbHApplication error telemetryScrubbed stack traces, event metadata (no PII, no request bodies)EU region2025-10
PostHog Inc.Product analytics (consented)Page views, feature events, distinct user IDeu.posthog.com (Frankfurt)2025-10
Google Cloud EMEA Ltd (Vertex AI / Gemini)Social Value narrative generationContract profile inputs; output narrativeseurope-west4 (Amsterdam)2026-01
Upstash, Inc.Redis rate-limit countersUser ID or IP hash, counter values (no PII)eu-west-1 (Ireland)2026-02
Anthropic, PBCInternal portal reasoning only - not used on the customer platformFounders portal data only; no customer data sentUS with SCCs + UK IDTA2026-03

Change notification

We notify customers by in-app banner and email to the billing contact at least 30 days before adding a new sub-processor or moving an existing sub-processor to a new region. Customers may object on reasonable grounds; where an objection cannot be resolved, the Customer may terminate the affected services.

Removed sub-processors

No sub-processors have been removed since the platform launch. Future removals will be listed here with the date they stopped processing data.