Customer data glossary

Data localisation

By Art Kukharenko · Published · Updated

Browse learn glossary resources

Data localisation is a legal requirement that certain data be stored or processed within the borders of a specific country or region.

Part of the Learn hub and the customer data glossary.

What it means in practice

Localisation turns a location preference into a rule. Where residency is a choice, localisation is an obligation set by statute, regulator or licence condition. Rules take different forms: a primary copy must be local; a copy or mirror must be kept locally even if the main store is abroad; processing must take place locally; or transfers are allowed only through approved mechanisms.

For a customer data platform (CDP), localisation drives deployment: in-country hosting, local key custody, and attention to backups, logs, support access and AI inference.

Example (iGaming): an operator licensed in Brazil keeps betting systems and player data in Brazilian data centres, so a foreign analytics copy is not an option unless the narrow exception applies.

Where it matters

Back to the customer data glossary or the Learn hub.

Frequently asked questions

Is data localisation the same as data residency?

No. Residency is where data happens to be, or where you choose to put it. Localisation is a legal requirement to keep it there.

Does GDPR require data localisation?

No. GDPR regulates transfers to third countries but does not require storage in the EU. Some national and sector rules do.

Do localisation rules cover backups and logs?

Often, if they contain the regulated data. Read the rule's scope, and ask the regulator or counsel when it is unclear.

Sources

  1. Gaming Compliance, Brazil (secondary source) Open source
  2. Al Tamimi & Co., health data transfers outside the UAE (secondary source) Open source
  3. Regulation (EU) 2018/1807, free flow of non-personal data Open source

This entry is general information, not legal advice.

Further reading

Published: · Updated:

Publication date recorded for the approved release. Editorial updates do not establish legal approval or a customer result.

Need help?

Ask the PrivyCDP Assistant