← Docs
Recipe

Data Residency Doc

How Meridian keeps your data where you need it — region by region.

Overview

Meridian processes and stores all customer data within the geographic region you select during onboarding. No data leaves that region unless you explicitly configure cross-region replication.

Supported Regions

  • US East — Virginia (us-east-1)
  • EU West — Frankfurt (eu-central-1)
  • AP Southeast — Singapore (ap-southeast-1)

What Stays In-Region

  • License keys and activation records
  • Hardware fingerprints and machine metadata
  • Session tokens and auth logs
  • Analytics events (if opted in)

Cross-Region Traffic

The Meridian dashboard CDN (Vercel Edge) may serve static assets from the nearest point of presence globally. No customer PII or license data traverses the edge — only cached UI bundles and public assets.

Compliance

Meridian is SOC 2 Type II audited annually. Data residency controls are tested as part of that audit. DPA and regional addenda are available upon request.