Back

Data Localisation: When an IT Business Cannot Simply Store Data “In the Cloud”. Part 2

Continuing the discussion.

5. Which markets are particularly important for IT businesses?

Data localisation requirements vary significantly between jurisdictions.

That is precisely what makes the issue important for companies entering new markets.

Different countries may establish specific requirements concerning:

  • citizens' personal data;
  • children's data;
  • financial information;
  • health data;
  • government information systems;
  • critical infrastructure.

For an IT business, the practical implication is clear:

There is no universal cloud architecture that can simply be copied from one market to another without review.

6. FinTech can be particularly complicated

For FinTech businesses, data localisation can be especially important.

Financial companies do not deal only with emails and phone numbers.

They may process:

  • bank account information;
  • transaction data;
  • KYC information;
  • identity documents;
  • financial history;
  • credit information;
  • AML-related information.

On top of general privacy law, financial regulators may impose additional requirements.

So a FinTech company entering a new market should not ask only:

“Does privacy law allow us to transfer this data?”

It should also ask:

“Are there additional requirements imposed by the financial regulator?”

7. What about employee data?

Customer data gets most of the attention.

Employee data gets much less.

But an international IT company may centrally store:

  • HR records;
  • payroll information;
  • passport or ID details;
  • performance data;
  • health information;
  • background-check information.

For example, a Ukrainian company may use one HR platform for employees across ten countries.

From a business perspective, that is efficient.

But each jurisdiction may have its own rules for employee data.

So HR data should also be included in the data map.

8. Localisation can change the IT architecture

Sometimes the legal conclusion is not:

“Add a paragraph to the Privacy Notice.”

It is:

“You need to redesign part of the system.”

For example:

Global infrastructure

may become:

Global infrastructure + local data storage

or:

Local database → controlled transfer → global processing

or:

Local processing → anonymised data → global analytics

That is no longer only a legal decision.

It affects:

  • CTO;
  • engineering;
  • security;
  • DevOps;
  • product;
  • finance.

This is why privacy counsel should be involved before the product launches in a new market.

9. What happens if a company ignores localisation?

The consequences depend on the jurisdiction.

Potential risks may include:

  • fines;
  • regulatory orders;
  • restrictions on processing;
  • requirements to move or delete data;
  • problems with local customers;
  • disruption of certain operations;
  • reputational damage.

For SaaS businesses, there is another problem.

If the product is already live and the company later discovers that its architecture does not comply with local requirements, fixing it can be significantly more expensive than designing the right architecture from the start.

10. How should you assess data localisation before entering a market?

Before launch, conduct at least a basic Data Flow Mapping exercise.

Identify:

1. What data do we collect?

2. Does it include special or sensitive categories?

3. Where is it stored?

4. Where is it processed?

5. Who has access?

6. Which cloud providers and subprocessors are involved?

7. Is data transferred across borders?

8. What local rules apply to each category of data?

9. Is local storage or a local copy required?

10. Does the current IT architecture meet those requirements?

Only then can the company understand whether changes are necessary.

Global product, local rules

For an international IT business, the most effective model often looks like:

  • one global privacy strategy
  • local legal requirements
  • flexible cloud architecture.

You do not necessarily need a separate product for every country.

But you do need enough flexibility to ensure that local requirements do not break the entire system.

This is no longer just a compliance issue.

It is a question of international business architecture.

Conclusions

Data localisation is not simply about where the server is located.

It is about:

where data is stored, where it is processed, who can access it and across which jurisdictions it moves.

For international IT businesses, it is particularly important to distinguish between:

data localisation;

data residency;

cross-border data transfers.

Requirements may apply not to all data, but only to specific categories or types of activity.

Sometimes compliance can be achieved through contracts and procedures.

Sometimes the cloud architecture itself has to change.

That is why data localisation should be assessed before entering a new market, not after the product has already scaled.

Entering a new market and unsure whether your cloud architecture meets local requirements?

Avitar can conduct a Data Localisation & Cross-Border Transfer Assessment to analyse data flows, cloud infrastructure, vendors and jurisdiction-specific requirements — and identify what needs to change.

Request an assessment →

Subscribe to our channels on social networks:

LinkedIn

Instagram

Facebook

Telegram

Medium

Contact us: business@avitar.legal

Authors:

Violetta Loseva

,

11.16.2026 10:30
Іконка хрестик закрити

Let's discuss your project

Application successfully sent
Request submission error
By clicking "Allow all" you agree to store cookies on your device to enhance website navigation, analyse usage and assist in our marketing efforts
Allow chosen

Submit

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
You can find more in our
Cookie Policy
Text Link
Data Protection
Text Link
Privacy