Back

GDPR vs Local Privacy Laws: What IT Businesses Need to Know When Entering a New Market. Part 1

GDPR is not always where you think it is

International IT businesses often have a simple plan:

“We already have GDPR compliance — so our privacy is covered.”

That may be a good starting point for the European market.

But once a company moves beyond the EU, this logic quickly becomes less reliable.

Kazakhstan has its own personal data rules. Uzbekistan has its own. Georgia has its own. South Africa has its own. Kenya has its own.

And while many modern privacy laws share principles with the GDPR, they are not copies of it.

They may differ in:

  • legal bases for processing;
  • consent requirements;
  • individual rights;
  • cross-border transfer rules;
  • data localisation;
  • breach notification;
  • regulatory registration or notification;
  • local representative requirements;
  • liability and penalties.

So GDPR compliance does not automatically equal local privacy compliance.

1. First: does GDPR actually apply to you?

GDPR does not automatically apply to every company that processes personal data.

For businesses outside the EU, relevant factors may include:

  • where the company is established;
  • whether it has an establishment in the EU;
  • whether it offers goods or services to individuals in the EU;
  • whether it monitors their behaviour.

For example, a Ukrainian SaaS company may have no office in the EU but sell its product to European users.

GDPR may still be relevant.

But if the same company starts operating in Kazakhstan or Kenya, that does not mean local privacy law can simply be replaced by GDPR.

A separate assessment is required.

2. Local privacy law can apply independently of GDPR

This is probably the most important rule in international privacy compliance.

A company can be subject to several privacy regimes at the same time.

For example:

Ukrainian company

↓

GDPR

↓

local law of the customer's country

↓

rules of the country where the data is physically stored or processed

Each layer may create separate obligations.

So the question is not:

“GDPR or local law?”

It is:

“Which rules apply to this particular data processing activity?”

3. Consent does not always mean the same thing

One of the clearest differences between privacy regimes is the treatment of consent.

GDPR sets relatively high requirements for valid consent.

Consent must be:

  • freely given;
  • specific;
  • informed;
  • unambiguous.

But local laws may impose additional requirements.

For example, they may regulate:

  • the form in which consent must be obtained;
  • the language in which information must be provided;
  • how consent must be documented;
  • whether separate consent is required for specific processing activities;
  • special rules for biometric or other sensitive data.

So an EU consent model should not simply be copied into a new market without checking local requirements.

To be continued.

Subscribe to our channels on social networks:

LinkedIn

Instagram

Facebook

Telegram

Medium

Contact us: business@avitar.legal

Authors:

Violetta Loseva

,

11.6.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