{"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,"Basham, Ringe Y Correa, S.C.","Adolfo Athie"]
[]
[]
[]
["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","Mexico"]
["Key Legislation Overview"]
["1. What is the key legislation?","In the private sector, the law that governs the protection of personal data in Mexico is the \nFederal Law on Protection of Personal Data Held by Individuals (\nLey Federal de Protección de Datos de Personales en Posesión de los Particulares) (the \"\nLFPDPPP\"). Secondary legislation supplements the \nLFPDPPP. This includes the \nRegulations to the LFPDPPP (\nReglamento de laLey Federal de Protección de Datos de Personales en Posesión de los Particulares) (the \"\nRLFPDPPP\") and the \nGuidelines of the Privacy Notice (Lineamientos del Aviso de Privacidad) (the \"\nGuidelines\").\nIn the public sector, the law that governs the protection of personal data in Mexico is the \nGeneral Law on Protection of Personal Data held by Obliged Subjects (\nLey General de Protección de Datos Personales en Posesión de Sujetos Obligados) (the \"\nPublic Sector Law\"), as well as local laws addressing the subject within each state of the Mexican Republic.\n"]
["2. What are the key decisions applying that legislation?","To our knowledge, currently the new data protection authority has not yet issued any decision.\n"]
["Key Data Protection Provisions"]
["1. How are “personal data” and “sensitive data” defined?","Personal Data: Any information concerning an identified or identifiable person. A person is considered identifiable when their identity can be determined directly or indirectly through any information (Art. 2, V of the \nLFPDPPP)\nSensitive personal data: Those personal data that affect the most intimate sphere of the data subject, or whose improper use may give rise to discrimination or entail a serious risk for the data subject. By way of example, but not limited to, personal data that may reveal aspects such as racial or ethnic origin, present or future health status, genetic information, religious, philosophical and moral beliefs, political opinions and sexual preference are considered sensitive (Art. 2, VI of the \nLFPDPPP)\n"]
["2. How is the defined data protected?"," LFPDPPP states that personal data processing must be according to the following principles and obligations: \n \n Consent (articles 7, 8 and 9) \n Legality (article 6) \n Loyalty (article 6) \n Information (articles 14, 15, 16, 17) \n Purpose limitation (article 11) \n Proportionality (article 12)  \n Quality (article 10) \n Obligation to adopt and maintain security measures (article 18) \n Confidentiality (article 20) \n Accountability (article 13) \n The requirement of data protection by design and default is not expressly included in the LFPDPPP ; however, where the intensive data processing is considered with a high impact on privacy, a DPIA could be deemed as a best practice. \n \n Some specific measures must be taken when processing sensitive personal data:  \n \n Databases containing sensitive personal data must not be created without justification of their creation for purposes that are legitimate, concrete and consistent with the explicit objectives or activities pursued by the regulated party. \n Privacy notice must expressly state that it is dealing with this type of data. \n To transfer the data to a third party without the data subject’s consent, the data controller must dissociate them. The possibility of dissociation must be referred to in the relevant privacy notice, or unless such transfer is within the Law assumptions. \n It is necessary to process under a confidential basis and adopt technical, physical, and administrative security measures to protect personal data against damage, loss, alteration, destruction or unauthorized use, access or treatment. In adopting such security measures, the controller must consider the risks involved, any potential consequences to the data subjects if there is a security breach, the nature of the data, and technological development. \n Access restriction only for personnel who are authorized and trained for sensitive data processing. \n \n Processing of personal data will be done as necessary, appropriate and relevant with relation to the purposes set out in the privacy notice. For sensitive personal data, the data controller must make reasonable efforts to limit the processing period thereof to the minimum required. To do so, the data controller will verify what the period for sensitive personal data retention is, and once it has elapsed, delete the data, after blocking. "]
["3. Who is subject to privacy obligations?","The \nData Protection Law applies to all individuals and private legal entities. The \nGeneral Law applies to all obligated subjects.\nThe parties regulated under the \nData Protection Law are private parties, individuals or legal entities that process personal data, except for (i) credit bureaus; and (ii) individuals that carry out the collection and storage of personal data exclusively for personal use, and without purposes of disclosure or commercial use.\nThe \nGeneral Law regulates obligated subjects, which are public agencies pertaining to the three levels of government: federal, state, including Mexico City, and municipal, as well as the constitutional autonomous organisms, political parties and public trusts. \n"]
["4. How is “data processing” defined?","Processing: Any operation or set of operations carried out by means of manual or automated procedures applied to personal data, related to the collection, use, recording, organization, preservation, storage, processing, use, communication, dissemination, storage, possession, access, handling, use, disclosure, transfer or disposal of personal data, (Art. 2, XIX, \nLFPDPPP).\n"]
["5. What are the principles applicable to personal data processing?"," Generally, personal data must be collected with the data subject's consent, unless one of the exceptions for consent applies, and only after a privacy notice has been made available to them. When collecting personal data, the data protection principles must also be observed (e.g., information, consent, proportionality, purpose limitation, data quality, legitimacy and accountability). \n Note: Prior to collecting personal data, the data controller needs to make available to data subjects a privacy notice explaining the characteristics of the processing of their personal data. Such a privacy notice must include the name and address of the data controller, personal data that is going to be processed, the purposes of the processing, data transfers to be made, information regarding means for data subjects to exercise their rights, etc. \n Additionally, as a general rule consent from data subjects is needed in order to process their personal data. Written consent is necessary for the processing of sensitive personal data, explicit consent for the processing of financial data and implied consent for other categories of personal data. \n Consent will not be necessary when: \n \n a law so provides; \n the data are contained in publicly available sources; \n the personal data are subject to a prior dissociation procedure; \n they have the purpose of fulfilling obligations under a legal relationship between the data subject and the data controller; \n there is an emergency situation that could harm an individual in his person or property; or \n personal data is essential for medical attention, prevention, diagnosis, health care delivery, medical treatment or health medical management, where the data subject is unable to give consent. \n "]
["6. How is the processing of personal data regulated?","Personal data may only be used to fulfill the purposes of the processing, as stated in the privacy notice that was made available to data subjects.\nThe use and disclosure of personal data must only be done in accordance with what is established in the privacy notice and personal data may only be processed in connection with clearly defined and legitimate objectives, as mentioned in the privacy notice made available to data subjects.\nAdditionally, the use and disclosure of personal data must be done in compliance with the data protection principles of proportionality, purpose limitation, legality, consent, information, loyalty. In particular, personal data may only be used for purposes that are necessary, appropriate, relevant and not excessive in connection with the purposes for which personal data was collected. In addition, a data controller is obliged to make reasonable efforts to limit the personal data being processed to the minimum necessary.\n"]
["7. How are storage, security and retention of personal data regulated?","Personal data must be kept for as long as is needed to comply with the purposes of the processing. There must always be appropriate security measures to protect personal data from unauthorized use, access, disclosure or processing.\nIn general, personal data may be kept or stored for as long as it is necessary to comply with the purposes of the processing, and after that, for a period equal to the statute of limitations of the actions that could arise as a result of, or in connection with, the data processing.\nOnce personal data is no longer necessary, it must be securely deleted.\nData controllers must establish and maintain organizational, technical and physical security measures to protect personal data against damage, loss, alteration, destruction or unauthorized use, access or processing.\nData controllers should adopt security measures similar to the ones that they use to protect their own information.\nThe risk, previous security incidents, the sensitivity of the personal data and the possible consequences for the data subjects, technological development and the amount of data must be taken into account when determining the security measures that will be in place.\n"]
["8. What are the data subjects' rights under the data legislation?"," In Mexico, data subjects have the right to exercise the access, rectification, erasure (cancellation), and/or opposition, at any time. Therefore, controllers must be able to guarantee such exercise.  \n The data protection rights are: \n \n to access under Article 22 LFPDPPP (see ‘fair processing notices’ above in this table); \n to rectification under Article 23 LFPDPPP ; \n to erasure (cancellation) under Article 24 LFPDPPP ; \n to object to processing/profiling under Article 26 LFPDPPP   \n to limit the use or disclosure under Article 15, IV, LFPDPPP ; and \n to revoke consent Article 7 LFPDPPP \n to information when personal data is processed within a decision-taking procedure without human intervention, Article 112 RLFPDPPP \n to reconsideration of the decision taken with AI tools without human intervention Article 112 RLFPDPPP \n \n Notwithstanding, data subjects must always be able to exercise them, depending on the specific situation the right could be denied or not applicable. "]
["9. What are the consent requirements for data subjects?","Not applicable.\n"]
["10. How is authorization for use of data handled?","Not applicable.\n"]
["11. Are cross-border data transfers regulated? If so, what are the restrictions on cross-border data transfers?"," Data Controller to Data Controller data transfer rules: \n The data controller that transfers (whether national or international) personal data may use contracts and other legal instruments that contain at least the same obligations as those to which the data controller is subject under the Mexican data protection legislation, as well as the conditions under which the data subject consented to the processing of his personal data. \n The main rules for data transfer between data controllers:  \n \n The data subject must be informed by a privacy notice, and the transfer must be limited to the purposes that justify it. \n Any transfer of personal data, whether national or international, is subject to the consent of the data subject.  \n The transferring party (transferor) shall provide the privacy notice to the third-party recipient. \n Cross-border transfers of personal data are possible when the receiver of the personal data assumes the same obligations as the controller transferring the personal data.  \n For purposes of proving that the transfer, whether domestic or international, was made in accordance with the provisions of the Mexican data protection legislation, the burden of proof shall be, in all cases, on the transferring data controller and on the recipient of the personal data.  \n Cross-border or national data transfers to third-party controllers do not require data subject consent when the transfer is:\n \n made to a holding company, subsidiary, or affiliate under common control with the transferring party or to a parent company or any company of the same group as the transferring party, operating under the same internal processes and policies. \n made based on a law or treaty to which Mexico has agreed. \n If the transfer is required to maintain or fulfill a legal relationship between the transferring party and the data subject. \n If the transfer is required for medical diagnosis or prevention, health care delivery, medical treatment, or health services management. \n If the transfer is necessary by virtue of a contract executed or to be executed in the interest of the data subject between the data controller and a third party, or \n If the transfer is legally required to safeguard public interests or for the administration of justice, or for the recognition, exercise, or defense of a right in a judicial proceeding. \n \n \n "]
["12. How are data \"incidents\" and \"breaches\" defined?","Not applicable.\n"]
["13. Are there any notification requirements for incidents and/or data breaches?","When a data breach that could materially affect the rights or property of data subjects occurs, it is mandatory to immediately notify data subjects of the breach, so they can take appropriate actions to protect themselves.\nData controllers must inform the data subjects about the breaches that can significantly affect their rights or property, but first, they have to confirm that the breach has actually occurred, and the magnitude and scope of the breach. This must be done without delay so that the data subjects affected can take the appropriate measures to protect themselves or their rights.\nThe data protection authority does not need to be notified.\n"]
["14. Who is/are the privacy regulator(s)?","The National Institute of Transparency, Access to Information and Protection of Personal Data (\nINAI is its acronym in Spanish).\nThe \nINAI is an autonomous body responsible for promoting and disseminating the right to access public information and the right to data protection within governmental agencies and private parties. This body is committed to working with other federal, state and municipal authorities in order to promote data protection in different industries and sectors, such as the financial, educational and health sectors.\nThe \nINAI is also the competent authority to prosecute and sanction breaches of data protection and transparency laws and regulations.\n"]
["15. What are the consequences of a data breach?","In addition to the notification requirement, consequences may be the imposition of fines to the data controller or of imprisonment penalties for individuals that cause a security breach for profit.\nNote: The first consequence is the obligation to notify, without delay, the data subject when a breach occurs, in the terms referred to before.\nThen, an investigation could be initiated by \nINAI that may result in the imposition of a fine ranging from 100 to 320,000 units of account called UMA. Currently, one UMA amounts to MXN 96.22 (approx. EUR 4.20), thus fines range from approximately EUR 420 to EUR 1,341,000.00. If sensitive personal data was involved in the breach, the fine may double.  \nImprisonment may be imposed on any person who, with the intent of achieving an unlawful profit, causes a security breach.\n"]
["16. How is electronic marketing regulated?","Marketing is considered a secondary purpose of the processing, and as such, it must be clear in the privacy notice that this purpose is voluntary, as well as the means available to opt out of receiving marketing communications.\nThe privacy notice must inform data subjects that their personal data may be used for marketing purposes, and that such use is secondary or voluntary. Data controllers must provide means to opt out from receiving marketing communications, and such means can be included in the privacy notice (as boxes) or described in the privacy notice but included somewhere else (like unsubscribe). Marketing may be done on an opt-out basis.\n"]
["17.\tAre there sector-specific or industry-specific privacy requirements?","In Mexico, the data protection law is of the federal level, it is of a public order and of general observance throughout the national territory. Therefore, any sector or industry must observe this law; however, specific sectors may have additional or more stringent requirements, e.g., banking and health.  \n"]
["18.\tWhat are the requirements for appointing Data Protection Officers or similar roles?","In Mexico, all data controllers (no exceptions), regardless of the type or scale of processing activities or the type of personal data processed, must appoint a Data Protection Officer (“\nDPO”). (Article 29 \nLFPDPPP).\n\nIf a data controller´s local entity in Mexico processes any personal data in Mexico (e.g., from its employees, suppliers, etc.), it is mandatory for this local entity to appoint a \nDPO. There is no requirement for the \nDPO to be based in-country. Therefore, the \nDPO can be based overseas.\nAppoint a \nDPO and allocate to the \nDPO the responsibility for ensuring that biometric recognition-related policies and procedures are followed. It is not necessary or that the details of the \nDPO be provided to the SABG; however, they must be included in the relevant \nPrivacy Notices.\nFor further information, please see the guidance issued by the extinct \nINAI, available at: \nhttps://home.inai.org.mx/wp-content/uploads/Recomendaciones-para-los-sujetos-obligados-en-la-designaci%C3%B3n-del-oficial-de-protecci%C3%B3n-de-datos-personales-1.pdf  \nEven though this guidance (not mandatory) was issued by the extinct data protection authority and for authorities in the government sector that process personal data, we refer to it as an orientate document. \n"]
["19.\tWhat are the record-keeping and documentation obligations?","These obligations are not expressly mandated by the \nLFPDPPP."]
["20.\tWhat are the requirements for conducting Data Protection Impact Assessments (DPIAs)?","Undertaking a \nDPIA is not mandatory as such but recognized by the former data protection authority (\nINAI) as best practice. Similar to a \nDPIA, controllers, according to Article 48, V, \nRLFPDPPP, must implement a procedure to deal with data protection-related risks in the context of the implementation of new products, services, technologies and business models, as well as to mitigate them. In this regard, performing a \nDPIA is useful in this regard.\n"]
["21.\tWhat are the requirements for third-party vendor management and data sharing?"," When engaging a Processor (whether another group company or a third-party provider), the entity that is the Controller (or Joint Controller) of the personal data processed in connection with the operation of the biometric system retains the primary responsibility for the compliance of the Processor. The Controller is required under Article 51 RLFPDPPP to: \n \n ensure that the Processor provides sufficient guarantees to implement appropriate technical and organisational measures for the processing to comply with the UK GDPR (including with respect to security, storage and the use of properly trained staff). The Controller can, for example, ask the Processor to complete a supplier due diligence questionnaire to help it gather and assess the relevant information; and \n Enter into a written contract with the Processor, which must, at a minimum, include the terms set out in Article 50 RLFPDPPP . \n Data Subjects do not need to consent or be informed of domestic or international data remissions from a Controller to a Processor, as the controller is the party ultimately responsible for the processing of personal data. \n The agreements between the controller and processor related to the processing of personal data must be in accordance with the controller's privacy notice. \n \n Data Controller to Data Processor remissions of personal data rules: \n There must be a written agreement specifying the scope and content of the processing relationship. The contract must include the following obligations to data processors: \n \n Process personal data strictly in accordance with the instructions of the controller. \n Refrain from processing personal data for purposes other than those instructed by the controller. \n Implement the security measures required by Mexican legislation on data protection and other applicable laws and regulations. \n Maintain the confidentiality of personal data subject to processing. \n Delete the personal data once the legal relationship with the controller has concluded or upon instructions from the latter, provided that there is no legal obligation to retain the data. \n Refrain from transferring personal data unless instructed to do so by the data controller or where the transfer derives from a subcontracting authorized by the data controller, or where it is required by a competent authority. \n "]
["22.\tWhat are the penalties and enforcement mechanisms for non-compliance?"," Violations of this Law shall be sanctioned by the Secretariat with: \n \n A warning to the data controller to carry out the actions requested by the data subject. \n A fine ranging from 100 to 320,000 units called UMA in Mexico City, currently 113.14 Mexican pesos (approx. USD 5.9). Therefore, fines range from approx. USD 590 to approx. USD 1,888,000. \n \n In case of recurrence, additional fines may be imposed based on the previous paragraph, and if the violations were committed in the processing of sensitive personal data, the penalties may be doubled. \n Additionally, imprisonment may be imposed on those who unlawfully breach security measures or facilitate the violation of data in a database under their custody, or those who unlawfully profit from the processing of personal data by taking advantage of any error of the data subject. "]
["23.\tWhat are the ongoing compliance and audit requirements?"," Privacy and security policies must be kept up to date and according to Article 62 of the RLFPDPPP : Data controllers must update the list of security measures when the following events occur: \n \n I. Security measures or processes are modified for continuous improvement, derived from the revisions to the security policy of the Data Controller \n There are substantial modifications in the processing that result in a change in the level of risk \n The processing systems have faced a data breach \n There is an effect on personal data different from the above. \n \n In the case of sensitive personal data, the controllers will try to review and, where appropriate, update the corresponding relationships once a year. "]
["24. Are there any recent developments or expected reforms?","Mexico has acceded to \nConvention 108 and its Additional Protocol. Also, the United States, Canada and Mexico have agreed on a Trade Agreement that includes a chapter with provisions on the protection of personal data. \nAt the end of 2018, an amendment to different laws was proposed to the Senate. According to this proposal, explicit consent of data subjects will be required to carry out marketing.  This proposal has been approved by the Senate and must now be discussed in the Chamber of Deputies. \nNote: Mexico acceded to \nConvention 108 and its \nProtocol in June 2018, and such international treaties entered into force for Mexico on October 1, 2018. \nConvention 108 will have an impact in Mexico, especially regarding trans-border data flows. It is possible that reforms to Mexican legislation on data protection take place in the future to fully match current legislation to the treaties of reference. \nThe United States, Canada and Mexico have agreed on a new \nFree Trade Agreement, the \nUnited States-Mexico-Canada Agreement (\"\nUSMCA\"), that entered into force on July 1, 2020. This agreement\nincludes, among others, provisions on cross-border data flows, corporate binding rules and data location.  It is possible that reforms to Mexican legislation on data protection take place in the future in connection with this international agreement.\nThe proposed amendment regarding marketing practices has not been approved yet and does not seem to be a priority of this government. Thus, it may be left pending indefinitely. \n"]