Today it is common for a company to host its critical information on third-party services, and also to assume that, in doing so, the liability left along with the data. The 2025 data protection law says otherwise: the provider processes the information on the company’s behalf, and it is the company that is liable.
What the law requires
Controller and processor. The Federal Law on the Protection of Personal Data Held by Private Parties (Ley Federal de Protección de Datos Personales en Posesión de los Particulares, LFPDPPP), published in the Official Gazette of the Federation (DOF) on March 20, 2025, distinguishes the controller (responsable), which decides on the processing, from the processor (persona encargada), which processes personal data on the controller’s behalf (Article 2, section XII). Delivering data to the processor is not a transfer: the law defines a transfer as a communication to a person other than the data subject, the controller, or the processor (Article 2, section XX). For that reason, a cloud provider that only hosts and processes data on your company’s instructions does not need the data subject’s consent to receive the data, but neither does it assume the controller’s obligations before the authority.
What your company must guarantee. The controller must establish and maintain administrative, technical, and physical security measures, and may not adopt measures weaker than those it maintains for its own information; it must take into account the risk, the consequences for data subjects, the sensitivity of the data, and technological development (Article 18). It must establish controls so that everyone involved in the processing keeps the information confidential, even after the relationship ends (Article 20). And if a breach occurs that significantly affects the economic or moral rights of data subjects, it must inform them immediately (Article 19).
What the law no longer details. The 2025 law is brief on processors. It does not itself set the content of the contract with the provider or a deadline for the provider to notify the controller of an incident. The controller’s obligations remain intact and must be built through the contract, because the only way to comply with Articles 18, 19, and 20 with information hosted by a third party is for that third party to undertake the same obligations. Accordingly, the clauses described below are contractual best practice derived from those obligations, not literal requirements of the law.
When the provider stops being a processor. The provider is a processor as long as it processes the data on your company’s behalf. If it uses the data for its own purposes, such as compiling commercial statistics or training models, that communication may stop being a processing engagement and become a transfer. In that case, your company must provide the recipient with the privacy notice and the purposes, and the recipient assumes the controller’s obligations (Article 35). Transferring data outside the permitted cases, or without any express consent that is required, are infractions of the highest category (Article 58, sections XII and XIII).
Compensation reaches both. Data subjects who suffer harm due to a breach of the law by the controller or the processor may claim the applicable compensation (Article 53).
What to do and by when
- Classify your cloud providers by the type of data they host, and prioritize those that process sensitive, financial, or customer data.
- Verify that each contract requires the provider to process the data only in accordance with your instructions and for the purposes stated in the privacy notice.
- Require security measures equivalent to or stronger than your own, with the right to request evidence, independent audit reports, or certifications.
- Agree on a fixed deadline, measured in hours, for the provider to notify you of any incident, so that you can inform data subjects immediately.
- Regulate subcontracting: a list of subcontractors, prior notice of changes, and the right to object to them.
- Expressly prohibit the provider from using the data for its own purposes, including model training, unless authorized by you and, where applicable, by the data subject.
- Define the exit: return of the data in a usable format, a transition period, and a certificate of deletion upon termination.
- Keep the contract and the evidence of compliance for at least ten years, as required by Article 49 of the Commercial Code (Código de Comercio).
Recommendations to mitigate risk
The authority in this area, the Ministry of Anti-Corruption and Good Governance (Secretaría Anticorrupción y Buen Gobierno), sanctions the controller. Breaching the security of databases, programs, or equipment, when attributable to the controller, and failing to comply with the duty of confidentiality are punishable by a fine of 200 to 320,000 times the Unit of Measurement and Update (UMA), that is, MXN 23,462 to MXN 37,539,200, under Articles 58, sections VIII and XI, and 59, section III. If sensitive data are involved, the penalties may be increased up to twofold (Article 59, section IV). In setting the fine, the authority considers the nature of the data, whether the conduct was intentional, the controller’s economic capacity, and recidivism (Article 60). Without an adequate contract, your company pays that penalty and has no clear avenue to seek recovery from the provider.
Self-assessment
Answer yes or no about your own company.
- Have you identified the cloud providers that host personal data of customers or employees?
- Does each contract require the provider to process the data only in accordance with your instructions?
- Does the contract set a fixed deadline for the provider to notify you of an incident?
- Can you request evidence of the provider’s security measures?
- Do you know which subcontractors your provider uses, and can you object to changes?
- Has it been agreed how you recover your data and how it is deleted when the contract ends?
- Does the contract prohibit the provider from using your data for its own purposes?
How we approach it at LEXURE
We review contracts with critical providers against the obligations the law imposes on your company as controller, and we negotiate the schedules on processing, security, incidents, and exit. When the provider only offers standard terms, we document internal compensating measures so that the company can show the authority that it acted with due diligence.
If your critical information lives on third-party services, schedule a diagnostic meeting with us and let us review how well protected your company is.
Legal basis
- Federal Law on the Protection of Personal Data Held by Private Parties (Ley Federal de Protección de Datos Personales en Posesión de los Particulares), DOF March 20, 2025, last amended DOF November 14, 2025, Articles 2, sections XII and XX, 18, 19, 20, 35, 53, 58, sections VIII, XI, XII, and XIII, 59, and 60. Current text (opens in a new tab)
- Commercial Code (Código de Comercio), Article 49. Current text (opens in a new tab)
- Value of the Unit of Measurement and Update 2026, National Institute of Statistics and Geography (INEGI). Official publication (opens in a new tab)
This note is for information only and describes the law in force on the verification date. It is not legal advice on a specific matter. It is a translation of the Spanish original: Mexican law is published in Spanish, and the official Spanish texts prevail.