Where are Valid Email Checker's servers located? (data residency)

Last updated May 20, 2026Privacy & policies

Valid Email Checker runs on Supabase, which provisions PostgreSQL databases on top of AWS infrastructure. Your data lives in an AWS region selected at provisioning time. For the default Valid Email Checker tenant, that region is in North America, which is where the bulk of our customers connect from. Enterprise customers with EU-residency requirements can request provisioning in an EU region instead, which keeps verification data inside the EU at rest. Edge functions — the small serverless workers that handle webhooks, integrations, and bursty traffic — run globally on Cloudflare to keep latency low for users everywhere.

Where the data actually sits

  • Primary database (Postgres on AWS) — default region is in North America. Holds your account, verification tasks, results during the 15-day window, and Credits History.
  • Object storage — same region as the database. Holds the uploaded CSVs/TXTs during the 15-day retention window, then deleted by the cleanup job.
  • Edge functions — Cloudflare's global network. Functions are stateless code; they read from and write back to the primary database. No persistent data lives in the edge layer.
  • Backups — encrypted, region-pinned to the same AWS region as the primary database. Retention follows our backup policy and is purged after the documented window.

EU data-residency option

For customers with a strict GDPR residency requirement — typically EU public sector, regulated industries, or companies whose own privacy commitments require EU-only processing — we can provision an EU-region tenant. The database, storage bucket, and backups all live in an AWS EU region (Frankfurt or Ireland depending on the contract). Verification data never leaves the EU at rest. Edge functions still run globally, but they are stateless and only forward requests into the EU database. Talk to support during onboarding if you need this — it cannot be switched on after the account is created, because moving a populated tenant between regions is operationally messy.

What we share across regions

Nothing about your verification data crosses regions unless you explicitly route a request that way (e.g. you connect to an integration whose API is hosted elsewhere — those external calls leave VEC by definition). Within VEC, your tenant's data stays in the region it was provisioned in. Cross-region replication for disaster recovery uses the same region family — an EU tenant's DR snapshot is also in the EU.

Subprocessors

Valid Email Checker uses Supabase (database hosting), AWS (underlying compute and storage for Supabase), Cloudflare (edge functions, DDoS, Turnstile captcha), Stripe and Paddle (payments), CoinPayments (crypto payments), and our email-sending provider for transactional mail. The full subprocessor list is available on request as part of the standard DPA — email support@validemailchecker.com if your legal team needs it.

Verification engine calls
The SMTP handshakes and DNS lookups that the verification engine makes go out to the recipient mail servers, which can be located anywhere in the world. This is unavoidable — to verify that mailbox@example.com exists, we have to talk to example.com's mail servers. Those requests carry the address being verified and nothing else.