Africa Fintech Regulatory Atlas · Egypt
Egypt's Personal Data Protection Law: what fintechs must do before the grace period ends
Egypt's Personal Data Protection Law (the PDPL, issued by Law No. 151 of 2020) became workable only when its Executive Regulations arrived in November 2025. Organisations it covers now have one year to obtain licences, appoint data protection officers and put records, breach procedures and transfer controls in place. This guide sets out who is in scope, what the law and the regulator require, and how a fintech can produce the evidence to show it.
Last reviewed: 11 October 2026 · Next review: 9 January 2027 · Written by Oluwafemi Ofobutu, founder
This guide is general information, not legal advice. The official text is the authority. Local legal interpretation should come from qualified counsel in Egypt.
Verification status, 11 October 2026: of 51 ledgered statements, 18 match official sources automatically; 21 more, including scope, the banking carve-out, the deadline, breach notice and penalties, were checked against the Arabic gazette text. The StackWeaver compliance research team is checking the other 12.
Executive summary
Sourced
- The clock is running. The issuing law gives those covered one year from the issue of the Executive Regulations to comply (Law 151/2020, Art. 6). The regulations were published on 1 November 2025 (Decree 816/2025), so the window closes on or around 1 November 2026.
- Banks are largely outside it; most other fintechs are inside it. Personal data held by the Central Bank of Egypt and the entities it supervises is excluded, except money-transfer and exchange companies (Art. 3(6)). The PDPC names non-bank wallets, payment processors and lending platforms in its own guidance (PDPC DPO categories).
- No licence, no processing. Controllers need a PDPC licence or permit (Art. 4(10)), and the PDPC's guidance says processing may start only once one is granted (Licenses and Permits Guidelines).
- Seventy-two hours. Breaches go to the PDPC within 72 hours of awareness and to affected individuals within three working days of that report (Art. 7).
- Financial data is sensitive. The PDPC defines sensitive data to include financial details (Key Terms), which brings express written consent and the law's heaviest penalties into play (Art. 41).
Who is in scope
Sourced, with our reading marked
The PDPL applies to personal data that is processed electronically, in whole or in part, by anyone who holds, controls or processes it, where the data relates to natural persons (issuing law, Art. 1). "Electronic" is broad in practice: a fintech's core banking or ledger system, its customer app, its CRM, its support tooling and its analytics warehouse are all electronic processing. Paper-only records sit outside the definition, but few fintechs keep anything only on paper.
The most important scoping rule for financial services is the carve-out in Article 3(6) of the issuing law. The law does not apply to personal data held by the Central Bank of Egypt and the entities that are subject to its supervision and control, except money-transfer companies and exchange companies. Those two groups must still observe the rules the Central Bank sets for handling personal data (Art. 3(6)).
That carve-out produces three practical groups. A licensed bank, or a payment business supervised by the Central Bank, is mostly outside the PDPL and is governed by the Central Bank's rules instead. A money-transfer or exchange company is inside the Central Bank's perimeter but expressly brought back into the PDPL. Everything else, including non-bank lenders, consumer-finance and insurance businesses, credit-scoring and data platforms, wealth and investment apps, and the technology vendors that process data for banks, should plan on the PDPL applying in full.
StackWeaver view · The carve-out turns on who supervises you, not on what you call yourself. A company that partners with a bank but is not itself supervised by the Central Bank does not inherit the bank's exclusion. Treat your scoping decision as a written legal opinion, not an assumption, and keep it in your evidence pack.
The regulator's own material supports this reading for non-bank fintechs. The PDPC's guideline on data protection officer categories lists "digital wallets, fintech startups, and payment processing platforms (non-bank)" and "financial technology platforms offering credit scoring, loans, or insurance products" as examples in its highest category, and medium-scale non-bank wallets and payment gateways in the next one (PDPC DPO categories; Category B).
Reach beyond Egypt is real. The criminal provisions apply to Egyptians wherever the offence happens and to non-Egyptians outside Egypt when the data concerns Egyptians or foreigners living in Egypt (issuing law, Art. 2). A controller established outside Egypt must appoint a representative inside Egypt (Art. 4(11)). A regional fintech serving Egyptian customers from Dubai, Lagos or Nairobi should therefore assume it is in scope for that customer base.
The law also lists other exclusions: data kept by individuals for personal use, data processed for official statistics or under a legal provision, data processed solely for journalism, data in judicial records and investigations, and data held by national security bodies. None of these is likely to cover a commercial fintech.
The regulators
Sourced
The Personal Data Protection Center (PDPC). The law creates the PDPC as a public economic authority that reports to the competent minister (Art. 19), and the Executive Regulations were issued by the Minister of Communications and Information Technology (Decree 816/2025). The PDPC issues licences and permits, keeps the register of data protection officers, receives complaints, inspects data users and checks cross-border transfers. It has published guidelines on key terms, lawful bases, consent, privacy notices, records of processing, data protection officers, breach notification, direct marketing, and licences and permits.
The Central Bank of Egypt. For banks and other entities it supervises, the Central Bank's own rules on personal data apply instead of the PDPL, and money-transfer and exchange companies must follow those rules as well as the PDPL (Art. 3(6)). If your licence comes from the Central Bank, your data-protection programme should be built against its requirements first.
The economic courts. Crimes under the PDPL are heard by Egypt's economic courts (issuing law, Art. 5). That matters because most of the penalties in the law are criminal fines, and several carry prison terms.
StackWeaver view · Non-bank financial firms also answer to the Financial Regulatory Authority, whose FinTech Law adds a confidentiality duty with per-victim fines, plus customer verification and outsourcing rules. Our Egypt FinTech guide covers them.
How the PDPC can act. According to its guidance, the PDPC can warn a non-compliant data user and order the violation cured, suspend a licence in part or in full, revoke it, place the data user under technical supervision at its own cost, and publish proven violations in the media at the violator's expense (Licenses and Permits Guidelines §6).
Obligations and the evidence that demonstrates them
Sourced obligations · evidence column is StackWeaver view
The table lists each obligation, its legal source, who it applies to, the evidence that shows it is met, and its deadline. The legal-source column links to the official text; the evidence column is our practical suggestion.
| Obligation | Legal source | Applies to | Evidence | Deadline |
|---|---|---|---|---|
| Hold a PDPC licence or permit before processing personal data (controller, processor, or both). | PDPL Art. 4(10); PDPC Licenses and Permits Guidelines §1–2 | Controllers and processors in scope | PDPC licence or permit, the portal application record, and the ‘Company Journey’ answers that set its type | Apply within the one-year window that closes on or around 1 November 2026 |
| Obtain supplementary licences or permits for cross-border transfers (including foreign cloud hosting), video surveillance and direct electronic marketing. | PDPC Licenses and Permits Guidelines §2.2 | Data users doing those activities | Supplementary licence or permit linked to the general licence; list of foreign hosting locations | Same window; supplementary approvals need a valid general licence |
| Keep a record of processing covering categories of data, recipients, retention, cross-border transfers and security measures. | PDPL Art. 4(9) and 5(9); PDPC RoPA Guidelines | Controllers and processors | Record of processing activities with an owner and a last-reviewed date | Ongoing; must exist before licensing |
| Process only on a lawful basis and for legitimate, specific and declared purposes. | PDPL Art. 3 and Art. 6 | Controllers | Lawful-basis register per processing activity; consent records where consent is the basis | Ongoing |
| Let data subjects access their data, withdraw consent, correct or erase it, restrict processing, object, and learn of breaches. | PDPL Art. 2 | Controllers (processors assist) | Data-subject request procedure, request log with response dates, fee policy | Ongoing |
| Keep personal data no longer than its purpose requires, then erase it or make it non-identifying. | PDPL Art. 3 and Art. 4 | Controllers | Retention schedule and deletion records, reconciled with sector record-keeping rules | Ongoing |
| Apply technical and organisational measures that protect personal data from breach, loss or alteration. | PDPL Art. 4 and Art. 5 | Controllers and processors | Security policy, access reviews, encryption settings, vulnerability and change records | Ongoing |
| Report a personal data breach to the PDPC within 72 hours of awareness and inform affected data subjects within three working days of that report. | PDPL Art. 7; PDPC Data Breach Notification Form | Controllers and processors | Incident response plan, breach register, completed PDPC notification form, data-subject notices with timestamps | 72 hours / three working days per incident |
| Appoint an in-house data protection officer and register them with the PDPC. | PDPL Art. 8; PDPC DPO Guidelines | Juristic persons acting as controller or processor | Board or management appointment letter, DPO Registry entry, DPO qualifications matched to the PDPC category | Before licensing; maintained continuously |
| Treat financial details and other sensitive data under the stricter regime: PDPC licence and express written consent unless the law allows otherwise. | PDPL Art. 12; PDPC Key Terms | Any data user processing sensitive data | Data classification marking financial data as sensitive; written consent records; licence scope covering sensitive data | Ongoing |
| Transfer personal data abroad only to a country with protection at least equal to the PDPL and with a PDPC licence or permit; document a transfer impact assessment. | PDPL Art. 14; PDPC Data Users Guidelines §3.11 | Data users sending data outside Egypt | Transfer inventory, transfer impact assessments, cross-border licence or permit | Before each transfer |
| Appoint a representative in Egypt when the controller is established outside Egypt. | PDPL Art. 4(11) | Foreign controllers | Representative appointment and contact details on file with the PDPC application | Before licensing |
| For electronic direct marketing, keep electronic records of consent and objections for three years after the last message. | PDPL Art. 18 | Senders of electronic direct marketing | Consent and opt-out records with send history | Three years from the last message |
| Keep the means to prove compliance and allow the PDPC to inspect. | PDPL Art. 4(12) | Controllers | An evidence pack: policies, records, decisions and logs that an inspector can trace | Ongoing |
Three obligations deserve more detail because fintechs most often underestimate them. First, licensing is layered: a general licence or permit for your role (controller, processor or both), then supplementary approvals for cross-border transfers, video surveillance and direct electronic marketing. Licences last three years and must be renewed at least three months before expiry; permits last at most a year (validity; permits). The PDPC decides an application within 90 days, and silence counts as refusal (§3.2).
Second, cross-border transfers reach further than many teams expect. Hosting customer data with a cloud provider whose servers are outside Egypt is itself a transfer that needs the supplementary approval (§2.2(a)), and the destination must offer protection at least equal to the PDPL (Art. 14). The PDPC expects a documented transfer impact assessment (Data Users Guidelines §3.11).
Third, the data protection officer must be an employee inside the company, not only an outside adviser (Art. 8), and must be entered on the PDPC's DPO Registry (DPO Guidelines). The PDPC grades officers by the number of records an organisation holds: its top category starts above 2,000,000 records (Category A). A fast-growing wallet can move up a category within a year, so plan the role for where your customer base is heading.
Timeline of key dates
Sourced; derived dates are marked as our reading
-
Law No. 151 of 2020 issued by the President · source
-
Law published in the Official Gazette, issue 28 bis (H) · source
-
Law in force: three months after the day following publication (our reading of Article 7 of the issuing law) · source
-
Executive Regulations (Decree No. 816 of 2025) published in Al-Waqa'i' al-Misriyya No. 244 (follow-on A) · source
-
Executive Regulations take effect (the day after publication) · source
-
PDPC guidelines published as Version 1.1 · source
-
One-year window to comply ends, counted from the regulations' issue (our reading; confirm the exact day with counsel) · source
Two of these dates are calculated rather than printed in the text: the law's start date and the end of the window. Some advisers give 31 October 2026 for the end; the primary text counts one year from the regulations' issue, and the regulations were published on 1 November 2025. File well before either date.
Enforcement record
StackWeaver view, with the penalty schedule sourced
As of 11 October 2026 we found no enforcement decision published by the PDPC. That is expected during a grace period that the PDPC's own guidance describes as a period to apply for licences and adjust (§7; direct marketing guidance). We will add decisions to this section, each with a link, as the PDPC or reputable outlets publish them.
The penalty schedule in the law tells you what the regulator and the courts can do once the window closes:
- Unlawful collection, processing or disclosure: EGP 100,000 to EGP 1 million (Art. 36).
- Committed for gain or to harm the person: at least six months in prison and EGP 200,000 to EGP 2 million, or either (Art. 36, second paragraph).
- A controller or processor failing its core duties, including breach notification: EGP 300,000 to EGP 3 million (Art. 38).
- No data protection officer: EGP 200,000 to EGP 2 million for the company's legal representative (Art. 39).
- A data protection officer failing the role: EGP 200,000 to EGP 2 million; EGP 50,000 to EGP 500,000 if negligent (Art. 40).
- Sensitive data without consent: at least three months in prison and EGP 500,000 to EGP 5 million, or either (Art. 41).
- Breaking the cross-border rules: the same range as sensitive data (Art. 42).
- Breaching the licence and permit provisions: EGP 500,000 to EGP 5 million (Art. 45).
StackWeaver view · For a fintech, the licensing and cross-border penalties are the ones to plan around. They apply to the most common failure, which is processing customer data in a foreign cloud without the right approval, and they are set at the top of the scale.
A practical 90-day plan
StackWeaver view
If you are reading this before the window closes, front-load the licensing work: the PDPC can take up to 90 days to decide, so the first fortnight matters more than the rest.
Days 1–14: decide scope and file
Get a written view on whether the Central Bank carve-out covers you. Appoint the data protection officer. Map every processing activity and your role in it. Answer the PDPC portal's “Company Journey” questions and file the general application, then the supplementary ones your activities need. Keep the submission receipts: they are your best evidence of good faith if a decision is pending when the window closes.
Days 15–45: build the records
Write the record of processing, the lawful-basis register and the retention schedule. Classify financial data as sensitive and check you hold express written consent where you rely on consent. Inventory every vendor and foreign hosting location and complete transfer impact assessments. Update the privacy notice so it names recipients and countries.
Days 46–75: prove the controls work
Run a breach tabletop timed against the 72-hour and three-working-day clocks. Process a sample of data-subject requests end to end. Collect security evidence for the systems that hold personal data: access reviews, encryption settings, change approvals and vulnerability scans.
Days 76–90: assemble and rehearse
Put the evidence into one indexed pack that traces each obligation in the table above to proof. Have someone outside the team pick five obligations at random and find the evidence without help. Fix whatever they could not find.
Common mistakes
StackWeaver view
- Assuming a bank partner's exclusion covers you. The carve-out follows Central Bank supervision of your own entity.
- Treating cloud hosting as an IT detail. Foreign hosting needs its own approval; list every region your vendors use, including backups and support tooling.
- Naming an outside lawyer as the DPO. The law asks for an employee inside the organisation, registered with the PDPC.
- Copying a GDPR programme unchanged. Licensing, the three-working-day notice to individuals and the treatment of financial data as sensitive have no direct GDPR equivalent.
- Leaving consent records unproven. For sensitive data the law asks for consent that is written and express; a pre-ticked box in an app flow will not show that.
- Waiting for the last week. A 90-day decision period means an application filed late may still be pending when the window closes.
- Keeping evidence in inboxes. Inspection rights mean you must be able to show the proof, not only have done the work.
Egypt PDPL evidence checklist
StackWeaver view, built on the sourced obligations above
| Area | Task | Owner | Evidence to keep |
|---|---|---|---|
| Scope | Confirm whether your entity is supervised by the Central Bank of Egypt and whether the Article 3(6) carve-out covers it; record counsel's view. | Legal / compliance | Signed scoping memo |
| Scope | List every processing activity and decide, per activity, whether you act as controller, processor or both. | DPO | Role map per activity |
| Licensing | Complete the PDPC portal's ‘Company Journey’ questions and file the general licence or permit application. | DPO | Application reference and submission receipt |
| Licensing | Identify supplementary approvals needed: foreign cloud or outsourcing, CCTV, direct electronic marketing. | DPO + IT | Supplementary application references |
| Governance | Appoint the in-house DPO, match qualifications to the PDPC category for your record volume, and register them. | Board / CEO | Appointment letter and DPO Registry entry |
| Records | Build the record of processing: data categories, purposes, recipients, retention, transfers and security measures. | DPO | Record of processing (dated) |
| Lawful basis | Record a lawful basis for each activity; collect express written consent for sensitive data, including financial details. | Product + legal | Lawful-basis register and consent records |
| Transparency | Publish a privacy notice that names recipients and countries of transfer. | Legal | Published notice with version history |
| Rights | Run a data-subject request process with logged response dates. | Support + DPO | Request log |
| Security | Map security controls to personal data stores: access reviews, encryption, change management, vulnerability management. | CISO / engineering | Control evidence (reviews, configs, scans) |
| Breach | Test the breach process against the 72-hour and three-working-day clocks with a tabletop exercise. | CISO + DPO | Tabletop report and updated runbook |
| Transfers | Inventory foreign hosting and vendors; complete a transfer impact assessment for each. | IT + procurement | Transfer inventory and assessments |
| Processors | Put written processing terms in place with every vendor that handles personal data. | Procurement + legal | Executed data processing terms |
| Retention | Reconcile retention periods with sector record-keeping rules and schedule deletion. | DPO + finance | Retention schedule and deletion logs |
| Evidence | Assemble an inspection-ready evidence pack that traces each obligation to proof. | DPO | Indexed evidence pack |
Control crosswalk: PDPL to SOC 2 and ISO 27001
Draft mapping, pending named reviewer sign-off. SWC numbers refer to StackWeaver's common controls; SOC 2 references are Trust Services Criteria and ISO references are ISO/IEC 27001:2022 Annex A controls. Use it to reuse evidence, not as a statement that one framework satisfies another.
| PDPL obligation | StackWeaver control | SOC 2 | ISO 27001:2022 |
|---|---|---|---|
| Licence or permit (Art. 4(10)) | SWC-29 Regulatory registration and filings | CC2.3 | A.5.31 |
| Record of processing (Art. 4(9), 5(9)) | SWC-12 Asset, system and data inventory | P4.1 | A.5.9, A.5.34 |
| Lawful basis and purpose limitation (Arts. 3, 6) | SWC-23 Lawful basis and consent | P2.1, P3.1 | A.5.34 |
| Privacy notice (Art. 2) | SWC-24 Privacy notice | P1.1 | A.5.34 |
| Data-subject rights (Art. 2) | SWC-25 Data subject rights | P5.1, P5.2 | A.5.34 |
| Retention and erasure (Arts. 3, 4) | SWC-26 Retention and disposal | P4.2, P4.3 | A.8.10 |
| Security measures (Arts. 4, 5) | SWC-09 Access provisioning and least privilege; SWC-13 Secure configuration baselines; SWC-17 Network security; SWC-18 Encryption and key management | CC6.1, CC6.6 | A.5.15, A.8.24 |
| Breach notification (Art. 7) | SWC-22 Incident response and breach notification | CC7.3, CC7.4 | A.5.24, A.5.26 |
| Data protection officer (Art. 8) | SWC-02 Named accountable roles | CC1.3 | A.5.2 |
| Sensitive data, incl. financial details (Art. 12) | SWC-18 Encryption and key management; SWC-23 Lawful basis and consent | P3.2 | A.5.12, A.5.34 |
| Cross-border transfers (Art. 14) | SWC-28 Cross-border transfer safeguards | CC9.2 | A.5.14, A.5.23 |
| Processor terms (Art. 5) | SWC-07 Third-party and processor management | CC9.2 | A.5.19, A.5.20 |
| Proof of compliance and inspection (Art. 4(12)) | SWC-16 Logging, monitoring and retention; SWC-36 Independent testing of the compliance programme | CC4.1 | A.5.35 |
If you already run a SOC 2 or ISO 27001 programme, much of the security evidence carries over. The gaps are usually licensing, the DPO registration and the Egypt-specific notice clocks. Teams that also operate in Nigeria can compare this with our guides to the NDPA, the NDPA compliance guide and CBN AML/CFT.
Frequently asked questions
When does the PDPL grace period end?
The issuing law gives those covered one year from the date the Executive Regulations were issued. The regulations were published on 1 November 2025 and took effect the next day, so the window closes on or around 1 November 2026. Ask Egyptian counsel to confirm the exact day for your filings.
Does the PDPL apply to banks and payment companies?
Article 3(6) of the issuing law excludes personal data held by the Central Bank of Egypt and the entities it supervises, apart from money-transfer and exchange companies, which must follow the Central Bank's own personal-data rules. Firms outside Central Bank supervision should plan on the PDPL applying in full.
Do we need a licence to process personal data?
Yes, for those in scope. The law requires controllers to obtain a licence or permit from the Personal Data Protection Center, and the PDPC's guidance says processing may start only after one is granted. Licences last three years; permits for specific activities last at most one year.
Is cloud hosting outside Egypt a cross-border transfer?
The PDPC says it is. Its Licenses and Permits Guidelines state that using cloud providers that process or store personal data on servers outside Egypt falls under the cross-border transfer licence or permit. Article 14 of the law also requires an adequate level of protection in the destination country.
How fast must we report a data breach?
Article 7 requires the controller or processor to report a breach to the PDPC within 72 hours of becoming aware of it, or immediately where national security is involved. Affected data subjects must be told within three working days of that report, with the steps taken.
Do we need a data protection officer?
Yes, if you are a company acting as controller or processor. Article 8 requires the legal representative to appoint an employee inside the organisation as data protection officer, registered with the PDPC. The PDPC's guidance sets qualification categories by the number of records an organisation holds.
Is financial data sensitive under the PDPL?
Yes. The PDPC's Key Terms define sensitive personal data to include financial details, alongside health, biometric and children's data. Processing sensitive data needs a PDPC licence and the data subject's express written consent unless the law permits it, and penalties for misuse are among the highest in the law.
What are the penalties for non-compliance?
The law sets fines by offence. Failing core controller or processor duties carries EGP 300,000 to EGP 3 million. Breaching licence rules carries EGP 500,000 to EGP 5 million. Misusing sensitive data or breaking cross-border rules can add at least three months in prison.
Does the PDPL apply to companies outside Egypt?
It can. The criminal provisions reach non-Egyptians abroad where the data concerns Egyptians or foreigners living in Egypt, and Article 4(11) requires a controller based outside Egypt to appoint a representative in Egypt. Foreign fintechs serving Egyptian customers should take advice early.
Has the PDPC fined anyone yet?
We found no enforcement decision published by the PDPC as of our last review. The PDPC's guidance describes the tools it can use after the grace period: warnings, partial or full suspension of a licence, revocation, technical supervision, and publishing proven violations in the media.
How StackWeaver helps
StackWeaver gives your team one workspace to request, collect and review the evidence each obligation above needs, with every file fingerprinted and every review decision recorded. Reviewed evidence can be exported as an Evidence Package that your counsel, an auditor or a partner firm can check offline. We are remote-first; we work with local counsel and advisory partners, and our Evidence Readiness Assessment is the starting point if you want help building the evidence pack.
Next steps
Advisory, audit or legal firm in Egypt? Partner with us
Firms that advise Egyptian fintechs can run client evidence in StackWeaver workspaces and keep their own advice and audit work. Tell us about your practice and we will be in touch.
Partner with usSources and method
We cite the official Arabic text of Law No. 151 of 2020 (Official Gazette No. 28 bis (H), 15 July 2020), Decree No. 816 of 2025 (Al-Waqa'i' al-Misriyya No. 244 (follow-on A), 1 November 2025) and the PDPC's guidelines (Version 1.1, 26 January 2026). The PDPC website did not respond from outside Egypt when we checked, so our links go to the Internet Archive's unaltered copies of the PDPC's own files. English wording of the law is our translation; the Arabic text governs.
Every statement of law on this page is recorded in a public claims ledger with its source, section, retrieval date and the exact supporting words, and our build checks each source before publication. Facts are labelled “Sourced”; opinions and recommendations are labelled “StackWeaver view”, as our editorial policy explains. AI tools helped research and draft this guide; a named person at StackWeaver is accountable for it, and every legal statement was checked against the official text.
Spotted an error? Email [email protected]. More countries are in the Africa Fintech Regulatory Atlas.