Skip to content
Data Protection

Banking on Data: Regulatory Expectations for Data Storage, Protection, and Localization in Ethiopia’s Financial Sector

By Haymanot & Advocates 7 November 2025 6 min read

  1. Introduction

As Ethiopia gradually opens its financial sector to foreign investment, the regulation of data has become a central element of the country’s broader regulatory strategy. Given the inherently data-intensive nature of banking operations where vast volumes of sensitive customer and financial information are routinely processed and stored, the question of where, how, and under what safeguards this data is managed has assumed national and systemic importance.

To address operational, supervisory, and security concerns, the National Bank of Ethiopia (NBE) has introduced regulatory frameworks that, while initially focused on ensuring institutional soundness and operational control, have increasingly incorporated provisions on data protection and localization. The Licensing and Renewal of Banking Business and Representative Office Directive No. SBB/94/2025(the Directive) issued by the NBE as part of the banking sector’s regulatory scheme, sets out specific requirements for institutions to localize data and maintain IT systems that are accessible and auditable within Ethiopia.

These evolving priorities build upon earlier legislative efforts, particularly the Personal Data Protection Proclamation No. 1321/2024 (PDPP), which establishes overarching principles for lawful data processing, cross-border data transfers, and the protection of individual rights. Together, the directive and the proclamation contribute to a more coherent and comprehensive data governance framework.

Focusing on foreign banks, this article explores Ethiopia’s legal expectations around data storage, protection, and localization, including the alignment between the Directive and PDPP. It emphasizes that foreign entrants must carefully consider how to structure their IT systems and data governance models to comply with Ethiopia’s regulatory and data sovereignty requirements.

  • Data Governance Under Directive SBB/94/2025

Among its key provisions applicable to the pre-application and commencement phases for foreign banks, the Directive establishes a data governance framework. Outlined in Part 5 of the Directive, this framework sets forth regulations governing data localization, storage, processing, and cross-border transfer.

One of the Directive’s key regulatory provisions is the mandatory data localization requirement. It mandates all banks, including foreign subsidiaries and branches, to store and process customer data, account information, transaction records, and other core banking data exclusively within Ethiopia. This requirement applies to both primary and backup data. Even when a foreign bank branch is permitted to use its parent company’s core banking infrastructure, the Directive still requires local storage and processing of all customer data to be ensured.

The directive also introduces tight bound data transfers. For any data other than customer-related information such as transaction records or account information data, banks must meet stringent conditions before transferring data outside Ethiopia. These include:

  • Prior written approval from the National Bank;
  • Disclosure of data transfer locations;
  • Demonstration of adequate data protection standards in the receiving jurisdiction;
  • Implementation of service level agreements with third party providers covering confidentiality, encryption, audit mechanisms, and access control.  

In limited cases, and only with the explicit approval of the National Bank, data that doesn’t include personal identifiers may be transferred for legitimate business purposes. Nevertheless, the Directive’s default stance strongly favors domestic control over financial data, in line with national security priorities and Ethiopia’s long-term goal of strengthening its local digital infrastructure.

Accordingly, foreign banks seeking to enter the Ethiopian market must integrate these data governance obligations into their early planning and compliance strategies. This entails not only adapting engagement models but also designing IT systems and data handling frameworks that are fully aligned with the Directive’s localization and security requirements from the outset.

  • Alignment with the Personal Data protection Proclamation

The PDPP provides a comprehensive legal framework governing the collection, processing, storage, and transfer of personal data, forming the foundation of Ethiopia’s data governance regime. Its core principles align closely with the data localization and security requirements set out in the Directive.

The directive’s data localization and security mandates align closely with the personal data protection proclamation’s core principles, including:

  • Lawfulness of processing: The PDPP permits processing of personal data only under specific lawful grounds, such as consent, contract performance, compliance with legal obligations, or public. The directive supports this by limiting what type of data may be transferred and under what legal justification.
  • Security and Confidentiality: The PDP requires appropriate technical and organizational safeguards to prevent unauthorized access, destruction, or misuse of personal data. The directive reinforces this by mandating encryption, internal audits, access controls, and service-level agreements for outsourced data processing.
  • Cross-Border Transfers:  The PDPP prohibit transfers of personal data to jurisdictions that do not offer “an appropriate level of protection,” unless specific conditions are met, including data subject consent, legal necessity, or public interest. The directive adopts the same protective posture by requiring prior approval from the central bank, alongside proof of adequate safeguards.
  • Data Sovereignty: The PDP establishes a clear expectation that certain categories of data, especially sensitive or critical data, must be stored within Ethiopia. This mirrors the directive’s requirement that core banking data, both primary and backup, must be stored and processed locally.

Taken together, this close alignment means that banks operating under the Directive must adopt a holistic compliance approach, ensuring their regulatory, operational, and contractual frameworks fully satisfy both the licensing requirements and the broader personal data protection standards set out by the PDPP.

  • Cross Border Data Transfers

The other critical aspect of the Directive’s data governance framework concerns the cross-border transfer of data. Both the Directive and PDPP impose stringent controls on the Cross border transfer of personal and financial data, underscoring the country’s emphasis on data sovereignty and protection.

Under the Directive, customer data   including account and transaction records  must be stored and processed within Ethiopia. Even for foreign bank branches using their parent company’s core banking system, the directive explicitly mandates that both primary and backup data be stored locally. Cross-border transfers of core banking data are prohibited unless anonymized and explicitly approved by the National Bank.

The PDPP adopts a complementary, yet broader, approach to cross-border data transfers. It permits such transfers only under tightly defined and regulated circumstances. These include where:

  • The receiving country provides an “appropriate level of protection;
  • The data subject provides explicit, informed consent;
  • Prior approval is obtained from the authority, especially for sensitive or critical personal data.

Before authorizing any transfer, the authorities may require proof of adequate safeguards, such as encryption, access control, and clear service-level agreements. the Directive also mandates that banks disclose the data’s destination, demonstrate security controls, and obtain prior written approval from the NBE. Moreover, the PDPP prohibits transfers to jurisdictions that do not offer sufficient protection, unless narrowly justified and explicitly authorized. This requires foreign banks to carefully assess the legal framework of the jurisdictions to which they propose to transfer any personal data and prepare for possible regulatory scrutiny.

Collectively, these provisions highlight the critical need for foreign financial institutions to establish Ethiopia-specific data governance and localization models. This will likely involve setting up dedicated infrastructure and comprehensive compliance protocols within the country. All cross-border data strategies, therefore, must be legally justified, technically sound, and regulator-approved.

Conclusion

The entry of foreign banks into Ethiopia marks a pivotal moment in the country’s financial sector liberalization. While Directive SBB/94/2025 primarily provides the regulatory framework for licensing and supervising foreign bank operations, it also introduces clear expectations around data handling, specifically data storage, protection, and localization.

These data governance requirements form a critical component of a broader supervisory agenda that emphasizes regulatory certainty, operational resilience, and alignment with national interests. The stipulation that customer and core banking data must be stored within Ethiopia, coupled with layered approvals for cross-border data transfers, reflects the intersection of financial regulation with data sovereignty and personal data protection law.

Foreign banks looking to operate in Ethiopia must, therefore, plan their entry strategies not only around capital and organizational requirements but also in a manner that ensures their data infrastructure complies with local rules. This includes aligning with the Personal Data Protection Proclamation, which establishes baseline principles for lawful data processing, security safeguards, and transfer conditions.

As the financial sector continues to open, regulatory compliance across both banking operations and data governance will be essential for institutions seeking to build sustainable and trusted operations in the Ethiopian market.

This article is general information and not legal advice. Contact us about your specific situation.

H&A

Published by

Haymanot & Advocates

Legal update · Data Protection practice