
For the user, it is simple.
They sign up for your SaaS.
They enter their name, email, phone number and payment details.
They click Sign up.
And then the real story begins.
The data may move through:
CRM → cloud provider → backup → analytics → support → payment provider.
Each of these services may store or process information in a different country.
For the IT team, this is standard cloud architecture.
For the legal team, the question is different:
Does the law of the country where the user is located allow this model?
This is where data localisation becomes relevant.
The term data localisation is often used as if it had one universal meaning.
In practice, requirements can be very different.
A law may:
So the question:
“Do we need to localise our data?”
always needs to be followed by:
Which data? Where? For how long? For which operations? And what exactly does local law mean by localisation?
One of the biggest mistakes is treating “user data” as a single category.
A real product may process dozens of data types:
Local legislation may impose different requirements on different categories.
For example, ordinary contact information may be treated differently from biometric, health or government-related data.
That is why the first step should be data mapping.
The company needs to know what it collects, why it collects it and where it goes.
Another trap is focusing only on where data is stored.
Data may:
For example:
User in Kenya
↓
Application hosted in Europe
↓
CRM in the US
↓
Support team in Ukraine
↓
Backup in another region
So where does the processing take place?
The answer depends on the specific activity and applicable law.
That is why legal analysis should consider not only data at rest, but also data in transit and actual access and processing activities.
Cloud infrastructure is one of the reasons data localisation has become more complicated.
A company may use a large international cloud provider without knowing exactly where every copy of its data is stored.
For example:
“Our cloud provider stores the data in the EU region.”
Fine.
But what about:
For privacy compliance, knowing the primary storage region may not be enough.
That is why a cloud provider agreement is not merely a technical procurement issue.
It is part of data governance.
These concepts are often mixed together.
They should not be.
Data residency generally refers to where data is physically stored.
Data localisation is a broader concept concerning legal requirements around where data must be stored or processed.
Cross-border transfer concerns the movement of data from one jurisdiction to another.
They can overlap, but they are not identical.
A law may allow data to be stored abroad while imposing conditions on cross-border transfers.
Another jurisdiction may require a local copy of certain data.
So you should not assume:
“The data is physically stored in the country, therefore we comply with all privacy requirements.”
Not necessarily.
To be continued.
Subscribe to our channels on social networks:
Contact us: business@avitar.legal
Violetta Loseva
,