Data residency

curl https://api.dairo.app/v1/account/residency \
  -H "Authorization: Bearer $DAIRO_API_KEY"

const residency = await dairo.account.residency();
console.log(residency.dataResidency, residency.controllerParent);
console.log(residency.cloudActExposed, residency.noUsEgress);
for (const s of residency.subprocessors) {
  console.log(s.name, s.role, s.region, s.country, s.status);
}

residency = dairo.account.residency()
print(residency.data_residency, residency.controller_parent)
print(residency.cloud_act_exposed, residency.no_us_egress)

Tool: get_compliance_reports   (scope account:read)
Args: { "action": "getResidency" }

{
  "type": "dairo.residency.v1",
  "primaryRegion": "EU",
  "dataResidency": "EU",
  "noUsEgress": true,
  "controllerParent": "EU",
  "cloudActExposed": true,
  "subprocessors": [
    {
      "name": "Amazon Web Services",
      "role": "Cloud infrastructure and hosting",
      "region": "EU",
      "country": "US",
      "url": "https://aws.amazon.com",
      "status": "active"
    }
  ],
  "subprocessorListVersion": 3,
  "subprocessorListUpdatedAt": "2026-06-01T00:00:00Z",
  "checkedAt": "2026-06-12T10:00:00Z"
}

​

What the response asserts

• dataResidency / noUsEgress — your data is stored and processed in the EU, and noUsEgress is true when there is no cross-region transfer.
• controllerParent — the home jurisdiction of the data controller (Dairo) — the EU.
• subprocessors — the formal, versioned register (subprocessorListVersion) of every subprocessor, each with its role, region, country, and status.
• cloudActExposed — the honest posture. Dairo does not claim CLOUD Act immunity: some subprocessors are US-incorporated, so under the US CLOUD Act they may in theory be compelled to produce data regardless of where it’s stored. When this is true, that exposure applies.

​

The subprocessor register

​

Next steps