PDPL data requests are requests from individuals to exercise applicable rights over their personal data held by a business. A customer may want to know what information an organisation holds, obtain access to it, correct inaccurate details or request deletion where the applicable requirements allow it. Saudi businesses need a clear process for receiving, assessing and handling these requests across their websites and internal systems.
The challenge is not simply answering an email. Customer information may be spread across website forms, CRM records, email platforms, WhatsApp conversations, support tools and external service providers. A request must be understood, routed to the right people and assessed against the Saudi Personal Data Protection Law (PDPL), its Implementing Regulations and the circumstances of the processing. This is also why data-request handling should be considered when planning a website or digital system implementation.
A practical process helps your organisation respond consistently, protect personal information during verification and avoid promising actions that may not be legally or technically appropriate.
What are PDPL data requests?
PDPL data requests are communications from individuals seeking to exercise rights relating to their personal data. Depending on the circumstances and applicable requirements, these may include requests to be informed about processing, access personal data, obtain a copy in a readable format, correct or complete information, request destruction where applicable, or withdraw consent when processing relies on consent.
The exact right, conditions and response obligations depend on the applicable legal provisions and the facts of the request. A deletion request, for example, should not automatically be treated as an instruction to erase every record immediately. The organisation may need to assess whether it has a lawful reason or obligation to retain particular information.
SDAIA's guidance on the PDPL provides supporting explanations of data-subject rights and the responsibilities of organisations that process personal data. Businesses should refer to the law and its regulations for the binding requirements and seek qualified advice where the circumstances are unclear.
The important operational point is that a request should not disappear into a general customer-service inbox. It needs an identifiable owner, a documented assessment and a controlled response.
Which customer rights should your team understand?
Your employees do not need to become legal specialists, but the people handling customer information should recognise the types of requests that may involve personal data rights.
Common request types include:
- Information about processing: An individual asks whether their personal data is being processed and wants to understand relevant details about that processing.
- Access to personal data: An individual asks to access personal information held by the organisation, subject to the applicable requirements.
- Obtaining a copy: An individual requests a copy of their personal data in a readable or otherwise applicable format.
- Correction or completion: An individual identifies information that is inaccurate, incomplete or out of date and asks for it to be corrected or completed.
- Destruction of personal data: An individual asks for personal data to be destroyed where the applicable conditions for doing so are met.
- Withdrawal of consent: An individual withdraws consent where consent is the legal basis for the relevant processing.
These requests can arrive in ordinary language. A customer may write, "Please show me what information you have about me," or "Remove my details from your records." Your staff should recognise the potential privacy request even if the customer does not use formal legal terminology.
It is also important to distinguish a privacy-rights request from an ordinary account or service request. A customer asking to update a delivery address may need a routine account change. A customer asking for all personal information held by the business may require a more formal privacy assessment.
PDPL data requests: How to receive and record them
A reliable process starts with making it easy for individuals to contact the organisation. They should not have to guess which department handles privacy questions or search through unrelated website pages to find a contact method.
Your organisation can provide a dedicated privacy contact address, a suitable website contact route or another controlled channel. Whatever method you choose, make sure the relevant employees know how to recognise and forward a request.
When a request arrives, record the information needed to manage it:
- Date the request was received.
- Contact details supplied by the requester.
- The right or action the individual appears to be requesting.
- Relevant account, service or transaction references, where available.
- Systems or departments likely to hold the information.
- Verification steps taken and their outcome.
- The person or team responsible for assessment.
- Decisions, actions and communications relating to the request.
Keep the record proportionate. Do not collect additional sensitive information simply because a customer has made a privacy request. The purpose of recording is to manage the request securely and demonstrate how it was handled.
A central register can help management see which requests are open, who owns them and whether further information or internal review is needed. Access to this register should be restricted to employees who need it for their responsibilities.
How should you verify the identity of the requester?
Before disclosing personal information or making changes to a customer record, the organisation should take appropriate steps to establish that the requester is entitled to make the request.
Verification should be proportionate to the sensitivity of the information and the risk of unauthorised disclosure. A request relating to a basic contact preference may require a different approach from a request for a copy of a detailed customer record.
Consider the following principles:
- Use an existing authenticated customer account where it is appropriate and secure.
- Check information already held by the organisation without asking for unnecessary additional data.
- Use a suitable verification process for requests involving sensitive or extensive records.
- Avoid sending personal information to an email address or telephone number that has not been appropriately verified.
- Keep a record of the verification method and its outcome.
- Escalate cases where identity or authority remains uncertain.
Do not ask customers to send passwords, full payment-card details or unrelated identity documents through an ordinary contact form. If additional evidence is genuinely needed, use a controlled process and explain why it is required.
Requests made by someone acting on behalf of another individual may require additional checks to establish their authority. The organisation should assess these cases according to the applicable requirements rather than assuming that any person contacting customer support can act for the data subject.
How to handle a request to access personal data
An access request requires the organisation to identify the relevant personal data and assess what can appropriately be provided under the applicable rules.
Start by identifying the systems that may contain information about the requester. These might include:
- Website accounts and enquiry forms.
- CRM and sales records.
- Customer support tickets.
- Email correspondence and subscription platforms.
- WhatsApp business conversations.
- Booking, order or service-management systems.
- Relevant records held by service providers processing information on the organisation's behalf.
Search using reliable identifiers and take care not to confuse the requester with another person who has a similar name or contact detail.
Before providing a copy, review the material for information about other individuals, confidential content and any applicable restrictions. The organisation should not disclose another customer's personal information simply because it appears in the same conversation or document.
Prepare the response in a readable and secure format. Confirm that the recipient is verified and use an appropriate delivery method. Avoid attaching an unrestricted export of an entire CRM record when a more focused response is suitable.
If the organisation cannot provide some requested information, it should assess the reason under the applicable requirements and communicate the outcome appropriately. Staff should not invent a reason or make a blanket refusal without review.
How to assess customer deletion requests
Deletion requests require particular care because businesses may hold information for different purposes and under different legal or operational obligations.
When a customer asks for information to be deleted, first identify the records covered by the request. Then assess the purpose for which each relevant category is held and whether the applicable requirements allow or require it to be retained or destroyed.
For example, a customer may ask an online retailer to remove an old marketing profile. That profile may be separate from transaction or accounting records that the business must assess under other applicable obligations. The organisation should not assume that the same deletion decision applies to every record.
A structured assessment should consider:
- What personal data is covered by the request.
- Which systems and service providers hold the relevant information.
- The original and current purposes of processing.
- Whether a legal or other applicable basis supports continued retention.
- Whether the conditions for destruction have been met.
- Whether information can be removed, restricted or otherwise handled appropriately.
- How the outcome should be communicated to the individual.
Where deletion is appropriate, coordinate the action across relevant systems. Removing a CRM record while leaving the same unnecessary information in a connected marketing platform may leave the underlying problem unresolved.
Where information must or may lawfully be retained, do not simply ignore the request. Document the assessment and explain the outcome in a clear and appropriate way, subject to the applicable requirements.
How to coordinate requests across CRM, email and WhatsApp
A request may affect several systems, even when the customer contacts only one department. This is common when sales, marketing and customer support use separate platforms.
For example, a service customer may appear in a CRM, an email subscription list, a WhatsApp conversation and a support system. An access or deletion request may require the organisation to identify information across these locations and coordinate the response.
Create an internal process that identifies the system owners and explains how privacy requests are passed between departments. The process should cover both information stored directly by the organisation and relevant processing carried out by service providers.
Review these operational questions:
- Who can search each system for customer information?
- Which team is responsible for approving access or deletion actions?
- How are requests communicated to external processors where necessary?
- How are marketing preferences and withdrawals reflected in connected platforms?
- How does the organisation avoid deleting information belonging to the wrong person?
- How are completed actions recorded?
Your PDPL website checklist covers the wider website and customer-data practices that should support this process. The objective here is to turn those responsibilities into a working request-handling procedure.
Common mistakes when responding to PDPL data requests
Even organisations with a published privacy policy can struggle when a real request arrives. The most common problems are usually operational rather than caused by a lack of policy wording.
Watch for these issues:
- No clear contact route: Customers do not know where to send privacy requests, and employees do not know where to forward them.
- Treating every request as a deletion instruction: Access, correction, information and destruction requests require different assessments.
- Skipping identity checks: Disclosing records without suitable verification can expose personal information to an unauthorised person.
- Searching only one platform: Relevant information may exist in CRM, email, support and external service-provider systems.
- Deleting records without assessing retention: Some information may need to be retained under an applicable legal or other basis.
- Ignoring connected systems: An action in one platform may not update other systems holding the same information.
- Failing to document decisions: Without a record, the organisation may struggle to explain how it assessed and handled the request.
- Making unsupported promises: Employees should not promise immediate deletion or unrestricted disclosure before the request has been assessed.
Training customer-facing teams to recognise requests and follow an escalation process can reduce these problems. The process should be easy to use, not buried in a policy document that employees rarely consult.
Building a practical data-request workflow
A workable procedure does not need to be complicated. It needs to assign responsibility and provide a repeatable path from receipt to closure.
A practical workflow can follow these stages:
- Receive: Accept the request through an identified channel and acknowledge it appropriately.
- Record: Create a controlled case record with the request details and responsible owner.
- Verify: Confirm identity or authority using proportionate checks.
- Clarify: Ask for clarification when the requested action or relevant information is unclear.
- Locate: Identify the systems, departments and service providers likely to hold relevant information.
- Assess: Review the request against the PDPL, its Implementing Regulations and the circumstances of processing.
- Act: Complete the appropriate access, correction, deletion or other action where applicable.
- Review: Check that the action has been applied consistently across relevant systems.
- Respond: Communicate the outcome securely and clearly.
- Close: Record the decision, actions taken and relevant communications.
Assign a process owner who can coordinate between customer support, marketing, IT and management. The legal or compliance adviser should be involved when a request raises uncertainty about the applicable rights, restrictions or retention obligations.
How LtsThink can help improve your data-request process
At LtsThink, we help businesses connect website functionality, customer-management systems and digital workflows. This can include reviewing how personal information enters the organisation, where it is stored and how internal teams can locate and manage it when a request is received.
Depending on the project, our technical work can include:
- Reviewing website forms and customer-account data flows.
- Mapping CRM fields and connected customer records.
- Improving internal request-routing and case-tracking workflows.
- Connecting relevant systems so authorised teams can locate records more consistently.
- Reviewing access permissions and administrative roles.
- Supporting coordinated updates across CRM and marketing integrations.
- Documenting technical processes for internal review and ongoing improvement.
The exact implementation depends on the systems your business already uses and the responsibilities established by its privacy and legal teams. We do not provide legal certification or replace a qualified legal adviser. Instead, we can help implement the technical processes that support the organisation's approved approach.
Explore our web development services to see how website forms, customer portals and business systems can be designed around practical operational requirements.
What should your business do next?
Review how customers currently contact your organisation and whether employees can recognise a request involving personal data. Identify the systems that hold customer information and the people responsible for each system.
Then document a process for receiving, verifying, assessing and responding to requests. Include access, correction, deletion and consent-withdrawal scenarios where relevant. Make sure the process considers retention requirements and information held by connected service providers.
Test the workflow internally using a hypothetical customer request. Check whether the right teams can locate the relevant information, verify the requester, assess the action and record the outcome securely.
Finally, review the process whenever your business changes its website, CRM, customer-support tools or marketing integrations. New systems can create new places where personal data is stored, so the request-handling procedure should evolve with the organisation.
A clear process makes it easier to respect individual rights while protecting customer information and maintaining appropriate business records. Confirm the specific legal requirements for your organisation with SDAIA guidance and a qualified legal adviser.
This article provides general information, not legal advice.
Work with us: Need help with PDPL compliance in Riyadh, Jeddah or elsewhere in the Kingdom? If your website and business systems need a more organised way to locate, review and manage customer information, explore our web development services or contact LtsThink to discuss your requirements. We can review your forms, CRM structure and internal workflows, then provide a fixed-price proposal after a short call based on the agreed scope.
FAQ
What are PDPL data requests?
They are requests from individuals to exercise applicable rights relating to their personal data. Depending on the circumstances, these may include requests for information, access, a copy, correction, destruction or withdrawal of consent where consent is the basis for processing.
Can a customer ask a Saudi business to delete all their personal data?
An individual may request destruction of personal data where the applicable conditions are met. The organisation should assess the information involved and whether any applicable legal or other basis supports continued retention before deciding what action to take.
How should a business verify someone requesting access to personal data?
Use proportionate identity checks suited to the sensitivity and scope of the information. Avoid disclosing personal data until the requester or their authorised representative has been appropriately verified.
Do deletion requests need to be applied to CRM and marketing platforms?
The organisation should identify relevant systems and service providers that hold the information and coordinate appropriate actions across them. The required action depends on the request, the applicable legal requirements and any valid retention basis.





