PDPL and your CRM: client data to stop collecting
The UAE Personal Data Protection Law (PDPL, Federal Decree-Law No. 45 of 2021) has been in force since 2 January 2022. It says you should collect only the data you need for a specific purpose and not keep it once that purpose is met. For a Bitrix24 portal that boils down to three questions: which fields are surplus, who can open client records, and what happens to the data after the deal.
What the PDPL expects from a company running a CRM
According to the government portal u.ae, the law bans processing personal data without the owner's consent, apart from listed exceptions. One of them matters for sales: processing needed to perform a contract with the client (Article 4). Article 5 requires data to be sufficient for and limited to its purpose, and not kept after that purpose is fulfilled unless it has been anonymised.
The law treats some data as sensitive: family details, racial origin, religious and political views, criminal records, biometrics and health. Clients can ask what you hold about them, correct it, ask for deletion and object to direct marketing. A breach must be reported to the UAE Data Office. Location matters too: DIFC and ADGM have their own data protection laws, and the PDPL does not replace them.
Fields worth dropping from your portal
- Sensitive fields "just in case". Religion, marital status and health notes on a contact record are almost never needed to close a deal.
- Passport and Emirates ID scans in the deal feed. If you need the document for a contract, keep it in one place with restricted access, not as an email attachment anyone can open.
- Fields nobody owns. Every custom field should have a clear purpose. If no one can name it, archive the field.
- History that never expires. Closed and lost deals need a retention period and a rule for what gets deleted or anonymised after it.
Who should see what
Bitrix24 CRM permissions are role based: reps see their own deals, managers see their team, and exporting the database can be limited to one or two people. That is your main protection against the whole client list walking out on a departing employee's laptop. We set roles up from day one as part of Bitrix24 implementation.
What it means for your budget
Auditing fields and roles in a live portal usually takes a few hours at AED 200 an hour, or fits into a support plan from AED 1,250 a month for 5 hours. In a new project from AED 10,000, roles and fields are designed in from the start, so there is nothing to redo later. The payoff is less exposure: the less surplus data you hold, the smaller any breach and the faster you can answer a client asking what you store about them. If your CRM also feeds tax reporting, check the fields from our corporate tax article too. Full rates are on the pricing page.
Quick answers
Do I need client consent just to keep them in the CRM? Not always. Article 4 of the PDPL allows processing needed to perform a contract with the client. Marketing mailings do need consent.
Does the PDPL apply in DIFC and ADGM? No, both have their own data protection laws.
What does a portal clean-up cost? Usually a few hours at AED 200, or a support plan from AED 1,250 a month.
We'll flag surplus fields and set role-based CRM permissions, starting with a short audit
Let us discuss your project
Leave a contact and we reply within a business day. We run a short diagnostic and tell you where to start
