What the law asks of you
In broad terms, PDPL-regulated processing requires a lawful basis, a stated purpose, transparency to the data subject, limits on collection and retention, controls on sharing and cross-border transfers, security safeguards, and a route for individuals to exercise their rights.
Several points deserve care in practice:
- Consent is one basis, not the only basis. Employment, contract performance, and legal obligation often provide a firmer foundation than consent — and consent that is not genuinely free is weak.
- Sensitive data has stricter handling. Health, biometric, genetic, and similar categories require a higher standard and, in some cases, additional approvals.
- Transfers outside Saudi Arabia are regulated. A vendor hosting data abroad is a transfer question, not a procurement detail.
- Breach response is time-bound. The obligation is to assess and notify where required, not to hope the incident stays quiet.
The nine-step checklist
00 of 09 complete
The evidence to keep
A readiness program is judged by what it can produce on request. Keep the evidence with the decisions, not in a folder nobody opens. Auditors, clients, and regulators tend to ask for the same ten items:
- The management decision that appointed the owner and approved the scope.
- The current data map, with a version date and an owner for each process.
- The lawful-basis register, including the reasoning for each purpose.
- The archive of privacy notices, with the date each version went live.
- Consent records showing what was displayed, when, and how withdrawal works.
- A log of rights requests: date received, identity check, outcome, and response date.
- The vendor register, with processing location and transfer assessment for each entry.
- The retention schedule, and evidence that deletion runs as scheduled.
- Training records for staff who handle personal data.
- The incident log, including near misses and the report of the last exercise.
A program with these ten items can answer most questions in a day. A program with only a policy cannot answer any of them.
Roles and responsibilities
The privacy lead coordinates; the business owns the facts. Where a role is unfilled, name the person acting in it. An empty box is a finding, not a plan — and it is the first thing a reviewer will notice.
| Role | Accountable for |
|---|---|
| Data owner | Approves purposes, retention, and access for a process |
| Privacy lead | Runs the program, maintains the map and register, reports progress |
| IT and security | Access control, logging, patching, backup and restore testing |
| HR | Employee data, notices, and training records |
| Procurement | Vendor due diligence and transfer review before signature |
| Marketing | Consent capture, list hygiene, and withdrawal handling |
| Legal counsel | Legal characterization, notices, contracts, and incident assessment |
Where Saudi businesses get stuck
None of these gaps requires new technology to close. They require decisions and a record of those decisions.
- The map stops at IT. Personal data also lives in spreadsheets, inboxes, HR files, and vendor portals.
- Consent is used as a default. It is recorded in a checkbox and never reviewed.
- The privacy notice is copied. It describes international processing the business does not perform, and omits processing it does.
- Transfers are invisible. A cloud tool is adopted by a team, not by procurement.
- Rights have no owner. Requests arrive by email and are answered informally.
- Retention is theoretical. Backups and archives are never addressed.
A 90-day plan
This is not a complete program. It is enough to show regulators, clients, and your own board that the organization is operating a system rather than reacting to events.
| Phase | Focus | Output |
|---|---|---|
| Days 1–30 | Owner, scope, and map | Appointed owner; draft data map for the top five processes |
| Days 31–60 | Basis, notices, vendors | Lawful-basis register; revised notices; vendor and transfer list |
| Days 61–90 | Rights, retention, breach | Rights workflow; retention schedule; tested breach playbook |
When to bring in counsel
Bring in counsel when the processing is sensitive, when a transfer has no clear mechanism, when a regulator or client asks for assurances you cannot support, or when an incident occurs. A lawyer cannot run the data map for you; the business owns the facts. But the legal characterization of those facts should be reviewed before it is committed to a notice, a contract, or a filing.
