Glossary

Data residency

Data residency is the rule that data must be stored and processed inside a set country or region. Data residency for AI agents covers the documents they read, the model calls they make and the record of each job.

In a run

You choose where processing runs and which model handles which data. Each call goes where your rule sends it, and the record shows where each call ran.

Our word for it

Hosting inside your own country.

Where the data sits in each shape

  • Cloud: your tenant runs in the region agreed for it.
  • Hybrid: your agents and their data stay in your environment. Prompts, model outputs and secrets never move. Console sessions move only if you allow them.
  • On-prem: nothing leaves your building, the record included.

Residency routing works in every shape: by region in the cloud, and in full in hybrid and on-prem.

What Ares keeps

We do not store prompts, outputs or documents unless you turn on retention for audit. Your administrators reach the record under the roles you set in your directory. We never disclose one customer’s data to another.

When a subscription ends, we delete or anonymise customer personal data unless the law or a written agreement says otherwise. On-prem, that data never left your building.

Where it stops

Ares routes each call and records where it ran. It does not certify that your organisation meets a residency law. We say which model runs which step, and where. We map requirements to what Ares does; you hold the result.

Read security and data handling for the questions a review asks about where data goes.

Related terms

  • On-prem AIOn-premises AI is AI that runs on hardware inside your own building instead of in a vendor’s cloud.
  • Hybrid deploymentA hybrid AI deployment splits a system between your own environment and a cloud service.

Tell us about one workflow.

We will say whether an agent should do it, and what the first step costs.

A senior member of the team replies within two business days.