Thiqa

We provide your data protection officer.

A qualified DPO appointed to your entity in Egypt, managing your PDPL requirements and equipped with Thiqa’s agentic platform.

Early access · work email only

Your DPO faster than others

Personnel

Appointed officers and the approvals that carry their name

Your data protection officer

Qualified appointment · monthly engagement · appointed 1 March

Active
Your Egypt entityCBE · PDPLAppointed
Your UAE entityCBUAE · ADGMAppointed
Your holding companyGroup — no licenceNot in scope

Approvals

4 this month
ArtefactAnswersDateApproved by
Records of processing — Q3PDPL · controller record12 MarApproved
Data subject request logPDPL · rights handling9 MarApproved
Processor due diligence — 4 vendorsPDPL · processor oversight3 MarApproved
Breach response runbookPDPL · incident dutiesTodayAwaiting officer
Approval, recorded against the obligation it answers.

Yours works inside Thiqa, gaining all of our agents advantages of speed, accuracy and traceability

How your DPO is appointed

From first call to an appointed officer in four steps.

  1. 01

    Scoping call

    We learn your entities, licences and data flows in thirty minutes. You leave knowing which grade DPO you need and what to expect from PDPL licensing.

  2. 02

    Matching

    We match a qualified DPO to your sector, you meet them and approve them before anything is signed.

  3. 03

    Onboarding

    Your DPO arrives with the Thiqa platform on day one, scoped to what each entity actually has to meet. Your record of processing starts immediately as automated evidence collection begins supervised by the DPO.

  4. 04

    Ongoing work

    Every decision, request and approval is recorded as it happens, and your board gets a report on where things stand.

Who must appoint a DPO under Egypt’s PDPL

Most likely, yes, if your entity processes personal data. The duty applies to each licensed entity, not just the parent company, so a group may need more than one appointment. Confirm your status with counsel.

View source →

They own how your organisation handles personal data and are the named contact when anyone asks. In practice, that means keeping the record of processing current, assessing new processing before it launches, answering data subject requests, handling breaches, reviewing processors and transfers, and reporting to the board.

Not appointing is a compliance failure on its own, even if nothing ever happens to your data. It usually surfaces as a finding: an unanswered request, an unreported breach, or a question about who owns data protection that nobody can answer with a name.

This section describes the general shape of the obligation. It is not legal advice.

Don’t hire anyone. Get the real outcome.