30 Days Gen AI Risk Trial -Start Now
Skip to main content
Aona
Book a demo

AI Data Residency

AI data residency for employee prompts and records

Choose where Aona's backend is hosted and, separately, where Aona processes prompts. Review storage, retention and data flows for the configuration your workforce needs.

Review data-handling requirementsReview coverage
AONADATA-HANDLING REVIEW

Three separate
checks to make.

  1. 01Aona backend hosting
  2. 02Aona prompt processing
  3. 03Destination AI provider

Your Aona configuration does not determine the AI provider's data handling.

Deployment, on your terms

Your infrastructure. Your processing choice.

Choose where the Aona backend runs, then where Aona processes prompts.

Host the Aona backend

  • Your cloud
  • Your on-premises infrastructure
  • Aona-managed servers

Customer cloud, on-premises or Aona-managed hosting.

Process prompts with Aona

  • User device · on-edge
  • Your cloud
  • Your on-premises infrastructure
  • Aona-managed servers

On-device, in your infrastructure or on Aona-managed servers.

Confirm the hosting and processing combination, supported features, logs and retention for your deployment. The destination AI service has its own data handling; on-edge processing does not mean zero telemetry.

Discuss your architectureExplore data residency

Evaluation workflow

A procurement-ready data-flow review

Map the employee workflow and proposed deployment, then ask what is processed, where information is stored, which retention/deletion controls apply, and what must be confirmed in the applicable agreement before a pilot begins.

  1. 01

    Choose backend hosting

    Host Aona's backend in your cloud, on your premises or on Aona-managed servers.

  2. 02

    Choose prompt processing

    Aona can process prompts on the user device/on-edge, in your cloud or on-premises, or on Aona-managed servers. This is separate from backend hosting.

  3. 03

    Confirm the configured data flow

    Verify supported controls, integrations, file paths, storage, retention, telemetry and third-party AI-provider handling before rollout.

Your review record

Keep the evidence with each answer.

Separate the security service from the destination AI provider. Use the blank worksheet to record the proposed configuration.

Security backend
Where configuration, account records and retained events are hosted.
Prompt inspection
Where prompts or files are processed, and which content is retained.
Destination AI provider
The AI account's own processing, storage, training and retention terms.
What evidence should accompany each answer?

Record the data categories, processing and storage locations, retention and deletion terms, subprocessors and support access. Link the applicable contract, architecture or configuration evidence, and name an owner for unanswered questions. A local storage region does not establish the location of every processing or access path.

Download the blank data-handling review (CSV)

Blank review worksheet. It contains no observed product results.

Important boundaries

Confirm the supported configuration and contractual terms. Hosting and processing choices do not imply identical features or integrations, or that every existing client already uses on-edge processing.

Browser and native paths may have different data flows and should be reviewed separately.

On-device/on-edge prompt processing does not mean zero telemetry. Aona's deployment choice does not determine a third-party AI provider's processing or storage, or establish legal compliance.

Continue your evaluation

Useful evidence and next steps

Read the supporting reference before expanding the scope of a pilot.

Buying questions

Questions to resolve before a pilot

Where can we host Aona's backend?
In your cloud, on your premises or on Aona-managed servers. Agree the region, storage, retention, operating responsibilities and supported integrations for the selected configuration.
Where can Aona process prompts?
On the user device/on-edge, in your cloud or on-premises, or on Aona-managed servers. Select this separately from backend hosting, then confirm supported controls and data flows. On-edge processing does not by itself establish zero telemetry or file-processing parity.
Does data residency make us compliant?
No. Residency is one input to your privacy and security assessment, not a legal determination.
Does Aona's region determine where ChatGPT, Claude, Gemini or Copilot process data?
No. The destination AI provider and account have their own processing, storage, training and retention terms. Record those separately from Aona's backend and prompt-inspection configuration. Local storage also does not automatically settle access by overseas recipients or onward transfers.
What should we bring to a review?
Your target geography, employee workflows, endpoint model, data categories, retention needs, and procurement constraints.

Qualified evaluation

Review your data-handling requirements

Choose backend hosting and prompt processing separately, trace a synthetic workforce request, and review storage, retention, telemetry and the destination AI provider's data handling.

Review data-handling requirementsReview coverage