Skip to main content

subprocessors

Who processes data.

The full list of third parties in Vero's data flow, for your DPA and vendor review. One nuance worth stating plainly: Cloudflare terminates TLS, so a visitor's IP reaches the edge and is processed in memory there to derive the daily-rotating hash and the country. Nothing is stored: Vero never writes the IP down, and no other subprocessor receives it.

  • 7subprocessors, each with what it receives and where.
  • EUis where the database lives: Ireland (aws-eu-west-1), with no replicas.
  • 1sees a visitor’s IP: Cloudflare, in memory at the edge. Nobody stores it.
  • 3payment providers that only take part if you connect them.

Vero’s infrastructure

SubprocessorPurposeDataRegion
SubprocessorCloudflarePurposeEdge hosting, Workers runtime, CDN, DDoS protection, transactional email, bot check on the waitlist form (Turnstile), nightly database backup (R2)DataRequest metadata (no stored IP), account email addressRegionGlobal edge; backups in R2 EU jurisdiction
SubprocessorGitHub (Actions)PurposeRuns the nightly database backup jobDataA full copy of the database while the job runs, not kept after itRegionUS
SubprocessorTurso (libSQL)PurposePrimary databaseDataAggregated analytics, account & site config (no cookies, no IP)RegionEU (Ireland, aws-eu-west-1)
SubprocessorGoogle (Gemini API)PurposeAI features (Pro and beta): AI insights, Ask Vero, plain-language watches and the digest commentary. Each workspace can turn them off on its Team pageDataAggregated site metrics and the text of your question, per request. No single visit, no IP. On the paid tier, Google does not use them to improve its productsRegionGlobal (Google infrastructure, may be outside the EU)

Providers you connect

They only send or receive data if you connect their webhook to your site.

SubprocessorPurposeDataRegion
SubprocessorStripePurposeRevenue webhooks (customer-configured)DataPayment metadata linked to a sessionRegionUS / EU
SubprocessorLemon SqueezyPurposeRevenue webhooks (customer-configured)DataOrder id, amount, currency, customer id and the session when the checkout carried oneRegionUS
SubprocessorPaddlePurposeRevenue webhooks (customer-configured)DataTransaction id, amount, currency, customer id and the session when the checkout carried oneRegionUS / EU