If your app serves people in Egypt and its prompts carry their names, phone numbers, voice notes or ID photos, an LLM or speech-to-text API hosted abroad turns each request into a cross-border transfer. Egypt regulates that more tightly than most. This post sets out what Law 151 of 2020 and its executive regulations say, then gives a developer checklist. It is not legal advice; confirm your case with Egyptian counsel.
The article numbers below come from an English translation of the law and of Ministerial Decision No. 816 of 2025, hosted by the law firm Andersen in Egypt and read on 15 November 2026. It is not an official text. The Arabic text in the Official Gazette is the one that counts. For Saudi Arabia and the UAE, see the Saudi and UAE PDPL checklist.
When does an API call fall under Law 151?
Four definitions in Article 1 of the Personal Data Protection Law decide it:
- Personal data is any data about an identified or identifiable person, directly or indirectly, including name, voice, image, ID number and online identifiers.
- Processing covers almost any electronic operation, including sending, receiving, storing and analysing.
- Sensitive personal data includes health, genetic and biometric data, financial data, religious beliefs, political opinions and security status. Children’s data is always sensitive.
- Cross-border personal data flow is the transfer, storage, processing or making available of personal data from inside Egypt to outside it, or the reverse.
So a support bot that sends a customer’s complaint with their phone number to a model hosted in the US is in scope. So is a WhatsApp voice note sent for Egyptian Arabic transcription, because the voice itself is personal data. A prompt with no personal data in it is not a personal data transfer, which is why minimisation comes first below.
Two scope notes from the issuance articles. The law covers electronically processed data about natural persons only. Issuance Article 3 excludes data held by the Central Bank of Egypt and the entities it supervises, apart from money transfer and exchange companies, which follow the Central Bank’s own rules.
What do Articles 14 to 16 say about transfers?
| Article | What it says |
|---|---|
| 14 | Transfer, storage or sharing abroad is prohibited unless the destination’s protection is not lower than the law’s, and subject to a licence or permit from the Center |
| 15 | Transfers to a country without adequate protection may be allowed with the data subject’s explicit consent, in listed cases: medical care, legal claims, a contract for the data subject’s benefit, judicial cooperation, public interest, money transfers, or an international agreement Egypt is party to |
| 16 | Making data available to a controller or processor abroad needs a licence and three conditions: compatible purposes, a legitimate interest, and protection not lower than Egyptian law |
Article 42 sets imprisonment of at least three months and a fine of EGP 500,000 to EGP 5,000,000, or either, for breaching Articles 14 to 16. Article 45 sets the same fine range for breaching the licence and permit rules.
What do the executive regulations add?
The translated regulations are Decision No. 816 of 2025 of the Minister of Communications and Information Technology. CMS, a law firm, reports that they were issued on 1 November 2025 and made public on 25 December 2025. For an API buyer, five provisions matter most:
| Regulation article | What it adds |
|---|---|
| 16 | A licence or permit based on the Center’s adequacy assessment of the destination; the data subject’s consent before the transfer; transfers only to the countries named in the licence; the Center keeps the list of adequate countries |
| 17 | Disclosure to a controller or processor abroad needs a licence, compatible activities and equivalent protection |
| 24 | A legal person’s transfer licence application names the destination, the recipient’s activity, the data categories, volume and retention period, and the temporary and final storage locations |
| 26 | Applications go through the Center’s portal; the Center has up to 90 business days, and silence counts as rejection |
| 27 | The transfer licence fee is 50% of the controller or processor licence fee |
Article 24 matters for LLM APIs. You must say where the data will be stored, even briefly. That means you need a written answer from your provider on processing location and retention before you can file.
When must you comply?
Issuance Article 6 gives entities one year from the issuance of the executive regulations to bring their processing into line. CMS reads that as enforcement from 1 November 2026, and notes some uncertainty about whether the Center may treat the grace period as running to the end of 2026. On the strict reading the grace period ended on 1 November 2026; on the later reading it runs to the end of 2026. CMS also says the Center has published operational guidelines, with more expected on impact assessments, cross-border transfers and breach handling. Check the Center’s current guidance before you rely on any detail here.
What else applies to an LLM pipeline?
- Sensitive data needs its own licence. Article 12 bars collecting, transferring, storing or processing sensitive data without a licence from the Center, with written explicit consent. Invoices and bank statements read by a vision model are financial data. Children’s data needs a parent’s or guardian’s consent.
- Local representative. Articles 4 and 5 require a controller or processor outside Egypt to appoint a representative in Egypt. Regulation Article 3 says the Center approves that representative for the term of the licence.
- Breach notice. Article 7 gives 72 hours to notify the Center, immediately where national security is involved, and three working days to inform the data subject.
- Records. Article 4 requires a controller’s register to include cross-border transfer details and the security measures used.
- Data protection officer. Article 8 requires every legal person acting as controller or processor to appoint and register one.
Which questions should you ask an LLM API provider?
| # | Question | Why Egyptian law cares |
|---|---|---|
| 1 | In which country are my requests processed, for each model? | Regulation Article 24 asks for destinations |
| 2 | Is anything stored, even temporarily? Where, and for how long? | Article 24 asks for temporary and final storage locations and retention |
| 3 | Are any models partner-hosted? By whom, and where? | Each recipient is part of the transfer |
| 4 | Will you commit to a processing location in writing? | Licences name specific countries |
| 5 | Is my data used to train or evaluate models? | Law Article 3 (not the issuance or regulation Article 3) requires processing to fit the declared purpose |
| 6 | What metadata do you keep, and does it contain personal data? | Logs are processing too |
| 7 | How fast will you tell me about a breach? | You have 72 hours to notify the Center |
| 8 | Can I restrict keys to my servers? | It limits who can send data at all |
For the GDPR version of this list see GDPR and LLM APIs: 15 questions. For the retention side see the zero data retention checklist.
How do you minimise what leaves Egypt?
- Strip identifiers before the call. Replace names, national ID numbers, phone numbers and account numbers with placeholders, and map them back afterwards. Sending sensitive data to an LLM API shows the pattern.
- Send only the fields the task needs. A ticket classifier needs the complaint, not the customer record.
- Treat audio and images as personal data. Crop ID photos to the fields you need. For voice, decide whether a transcript made in Egypt would do instead.
- Keep children’s and health data out unless you hold the licence and consent Article 12 requires.
- Log less. Store token counts and cost, not prompts: usage logging with PII redacted.
- Lock keys to your servers with an IP allow-list.
Minimisation reduces what you transfer. It does not remove the need for a lawful basis for whatever personal data still leaves the country. See PII, data residency and the PDPL glossary entry for the terms.
Where BroadNet Inference fits
BroadRouter is BroadNet’s own website, so weigh this accordingly. BroadNet’s inference privacy statement says its own models and the open-weight models it hosts run on BroadNet-owned or leased hardware in the United States, with partner capacity as backup. DeepSeek V4.1 Flash is partner-hosted. There is no self-serve region choice. BroadNet’s Terms (§7.3a) say: “Contact us to agree processing locations for your deployment before sending data with residency requirements.”
So a request from Cairo to BroadNet Inference is a transfer to the US. Under Egyptian law you need the licence, consent and adequacy analysis above before personal data goes into it. If you need processing inside Egypt, BroadNet is not the default fit. Agree a location with BroadNet in writing first through the contact page, or choose an in-country option. Self-serve has no SLA (Terms §7.4).
What BroadNet does offer is retention that is simple to describe in a licence application. “Inference content is not retained. Necessary account, billing and security metadata is retained as described in our privacy statement.” Its API reference says prompts, audio, images, answers and transcripts are not kept. Read the details on zero data retention and BroadRouter’s own privacy page. For Egyptian Arabic audio, BroadNet says its Transcribe Arabic model covers Egyptian dialect; see Arabic transcription and test it on your own recordings.
