Feature
PDPL compliance tracked alongside every other control
Tenant and owner personal data flows through a property management platform constantly — leases, IDs, payment details. Meridian's PDPL module tracks the privacy side of that data with the same rigor as RERA or DLD compliance.
The problem
Privacy obligations under PDPL — consent records, access logs, subject access requests — are usually handled ad hoc, if at all, separate from the rest of compliance tracking.
Why it matters
A data subject access request or a breach incident with no documented process behind it is a regulatory exposure most PM companies haven't actually tested until it happens.
How Meridian helps
- Privacy notices and consent records tracked per tenant and owner
- Access logs showing who viewed or exported personal data, and when
- DSAR (data subject access request) handling tracked from request to response
- Breach incident logging as part of the same 14-control compliance engine covering RERA, DLD, Ejari and Mollak
FAQ
Is PDPL tracked separately from the rest of compliance?
No — it's one of the 14 control areas in the same compliance engine, reviewed and scored alongside RERA, DLD, Ejari and Mollak.
Can I see who accessed a specific tenant's data?
Access logs record who viewed or exported personal data records, providing an audit trail for PDPL accountability.