← All articles
Data Privacy2 March 2025

Where Does Your Data Go When You Use Cloud AI?

Most organisations can't answer a basic question: where is your data right now? Here's what actually happens when you send data to cloud AI providers, and what to ask before you do.

Most organisations using cloud AI cannot answer a simple question: where is my data right now?

Not roughly. Not "somewhere in Europe." Exactly where, on whose servers, under whose jurisdiction, and for how long.

If you work in finance, healthcare, or law, that gap in knowledge is a compliance liability.

What Happens When You Send Data to Cloud AI

When you send a prompt to a cloud AI service, your data typically passes through several stages. Each one introduces risk.

Transit. Your data travels from your network to the provider's data centre. Depending on your provider and plan, that data centre might be in your country. It might not. Many providers route traffic dynamically, meaning your data could cross borders without you knowing.

Processing. The AI model processes your input. During this step, your data exists in memory on the provider's hardware. Some providers also log inputs and outputs for quality monitoring, model improvement, or abuse detection.

Storage and retention. This is where it gets murky. Retention policies vary wildly:

  • OpenAI retains API data for 30 days by default (with opt-out available on certain plans)
  • Microsoft Azure OpenAI Service offers zero data retention on select tiers
  • Google Cloud's Vertex AI stores data according to your project settings, but default logging can capture inputs
  • Many providers reserve the right to use your data for model training unless you explicitly opt out

Third-party sub-processors. Most cloud providers use sub-processors for infrastructure, monitoring, or support. Each sub-processor is another link in the chain, another entity with potential access to your data.

The Jurisdiction Problem

Data localisation is not just a preference. Under GDPR, transferring personal data outside the EEA requires specific legal mechanisms (Standard Contractual Clauses, adequacy decisions, or Binding Corporate Rules). Under Swiss FADP (revised 2023), similar restrictions apply.

FINMA's operational risk guidelines expect regulated firms to know exactly where their data is processed and by whom. "We use AWS" is not an answer that satisfies an auditor.

The problem compounds with AI specifically. Unlike traditional SaaS where data sits in a database, AI workloads involve data being loaded into GPU memory, potentially cached, and processed alongside other customers' workloads in multi-tenant environments.

Five Questions to Ask Your AI Provider

Before sending any sensitive data to a cloud AI service, get written answers to these:

  1. Where exactly is my data processed? Not "Europe." Which data centre, which country, which region? Can you guarantee it stays there?

  2. What is your data retention policy? How long do you keep inputs, outputs, and logs? Can I set retention to zero? Is that default or opt-in?

  3. Do you use my data for model training? If so, can I opt out? Is the opt-out retroactive?

  4. Who are your sub-processors? Which third parties have potential access to my data? Where are they based?

  5. Can you provide audit logs? Can I see exactly when my data was accessed, by whom, and for what purpose?

If your provider cannot answer these clearly, in writing, you do not have enough control for regulated work.

What the Alternative Looks Like

The simplest way to eliminate these risks is to keep AI processing inside your own infrastructure. When the model runs on your hardware, in your building, on your network:

  • Data never leaves your jurisdiction
  • There are no third-party sub-processors
  • Retention is whatever you set it to be
  • Audit logs are yours to configure and own

This is not theoretical. Organisations running private AI infrastructure today get the same model capabilities without the data residency uncertainty.

The Bottom Line

"The cloud" is not a place. It is someone else's computer, in a location you may not know, governed by policies you may not have read, in a jurisdiction that may not protect you.

For non-sensitive work, that trade-off can be acceptable. For regulated industries handling client data, it rarely is.

AlpinEdge helps professional services firms deploy private AI infrastructure where data never leaves their control. If you are not sure where your data is going today, that is a conversation worth having.

Want to discuss this for your business?

Book a free 30-minute call. We'll map where AI fits your operations.