User Questions On PDPA 2010 & Personal Data Protection Answered By Lawyers

83 Questions On PDPA 2010 & Personal Data Protection Answered By Lawyers

Table of Contents

Though we have in-depth guides on many areas of the PDPA 2010, personal data protection obligations often raise questions specific to a business’s legal or commercial circumstances that may not be addressed in detail elsewhere.  

In this article, the ELP team answers these questions, consolidating over 5,000 unique queries into what we believe is the most complete list of questions on Malaysia’s PDPA 2010, updated for the 2024 amendments. 

Of course, feel free to skip the reading and get in touch for a free consultation. 

Otherwise, click on the relevant area in the table of contents to skip to that part. 

PDPA basics 

These questions cover what the PDPA is, who it applies to, who enforces it and how the 2024 amendments changed it. For full details, see our PDPA 2010 summary for Malaysian SMEs and our overview of the 2024 amendments. 

What is the PDPA? 

The Personal Data Protection Act 2010 (PDPA) is Malaysia’s law governing how organisations collect, use, store and disclose personal data in the course of commercial transactions. 

It sets out seven data protection principles that organisations must follow and gives individuals rights over their own personal data. The PDPA was amended by the Personal Data Protection (Amendment) Act 2024, which introduced mandatory DPOs, breach notification, data portability and higher penalties. 

What are the seven data protection principles under the PDPA? 

The PDPA sets out seven principles that every organisation in scope must follow:  

  1. General (consent) 
  2. Notice and Choice 
  3. Disclosure 
  4. Security 
  5. Retention 
  6. Data Integrity 
  7. Access 

            Together they govern how personal data is collected, used, shared, protected, kept and corrected. For a plain-English explanation of each, see our guide to the 7 principles of Malaysia’s PDPA. 

            Is there a data protection law in Malaysia? 

            Yes. The PDPA is Malaysia’s main data protection law and applies to personal data processed in commercial transactions. 

            Separately, organisations designated as national critical information infrastructure (NCII) entities have cyber security obligations under the Cyber Security Act 2024, which covers incidents affecting their systems rather than personal data as such. See how cyber security incident reporting differs from PDPA data breach notification. 

            The DPO role is also distinct from that of a chief security officer, although the two are sometimes confused. See our guide to the difference between a DPO and a CSO. 

            Is the PDPA compulsory in Malaysia? 

            Yes. Any organisation that processes personal data in commercial transactions must comply with the PDPA, regardless of its size. It applies to: 

            • any person or commercial organisation established in Malaysia, and 
            • foreign organisations that use equipment in Malaysia to process personal data, other than merely for transit through Malaysia 

            It does not apply to: 

            • the federal and state governments, or 
            • personal data processed purely for personal, family or household purposes 

            Compliance with the seven principles is compulsory for every organisation in scope, but registration with the Commissioner is only compulsory for 13 prescribed classes of businesses (see the registration section below). 

            When was the PDPA enacted? 

            The Personal Data Protection Act 2010 (PDPA) received Royal Assent on 2 June 2010, was published in the Gazette on 10 June 2010, and came into force on 15 November 2013. 

            What were the key amendments to the PDPA in 2024? 

            The Personal Data Protection (Amendment) Act 2024 made eight main changes: 

            Area Before After the 2024 amendments 
            Terminology ‘data user’ ‘data controller’ 
            Biometric data not defined defined and classed as sensitive personal data 
            Data processors not bound by the Security Principle must comply with the Security Principle 
            Penalties fines up to RM300,000 and up to 2 years’ imprisonment fines up to RM1,000,000 and up to 3 years’ imprisonment 
            Data Protection Officers no requirement mandatory for organisations meeting set thresholds 
            Breach notification no requirement notify the Commissioner within 72 hours and affected individuals within 7 days where significant harm is likely 
            Data portability no right individuals can ask for their data to be transferred to another data controller 
            Cross-border transfers only to places on a Ministerial whitelist (never gazetted), or on specified grounds whitelist removed; allowed to places with substantially similar laws or adequate protection, with the existing grounds retained 

            The amendments came into force in phases. The first phase, on 1 January 2025, covered largely administrative changes.

            The second, on 1 April 2025, brought in the ‘data controller’ terminology, biometric data as sensitive personal data, the Security Principle for data processors, the higher penalties and the new cross-border transfer regime. The third, on 1 June 2025, introduced mandatory DPOs, breach notification and data portability. 

            Which department is in charge of the PDPA? 

            The PDPA is administered by the Personal Data Protection Department (PDPD, or Jabatan Perlindungan Data Peribadi), and enforced by the Personal Data Protection Commissioner (PDPC). Organisations deal with the Commissioner for matters such as data controller registration, DPO registration through the SPDP system and data breach notifications. 

            Does the PDPA apply to non-Malaysian citizens? 

            The PDPA applies based on who processes the data and where, not on the nationality of the individual. A business established in Malaysia must handle the personal data of foreign customers, employees and job applicants in the same way it handles Malaysians’ data. 

            Under section 2(2), the PDPA applies to businesses established in Malaysia, and to businesses outside Malaysia that use equipment in Malaysia to process personal data, other than merely for transit. Under section 3(2), the Act does not apply to personal data processed outside Malaysia unless that data is intended to be further processed in Malaysia. 

            Do diagnostic clinics fall under the PDPA? 

            Yes. Any clinic or diagnostic centre that processes personal data in the course of its business must comply with the PDPA’s seven principles, and patient health information is sensitive personal data, which requires explicit consent and a higher standard of protection. 

            Whether it must also register with the Commissioner depends on how it is licensed. Private medical and dental clinics fall within the health class of data controllers that must register. Standalone diagnostic laboratories should check the specific entries in the health class of the Class of Data Users Order, since whether registration applies depends on how the facility is licensed.

            Clinics and labs choosing patient management software should also read our guide to PDPA compliance for healthcare software. 

            What is a PDPA framework? 

            A PDPA compliance framework is the set of policies, processes and people an organisation puts in place to apply the seven principles in its daily operations. A practical framework usually includes: 

            • a privacy notice in Bahasa Malaysia and English 
            • PDPA training for staff, especially in HR, marketing, customer service and IT 
            • a data protection manual setting out roles, controls and escalation procedures 
            • internal and external compliance audits 
            • Data Protection Impact Assessments (DPIAs) for higher risk processing 
            • a Data Protection Officer, where the appointment threshold is met 

            Smaller businesses can start with essentials (a privacy notice, core policies and a basic breach response plan) and build up. See our PDPA compliance framework for more. 

            Is the PDPA based on any international instruments on privacy or data protection? 

            The PDPA does not formally adopt a single international instrument, but its seven principles reflect concepts common to international data protection frameworks, such as the OECD Privacy Guidelines, the EU’s former Data Protection Directive and the APEC Privacy Framework. Malaysia has since deepened that international alignment. The 2024 amendments moved the PDPA closer to the EU’s GDPR, particularly on breach notification, DPOs and data portability, and in November 2026 Malaysia was accepted as a full member of the APEC Cross-Border Privacy Rules (CBPR) System, a voluntary certification that helps organisations demonstrate compliance when transferring personal data between participating economies. 

            What is the online privacy protection act in Malaysia? 

            Malaysia does not have a separate online privacy protection act. Personal data collected online, such as through websites, apps and digital forms, is covered by the PDPA in the same way as data collected offline. Several other laws regulate different aspects of online activity, and some may touch personal data indirectly: 

            • Online Safety Act 2025: it deals with harmful content on online platforms rather than personal data, although it is sometimes mistaken for an online privacy law. 
            • Communications and Multimedia Act 1998: regulates certain online conduct and content. 
            • Cybercrimes Bill 2026: passed by Parliament in July 2026 but not yet in force, it will replace the Computer Crimes Act 1997 and create specific offences for identity theft and impersonation, which often involve the misuse of personal data. 
            • AI governance: the Commissioner’s Automated Decision-Making and Profiling Guideline already applies where AI systems process personal data. Separately, the government is developing a dedicated AI Governance Bill, which completed public consultation in July 2026.

            See our submission to the AI Governance Bill consultation.

            How do the PDPA 2010 and Cybersecurity Malaysia help safeguard personal data? 

            The PDPA safeguards personal data by requiring organisations to protect it under the Security Principle, report breaches likely to cause significant harm and limit how long data is kept. The Personal Data Protection Department, which administers the PDPA, and CyberSecurity Malaysia both sit under the Ministry of Digital and play complementary roles. The Personal Data Protection Department regulates how organisations handle personal data, while CyberSecurity Malaysia is a technical agency that provides incident response support and cyber security expertise.  

            The Cyber Security Act 2024 adds a separate layer for National Critical Information Infrastructure (NCII) entities, which must report cyber security incidents to the National Cyber Security Agency (NACSA).  

            Personal data & sensitive personal data 

            These questions cover what counts as personal data and sensitive personal data under the PDPA, including common edge cases. For details, see our PDPA 2010 summary for Malaysian SMEs. 

            What is personal data under the PDPA? 

            Personal data is any information that can directly identify a person, or that can identify them when combined with other information. In a business context, this commonly includes: 

            • names 
            • identification numbers, such as NRIC or passport numbers 
            • phone numbers and email addresses 
            • residential addresses 
            • employment records 
            • financial or transaction details 

            Personal data is covered whether it is held electronically, such as in databases and CRMs, or in physical documents like application forms, contracts and personnel files. 

            Is an IP address personal data under the PDPA? 

            It can be. The PDPA treats information as personal data where it relates to an individual who can be identified from it, or from it combined with other information the business holds. An IP address on its own may not identify anyone, but where a business can link it to a user account, login or other records, it is likely to be personal data. Where cookies or analytics tools collect IP addresses, this should be covered in the privacy notice. 

            Does the PDPA cover credit card numbers? 

            Yes. A credit card number linked to an individual is financial information that can identify them, so it is personal data under the PDPA and must be protected under the Security Principle. 

            Exposure of financial information is also one of the factors that makes a data breach likely to cause ‘significant harm’, which triggers mandatory breach notification. The PDPA has no rules specific to card data, but financial information counts towards the lower 10,000-person threshold for appointing a DPO and carrying out a DPIA. Businesses that process card payments are usually also bound by the PCI DSS standard through their payment provider, which is a contractual requirement rather than a legal one. 

            Is business contact information covered under the PDPA? 

            Under the PDPA as it currently stands, there is no general exemption for business contact information. A work email address or direct line that identifies a specific person, such as a client’s employee, is likely to be personal data. Generic contact details, such as a general enquiries address or main office line, are not, because they do not identify an individual.

            This may change. In a 2025 public consultation on amendments to the Personal Data Protection Regulations 2013, the Commissioner proposed a definition of “business contact information”, with the stated aim of distinguishing data used in a business context from personal data protected under the Act.

            The amendments have not yet been finalised, so for now businesses should continue to treat identifiable business contact details as personal data. 

            What does C4 data mean under the PDPA? 

            “C4” is not a term used in the PDPA or in the Commissioner’s guidelines. It usually comes from a company’s internal information classification scheme, often set up as part of an ISO 27001 information security programme, where documents are labelled by how sensitive they are. C4 is usually the most restricted category, although some organisations number their levels the other way round. Check how your own policy defines it. The label does not decide your PDPA obligations; the content does.  

            A document marked C4 may contain personal data or sensitive personal data, such as health or biometric information, or it may contain no personal data at all, such as a commercial strategy. The PDPA’s own categories are personal data and sensitive personal data, and its obligations apply according to what the document actually contains, whatever the internal label says. 

            What is sensitive personal data under the PDPA? 

            Sensitive personal data is a special category of personal data that needs extra care. Under the PDPA, it covers information about a person’s: 

            • physical or mental health 
            • religious beliefs or other beliefs of a similar nature 
            • political opinions 
            • commission or alleged commission of an offence 
            • biometric data, added by the 2024 amendments 

            Processing sensitive personal data generally requires the individual’s explicit consent, rather than ordinary consent. 

            What is special category data under Malaysian data protection law? 

            ‘Special category data’ is the term used under the EU’s GDPR. Malaysia’s PDPA uses the term ‘sensitive personal data’ for the equivalent category, covering health, religious beliefs, political opinions, offences and biometric data. 

            Are mental health, characteristics and political views considered sensitive data under the PDPA? 

            Mental health and political opinions are both sensitive personal data under the PDPA. 

            Physical, physiological or behavioural characteristics are only sensitive where they are biometric data, meaning data that results from technical processing of those characteristics, such as fingerprint scans or facial recognition templates. 

            Is salary sensitive personal data under the PDPA? 

            No. Salary is personal data when it is linked to an identifiable employee, but it does not fall under any of the sensitive personal data categories. 

            It should still be handled carefully, since salary information is confidential and its exposure in a breach may involve financial harm. Separately, the Commissioner’s DPO and DPIA guidelines count ‘financial information’ alongside sensitive personal data when applying the 10,000-person threshold. The guidelines do not define financial information, so it is not clear whether salary records fall within it. As a precaution, employers should treat salary records as financial information when assessing whether they meet the 10,000-person threshold for appointing a DPO or carrying out a DPIA. 

            Does a Malaysian passport contain sensitive personal data? 

            A passport number, name and date of birth are personal data. A photocopy or scan of a passport is not biometric data merely because it shows a photo, since biometric data under the PDPA results from technical processing of a person’s physical characteristics, such as a facial recognition template. The biometric data held in the passport chip is not captured by a photocopy. A passport copy should still be handled with care, because identity document numbers are among the details that make a breach likely to cause significant harm through identity fraud.  

            Are pictures sensitive data under the PDPA? 

            A picture where a person can be identified is personal data, which is why using customer or employee photos in marketing needs consent. 

            A picture is not automatically sensitive personal data, but it can be, depending on what it shows and how it is used. A photo of a medical report or prescription is health information, and therefore sensitive, regardless of the format. An image that reveals a person’s physical or medical condition, such as someone in a wheelchair or receiving treatment, may also be treated as sensitive personal data. Images that suggest a sensitive characteristic, such as religious attire, need particular care. 

            Registration 

            These questions cover which businesses must register as data controllers with the Personal Data Protection Commissioner. For details, see our guide to data controller registration. 

            Who needs to register under the PDPA? 

            Registration is mandatory for businesses in 13 prescribed classes, regardless of the size of the organisation or the volume of personal data processed: 

            Sector Details 
            Communication licensed under the Communications and Multimedia Act 1998 and Postal Services Act 2012 
            Banking and financial services licensed banks, Islamic banks and development financial institutions 
            Insurance licensed insurers and takaful operators 
            Health hospitals, private medical or dental clinics and pharmacies 
            Tourism and hospitality licensed tour operators, travel agents and tourist guides 
            Transportation airlines 
            Education higher education institutions and private schools 
            Direct selling licensed under the Direct Sales and Anti-Pyramid Scheme Act 1993 
            Services including legal, audit, accountancy, engineering, architecture and private employment agencies 
            Real estate licensed housing developers 
            Utilities water and electricity suppliers 
            Pawnbrokers licensed under the Pawnbrokers Act 1972 
            Moneylenders licensed under the Moneylenders Act 1951 

            Registered businesses receive a certificate of registration. Businesses outside these classes do not need to register, but they must still comply with the PDPA’s seven principles. 

            The Commissioner’s Circular No. 1/2026 on the registration of data controllers came into force on 1 June 2026 and sets out the current registration requirements. Businesses in a prescribed class should check their registration against it. 

            Does a will writing business need to register under the PDPA? 

            A standalone will writing business is not one of the 13 prescribed classes, so it does not need to register. It must still comply with the seven principles, particularly given the sensitive family and financial information it handles. 

            The exception is where the will writing is carried out by a law firm, since legal services fall under the services class. 

            How do I renew my registration with the Personal Data Protection Commissioner? 

            A certificate of registration is valid for the period selected when applying and must be renewed before it expires, and the current certificate must be displayed at the business premises. Renewal is done through the Commissioner’s SPDP system, which usually sends a reminder to the registered email 90 days before the certificate expires. The renewal fee depends on the type of business and the validity period selected. Failing to renew is an offence, carrying a fine of up to RM250,000, imprisonment of up to 2 years, or both. 

            Consent & notice 

            These questions cover how businesses obtain consent and give notice before collecting personal data. For full details, see our PDPA compliance framework. 

            Does a questionnaire without a consent form go against the PDPA? 

            Not automatically. The PDPA does not require a separate consent form, but a business collecting personal data through a questionnaire must meet two requirements: 

            • give a written notice (privacy notice) before or at the point of collection, explaining what data is collected, why and who it may be shared with, under section 7 
            • have the individual’s consent, unless an exemption applies. This does not need to be a separate signed form. Consent can be behavioural, such as someone voluntarily filling in the questionnaire after being shown a clear notice.  

            If the questionnaire asks about health, religious beliefs or other sensitive categories, explicit consent is required. 

            As best practice, a signed consent form or a clear tick box is always recommended, even where consent through conduct would be enough. It gives the business clear evidence of consent if it is ever questioned. See our guide to what counts as valid consent under the PDPA.  

            The risk lies in collecting personal data with no notice at all, or using the answers for a purpose the respondent was not told about. 

            Must PDPA consent be in BM and English? 

            The consent itself does not have to be in both languages. The dual-language requirement applies to the privacy notice: under section 7(3) of the PDPA, the written notice must be provided in both the national language (Bahasa Malaysia) and English. In practice, though, the two usually appear together. Where a form contains the privacy notice with the consent declaration at the bottom, businesses typically present the whole form in both languages, so individuals can clearly understand what they are consenting to. 

            What is the difference between a PDPA policy and a privacy notice? 

            A privacy notice is the external document that tells customers and other individuals what personal data you collect, why and who it is shared with. A PDPA policy is the internal document that tells your own staff how to handle that data in practice, such as who is responsible, how requests are handled and what to do if a breach occurs. Most businesses need both, and the two should describe the same practices. See our guide to writing a PDPA-compliant privacy policy. 

            Do we need to notify customers if there is a change of customer info under the PDPA? 

            Under the Data Integrity Principle, businesses must take reasonable steps to keep personal data accurate, complete and up to date, so customer records should be updated when a customer tells you their details have changed. To help keep records current, some businesses send customers periodic reminders to review and update their details, for example at annual renewal, during account login, or through a yearly email. This is not mandatory, but it is a practical way to show the business is taking reasonable steps to keep data accurate. 

            If what changes is how your business uses customer data, such as a new purpose or new third parties, you should update your privacy notice and get consent for the new purpose before using the data for it. 

            What is a disclosure request under the PDPA? 

            The PDPA does not define a ‘disclosure request’, but the term usually refers to a third party, often an authority such as the police, asking a business to hand over personal data. Under the Disclosure Principle, personal data should not be disclosed for a purpose other than the one it was collected for, or to a party not covered in the privacy notice, without consent. The PDPA allows disclosure without consent in limited cases, for example where it is necessary to prevent or detect a crime, or where it is required by law or a court order. Before responding, verify who is asking and on what basis, and disclose only what is needed. 

            Direct marketing 

            These questions cover using personal data for promotional emails, SMS, calls and other marketing. For full details, see our guide to PDPA-compliant marketing in Malaysia. 

            Does the PDPA require consent for direct marketing? 

            Yes. Under the General Principle in section 6, a business needs consent to process personal data unless the processing is necessary for a specified purpose, such as performing a contract with the individual or complying with a legal obligation. Marketing generally does not fall within these exceptions, so consent is needed. The business must also give a privacy notice before or at the point of collection under section 7, explaining that the data will be used for marketing. 

            Where personal data is used for marketing, the privacy notice should at minimum cover: 

            • the types of personal data involved 
            • the marketing purposes, such as newsletters and promotions 
            • whether the data will be disclosed to third parties 
            • the individual’s right to withdraw consent and opt out of marketing 

            Individuals can also object to their data being used for direct marketing at any time, and businesses must stop when they do. 

            Can a website send direct marketing emails to logged-in users without their subscribing consent? 

            Generally, no. Data collected for one purpose, such as account registration, cannot later be used for marketing without proper notice and consent. This is known as purpose creep, and it is one of the most common PDPA breaches in marketing. 

            Being a registered user or an existing customer does not automatically mean someone has consented to receive marketing emails. To market to them, the sign-up notice should clearly cover marketing and give users a way to opt out. 

            A common approach is to use two separate boxes at sign-up: one to accept the terms and the privacy notice for the core service, and a separate, optional box to agree to receive marketing. You will often see this when signing up for apps or online accounts. Keeping the two separate means users can use the service without agreeing to marketing, which also makes the marketing consent clearer and easier to rely on. 

            Data Protection Officers (DPOs) 

            These questions cover when a DPO is mandatory, who can be one and how the appointment works. For full details, see our FAQs on DPO appointments in Malaysia. 

            What is the threshold for a mandatory DPO in Malaysia? 

            Since 1 June 2025, a business must appoint a DPO if it: 

            • processes the personal data of more than 20,000 individuals 
            • processes the sensitive personal data (such as health data), including financial information, of more than 10,000 individuals, or 
            • carries out regular and systematic monitoring of individuals as part of its business activities 

            Businesses below these thresholds may keep a record of why they have not appointed a DPO, and it is good practice to designate a senior officer to handle breach reporting and act as the contact point for the PDPD. 

            What is regular and systematic monitoring? 

            Regular and systematic monitoring is one of the three triggers for a mandatory DPO, and also one of the qualitative triggers for a DPIA. Common examples include CCTV surveillance and tracking of individuals’ location or behaviour.

            The Commissioner’s DPO Guideline does not give a formal definition, but its examples include tracking or profiling people online or offline for behavioural advertising, a retail website using algorithms to recommend products based on users’ searches and purchases, operating a telecommunications network, monitoring health or fitness data through wearable devices, and activities involving CCTV or connected devices such as smart cars. 

            Must a DPO be Malaysian? 

            The DPO eligibility criteria focus on presence and ability rather than nationality. A DPO must: 

            • be resident in Malaysia (physically present for at least 180 days in a calendar year), or otherwise be easily contactable 
            • be proficient in Bahasa Melayu and English 
            • have no conflict of interest 
            • understand the organisation’s operations 
            • report directly to top management 

            In practice, the language requirement means most DPOs appointed in Malaysia are Malaysians, but a foreign national who meets all the criteria can be appointed. 

            Does a DPO need to be in Malaysia and speak Bahasa Malaysia? 

            Not necessarily on the first point, but yes on the second. Under the Commissioner’s DPO Guideline, a DPO must either be resident in Malaysia, meaning physically present for at least 180 days in a calendar year, or be easily contactable. Either way, they must be proficient in both Bahasa Melayu and English. 

            This applies to outsourced DPOs too. In practice, a DPO who is local and readily available is easier to rely on when a breach has to be reported within 72 hours. 

            How do I notify the appointment of a DPO? 

            The organisation must register its DPO with the PDPD through the SPDP system within 21 days of the appointment. Any change to the DPO or their contact details must be updated within 14 days. Alongside registration, you should: 

            • formalise the appointment in a letter of appointment (and a service contract, if outsourced) 
            • set up an official DPO email address, such as [email protected] 
            • keep records of the DPO’s reports, communications and audits 

            How do I register as a DPO under SPDP as an individual? 

            DPO registration on SPDP is done by the appointing organisation, which registers the person it has appointed.  

            Is a DPO personally liable under the PDPA? 

            Only in limited cases. Legal responsibility for PDPA compliance stays with the data controller or data processor. This is also true when the DPO role is outsourced, since outsourcing delegates the tasks but not the legal responsibility. A DPO cannot be dismissed for doing the job honestly. But the company may dismiss a DPO who breaches the law, is negligent or commits misconduct.  

            What is the penalty for DPOs under the PDPA? 

            The penalty risk sits with the organisation rather than the DPO. The PDPA does not set a specific penalty for failing to appoint a DPO, but that does not mean there is no penalty. The Act’s general penalty provision applies, carrying a fine of up to RM250,000, imprisonment of up to 2 years, or both. The Commissioner can also use its enforcement powers, such as serving an enforcement notice requiring the organisation to comply, and failing to comply with an enforcement notice is an offence. A DPO is not personally liable under the PDPA merely because they hold the role. 

            Employment & HR 

            These questions cover how the PDPA applies to job candidates, employees and HR processes. For full details, see our business guide to employee data privacy and our guide to confidentiality policies. 

            How does the PDPA relate to job candidates? 

            The PDPA applies from the moment a job application is received, not from the first day of work. When handling candidate data, employers should: 

            • collect only what is necessary to assess the application, avoiding details like marital status unless the role genuinely requires them 
            • give candidates a PDPA notice at the point of collection, ideally at the interview stage 
            • check that any recruitment agency they use has its own proper PDPA procedures 
            • keep unsuccessful applications only for a defined period, commonly around 6 to 12 months 

            If you want to refer a candidate to a related company in your group, the notice should say so upfront, or you should get fresh consent before passing the application on. 

            Are job applications and CVs covered by data protection rules in Malaysia? 

            Yes. Job applications and CVs contain personal data, so they are covered by the PDPA, Malaysia’s main data protection law. This includes CVs, identity documents, references and background check results. 

            Employers must give notice when collecting them, keep them secure and not retain them indefinitely. Rejected applications are commonly kept for 6 to 12 months unless the candidate agrees to be kept on file for future roles. 

            Is information processed in the context of employment covered under the PDPA? 

            Yes. The PDPA applies to employee personal data in the same way it applies to customer data. Employer obligations shift across the employment lifecycle: 

            Stage Typical data collected Key obligation 
            Recruitment resumes, identity documents, references, background checks collect only what is necessary and give a PDPA notice at the point of collection 
            Onboarding bank details, EPF and SOCSO numbers, emergency contacts, next of kin issue the full employee privacy notice, typically with the letter of offer or handbook 
            During employment payroll, performance reviews, disciplinary records, medical certificates, leave records, monitoring data keep data accurate and secure, and let employees access and correct their records 
            Termination exit interview records, final settlement details, reference letters retain only as long as statutory requirements or legal risk justify, then destroy 

            Medical records and other sensitive personal data collected along the way need explicit consent. Most employers rely on a mix of consent and legitimate grounds, such as performing the employment contract and meeting EPF, SOCSO and tax obligations. 

            Do employers need personal data consent to use employee photos on the company website or social media? 

            Yes. Using an employee’s photo, video or likeness in marketing is a separate purpose from employment, so consent to be employed does not cover it. 

            Employers should get specific consent through a standalone consent form rather than a clause in the employment contract, so the employee can decline without it affecting their job. If consent is later withdrawn, the business should stop using the image and remove it where practicable. 

            How do data privacy laws regulate background check vendors in Malaysia? 

            A background check vendor processes candidate or employee personal data on the employer’s behalf, so the employer remains responsible for how that data is handled. Employers should: 

            • disclose in the candidate privacy notice that personal data may be shared with background check providers 
            • sign a data processing agreement with the vendor covering data handling, confidentiality and security 
            • confirm the vendor has its own proper PDPA procedures in place 

            If the vendor stores or processes data outside Malaysia, the cross-border transfer rules under section 129 also apply. See our guide to PDPA and employee background checks. 

            Which department should own PDPA policies, HR or IT? 

            Usually neither. Legal responsibility sits with the organisation as data controller, but in practice the day-to-day owner of PDPA policies, the person who monitors, implements and updates them, is typically the legal or compliance function, or the DPO where one has been appointed. Whoever holds the role should report directly to top management. A data protection manual should set out each department’s role. HR, IT, marketing, legal and customer service all handle personal data, so each should have trained staff acting as liaisons to the DPO. 

            How do I report staff who breach the PDPA and company confidentiality? 

            Internally, suspected breaches should be reported to HR or a direct manager, or through the company’s whistleblower channel if the issue cannot be raised through the normal reporting line. The company can then take disciplinary action for intentional disclosure, negligence or unauthorised access. 

            If the staff member’s actions amount to a personal data breach likely to cause significant harm, the company must also notify the Personal Data Protection Commissioner within 72 hours. 

            Can a company ask employees to share their MyTax password and ID? 

            It should not. Login credentials give full access to an individual’s tax account, and collecting them goes well beyond what an employer needs. Holding staff passwords also exposes the business under the Security Principle if those credentials are later misused or leaked. Where an employer needs tax information, it should ask employees to provide the relevant documents themselves rather than share their login. 

            Why do Malaysian employers need a clear confidentiality policy? 

            A confidentiality policy tells employees what information they must not disclose and the consequences of doing so. It protects the business in three areas: 

            • trade secrets that affect its competitive position 
            • confidential information received from business partners, often under an NDA 
            • customer personal data, where unauthorised sharing can lead to a data breach and a breach of the PDPA’s Security Principle 

            It also fills the gaps left by short confidentiality clauses in employment contracts and applies consistent rules to employees who have not signed an NDA. 

            Data retention 

            These questions cover how long businesses can keep personal data and how to set retention periods. For full details, see our guide to data retention periods under the PDPA. 

            How long should personal data be retained under the PDPA? 

            The PDPA does not set a fixed retention period. Under the Retention Principle (section 10), personal data must not be kept longer than necessary for the purpose it was collected for. The right period for each category of data depends on three considerations: 

            • the original purpose, meaning how long the data is genuinely needed to fulfil it 
            • other statutory retention requirements, such as 7 years for tax records 
            • legal risk exposure, such as the 6-year limitation period for contract claims under the Limitation Act 1953 

            The retention period is usually the longer of the time needed for the original purpose and any statutory minimum. After that, the data should be deleted or anonymised, not kept ‘just in case’. 

            What are the exceptions to data retention in Malaysia? 

            Personal data can be kept beyond its original purpose where there is a continuing reason to hold it. The main situations are: 

            • the purpose is still ongoing, such as an active customer relationship or a warranty period 
            • another law requires a minimum retention period, such as tax or employment record-keeping rules 
            • the data is subject to an ongoing legal dispute or investigation 

            What is not allowed is keeping data indefinitely because it might be useful someday, with no defined purpose or timeframe. 

            What is a data retention policy? 

            A data retention policy sets out how long a business keeps each category of personal data and what happens when that period ends. It should cover: 

            • a data inventory listing the categories of personal data held and where they are stored 
            • defined retention periods for each category, based on purpose and statutory requirements 
            • a deletion or anonymisation process, ideally automated 
            • an exceptions process for data under a legal dispute or investigation 
            • ownership, meaning who monitors and enforces the schedule, often the DPO 

            A retention policy usually forms part of a broader PDPA compliance framework. 

            What is the document retention law in Malaysia? 

            There is no single document retention law in Malaysia. Retention periods come from several laws, depending on the type of record: 

            Record type Typical retention period Source 
            Tax records, including payroll and tax records of employees 7 years income tax record-keeping requirements 
            Contracts and transaction records 6 years after the relationship ends limitation period under the Limitation Act 1953 
            Employee registers and records at least 6 years for registers kept under the Employment Act 1955 Employment Act 1955, EPF and SOCSO regulations 
            Company accounting records 7 years Companies Act 2016 

            Personal data in these records can be kept for these periods, but should be deleted or anonymised once they end and no other purpose remains. 

            Cross-border data transfers 

            These questions cover transferring personal data from Malaysia to other countries under section 129 of the PDPA. For details, see our guide to cross-border data transfers. 

            What are the requirements for data export from Malaysia? 

            Under section 129 of the PDPA and the Cross Border Personal Data Transfer (CBPDT) Guidelines, a data controller can transfer personal data outside Malaysia if the destination: 

            • has a law that is substantially similar to the PDPA, or 
            • ensures an adequate level of protection at least equivalent to the PDPA 

            If the destination meets neither, the transfer can still go ahead under section 129(3) where, for example: 

            • the individual has given informed consent after being told the purpose of the transfer and the categories of recipients 
            • the transfer is strictly necessary to perform a contract with the individual, or a contract with a third party made at their request or in their interest 
            • the transfer is needed for legal proceedings, legal advice or defending legal rights, or to protect the individual’s vital interests 
            • the data controller has taken all reasonable precautions and exercised due diligence, such as through binding corporate rules, contractual clauses or recognised certifications 

            Data controllers must keep records of every cross-border transfer, including the recipient, destination country, type of data, purpose and proof of compliance. 

            Can a company transfer staff data to its parent company overseas? 

            Yes, as long as the transfer meets one of the section 129 routes above. Sharing within a group is still a disclosure to a separate legal entity, even where the companies share ownership or management. 

            Multinational groups commonly rely on binding corporate rules, which are legally binding internal policies regulating intra-group transfers. The employee privacy notice should also disclose that personal data may be shared with group companies overseas. 

            Is a transfer impact assessment required when transferring data to an overseas parent company? 

            Practically, yes, if the transfer relies on section 129(2). Although the Commissioner’s Guideline says a data controller “may” carry out a transfer impact assessment (TIA), the same Guideline lists the record of the TIA and its findings as the records a business must keep when relying on this route. A business relying on section 129(2) therefore needs a TIA to show how it concluded that the destination country has substantially similar laws or adequate protection. A TIA considers factors such as: 

            • whether the country has a data protection authority similar to Malaysia’s PDPD 
            • whether it has data breach notification requirements 
            • whether it requires a Data Protection Officer 
            • the recipient’s compliance history and any past data breaches 

            TIA findings are valid for up to 3 years, after which a follow-up assessment is needed. Where the destination does not pass, the group can rely on binding corporate rules or contractual clauses instead. 

            Is a transfer impact assessment required when relying on the individual’s consent? 

            A TIA is the mechanism for assessing whether a destination meets the section 129(2) standard. Consent is a separate route under section 129(3)(a), which depends on the individual being told the purpose of the transfer and the categories of recipients before they consent. 

            So a TIA is not expected for a consent-based transfer. The Guideline’s documentation requirements for that route are the privacy notice and a record of the individual’s consent. 

            Can I refuse to let a supplier upload company data to the cloud or an unknown US server? 

            It depends on what the data is. If it includes personal data, uploading it to an overseas server is a cross-border transfer, and the supplier’s arrangement must meet one of the section 129 routes, usually backed by contractual clauses. 

            Pure company data, such as financials or internal documents, falls outside the PDPA. Whether you can refuse is then a matter of your contract with the supplier and any confidentiality terms, so it is worth setting data location and security requirements in the contract from the start. 

            Data breaches 

            These questions cover when and how a personal data breach must be reported, and how this differs from cyber security incident reporting. For full details, see our step-by-step guide to handling data breach notifications. 

            Is there data breach reporting in Malaysia? 

            Yes. Since the 2024 amendments, data breach notification is mandatory under section 12B of the PDPA, supported by Circular of Personal Data Protection Commissioner No. 2/2025 and the Data Breach Notification (DBN) Guideline. 

            Where a breach causes or is likely to cause significant harm, the data controller must notify the Commissioner within 72 hours of becoming aware of it, and affected individuals within 7 days after that. 

            Is it a PDPA data breach if a bank mistakenly sends an email to the wrong recipient? 

            Yes. Sending an email, letter or form containing personal data to the wrong recipient is one of the DBN Guideline’s own examples of a personal data breach. 

            Whether it must be reported depends on whether it causes or is likely to cause significant harm, which includes: 

            • risk of physical harm, financial loss, negative effects on credit scores or property damage 
            • potential misuse for illegal purposes 
            • exposure of sensitive personal data, such as health, financial or biometric data 
            • risk of identity fraud 
            • a breach involving more than 1,000 data subjects 

            The last factor, scale, decides whether the Commissioner must be notified, but it does not by itself require notifying affected individuals. 

            A misdirected email from a bank containing account or financial details is likely to meet this threshold. Even if it does not, the breach should be recorded in the organisation’s data breach register. 

            When must data subjects be notified of a data breach? 

            Where a breach is likely to cause significant harm to an individual, they must be notified within 7 days after the Commissioner is notified. The notification should be sent directly, by email, SMS, direct message or letter, and must include: 

            • the nature of the breach and what data was affected 
            • the possible consequences for the individual 
            • the steps the organisation has taken 
            • the actions the individual should take 
            • a contact point for enquiries, such as the DPO 

            A public notice on the website or social media is only acceptable where contacting individuals directly is impractical, such as when the numbers are very large or contact details are outdated. 

            What is the consequence of failing to report a personal data breach? 

            Under section 12B(3) of the PDPA, failing to notify a reportable breach can lead to a fine of up to RM250,000, imprisonment of up to 2 years, or both. 

            If the 72-hour deadline is missed, the late notification must come with a written justification for the delay and supporting documents. 

            What does a DPO for a data processor need to do when they identify a reportable data breach? 

            They should inform the data controller promptly. The legal duty to notify the Commissioner rests solely with the data controller, even where the breach happened at the processor’s end. 

            The processor should then cooperate with the data controller in assessing, investigating and containing the breach. Data controllers usually make this a contractual requirement in their data processing agreements. 

            Which PDPA principle is breached if customer medical records are sent overseas through unsecured email? 

            The main concern is the Security Principle, which requires practical steps to protect personal data from loss, misuse and unauthorised access, and now applies to data processors too. Medical records are sensitive personal data, so they call for stronger protection. Sending them by unsecured email is unlikely to meet that standard, even if nothing goes wrong. 

            Sending them this way does not by itself mean a personal data breach has occurred, but it significantly increases the risk of one. If the email is intercepted, misdirected or accessed by someone unauthorised, that would be a personal data breach, and because medical records are sensitive personal data, it would likely meet the significant harm threshold for notifying the Commissioner. 

            Separately, sending the records overseas brings in section 129, which requires the transfer to meet one of the cross-border transfer routes. 

            Must an organisation that was hacked report it to the Ministry of Finance? 

            No. Under Malaysia’s data protection and cyber security laws, a hacking incident is reported to: 

            • the Personal Data Protection Commissioner, within 72 hours, if personal data is involved and significant harm is likely 
            • the National Cyber Security Agency (NACSA), immediately, with prescribed details within 6 hours, if the organisation is a designated NCII entity 

            Non-NCII entities can also report cyber security incidents to NACSA voluntarily. 

            What are the reporting requirements for a cybersecurity breach in Malaysia? 

            Under section 23 of the Cyber Security Act 2024, only designated NCII entities must report cyber security incidents, including suspected ones. The requirements differ from PDPA breach notification: 

            Requirement PDPA (personal data breach) Cyber Security Act 2024 (cyber security incident) 
            Who must report data controllers, where significant harm is likely or more than 1,000 individuals are affected NCII entities 
            Notify Personal Data Protection Commissioner Chief Executive of NACSA and the relevant NCII sector lead 
            Deadline within 72 hours immediate notification, prescribed details within 6 hours and supplementary information within 14 days 
            Notify affected individuals within 7 days, if significant harm is likely no express obligation 
            Penalty for not reporting fine up to RM250,000, up to 2 years’ imprisonment, or both fine up to RM500,000, up to 10 years’ imprisonment, or both 

            An incident that compromises an NCII entity’s systems and exposes personal data may need both notifications. 

            Compliance & enforcement 

            These questions cover how businesses put PDPA compliance into practice, including DPIAs and workplace monitoring, and what happens when they fall short. For full details, see our full guide to DPIAs in Malaysia and overview of PDPA breach penalties. 

            How do organisations in Malaysia comply with the PDPA? 

            Compliance starts with applying the seven principles (General, Notice and Choice, Disclosure, Security, Retention, Data Integrity and Access) and then building a framework around them. A practical framework includes: 

            • a privacy notice in Bahasa Malaysia and English 
            • PDPA training for staff 
            • a data protection manual with roles, controls and escalation procedures 
            • internal and external compliance audits 
            • DPIAs for higher risk processing 
            • a DPO, where the threshold is met 
            • a breach response plan that can meet the 72-hour notification deadline 

            Smaller businesses can start with the essentials and build up, while larger businesses should embed compliance across departments with regular audits and training. 

            What does the Security Principle require? 

            The Security Principle requires a business to take practical steps to protect personal data from loss, misuse, unauthorised access, alteration or destruction. What counts as practical depends on the nature of the data, where it is stored, the security built into the systems holding it and the reliability of the staff who can access it. Since the 2024 amendments, data processors are bound by this principle too. See our guide to the PDPA Security Principle. 

            What does the Data Integrity Principle require? 

            It requires a business to take reasonable steps to keep personal data accurate, complete, not misleading and up to date, having regard to the purpose it was collected for. In practice, this means validating data at the point of collection, acting on signs that records are out of date and making sure corrections reach every system holding the data. See our guide to the PDPA Data Integrity Principle. 

            How should a business handle a data access or correction request? 

            Under the Access Principle, individuals can ask to access the personal data a business holds about them and to have it corrected. A request must be in writing, and a fee may be charged for access. The business should verify the requester’s identity, search all relevant systems, remove or redact other people’s personal data before releasing anything, and respond in writing, explaining anything it withholds. See our guide to the PDPA Access Principle. 

            Do staff need PDPA training? 

            The PDPA does not expressly require training, but the Security Principle requires a business to consider the reliability and competence of the staff who handle personal data, and most breaches start with an ordinary staff action. The Commissioner’s DPO Guideline also expects DPOs to receive sufficient training to carry out their role. A baseline session for all staff, with role-specific modules for teams such as HR, marketing and IT, is a practical starting point. See our guide to PDPA training for Malaysian businesses. 

            Is a DPIA required under the PDPA? 

            A DPIA is required under the Commissioner’s DPIA guideline where a processing activity is likely to result in a high risk to personal data. The guideline uses a two-step test: 

            • a quantitative threshold, where processing involves more than 20,000 individuals, or sensitive data, including financial information, of more than 10,000 individuals 
            • a qualitative threshold, which covers activities such as automated decision-making, AI or new technologies, location or behaviour tracking, systematic monitoring, restricting user rights and targeting children or vulnerable groups 

            Companies carry out their own DPIAs, since the responsibility rests with the data controller. The guideline provides a five-step DEICA approach (Describe, Evaluate, Identify, Consider and Assess), a risk scoring method and sample templates, with the DPO advising. A DPIA is generally valid for 2 years, and its records should be kept for at least 2 years after the processing ends. 

            Does collecting children’s medical and allergen information require a DPIA? 

            Very likely, yes. Children’s medical and allergen information hits two of the DPIA guideline’s qualitative triggers: it is sensitive personal data (health), and the processing targets children. 

            If the business holds this data for more than 10,000 children, it also meets the quantitative threshold. Separately, consent for processing a child’s personal data should come from a parent or legal guardian. 

            Is CCTV allowed on a production line if it only shows operators’ hands? 

            Yes. Workplace monitoring through CCTV is not prohibited under Malaysian law, but footage of identifiable employees is personal data. To use it lawfully, employers should: 

            • inform employees that monitoring takes place, ideally through a workplace monitoring policy 
            • make sure the monitoring is proportionate to a legitimate purpose, such as quality control, safety or security 
            • not use the footage for purposes beyond what employees were told 
            • keep footage only for a short, defined period unless it is needed for an investigation 

            Camera angles that only capture operators’ hands are a good way to keep monitoring proportionate, since they limit how much identifiable data is collected. 

            Can individuals file civil suits under the PDPA? 

            The PDPA does not give individuals an express right to sue an organisation for breaching the Act, and the Commissioner has no power to award compensation. Malaysian courts have indicated that non-compliance with the PDPA cannot by itself found a civil claim. Affected individuals may still bring claims on other grounds, such as breach of contract, breach of confidence or negligence, so a data breach can still lead to civil liability alongside regulatory penalties.  

            PDPA vs GDPR 

            These questions cover how the EU’s GDPR affects Malaysian businesses and how it compares with the PDPA. For details, see our guide to PDPA vs GDPR for Malaysian businesses. Note: Edwin Lee & Partners advises on Malaysian law. Where the answers in this section refer to foreign data protection laws, such as the EU’s GDPR, the UK GDPR or China’s Personal Information Protection Law, they explain how those laws may affect Malaysian businesses and how they compare with the PDPA, but they are not advice on foreign law.

            Where a foreign law applies to your business, we recommend seeking advice from a lawyer qualified in that jurisdiction. 

            Does Malaysia follow the GDPR? 

            No. Malaysia has its own law, the PDPA, which has moved closer to the GDPR since the 2024 amendments. However, the GDPR can still affect a Malaysian business in three ways: 

            • direct applicability, if the business offers goods or services to individuals in the EU or monitors their behaviour, such as through website tracking 
            • group policy, where a Malaysian office of a multinational group is told to follow the group’s GDPR-aligned standards 
            • counterparty requirements, where an EU customer, supplier or parent company requires GDPR-standard safeguards before sending personal data to Malaysia 

            Only the first is a genuine legal obligation under EU law. The other two are an internal policy decision and a contractual negotiation respectively. 

            Does Malaysia have an adequacy decision under the GDPR? 

            No. Malaysia does not hold an EU adequacy decision, so the European Commission has not formally recognised it as offering an adequate level of data protection. 

            This is why EU parties sending personal data to Malaysia usually ask the Malaysian business to sign Standard Contractual Clauses (SCCs) or a data processing agreement with GDPR-standard protections. 

            Does Malaysia have adequacy under the UK GDPR? 

            No. Malaysia is not covered by the UK’s adequacy regulations. UK organisations sending personal data to Malaysia therefore generally rely on the UK’s own transfer safeguards, such as the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses. 

            When does the GDPR apply to a Malaysian entity providing services to another Malaysian entity? 

            The GDPR only applies directly to a Malaysian business if it offers goods or services to individuals in the EU, or monitors the behaviour of individuals in the EU. A service provided by one Malaysian entity to another, with no EU individuals involved, does not trigger the GDPR on its own. 

            It can still come in indirectly, such as where the client’s group requires GDPR-aligned standards, or where the data being handled originally came from the EU under SCCs. 

            Can an agreement include both GDPR and PDPA? 

            Yes. Agreements commonly cover both, particularly data processing agreements between Malaysian businesses and EU counterparties, which combine PDPA obligations with GDPR-standard clauses such as SCCs. 

            Where a business has any EU exposure, building consent and data handling to the GDPR standard generally satisfies most of the PDPA as well. Data processing agreements are negotiable and should reflect what the business actually does with the data. 

            Where a group’s headquarters operates under the GDPR, its templates and policies are usually localised when rolled out in Malaysia. A GDPR-based document will not automatically cover Malaysia-specific requirements, such as providing the privacy notice in both Bahasa Malaysia and English, notifying the Commissioner of a breach within 72 hours, registering the DPO with the Commissioner, data controller registration for businesses in the prescribed classes, and meeting one of the section 129 routes for cross-border transfers. 

            Is China’s data protection law similar to Malaysia’s PDPA? 

            Both laws regulate how personal data is collected, used, protected and transferred abroad, and both include consent requirements and security obligations. China’s Personal Information Protection Law (PIPL) is generally regarded as stricter, particularly on cross-border transfers, which may require a government security assessment, a standard contract filed with the regulator, or certification. Businesses operating in both countries should take advice on PIPL from a China-qualified lawyer. 

            PDPA compliance in 90 days 

            If you have a question that is not answered here, or need help putting these requirements into practice, we help Malaysian businesses with PDPA compliance, including privacy notices and internal policies, outsourced DPO services, DPIAs, breach response planning and staff training. To discuss your situation, book a consultation with us. 

            shen-ming-casual

            Wong Shen Ming

            Shen Ming is a corporate and commercial lawyer who is deeply committed to supporting her clients in achieving their business goals. Specialising in commercial and employment law, she demonstrates her expertise by crafting and reviewing various types of commercial agreements.

            View her full profile here.

            Let us know how we can support your business

            Drop us a message and let us better understand your needs. Get your first consultation within 24-hours.
            Share this article:
            Post might interest you:

            ABOUT THE AUTHOR

            Wong Shen Ming

            A Full Guide To Automated Decision-Making & Profiling (ADMP) In Malaysia

            A Full Guide To Automated Decision-Making & Profiling (ADMP) In Malaysia

            For businesses in Malaysia using data to screen candidates and assess customers through automated systems, the new guideline on Automated Decision-Making and Profiling (ADMP) by the Personal Data Protection Department regulates how those decisions are made, and whether they are properly assessed and justified.  This

            guide to tag along rights for shareholders' agreement in malaysia

            The Shareholder’s Guide To Tag-Along Rights

            While crucial for minority shareholders, it’s important for all company shareholders to know how tag along rights work, as they affect everyone.   Below, we unpack tag-along rights and by the

            Want more content like this?

            Drop us your email and be the first to know when we have more informative contents on the latest legal updates, just like this one.

            Responsibilities of Executor:

            • Apply for and extract the grant of probate.
            • Make arrangements for the funeral of the deceased.
            • Collect and make an accurate inventory of the deceased’s assets.
            • Settling the debts and obligations of the deceased.
            • Distributing the assets.

            Note for Digital Executor:
            If you wish to leave your digital assets to certain people in your Will, there are important steps that need to be taken to ensure that your wishes can be carried out:

            • Keep a note of specific instructions on how to access your username and password of your digital asset.
            • You are advised to store these private and confidential information in a USB stick, password management tool or write them down.
            • Please inform your executor or a trusted person of the whereabouts of the tools so that they will have access to your digital asset.