Data Residency Coverage Score

Score the share of production data flows that satisfy residency policy, including documented exemptions and enforcement strength adjustments.

Count of distinct production data flows or services that process user data.
Number of flows already constrained to compliant regions or sovereign clouds.
Defaults to 0. Include temporary or regulator-approved exemptions.
Defaults to 100%. Discount coverage if enforcement relies on soft controls.

Governance planning aid. Validate against your data map, DPA commitments, and regional legal advice.

Examples

  • 120 total flows, 88 compliant, 6 exemptions, 90% control strength ⇒ 79.17% residency coverage
  • 60 total flows, 48 compliant, no exemptions, strength left blank ⇒ 80.00% coverage

FAQ

What counts as a data flow?

Use a consistent unit such as service-to-service pathways, event pipelines, or batch jobs that process production user data.

How should I set control strength?

Leave it at 100% for hard enforcement like infrastructure-as-code guardrails. Lower it when controls rely on manual reviews or detective monitoring.

Should backups be included?

Yes. Residency policies usually cover backups and disaster-recovery replicas, so count them as separate flows if they are independently routed.

Can coverage exceed 100%?

No. The calculator caps the adjusted coverage at 100% even if compliant and exempt counts sum above the total.

Additional Information

  • Coverage is capped at 100% even if compliant and exempt counts exceed total flows.
  • Control strength scales the fraction to reflect hard versus soft enforcement.
  • Outputs use two decimal places and require at least one total data flow.
  • Use exemptions for regulator-approved cross-border transfers documented in your data map.

Related calculators