Skip to content
ENS.EG

Egypt’s Personal Data Protection Law: What It Means for Your App and Website

17 Nov 2026

Law No. 151 of 2020 sets rules for collecting, keeping and transferring customer data. This is not legal advice. It explains what a developer should build into the app or system so the company can comply: consent, collecting less, permissions, logs, and deletion.

Most companies hear about the personal data protection law when a large customer or a foreign partner asks about it, or after something goes wrong. It is better to bring the law into the project at the first meeting, because most of compliance is not legal paperwork. It is design decisions: what we collect, where we keep it, who can see it, and when we delete it.

Egyptian Law No. 151 of 2020 regulates the processing of personal data and establishes a Personal Data Protection Centre that issues licences and receives reports. Implementing details and licences come through executive regulations and decisions, and a lawyer should review them with the company. Our role as developers is to build a system that lets you carry out what your lawyer decides, not to decide for them.

What gets built into the system itself

Clear consent

When a customer signs up or fills in a form, they should know why their data is collected. Consent to marketing messages is a separate choice, not a pre-ticked box and not part of accepting the terms. The system records when the customer agreed and to which wording, so you can show it later.

Collecting less

Every field on a form needs a reason. Date of birth, national ID number and a photo of the ID card are sensitive to store. If the service does not actually need them, do not collect them. Data you never hold cannot leak from you.

Permissions by role

A customer service agent needs the phone number and the order history. They do not need to export the whole customer base. A good system defines what each role sees, restricts bulk export to a named role, and records who exported what and when.

Logs

A log of who opened, changed or deleted a customer’s data is what you need when someone asks who saw it. Without one, any investigation into a leak becomes guesswork.

Deletion and correction

The law gives data subjects rights, including knowing what you hold about them, correcting it, and in some cases having it erased. If the system has no way to do that, every request becomes manual work inside the database, which is a risk in itself.

Where the data lives

The law restricts transferring personal data outside Egypt. Raise that when choosing hosting and third-party services: the server, the email service, the analytics tool, the messaging provider. Write a list of every service customer data passes through and where it is located, and review it with your legal adviser.

When there is a breach

  • Who inside the company is told first, and who decides on notifying the authority and customers?
  • Can you tell which data was affected and since when?
  • Are backups encrypted and stored somewhere other than the same server?
  • Are passwords stored in a way that cannot be read even if the database is stolen?

The law requires breaches to be reported within a set deadline. You cannot meet a deadline when you do not know what happened, which is why logs and alerts are built before they are needed.

Third parties that process your data

The development company, the host, the SMS provider and the customer service tool all process your customers’ data on your behalf, and the company remains responsible for choosing them. Each contract should state the purpose of processing, forbid any other use, and require deletion or handover when the contract ends. Inside the company, name the person who owns data protection and who answers requests from customers and the authority, so a request is not lost between sales and IT.

Start with a simple inventory

Before any change to the code, write a four-column table: what data we collect, why, where it is stored, and who can reach it. That table alone usually exposes fields nobody needs, permissions wider than necessary, and external services everyone forgot. It is also the first thing a lawyer or auditor will ask for.

If you are choosing a company for a new project, ask about these points as part of how to choose a software company, and write them into the development contract. Our custom software development service builds these controls into the system from the start.

To review an existing system or build a new one with these requirements in mind, begin at start your project.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project