{"text_format":"2","workbook":"xlsx","n_sheets":2,"sheets":["Coversheet","Global Data Privacy Guide"],"not_rendered":{"charts":0,"images":1,"macros":0,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Coversheet","index":0,"n_rows":12,"n_cols":3,"rows_kept":12,"cut":false,"hidden":false,"merged":[]}
[]
[]
[null,"Prepared By:","Contributors:"]
[null,"Skrine","Jillian Chia"]
[]
[]
[]
["Global Data Privacy Guide"]
[]
["Report Generated: 11/19/2025"]
[]
["View your report results on next tab"]

{"sheet":"Global Data Privacy Guide","index":1,"n_rows":29,"n_cols":2,"rows_kept":29,"cut":false,"hidden":false,"merged":[]}
["Question","Malaysia"]
["Key Legislation Overview"]
["1. What is the key legislation?","The \nPersonal Data Protection Act 2010 (“\nPDPA”) governs the processing of personal data in respect of commercial transactions. The PDPA contains principles of consent, notice, disclosure, security, data retention, data integrity and access.  \nThe key legislation governing data protection in Malaysia is the \nPDPA. The\n PDPA came into force on November 15, 2013, and it sets out seven key principles in the processing of personal data by a data controller. Six further pieces of subsidiary legislation have been enacted pursuant to the \nPDPA to further facilitate the enforcement of the \nPDPA.\nThe \nPersonal Data Protection Standard 2015 (“\nPDP Standards”) was also issued by the Personal Data Protection Commissioner (“\nPDP Commissioner”). The \nPDP Standards spell out three main standards, namely: Security Standards, Retention Standards and Data Integrity Standards, which have application to both personal data which are processed both electronically and non-electronically.\nIn 2024, the \nPersonal Data Protection (Amendment) Act 2024 (“\nAmendment Act”) was gazetted with its amendments coming into force in three stages, i.e., 1 January 2025, 1 April 2025, and 1 June 2025.\nTo date, three guidelines have been launched by the \nPDP Commissioner, namely the \nData Protection Officer Guidelines (“\nDPO Guidelines”), \nData Breach Notification Guidelines (“\nDBN Guidelines”) and \nCross-Border Personal Data Transfer Guidelines (“\nCBPDT Guidelines”).\n"]
["2. What are the key decisions applying that legislation?","Most of the reported cases considered the application of the general exemption of Section 45 of the \nPDPA. For example, in \nNewlake Development Sdn Bhd v Zenith Delight Sdn Bhd & Ors (No 2) [2021] 7 CLJ 88, it was held that if the court rules that the documents in question were relevant and admissible, the \nPDPA cannot be used as a shield to prevent such documents from being produced at trial under the guise of personal data protection.\nNotably, in \nGenting Malaysia Berhad v Personal Data Protection Commissioner & Ors [2022] 11 MLJ 898, the High Court held that the \nPDPA does not permit the Director-General of the Inland Revenue Board of Malaysia (“\nDGIR”) to issue blanket demands for personal data, given the protections afforded to data subjects under the\n PDPA. The Court emphasized that such request for data must comply with legal requirements and satisfy the test of necessity, in that “the interference with the rights of data subjects must be proportionate to the reality as well as to the potential gravity of the public interests involved” and “there must also be a specific instance as contemplated by the statute and not a general sweeping and inconsistent reasons for the disclosure to be given”. This decision was significant as it marked the first formal challenge to the powers of law enforcement authorities to request disclosure of personal data.\nHowever, in 2025, the Court of Appeal in \nDirector-General, Inland Revenue v Genting Malaysia Berhad [2025] MLJU 129 set aside the High Court’s decision on the ground that the \nDGIR’s letter was not a decision subject to judicial review. As a result, the High Court lacked jurisdiction to hear the case in the first place.\\\nThe Court of Appeal did not address the judgment concerning data protection issues under the \nPDPA, leaving it uncertain whether it remains the prevailing position. Note that Genting has filed a motion for leave to appeal to the Federal Court, but it was unanimously dismissed.\n"]
["Key Data Protection Provisions"]
["1. How are “personal data” and “sensitive data” defined?"," Personal data protects information in respect of a commercial transaction from which an individual is identified or identifiable.   \n Note: “Personal data” means any information in respect of commercial transactions, which— \n \n is being processed wholly or partly by means of equipment operating automatically in response to instructions given for that purpose; \n is recorded with the intention that it should wholly or partly be processed by means of such equipment; or \n is recorded as part of a relevant filing system or with the intention that it should form part of a relevant filing system, \n \n that relates directly or indirectly to a data subject, who is identified or identifiable from that information or from that and other information in the possession of a data controller, including any sensitive personal data and expression of opinion about the data subject; but does not include any information that is processed for the purpose of a credit reporting business carried on by a credit reporting agency under the Credit Reporting Agencies Act 2010. \n Examples of what would be considered personal data include name and contact details. “Sensitive personal data” means any personal data consisting of information as to the physical or mental health or condition of a data subject, his political opinions, his religious beliefs or other beliefs of a similar nature, the commission or alleged commission by him of any offence, biometric data, or any other personal data as the Minister may determine by order published in the Gazette. \n Examples of sensitive personal data would include data concerning an individual's health, political opinions, religion, as well as arrests and convictions for criminal offences. \n Note: “Biometric data” means any personal data resulting from technical processing relating to the physical, physiological or behavioural characteristics of a person.  "]
["2. How is the defined data protected?"," Generally, the defined data is protected under the PDPA through the exercise of seven personal data protection principles, namely:  \n \n General Principle; \n Notice and Choice Principle; \n Disclosure Principle; \n Security Principle; \n Retention Principle; \n Data Integrity Principle; and  \n Access Principle. \n \n Further details of these principles can be found in the questions below. "]
["3. Who is subject to privacy obligations?"," The PDPA applies to any person who processes or has control over the “processing” of any personal data (data controller). \n “Data controller” means a person who either alone, jointly, or in common with other persons processes any personal data or has control over or authorizes the processing of any personal data, but does not include a data processor. There is also a category referred to as “data processors,” which carries the following meaning:- \n “data processor”, in relation to personal data, means any person, other than an employee of the data controller, who processes the personal data solely on behalf of the data controller and does not process the personal data for any of his own purposes. \n A data controller would be primarily responsible for any data processors it utilizes. However, pursuant to the Amendment Act, the Security Principle has been extended to data processors, including direct imposition of penalties on data processors for breach – these amendments came into force on 1 April 2025.  \n The PDPA does not apply to personal data processed outside Malaysia unless the data is intended to be further processed in Malaysia and it also does not apply to a data controller who is not established in Malaysia unless that person uses equipment in Malaysia to process personal data (save where it is only for purposes of transit). \n The Malaysian Federal and State Governments are also exempt from the PDPA . \n Data controllers who fall within certain sectors are required to register with the PDP Commissioner . The sectors which have been specified are: \n \n Communications \n Banking and Financial Institutions \n Insurance \n Health \n Tourism and Hospitality \n Transportation \n Education \n Direct Selling \n Services, namely organizations carrying on the following businesses: legal, audit, accountancy, engineering or architecture, retail or wholesale dealing as defined under the Control Supplies Act 1961, and private employment agencies \n Real Estate \n Utilities \n Pawnbroker \n Moneylender \n "]
["4. How is “data processing” defined?"," “Processing” is defined widely under the PDPA and includes “collecting, recording, holding or storing the personal data or carrying out any operation or set of operations on the personal data, including—  \n \n the organization, adaptation or alteration of personal data; \n the retrieval, consultation or use of personal data; \n the disclosure of personal data by transmission, transfer, dissemination or otherwise making available; or \n the alignment, combination, correction, erasure or destruction of personal data”. \n "]
["5. What are the principles applicable to personal data processing?"," The PDPA prohibits a data controller from processing personal data without the consent of a data subject and the PDPA requires a data controller to inform a data subject of various matters relating to the information of a data subject, which is being processed by or on behalf of that data controller. \n The General Principle of the PDPA prohibits a data controller from processing personal data without the consent of the data subject unless it is for the following reasons: \n \n for the performance of a contract to which the data subject is a party; \n for the taking of steps at the request of the data subject with a view to entering into a contract; \n for compliance with any legal obligation to which the data controller is the subject, other than an obligation imposed by a contract; \n in order to protect the vital interests of the data subject; \n for the administration of justice; or \n for the exercise of any functions conferred on any person by or under any law. \n \n The Notice and Choice Principle of the PDPA requires a data controller to inform a data subject by written notice of the following, in both the national language (Malay) and English: \n \n that personal data of the data subject is being processed by or on behalf of the data controller, and shall provide a description of the personal data to that data subject; \n the purposes for which the personal data is being or is to be collected and further processed; \n of any information available to the data controller as to the source of that personal data; \n of the data subject’s right to request access to and to request correction of the personal data and how to contact the data controller with any inquiries or complaints in respect of the personal data; \n of the class of third parties to whom the data controller discloses or may disclose the personal data; \n of the choices and means the data controller offers the data subject for limiting the processing of personal data, including personal data relating to other persons who may be identified from that personal data; \n whether it is obligatory or voluntary for the data subject to supply personal data; and \n where it is obligatory for the data subject to supply the personal data, the consequences for the data subject if they fail to supply the personal data. \n \n Notice has to be provided as soon as practicable, which means:- \n \n when the data subject is first asked by the data controller to provide his personal data; \n when the data controller first collects the personal data of the data subject; or \n in any other case, before the data controller— \n \n uses the personal data of the data subject for a purpose other than the purpose for which the personal data was collected; or \n discloses the personal data to a third party. \n \n \n "]
["6. How is the processing of personal data regulated?"," Data controller cannot disclose any personal data of a data subject for any purpose other than the purpose disclosed (and directly related purpose) and to any party other than the class of third parties to the data subject. ( Disclosure Principle of the PDPA ) \n However, the disclosure of personal data is permitted where: \n \n consent has been given by the data subject; \n the disclosure is necessary to prevent or detect crime, or for the purpose of investigations; \n the disclosure is required or authorized by law or order of the court; \n the data controller had acted under the belief that he has a legal right to disclose the data to another person; \n the data controller had acted under the reasonable belief that he would have received the consent of the data subject if the data subject had known of the disclosure and the circumstances of such disclosure; or \n the disclosure was justified as being in the public interests in circumstances as determined by the Minister. \n "]
["7. How are storage, security and retention of personal data regulated?"," A data controller and data processor are obligated to take specified measures to protect personal data from loss, misuse, modification, unauthorized or accidental access or disclosure, alteration or destruction during its processing. ( Security Principle ) A data controller must also not retain longer than is necessary any data for the fulfillment of the purpose for which it is processed and must destroy or permanently delete all personal data, which is no longer required for the purpose for which it was processed. ( Retention Principle ) \n Where data is being processed, the data controller and data processor must take into account the following security factors: \n \n the nature of the personal data and the harm that would result from such loss, misuse, modification, unauthorized or accidental access or disclosure, alteration or destruction; \n the place or location where the personal data is stored; \n any security measures incorporated into any equipment in which the personal data is stored; \n the measures taken for ensuring the reliability, integrity and competence of personnel having access to the personal data; and \n the measures taken to ensure the secure transfer of the personal data. \n \n The PDP Standards also provide certain measures that have to be complied with under the Security Standards. Where processing of personal data is carried out by a “data processor” on behalf of a data controller, the data processor shall, for the purpose of protecting the personal data from any loss, misuse, modification, unauthorized or accidental access or disclosure, alteration or destruction— \n \n provides sufficient guarantees in respect of the technical and organizational security measures governing the processing to be carried out; and  \n takes reasonable steps to ensure compliance with those measures. \n \n For the Retention Principles , the PDP Standards also contain the Retention Standards, which specify the measures that have to be taken in terms of retention of data.   \n "]
["8. What are the data subjects' rights under the data legislation?","The \nAccess Principle confers the right on a data subject to access their personal data and to correct the same if it is inaccurate, incomplete, misleading or outdated.\nA data subject shall be given access to their personal data held by a data controller and be able to correct that personal data where the personal data is inaccurate, incomplete, misleading or not up-to-date, except where compliance with a request to such access or correction is refused under the \nPDPA.\nThe \nPDPA also grants rights to data subjects to request access to and/or correction of personal data. The \nPDPA prescribes the procedures, and there are also timelines that would have to be complied with by a data controller where there is an access and/or correction request.\nThe \nPDPA also provides the grounds on which such data access request may be refused such as where the burden or expense of providing access is disproportionate to the risks to the data subject’s privacy in relation to the personal data in the case in question or where the data controller cannot comply with the data access request without disclosing personal data relating to another individual, among other factors.\nA data correction request may also be turned down where the data controller is not supplied with such information as he may reasonably require to ascertain in what way the personal data to which the data correction request relates is inaccurate, incomplete, misleading or not up-to-date or where the data controller is not satisfied that the personal data to which the data correction request relates is inaccurate, incomplete, misleading or not up-to-date, among other factors.\nThe \nPDPA also provides data subjects with the right to withdraw consent for the processing of their personal data. The data controller must, upon receiving the written notices from data subjects, cease the processing of their personal data. \nMoreover, the data subjects also have the right to prevent processing of their personal data that is likely to cause damage or distress by providing a written notice to the data controller; however, such right subject to certain exceptions, such as where the processing is necessary for the performance of a contract which the data subject is party and where the processing is necessary for the data controller to comply with any legal obligation.\nThe data subjects also have the right to prevent their personal data from being processed for direct marketing purposes. Further details can be found in Question 16 below.\nLastly, the \nPDPA also grants data subjects the right to request the data controller to transmit their personal data to another data controller of their choice directly by giving a notice in writing by way of electronic means to the data controller. However, such a request is subject to technical feasibility and compatibility of the data format.\n"]
["9. What are the consent requirements for data subjects?","The \nPDPA does not define “consent” or prescribe a specific consent method, and the \nPersonal Data Protection Regulations 2013 merely require that consent must be in a form that can be “recorded” and “maintained”. The onus of proving consent falls on the data controller. \nWhere the form in which consent is to be given also concerns another matter, the requirement to obtain consent shall be presented distinguishable in its appearance from such other matter.\nThat said, explicit consent is required for the processing of sensitive personal data unless certain exceptions apply. \n"]
["10. How is authorization for use of data handled?","The \nPDPA does not contain specific provisions on how authorization for use (i.e., consent) should be handled. As mentioned above in Question 9, consent must be in a form that can be recorded and maintained.\n"]
["11. Are cross-border data transfers regulated? If so, what are the restrictions on cross-border data transfers?"," Yes. The PDPA contains provisions regulating cross-border data transfer. \n A data controller shall not transfer any personal data of a data subject to a place outside Malaysia unless to such a place which has in force any law which is substantially similar to the PDPA , or which ensures an adequate level of protection equivalent to the levels of protection afforded under the PDPA . To rely on either of these conditions, the CBPDT Guidelines provide that data controllers are required to conduct a transfer impact assessment (\" TIA \") to determine whether these conditions are met. \n Notwithstanding the prohibition, a data controller may transfer any personal data to a place outside of Malaysia if: \n \n the data subject has given their consent to the transfer; \n the transfer is necessary for the performance of a contract between the data subject and the data controller; \n the transfer is necessary for the conclusion or performance of a contract between the data controller and a third party which— \n \n is entered into at the request of the data subject; or \n is in the interests of the data subject; \n \n \n the transfer is for the purpose of any legal proceedings or for the purpose of obtaining legal advice or for establishing, exercising or defending legal rights; \n the data controller has reasonable grounds for believing that in all circumstances of the case— \n \n the transfer is for the avoidance or mitigation of adverse action against the data subject; \n it is not practicable to obtain the consent in writing of the data subject to that transfer; and \n if it was practicable to obtain such consent, the data subject would have given his consent; \n \n \n the data controller has taken all reasonable precautions and exercised all due diligence to ensure that the personal data will not, in that plac,e be processed in any manner which, if that place is Malaysia, would be a contravention of the PDPA ; or \n the transfer is necessary in order to protect the vital interests of the data subject. \n "]
["12. How are data \"incidents\" and \"breaches\" defined?","The \nPDPA does not use or define the term “data incident”. Instead, it specifically adopts the term “personal data breach,” which is defined to include any breach of personal data, loss of personal data, misuse of personal data or unauthorized access of personal data.\nThe \nDBN Guidelines further provide that the personal data breach includes but is not limited to modification, duplication, alteration or destruction, and may be caused by accidental or deliberate actions (either internally or externally).\n"]
["13. Are there any notification requirements for incidents and/or data breaches?"," Yes. The new Section 12B of the PDPA imposes a mandatory obligation on data controllers to notify both the PDP Commissioner and affected data subjects of personal data breaches where such personal data breach causes “significant harm”. \n A personal data breach will be considered to cause or is likely to cause “significant harm” if there is a risk that the compromised personal data: \n \n may result in physical harm, financial loss, a negative effect on credit records, or damage to or loss of property; \n may be misused for illegal purposes; \n consists of sensitive personal data; \n consists of personal data and other personal information which, when combined, could potentially enable identity fraud; or \n is of “significant scale”, i.e., if the number of affected data subjects exceeds 1000. \n \n The DBN Guidelines provide specific requirements and guidance on the procedures and timelines for handling personal data breaches:  \n \n Notification to the PDP Commissioner: Notification of data breaches that cause “significant harm” must be made as soon as practicable and no later than 72 hours from the occurrence of the personal data breach. A data controller who fails to notify the PDP Commissioner within 72 hours must submit a written notice to the PDP Commissioner detailing the reasons for the delay and providing supporting evidence. \n Notification to affected data subjects: Notification of data breaches that cause “significant harm” must be made without unnecessary delay, and no later than 7 days after the initial notification is made to the PDP Commissioner . Note that the “significant scale” criterion does not apply when determining whether notification to affected data subjects is required.  \n \n "]
["14. Who is/are the privacy regulator(s)?"," A PDP Commissioner will be appointed by the Minister to carry out the functions and the powers assigned to the PDP Commissioner by the PDPA . There is currently a PDP Commissioner appointed and also a Personal Data Protection Department which has been set up. \n The functions of the PDP Commissioner include: \n \n to advise the Minister on the national policy for personal data protection and all other related matters; \n to implement and enforce personal data protection laws, including the formulation of operational policies and procedures; \n to promote and encourage associations or bodies representing data controllers to prepare codes of practice and to disseminate to their members the codes of practice for the purposes of the PDPA ; \n to cooperate with bodies corporate or government agencies for the purpose of performing his functions; \n to determine in pursuance of Section 129 whether any place outside Malaysia has in place a system for the protection of personal data that is substantially similar to that as provided for under the PDPA or that serves the same purposes as the PDPA ; \n to undertake or cause to be undertaken research into and monitor developments in the processing of personal data, including technology, in order to take into account any effects such developments may have on the privacy of individuals in relation to their personal data; \n to monitor and supervise compliance with the provisions of the PDPA , including the issuance of circulars, enforcement notices or any other instruments to any person; \n to promote awareness and dissemination of information to the public about the operation of the  PDPA ; \n to liaise and cooperate with persons performing similar personal data protection functions in any place outside Malaysia in respect of matters of mutual interest, including matters concerning the privacy of individuals in relation to their personal data; \n to represent Malaysia through participation in events that relate to personal data protection as authorized by the Minister, whether within or outside Malaysia; and \n to carry out such activities and do such things as are necessary, advantageous and proper for the administration of the PDPA , or such other purposes consistent with the PDPA as may be directed by the Minister. \n "]
["15. What are the consequences of a data breach?"," Breaches of the provisions of the PDPA will result in a fine and/or imprisonment. Please also see Question 13 above for the data breach notification requirements and procedure.   \n Failure to comply with the provisions in the PDPA may amount to a criminal offence: \n \n Breach of any of the seven data protection principles attracts a fine of up to RM 1,000,000 and/or up to three years imprisonment. \n The unlawful collection, disclosure and sale of personal data attract a fine of up to RM 500,000 and/or up to three years imprisonment. \n \n If a body corporate is found to have committed an offence, the officers of such body corporate are deemed to have committed the offence personally. However, the officer(s) of such body corporate may not be found to have committed the offence if they can prove the offence was committed without their knowledge or consent and they had taken all reasonable precautions and exercised due diligence to prevent the commission of the offence. "]
["16. How is electronic marketing regulated?","There are no specific rules on electronic marketing under the \nPDPA; however, the \nPDPA has a general provision on the section on the processing of personal data for direct marketing.\n“Direct marketing” is defined in the \nPDPA as “the communication by whatever means of any advertising or marketing material which is directed to particular individuals”. This would be wide enough to encompass electronic marketing.\nThe \nPDPA stipulates that a data subject may, at any time by notice in writing to a data controller, require the data controller at the end of such period as is reasonable in the circumstances to cease or not to begin processing his personal data for purposes of direct marketing.\nWhere the data subject is dissatisfied with the failure of the data controller to comply with the notice, whether in whole or in part, the data subject may submit an application to the \nPDP Commissioner to require the data controller to comply with the notice. \nWhere the \nPDP Commissioner is satisfied that the application of the data subject is justified, the \nPDP Commissioner may require the data controller to take such steps to comply with the notice. A data controller who fails to comply with the requirement of the \nPDP Commissioner commits an offense and shall, on conviction, be liable to a fine not exceeding RM 200,000 or to imprisonment for a term not exceeding two years or to both.\n"]
["17.\tAre there sector-specific or industry-specific privacy requirements?","Under the \nPDPA, data controllers falling within the class of data controllers prescribed in the \nPersonal Data Protection (Class of Data Controllers) Order 2013 (to be read with Personal Data Protection (Class of Data Controllers) (Amendment) Order 2016) must register with the \nPDP Commissioner.  \nThe \nPDP Commissioner may designate a body as a data controller forum in respect of a specific class of data controllers for the purposes of the \nPDPA and such data controller forum may develop a code of practice on its own initiative, or upon request by the \nPDP Commissioner.\nThe following enforceable codes of practice have been registered: \nGeneral Code of Practice, Code of Practice for the Utilities Sector (Electricity), Code of Practice for the Insurance and Takaful Industry in Malaysia, Code of Practice for the Banking Sector and Financial Institutions, Code of Practice for the Malaysian Aviation Sector, Code of Practice for the Communications Sector, Code of Practice for the Utilities Sector (Water), and Code of Practice for Private Hospitals in the Healthcare Industry.Additionally, depending on the type of data in question and the industry in which the data controller and/or data subject are in, specific data protection requirements under other laws and regulations may apply, particularly in highly regulated sectors such as financial or healthcare sectors. \n"]
["18.\tWhat are the requirements for appointing Data Protection Officers or similar roles?"," The Amendment Act introduces a new obligation for both data controllers and data processors to appoint a Data Protection Officer (“ DPO ”). The appointed DPO shall be accountable to the data controller in relation to the data controller/data processor’s compliance with the PDPA and is required to be registered with the PDP Commissioner within 21 days from the date of the appointment via the Personal Data Protection System. This requirement came into force on 1 June 2025. \n According to the DPO Guidelines , only data controllers or data processors, whose processing of personal data involves either one of the following, are required to appoint a DPO :  \n \n personal data exceeding 20,000 data subjects; \n sensitive personal data, including financial information exceeding 10,000 data subjects; or involves activities that require “regular and systematic monitoring” of personal data. \n \n Data controllers and data processors must ensure their appointed DPOs can demonstrate a sound level of the following skills, qualities, and expertise: \n \n  knowledge on the PDPA , local data protection practices (including any other applicable data protection laws, where relevant); \n understanding of the data controller/processor’s business and personal data processing operations; \n understanding of information technology and data security; \n personal qualities such as integrity, understanding of corporate governance and high professional ethics; and \n ability to promote data protection culture within the organisation. \n \n DPOs may be appointed from among existing employees or through outsourcing services. Additionally, DPOs must: \n \n be resident in Malaysia (physically present in Malaysia for at least 180 days in one calendar year) or be easily contactable via any means; and \n be proficient in Bahasa Melayu and English. \n \n DPOs assume the following responsibilities: \n \n inform and advise the data controller and data processor on personal data processing; \n support the data controller and data processor in complying with the PDPA and other related data protection laws, and monitoring compliance with the same; \n support the carrying out of data protection impact assessments; \n ensure proper data breach and security incident management; \n act as a facilitator and point of contact for data subjects; and \n act as the liaison officer and main point of reference for the PDP Commissioner . \n "]
["19.\tWhat are the record-keeping and documentation obligations?"," The PDPA requires the data controller to keep and maintain a record of any application, notice, request or any other information relating to personal data that has been or is being processed by them. \n Additionally, the data controller must keep and maintain a list of disclosures to third parties (who are not specified in the privacy notices) in relation to personal data of the subject data that has been or is being processed by them.  \n The personal data system must be open for inspection, and the PDP Commissioner or the inspection officer may require the production of the following documents and information, which must therefore be properly recorded and maintained: \n \n Record of the consent from a data subject maintained in respect of the processing of personal data by the data controller; \n Record of a written notice issued by the data controller to the data subject; \n List of disclosures to third parties in respect of personal data that has been or is being processed by him; \n Security policy developed and implemented by the data controller; \n Record of compliance in accordance with the Retention Standards ; \n Record of compliance in accordance with the Data Integrity Standards ; or \n Such other related information as the PDP Commissioner or any inspection officer deems necessary. \n \n The PDP Standards also contain certain record-keeping requirements; for example, any transfer of personal data using removable media devices and cloud computing services must be recorded.  \n Under the DBN Guidelines and DPO Guidelines , the data controller must also keep records and maintain a register detailing personal data breaches for at least 2 years from the date of the notification to the PDP Commissioner and maintain records of their appointed DPOs . \n Under the CBPDT Guidelines , the data controller must also keep and maintain a record of the recipient to whom the personal data is transferred. "]
["20.\tWhat are the requirements for conducting Data Protection Impact Assessments (DPIAs)?","Presently, there is no express requirement on this in the \nPDPA.\nHowever, it should be noted that the new Section 12A of the \nPDPA mandates the appointment of a \nDPO and one of the responsibilities of the \nDPO is to provide support and advice on the implementation of data protection impact assessments (\nDPIA). In this regard, the \nPDP Commissioner is developing a guideline to provide guidance on conducting a \nDPIA. It is presently unclear whether this would be a mandatory requirement under the \nPDPA.\n"]
["21.\tWhat are the requirements for third-party vendor management and data sharing?"," Third-party vendors who process personal data solely on behalf of a data controller are considered “data processors: under the PDPA and are responsible for complying with the Security Principle . Pursuant to the Security Principle , a data controller shall ensure that data processors they engage shall, for the purpose of protecting the personal data from any loss, misuse, modification, unauthorized or accidental access or disclosure, alteration or destruction— \n \n provide sufficient guarantees in respect of the technical and organizational security measures governing the processing to be carried out; and \n take reasonable steps to ensure compliance with those measures      \n \n The above obligations may be incorporated into the data processing agreement with the third-party vendor as warranties and representations. The Security Standards under the PDP Standards also stipulate that contracts should be entered into with data processors. \n Additionally, under the DBN Guidelines , data controllers are required to contractually impose obligations on data processors to promptly notify the data controller about any personal data breach that has occurred, and to provide all reasonable and necessary assistance to the data controller to meet the data controller’s data breach notification obligation under the PDPA . "]
["22.\tWhat are the penalties and enforcement mechanisms for non-compliance?"," Breach of the PDPA may result in an inquiry or investigation by the PDP Commissioner (either on its own initiative or based on a complaint received). Where, following the investigation, the PDP Commissioner decides that the PDPA has been contravened, the PDP Commissioner may serve an enforcement notice, specifying inter alia the breach, the steps required to be taken to remedy the breach within a certain period and directing, if necessary, the relevant data controller to cease processing the personal data. Failure to comply with the PDP Commissioner’s enforcement notice may attract a fine not exceeding RM 200,000 and/or imprisonment for a term not exceeding two years. \n Depending on the nature of the offence, a breach of the PDPA may attract a maximum fine of RM 1,000,000, although certain offences are compoundable, which may allow reduced penalties.  \n Some examples of penalties are as follows: \n \n Contravention of the Personal Data Protection Principles may attract a fine not exceeding RM 1,000,000 and/or imprisonment for a term not exceeding three years; \n Processing personal data without a certificate of registration (where required by law) may attract a fine not exceeding RM 500,000 and/or imprisonment for a term not exceeding three years; and \n Non-compliance with the requirement to record and maintain consent, to develop and implement a security policy and to process personal data in accordance with any standards issued by the PDP Commissioner may attract a fine not exceeding RM 250,000 and/or imprisonment for a term not exceeding two years. \n \n Please note that any person who is aggrieved by the decision of the PDP Commissioner may appeal to the Appeal Tribunal by filing a notice of appeal with the Appeal Tribunal. The decisions that may be appealed are: \n \n the registration of data controllers; \n the refusal of the PDP Commissioner to register a code of practice; \n the failure of the data controller to comply with a data access request or correction request; \n the issuance of an enforcement notice; \n the PDP Commissioner’s refusal to vary or revoke an enforcement notice; and \n the PDP Commissioner’s refusal to conduct or continue an investigation based on a complaint. \n "]
["23.\tWhat are the ongoing compliance and audit requirements?","There are no express audit requirements under the \nPDPA, but see Question 21 about the obligations of data controllers to ensure that data processors take reasonable steps to ensure compliance with security measures. A recommended method would be for data controllers to have a right to audit data processors.\n"]
["24. Are there any recent developments or expected reforms?","As mentioned in Question 1 above, the \nPDPA was recently amended, and all amendments have come into force.\nThree DPO-related documents have been published by the \nPDP Commissioner, namely, the \nDPO Professional Development Pathway & Training Roadmap, the DPO Competency Guidelines, and the Management of DPO Training Service Providers Guideline.   The Personal Data Protection Department is currently developing five additional guidelines and has issued public consultation papers proposing requirements for (i) data subjects’ right to data portability; (ii) data protection impact assessment; (iii) data protection by design; (iv) automated decision making and profiling; as well as (v) amendments to the \nPDP Standards.\n"]