Overview
Personal Data Processing Activities Record Guideline – Third: Content Details of Personal Data Processing Activities Records sets out the minimum and extended content requirements that Controllers must document to demonstrate compliance with the Saudi Personal Data Protection Law and its Implementing Regulations.
The guideline explains what information must be captured for each personal data processing activity, how that information supports lawful processing, and when additional details are required due to higher-risk processing. It distinguishes between mandatory records, optional supporting information, and enhanced documentation required when an impact assessment is triggered.
SDAIA's Official Text
The text below reproduces official PDPL law, regulation, or guideline issued by the Saudi Data & AI Authority, verified against the original SDAIA source. No changes or reinterpretation applied.
Third: Content Details of Personal Data Processing Activities Records
The provided template for records of personal data processing activities assists entities in creating comprehensive and exhaustive records of their processing activities. This template facilitates detailed documentation of various information types and establishes meaningful connections between them. The template is structured as follows:
| 🟥 | Mandatory |
| 🟪 | Optional |
| 🟩 | Mandatory in cases requiring an impact assessment process |
| Field | Description |
|---|---|
| Controller Name | Specify the Controller name and relevant contact details. |
| Personal Data Protection Officer Details | Fill in the details related to the personal data protection officer, in the cases requiring its appointment. |
| Processing Activity | Detailed identification of all personal data processing activities aligned with the Controller’s operations and activities. This includes categorizing datasets containing personal data and classifying internal activities that directly handle personal data. |
| Activity Description | A comprehensive description of each personal data processing activity that provides sufficient detail to understand the impact and associated risks of the activity. |
| Activity Start Date | Commencement date of the personal data processing activity. |
| Activity End Date | Date of data destruction and deletion of personal data processing activities records, as the case may be. |
| Business Unit | Name of the business unit responsible for processing activities. |
| Processing Purpose | Clearly and precisely identifying the purpose for processing personal data. For example, marketing or recruitment. |
| Legal Basis | The legal basis to justify the specified purpose of processing personal data. |
| Personal Data Subject Categories | Description of the personal data subject categories whose data is being processed. Examples include employees, clients, members. |
| Processed Personal Data Categories | Description of the personal data categories being processed. Examples include contact details, location, health data, credit data. |
| Personal Dataset Names | Specifying names for the personal datasets. |
| Personal Datasets Owner | Specifying the individual or individuals who own the personal datasets. |
| Personal Datasets Tool or Location | The tools containing the personal datasets being processed or their storage locations. |
| Personal Data Categories Retention Periods | The planned retention period for personal data and, where possible, specific retention periods for each category of personal data. |
| The Entities to which Personal Data Was or Will Be Disclosed | Any entity to which personal data has been or will be disclosed, including documentation of the date of disclosure, method of disclosure, and purpose of disclosure. |
| Categories of Entities to which Personal Data is Being Disclosed | Describing the entities to which personal data is being disclosed. For example, vendors or governmental entities. |
| Personal Data Processor | Specifying the entities or individuals responsible for processing personal data. |
| Obligations between the Controller and Processor | Specifying the agreed-upon obligations between the Controller and Processor. |
| Personal Data Transfer | Describing whether the personal data has been or will be transferred or disclosed to an entity outside the Kingdom, and describing data transfer activities outside the Kingdom, including the legal basis for the transfer and the recipient entities and countries to which the personal data is being transferred or disclosed. |
| Organizational, Administrative, and Technical Measures | Describing, where possible, the organizational, administrative, and technical measures implemented to ensure the security of personal data. For example, encryption, access controls, training, and awareness raising. |
| Obtaining Data Subject Consent | Describing the procedures in place to obtain data subjects’ consent for the processing activity and its purpose. |
| Data Subject Rights | The procedures in place to empower data subjects to exercise their rights as stipulated in the Law. |
| Record Update | Regular reviews of the records of personal data processing activities should be conducted to ensure the accuracy and currency of records. Record keeping is an ongoing process, and the documented information should reflect the current state of personal data processing activities. Records can be updated when planning or commencing new processing activities, considering new purposes, modifying existing information, changing the legal basis or purpose, or altering data subject or personal data categories. |
| Entity Responsible for Latest Update | Entity responsible for the latest update. |
| Sensitive Data | Personal data revealing racial or ethnic origin, religious, intellectual, or political belief, data relating to security or criminal convictions and offenses, biometric or genetic data for identification purposes, health data, and data indicating that one or both of an individual’s parents are unknown. |
| Linking of Files Aggregated from Different Sources | Linking or combining two or more personal datasets obtained from different Controllers, aggregated, or processed from the outset for different purposes or all of the above. |
| Personal Data Processing of Lacks Full or Partial Legal Capacity | For example, underage children and those who lack full or partial legal capacity. |
| Number of Personal Data Subjects Whose Data is Being Processed | Specifying the number of data subjects involved in the processing activity. |
| Large-scale Personal Data Processing | Describing the personal data processing activity involving a large number of data subjects, the volume and type of personal data, the geographical scope of processing, and the different groups of personal data subject categories. |
| Processing Frequency | Specifying the number of times processing occurs and whether it is done continuously, periodically, or at specific time intervals. |
| Data Processing Using Novel Technologies | Describing processing involving novel technological or organizational solutions that have not been fully tested or recognized, or that could lead to risks harming the rights and interests of data subjects. |
| Automated Processing of Personal Data | Describing any form of automated processing of personal data on which decision-making processes are based. |
| Personal Data Processing within a Product or Service | Describing the processing of data embedded in a provided product or service that is likely to cause significant harm to the privacy of data subjects. |
| Personal Data Processing within Any Product or Service Provided to the Public | Description of personal data processing within any product or service offered to the public, according to the nature of the Controller’s activities. |
| Personal Data Breach Incidents Related to the Record | Procedures for reporting any breaches related to the personal data specified in this record. |
| Impact Assessment Procedure Description | Description of the reasons for conducting an impact assessment and whether it is mandatory or optional, as the case may be. |
| Impact Assessment Findings | Findings of the impact assessment after the discovery of a personal data breach and the actions taken in this regard. |
| Latest Impact Assessment Date | Date of the last impact assessment. |
| Impact Assessment Reference | Impact assessment report reference. |
| Summary of Impact Assessment Findings | Summary of the last impact assessment report. |
Plain-Language Explanation
The explanation below is provided to help you understand the SDAIA’s legal text and does not replace or override the official PDPL law, regulation, or guideline.
Mandatory Information Type
Controller Name
Personal Data Protection Officer (DPO) Details
Processing Purpose
Legal Basis
Personal Data Subject Categories
Processed Personal Data Categories
Personal Data Categories Retention Periods
The Entities to which Personal Data Was or Will Be Disclosed
Categories of Entities to which Personal Data is Being Disclosed
Personal Data Transfer
Organizational, Administrative, and Technical Measures
Record Update
Optional Information Type
Processing Activity
Activity Description
Activity Start Date
Activity End Date
Business Unit
Personal Dataset Names
Personal Datasets Owner
Personal Datasets Tool / Location
This field documents the systems or locations where personal data is stored or processed. It supports security management and access control oversight.
Personal Data Processor
Obligations between the Controller and Processor
Obtaining Data Subject Consent
Data Subject Rights
This field describes the procedures implemented to enable data subjects to exercise their rights as stipulated in the Law.
Entity Responsible for Latest Update
Mandatory in Cases Requiring an Impact Assessment Process
Sensitive Data
This field indicates whether the processing involves Sensitive Data, including data revealing racial or ethnic origin, religious, intellectual or political belief, security or criminal data, biometric or genetic data, health data, or data indicating unknown parentage. It supports identification of higher risk processing requiring enhanced safeguards.