PDPL Compliance for Marketing Agencies in Egypt

PDPL playbook for Egyptian marketing, CRM and growth agencies handling client data. Processor obligations, DPAs with brands, pixel ownership, audience uploads.

Frequently asked questions

Are we a processor or a controller?

Usually a processor on behalf of the brand for campaign and CRM data; sometimes a joint controller if you're co-deciding the purpose. Often controller for your own agency CRM, leads and prospects.

Can we keep using Meta / Google Customer Match?

Yes, with the brand's instruction in writing, valid consent from the underlying customers for the channel, and the platform's own data-processing terms accepted at account level.

What about scraping public data for outreach?

Scraped data is still personal data under PDPL. Cold outreach without a clear lawful basis (and a frictionless opt-out) is a complaint magnet. Run lead-gen through opt-in inputs instead.

Do we need to register with PDPC?

Most agencies fall under the controller/processor licensing regime in Decree 816/2025. Plan to register before enforcement starts in November 2026.

How do we handle a brand that asks 'where is our data?'

Maintain a current sub-processor list with regions. Be ready to point to encryption, access controls, and retention policies. A short trust page beats sending a different deck per RFP.

Explore Polily

  • Polily home — PDPL compliance for Egypt
  • Egypt PDPL compliance hub
  • Free PDPL privacy policy generator
  • PDPL readiness quiz
  • Find a verified PDPL lawyer in Egypt
  • PDPL founders' checklist
  • Polily blog — PDPL guidance
  • Pricing