Techbanq

Data protection · PDPL

Data protection is enforced by systems, not described by a policy

The law sets obligations on how personal data is processed, where it may be held and how quickly a breach is reported. A policy can state them; only the systems that hold the data can meet them. Readiness is finding the personal data you actually process, then making the controls real in the places it lives.

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The method

Why data-protection work starts with a search, not a policy

An organisation cannot protect data it has not located. The obligations only become controls once the data they apply to has a known home, so the sequence starts there.

STAGE 01

Discover the personal data

Find where personal data actually is — production databases, exports, spreadsheets, a supplier’s system — rather than where the data map says it should be. An inventory of personal data by system, purpose and residency.

STAGE 02

Test the obligations against reality

Compare where the law expects the data to be and who may reach it against where it is and who actually can. A gap list tied to specific systems, not abstract clauses.

STAGE 03

Make the controls real

Implement residency, access, retention and consent handling in the systems themselves, so the obligation is enforced rather than promised. Controls that hold at runtime, with the evidence they are working.

STAGE 04

Prepare to detect and report

Build the ability to notice a breach and notify within the required window, and rehearse it before it is needed. A tested detection-and-notification procedure against the timeline.

Why the policy is not the work

The consent nobody could actually withdraw

The gap that catches organisations is not the missing policy; it is the policy that describes a capability the systems do not have. A privacy notice promises a customer can withdraw consent or ask for their data to be deleted, and then the request arrives and the data is spread across four systems, two exports and a supplier, with no way to act on it in one place. The obligation was written down and never made real, and a document is exactly the wrong place to discover that.

So we treat readiness as an engineering exercise that a legal reading guides, not the other way round. Your own legal and compliance function owns what the law requires of you; our job is to make the systems capable of meeting it — to find the data, enforce the residency and access rules where it lives, and build the deletion, retention and breach-notification paths so the promises in the notice are ones the organisation can actually keep.

Our role

Where engineering ends and your legal reading begins

We build the controls; the interpretation of the law stays with the people accountable for it.

  1. 01

    Discovery and mapping

    We find the personal data you actually hold and map it to systems, purposes and residency, because everything after this depends on the map being real rather than aspirational.

  2. 02

    Controls in the systems

    We implement residency, access, retention, deletion and consent handling where the data lives, so an obligation is enforced by the system rather than asserted by a document.

  3. 03

    Breach detection and drill

    We build the capability to notice and report a breach within the required window and rehearse it, because a notification obligation is only met if the clock can actually be started in time.

What the law requires of your specific organisation is a determination for your legal and compliance function, not a supplier; we make your systems capable of meeting the reading they arrive at, and give them the evidence that the controls are working.

A note on residency

Where the data sits is a decision you have to be able to prove

Data residency is the obligation most often assumed and least often proven. A team believes its data stays in the Kingdom because the primary system is hosted there, and does not notice the analytics export, the backup replica or the third-party integration that quietly moves a copy elsewhere. Residency is not where you host the main database; it is where every copy of the data ends up, including the ones a supplier makes. We trace those paths and close them, so the residency you claim is one you can demonstrate rather than one you hope holds.

Common questions

What buyers ask

Is PDPL readiness a legal project or a technical one?+

Both, in that order of dependency: a legal reading tells you what the obligations mean for your organisation, and engineering makes the systems capable of meeting them. The failure we see most often is a strong legal analysis paired with systems that cannot actually enforce it — a policy that promises deletion the systems cannot perform, or residency the integrations quietly break. We work alongside your legal and compliance function rather than replacing it: they own what the law requires, and we make the data discoverable and the controls real so the requirement is met in practice, not only on paper.

We already have a privacy policy. Isn’t that most of the work?+

A privacy policy is the statement of intent, not the capability. The harder and larger part is making every promise in it something the systems can actually do: locating all the personal data including the copies in exports and suppliers’ systems, enforcing who may reach it, and being able to delete or export it on request from one place rather than four. Most organisations have a reasonable policy and a gap between it and their systems, and that gap is exactly what a data-protection review finds and closes.

How does data residency actually get verified?+

By tracing every copy, not by checking where the main system is hosted. We follow the data outward from the primary store to backups, analytics exports, logging platforms and third-party integrations, because those are where residency quietly breaks — a copy replicated to another region, an export to a tool hosted abroad, a supplier who processes elsewhere. The verified position is one where every path a copy of the data can take has been mapped and either kept in the Kingdom or closed, so residency is something you can demonstrate to a reviewer rather than an assumption about the primary database.

Find the data first

A data-protection readiness plan that starts from a map of the personal data you process and names the controls each system needs to enforce the obligations in practice.

Start the conversation