
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:
So GDPR compliance does not automatically equal local privacy compliance.
GDPR does not automatically apply to every company that processes personal data.
For businesses outside the EU, relevant factors may include:
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.
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?”
One of the clearest differences between privacy regimes is the treatment of consent.
GDPR sets relatively high requirements for valid consent.
Consent must be:
But local laws may impose additional requirements.
For example, they may regulate:
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:
Contact us: business@avitar.legal
Violetta Loseva
,