Back

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

Continuing the discussion.

4. A Privacy Notice is not a universal document

International SaaS and e-commerce businesses often have one Privacy Notice.

It was written for GDPR.

It was translated into English.

It was published on the website.

Done?

Not necessarily.

A Privacy Notice should explain to users what happens to their personal data.

But requirements concerning content, format, language, retention and other matters may differ across jurisdictions.

A local law may require additional information or establish specific rules for certain categories of data.

For an international business, it is therefore more useful to think in terms of a privacy framework rather than a single universal document.

5. Data transfers: where is the data?

Another major issue is cross-border data transfer.

For international IT businesses, this happens constantly.

The user is in one country.

The company is in another.

The cloud provider is in a third.

The CRM is in a fourth.

The support team may be distributed around the world.

This creates a simple question:

“Can we legally transfer this data across borders?”

GDPR has its own framework for international data transfers.

Countries outside the EU may have their own requirements.

These may involve:

  • data localisation;
  • regulatory approvals;
  • notifications;
  • contractual requirements;
  • restrictions on transfers to specific countries.

This is why cloud architecture and privacy compliance are becoming increasingly difficult to treat as separate issues.

6. Data localisation: when data must stay inside the country

Some jurisdictions place particular emphasis on data localisation.

This means requiring certain categories of personal data to be stored within the country.

For an IT business, this can be critical.

Especially when the company relies on global cloud infrastructure.

For example:

Customer → Local market → SaaS → Cloud → Data centre abroad

From an engineering perspective, this may be a standard architecture.

From a local legal perspective, it may create an issue.

That is why data location should be considered at the market-entry stage, not after the product is already live.

7. Breach notification: how much time do you have?

Another area where privacy regimes may differ is data breach response.

Under GDPR, in certain circumstances, a controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach.

Other countries may establish different rules concerning:

  • deadlines;
  • competent authorities;
  • notification thresholds;
  • notification of affected individuals.

For international businesses, the practical lesson is simple:

Your incident response plan should not assume there is only one jurisdiction.

8. Who controls the data: the company or the local partner?

Privacy risks do not arise only from the company's own operations.

Suppose an IT company enters a new market through a local partner.

The partner receives access to:

  • customer databases;
  • contact details;
  • user information;
  • payment information;
  • support tickets.

The next question is:

Who is the controller? Who is the processor? Is there joint determination of processing purposes?

Terminology and legal approaches may vary across jurisdictions.

That means a contract with a local partner is not simply an NDA or a standard Data Processing Agreement.

The actual data-processing model needs to be understood first.

9. GDPR can be a strong baseline — but not the final answer

Despite these differences, GDPR can still be a useful starting point.

If a company already has a mature privacy programme, adapting it to other markets can be significantly easier.

For example, the company may already have:

  • a data inventory;
  • records of processing activities;
  • a Privacy Notice;
  • cookie management;
  • Data Processing Agreements;
  • a data subject request procedure;
  • incident response procedures;
  • vendor due diligence;
  • a retention policy.

That is a strong foundation.

But before entering a new market, the company should perform a local gap analysis.

In simple terms:

What do we already have?

What does local law require?

What is missing?

10. The best approach is not to rewrite everything from scratch

An international business does not need to build a completely new privacy system for every country.

A more efficient model is:

Global Privacy Framework

plus:

Local Privacy Layer.

For example:

  • Global policies
  • Local Privacy Notice
  • Local consent requirements
  • Local data transfer rules
  • Local breach procedures
  • Local data localisation requirements.

This allows the business to maintain consistent privacy governance while adapting to the specifics of each market.

How should you prepare for a new market?

Before launch, answer at least these seven questions:

  1. What personal data do we collect?
  2. Where are our users located?
  3. Where is the data physically stored?
  4. Who has access to it?
  5. Who is the controller and who is the processor?
  6. Can the data be transferred across borders?
  7. Which local requirements differ from our existing privacy framework?

Only then should you decide whether changes are needed to contracts, Privacy Notices, IT architecture or internal procedures.

Conclusions

GDPR is not an “international personal data law.”

It is one of the world's most influential privacy regimes, but every new market still needs to be assessed separately.

For IT businesses, the key areas include:

  • GDPR scope;
  • local privacy laws;
  • consent;
  • Privacy Notices;
  • international data transfers;
  • data localisation;
  • breach notification;
  • relationships with local partners and vendors.

The most effective strategy is usually not to build a separate privacy system for every country.

It is to create a global privacy framework with local adaptations.

That turns market-entry privacy compliance from a chaotic rewriting exercise into a structured and scalable process.

Entering a new market and unsure whether your existing GDPR framework is enough?

We can conduct a local privacy gap analysis to compare your current privacy framework with the requirements of a specific jurisdiction and identify what needs to change in your documents, processes and IT architecture.

Request a Privacy Gap Analysis →

Subscribe to our channels on social networks:

LinkedIn

Instagram

Facebook

Telegram

Medium

Contact us: business@avitar.legal

Authors:

Violetta Loseva

,

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