Subprocessors

Last updated: 12 April 2026

This page lists the main third-party providers ExpressCSV uses to deliver the service. The exact services used for a given customer workflow can vary by feature set and deployment configuration.

Current public summary

Vercel

  • Purpose: application hosting, runtime, and delivery infrastructure
  • Data involved: application traffic, operational logs, and service data required to render or serve the app
  • Region notes: may process data in multiple regions

Cloudflare

  • Purpose: traffic routing, caching, and delivery acceleration
  • Data involved: request metadata, IP-related traffic data, and edge delivery logs
  • Region notes: global network

Neon / Postgres infrastructure

  • Purpose: primary application data storage
  • Data involved: account records, team metadata, billing-related metadata, importer operational records, and other service data
  • Region notes: depends on deployment configuration

Stripe

  • Purpose: subscriptions, checkout, invoicing, and payment operations
  • Data involved: billing identifiers, subscription records, invoice records, and payment metadata
  • Region notes: Stripe-controlled infrastructure

PostHog

  • Purpose: product analytics
  • Data involved: product usage events and related technical metadata
  • Region notes: ExpressCSV is configured to use the EU PostHog ingestion host for the app stack

Sentry

  • Purpose: error monitoring, tracing, and selected replay diagnostics
  • Data involved: error events, request context, and diagnostic metadata
  • Region notes: provider-controlled infrastructure

Crisp

  • Purpose: support chat
  • Data involved: support messages, account context, and chat-related usage data
  • Region notes: provider-controlled infrastructure

Cal.com

  • Purpose: demo scheduling
  • Data involved: meeting booking details voluntarily submitted by the user
  • Region notes: provider-controlled infrastructure

SMTP email provider

  • Purpose: transactional email delivery
  • Data involved: recipient email addresses and message delivery metadata
  • Region notes: depends on configured provider

OpenRouter and model providers

  • Purpose: AI-enabled docs answers and importer AI features when enabled
  • Data involved: prompts, limited schema context, and limited sample values needed for the requested feature
  • Region notes: depends on configured provider path

Notes