Skip to content
Guide 13 min read

Egypt’s data protection law for websites and apps: what Law 151/2020 means for your product

By Manager & CEO, SmartTech Studio

For five years Egypt’s Personal Data Protection Law, Law 151 of 2020, sat on the books without the executive regulations needed to apply it. That changed in late 2025, when the Minister of Communications and Information Technology issued them as Ministerial Decree No. 816 of 2025. The law now has the detail it lacked: how licences are granted, what a data protection officer does, and how the Personal Data Protection Center (PDPC) supervises the market.

If you run an online store, a booking app, a SaaS platform or a company website that collects names, phone numbers, locations or payment details from people in Egypt, this law applies to you. It also applies to businesses outside Egypt that process the data of Egyptians, which matters for regional brands that serve Egypt from Dubai, Riyadh or Abu Dhabi.

This guide is written for owners and product teams, not lawyers. It explains what the law asks for, then turns each requirement into something you can build: a screen, a log, a setting, a process. SmartTech Studio builds websites and apps for Egyptian clients remotely from Abu Dhabi; our Egypt page explains how we work there. This is general information checked against published legal commentary in November 2026, not legal advice, so confirm your licence category and obligations with an Egyptian adviser or the PDPC.

Does Egypt’s data protection law apply to my website or app?

Almost certainly, if you collect data about identifiable people. The law covers personal data processed electronically, in whole or in part, by a “controller” (the business that decides why and how data is used) or a “processor” (a business that handles data on the controller’s behalf, such as a hosting company, a CRM vendor or a development agency running your servers). A contact form, a newsletter sign-up, an account system, delivery addresses, app analytics tied to a device ID and a payment page all involve personal data.

Location is not the only test. Published commentary on the law agrees that it reaches Egyptians and residents of Egypt wherever their data is processed, and non-Egyptians whose data is processed inside Egypt. A store hosted in Frankfurt and run from Dubai that sells to customers in Cairo is in scope.

There are carve-outs. The law does not apply to data people keep for purely personal use, to official statistics, to judicial proceedings and national security matters, or, with some exceptions, to the Central Bank of Egypt and the entities it supervises, which follow banking rules instead. Those exceptions rarely help an ordinary business. Your payment gateway may sit under Central Bank supervision, but your store, your CRM and your app do not.

The practical starting point is to treat yourself as a controller for your customers’ data and to treat every vendor that touches that data as a processor. That framing drives most of what follows: who needs which licence, which contracts you need, and who answers when something goes wrong.

Licences, permits and the data protection officer

The law created the Personal Data Protection Center as the regulator and gave it the power to grant licences, permits and approvals. The executive regulations set out the categories and the process. In broad terms, controllers and processors need a licence or permit from the Center to process personal data, and separate approval is needed for the riskier activities: processing sensitive data, transferring data outside Egypt, and electronic direct marketing. The exact category, fee and documents depend on what you process and how much of it, so this is the point where an Egyptian adviser earns their fee.

Every controller and processor must also appoint a data protection officer (DPO) and register that person with the Center. The DPO is the internal owner of compliance: keeping the records of processing, handling requests from users, reviewing new features for privacy risk, liaising with the Center and leading the response to a breach. In a small company this can be an existing employee with time set aside for it; in a larger one it is a role in its own right. What matters is that the person exists, is registered, and actually has authority to stop a feature that collects data it should not.

For a product team, the licence process has a useful side effect: you cannot apply without knowing what data you hold, where it lives, who processes it and why. That inventory, usually called a data map or record of processing, is the foundation for everything else in this guide, and it is worth building even before the application.

Consent and the other lawful bases

The law starts from consent: personal data may be collected and processed with the explicit consent of the person it relates to. It also allows processing without consent in defined cases, such as when processing is necessary to perform a contract with that person, to comply with a legal obligation or court order, or to protect the person’s vital interests. In practice, an online store does not need a separate tick box to use a delivery address to deliver the order; the contract covers that. It does need consent for things the customer did not ask for, such as marketing messages or sharing data with partners.

Consent has to be real to count. That means a clear statement of what the person is agreeing to, an action they take themselves (not a pre-ticked box), a separate choice for each purpose that is not needed for the service, and an easy way to withdraw it later. Bundling marketing consent into the terms and conditions, or hiding it below a long privacy notice, is the most common way websites get this wrong.

Collect the minimum. The law requires data to be collected for a specific, legitimate purpose and kept no longer than that purpose needs. Every form field should earn its place. If you do not use date of birth, do not ask for it; if a city is enough for delivery pricing, do not ask for a national ID number at sign-up.

Privacy notice, cookies and analytics

People have the right to know what data you hold about them and why. The privacy notice is where you meet that duty for everyone at once. It should be written for your actual product, in Arabic as well as English if your users are Egyptian, and it should name: who the controller is and how to contact the DPO; what data you collect and from where; the purpose and lawful basis for each use; who receives the data (couriers, payment providers, hosting, analytics); whether data leaves Egypt; how long you keep it; and how a user exercises their rights.

A notice copied from a template, or written for European law and never adapted, usually fails on the specifics. It lists purposes you do not have and misses vendors you do. Generate it from your data map, and update both together whenever a feature changes.

Cookies and analytics deserve their own decision. Tags such as advertising pixels, session recording and cross-site tracking are not needed to run the site, and they collect data about behaviour that can identify a person. The safe pattern is a consent banner that loads those tags only after the user agrees, with essential cookies (login, basket, security) kept separate. For analytics, configure the tool to collect less: shorter retention, no advertising features unless you use them, and IP anonymisation where the tool offers it.

Mobile apps follow the same logic. Ask for device permissions such as location, camera and contacts at the moment a feature needs them, explain why in Arabic, and make sure the app still works when the user says no. The privacy answers you give in the App Store and Google Play listings should match the privacy notice and what the app really does.

Electronic direct marketing: SMS, WhatsApp and email

Egyptian businesses lean heavily on SMS and WhatsApp campaigns, and this is the part of the law most likely to change day-to-day habits. Electronic marketing to a person requires their prior consent. Each message has to identify the sender, give a clear and free way to opt out, and the business has to keep records of the consent it relies on. The regulations also bring electronic direct marketing within the Center’s licensing.

For a product, that means four things. A marketing opt-in that is separate from account creation and unticked by default. A consent record that stores who agreed, to what, when, and through which screen or form. An unsubscribe that works on every channel and takes effect quickly. And a suppression list that your CRM and messaging tools check before every campaign, so a customer who opted out on WhatsApp does not receive the same offer by SMS the next day.

Purchased phone lists are the trap. You cannot show consent for numbers you bought, so do not load them into your campaign tools. Build the list from your own customers and sign-ups, and keep the evidence.

Sensitive data: health, financial data and children

The law sets a stricter regime for sensitive personal data. The categories it lists include health data (physical and mental), genetic and biometric data, financial data, religious beliefs, political opinions and security status, and it treats children’s data as sensitive in all cases. Processing sensitive data requires explicit written consent from the person, or from the guardian for a child, as well as the Center’s approval.

This catches more products than owners expect. A clinic booking app that records the reason for the visit holds health data. A fintech feature that stores income or account details holds financial data. A school portal, a kids’ learning app or a nursery’s parent app holds children’s data. A gym app that uses fingerprint or face login holds biometric data.

If your product touches any of these, design for it from the start: collect the sensitive field only where it is truly needed, keep it in a separate table or service with tighter access, encrypt it at rest, log every access to it, and get the consent wording reviewed by an Egyptian lawyer. For card payments, the simplest protection is never to store card data at all: let the gateway’s hosted page or SDK handle it, as we explain in our guide to payment gateway integration in Egypt.

Hosting outside Egypt and cross-border transfers

Most Egyptian websites and apps run on cloud servers outside the country, and most use foreign tools for email, analytics, CRM and customer support. Each of these is a transfer of personal data abroad. The law allows transfers only to a country whose level of protection is not lower than Egypt’s, and only with a licence or permit from the Center, with limited exceptions such as explicit consent of the person for a specific transfer or necessity for performing a contract with them.

You do not have to move everything to an Egyptian data centre, but you do have to know and justify where data goes. List each destination in your data map: the hosting region, the backup region, and every SaaS vendor with the country where it stores data. Then decide, with your adviser, which transfers need the Center’s approval and which fall under an exception.

Two design choices make this easier. Choose a hosting region deliberately and keep production data and backups there, rather than letting each tool pick its own. And send vendors only what they need: an email tool needs an address and a first name, not an order history; a support desk needs the ticket, not the customer’s full profile.

Breaches: the 72-hour clock

If personal data is breached, the law requires the controller and processor to notify the Center within 72 hours of becoming aware of it, and immediately where the breach relates to national security. The people affected must also be informed, within a short period after the Center is notified, together with what was done about it.

Seventy-two hours is not long if you find out on a Thursday night. The time to prepare is before anything happens. Keep logs that let you see who accessed what and when; set alerts for unusual exports or logins; write a one-page response plan that names who decides, who investigates, who drafts the notice and who talks to customers; and keep the DPO’s and hosting provider’s contacts somewhere that does not depend on the system that might be down.

Contracts matter here too. Your processors, including your developers and hosting provider, should be obliged to tell you about a breach on their side without delay, because your clock may start when they find it. For a fuller checklist of technical controls, our article on preventing data breaches was written for UAE law, but the controls themselves apply equally in Egypt.

User rights, and what to build into the product

The law gives people the right to know what data is held about them and to obtain a copy, to withdraw consent, to have inaccurate data corrected, to have processing restricted or data erased once its purpose is served, to object to processing, and to be told about a breach that affects them. Requests should be free of charge in the normal case and answered within a set period. If these requests arrive by email and are handled by hand, they become slow and error-prone as soon as volume grows.

The table below turns the main obligations into product work. None of it is exotic; most of it is good engineering that also makes the system easier to maintain. If you are building a new product, it costs far less to include these from the first sprint than to retrofit them. Our web development and custom software teams build them in as standard for Egyptian clients.

Egypt’s PDPL obligations turned into product features
ObligationWhat to buildWho owns it
Know your dataA data map: each field, its purpose, lawful basis, storage location, vendors and retention periodDPO with the tech lead
Valid consentSeparate, unticked opt-ins per purpose; a consent log with user, version of wording, time and sourceProduct team
Cookies and trackingA consent banner that blocks non-essential tags until the user agreesWeb team
Access and copyA “download my data” function in the account, or an admin tool that exports one user’s dataEngineering
Correction and erasureEditable profiles; a deletion flow that removes or anonymises data across the database, backups schedule and vendorsEngineering with the DPO
RetentionScheduled jobs that delete or anonymise records when their period endsEngineering
Marketing opt-outOne-click unsubscribe on every channel and a shared suppression listMarketing with engineering
Breach readinessAccess logs, alerts on unusual activity, and a written 72-hour response planDPO with operations

Two smaller habits complete the picture. Keep personal data out of places it does not need to be, such as application logs, error reports, analytics events and test databases; use fake or masked data for development. And give staff access by role, so a delivery coordinator sees addresses and phone numbers but not payment history, and remove access the day someone leaves.

Penalties, and how the law fits with e-invoicing and payments

The law sets criminal penalties for violations: fines in Egyptian pounds that rise with the seriousness of the offence and are highest for sensitive data and unlicensed transfers, and imprisonment for some offences. It also makes the responsible manager of a company liable alongside the company where a violation results from a breach of their duties. The Center can, in addition, take administrative measures, including warnings and suspending or revoking a licence. Ask your adviser for the exact figures that apply to your activity rather than relying on a summary.

Data protection does not sit alone. If you sell to consumers in Egypt, your POS or store may already send every sale to the Egyptian Tax Authority under the e-receipt system, and your B2B invoices go through the e-invoice system; our guide to ETA e-invoice and e-receipt integration covers that. Tax law requires you to keep those records, which is a legal obligation and a lawful basis in its own right, so your retention rules should keep invoice data for the tax period while deleting marketing and profile data much sooner. Getting the two regimes to agree is a design decision, best made once in the data map.

A practical order of work

If you already have a live website or app, work in this order. First, build the data map: every form, table, log and vendor, with purpose and location. Second, appoint the DPO and, with your adviser, establish which licence or permit category you fall into and which activities need separate approval. Third, fix the visible items: the privacy notice in Arabic and English, the cookie banner, and separate marketing opt-ins with a consent log. Fourth, close the risky gaps: remove fields you do not need, stop storing card data if you do, restrict access to sensitive fields, and check where backups and vendor data sit. Fifth, build the rights and retention functions and write the breach plan.

If you are starting a new product, put the same list into the brief so it is designed in rather than added later. That is the difference between a privacy page that describes a system and a system that behaves the way the privacy page says.

Sources

FAQ

Is Egypt’s data protection law in force for websites and apps now?

Yes. Law 151 of 2020 was issued in 2020, and its executive regulations were issued as Ministerial Decree No. 816 of 2025, giving the Personal Data Protection Center the detail it needs to license and supervise. Any website or app that processes personal data of people in Egypt should be working to comply now.

Does the law apply if my company and servers are outside Egypt?

It can. Published commentary agrees the law reaches the data of Egyptians and residents of Egypt even when it is processed abroad. A store or app run from the UAE that serves customers in Egypt should assume it is in scope and take advice on licensing and cross-border transfers.

Do I need a data protection officer for a small online store?

The law requires controllers and processors to appoint a data protection officer and register them with the Center. In a small business this can be an existing employee with clear responsibility and time for the role. Check with your adviser how your licence category affects the requirement.

How fast must I report a data breach in Egypt?

The controller and processor must notify the Personal Data Protection Center within 72 hours of becoming aware of a breach, and immediately if it concerns national security. The affected people must also be informed shortly afterwards. Prepare logs, alerts and a written response plan in advance.

Can I send WhatsApp and SMS offers to my customers?

Yes, with their prior consent. Each message must identify you and offer a free, easy way to opt out, and you must keep records of the consent. Keep marketing consent separate from account sign-up, and never load purchased number lists into your campaign tools.

Can I host my Egyptian app’s data on servers in Europe or the Gulf?

Transfers abroad are allowed only to countries with a level of protection not lower than Egypt’s, and generally need a licence or permit from the Center, with limited exceptions such as specific consent or contract necessity. Record every hosting and vendor location in your data map and confirm the route with your adviser.

العربية