Law No. 1.565 vs GDPR for your AI projects in Monaco

Does a Monaco company deploying AI fall under Law No. 1.565 or the GDPR?
Every entity established in Monaco falls under Law No. 1.565 of 3 December 2024 supervised by the APDP. It also falls under the EU GDPR (Article 3(2)) whenever its AI tool serves to offer goods or services to people in the EU or to monitor their behaviour within the Union. The two laws diverge on Monaco’s third-country status, APDP formalities and fine ceilings.
Key points
- Every entity established in Monaco falls under Law No. 1.5651 (Article 3) and adds the GDPR2 (Article 3(2)) when its AI targets or monitors people in the EU, excluding internal payroll (EDPB 3/20183, Example 15).
- The APDP keeps local formalities4 and Monegasque law provides for fines of up to €5M or 2%, and €10M or 4% of global turnover, whichever is higher (Law No. 1.5651, Articles 53 and 54), versus €10M or 2% and €20M or 4% under the GDPR2 (Article 83).
- Two of the eight criteria in Order No. 2025-3615 make a processing operation likely to result in a high risk, hence the Article 35 impact assessment; purely formal approval does not remove a decision’s automated nature (EDPB WP251rev.016).
- With Monaco absent from the Commission’s adequacy page7 and the US absent from Order No. 2026-5488, EU-to-Monaco flows require a safeguard under Article 46 of the GDPR2 or an Article 49 derogation, and those to the US fall under Monaco Articles 98 to 100.
In Monaco, clients and staff cross the French and Italian border daily. Connecting an AI agent raises a question: does Law No. 1.565 of 3 December 20241 apply alone or with Regulation (EU) 2016/679 (GDPR)2? See also AI and personal data and data sovereignty in Monaco.
When a Monaco company falls under both laws
Under Article 3 of Law No. 1.5651, any controller or processor established in Monaco falls under local law, even hosted abroad; a foreign vendor targeting Monaco appoints a written representative (Article 25, save for occasional processing or other exceptions in Article 25), notified to the APDP (Article 7 of Sovereign Ordinance No. 11.3279).
The GDPR2 applies in addition (Article 3(2)) when a Monaco company with no EU establishment links its AI to an offer or monitoring in the EU, with a written representative outside exceptions (Article 27). Under Example 15 of the EDPB Guidelines 3/20183, payroll for French and Italian staff does not trigger the GDPR, unlike a sales agent targeting the EU, also covered by the AI Act (EU 2024/1689)10 (Article 2(1)(c)): see the AI Act in Monaco.
Authorities, retained formalities and sanctions
Article 37 of Law No. 1.5651 entrusts oversight to the APDP (succeeding the CCIN, Article 107); Article 51 of the GDPR2 establishes national authorities, with no one-stop-shop outside an EU establishment under the EDPB Guidelines 3/20183 (Article 56 GDPR).
The record exemption under 50 staff in Monaco (Article 27) or 250 under the GDPR (Article 30(5)) falls away for any recurring tool per the obligations published by the APDP11. Monaco keeps formalities before the APDP4: prior opinion for health research (Articles 58, 78, 79), public biometric or genetic data (Article 77) and criminal matters (Article 64), transfer authorisation (Article 100), and CCTV in premises not open to the public brought without delay to the attention of the APDP (Article 85).
Beyond daily penalties up to €10,000 (Article 51), Law No. 1.5651 caps fines at €5,000,000 or 2% of global turnover (Article 53: security, contracts, records, DPO, DPIA, breach) and €10,000,000 or 4% (Article 54: lawfulness, notice, sensitive data, rights, transfers), versus €10M and €20M under Article 83 of the GDPR2 at the same rates.
DPO, impact assessments and automated decisions
A Data Protection Officer12 is required for regular large-scale monitoring or large-scale sensitive data (Article 29 Law No. 1.565; Article 37 GDPR). Article 12 of Sovereign Ordinance No. 11.3279 requires internal rules ensuring that the DPO does not determine the means and purposes of a processing operation, and the EDPB3 bars combining DPO duties with the EU representative.
Under Ministerial Order No. 2025-3615, two of the eight criteria (innovation, profiling, automated decisions, monitoring, sensitive data, matching, vulnerable people, blocking a right), or one criterion on a considerable data volume (Article 3), suffice to presume a high risk and thus the Article 35 impact assessment (consultation within eight weeks extendable by six, Article 36); otherwise, no harm to rights must be demonstrable (Article 18 Ordinance No. 11.327).
Article 19 of Law No. 1.5651 and Article 22 of the GDPR2 bar solely automated significant decisions, save exceptions carrying where applicable a right to human intervention. Under the EDPB Guidelines WP251rev.016, nominal rubber-stamping remains solely automated.
Monaco as a third country for the EU: asymmetric flows
Monaco does not appear among the countries listed on the Commission’s adequacy decisions page7 and is not recognised as adequate: from the EU to Monaco, the GDPR2 requires, outside derogations (Article 49), Article 46 safeguards such as SCCs on the Commission’s dedicated page13.
From Monaco, Article 97 of Law No. 1.5651 and Order No. 2026-5488 recognise the EU, EEA, Switzerland and the UK, while the APDP notice14 states that the United States were removed from the list initially envisaged. The United States do not appear on the list in Order No. 2026-548, so DPF certification alone does not suffice for a transfer from Monaco, which requires an Article 98 safeguard (for example the Standard Protection Clauses adopted on 11 November 202615), explicit consent (Article 99) or authorisation (Article 100): see transfers outside Monaco.
What to do for an AI tool under each regime
Here are six checkpoints drawn from the texts cited above; when training a model on personal data, the CNIL’s AI recommendations16 also recall setting from the design stage a specified, explicit and legitimate purpose.
- Scope: Law No. 1.565 from local establishment (Art. 3); GDPR added on EU offer or monitoring (Art. 3(2)), with an EU representative outside exceptions (Art. 27).
- Rights: set purpose and legal basis (Art. 5 Law No. 1.565; Art. 6 GDPR), inform people and reply within one month (Arts. 11 and 12; Arts. 12 to 15 GDPR).
- Records and contracts: log every recurring AI tool in the record (Art. 27; Art. 30 GDPR) and bind each processor in writing (Art. 26; Art. 28 GDPR).
- Formalities: check health-research opinions (Arts. 58, 78, 79), transfer authorisation (Art. 100) and private CCTV brought without delay to the attention of the APDP (Art. 85); consult on high residual risk (Art. 36).
- DPO and DPIA: prevent DPO conflicts of interest (Art. 12 Ordinance No. 11.327) and run a DPIA on high risk, presumed from two criteria of Order No. 2025-361 (Art. 35).
- Flows and human review: host in the EU (Art. 97) or frame transfers to the US (Arts. 98 to 100) and from the EU to Monaco (Art. 46 or 49 GDPR), with genuine human validation.
Designing compliant AI with PRAGMA
From the AI audit in Monaco onwards, PRAGMA designs your tools within the framework of Law No. 1.565 and, when you target the Union, the GDPR.
- Human validation: every outgoing message is validated by a person.
- Access and logs: scoped access per agent and full logging of every action.
- Models: client data never trains an external model.
- Hosting: Your tools run today on European servers that we administer ourselves. Hosting in Monaco is available on request, subject to technical and contractual validation.
See also AI for family offices in Monaco and AI in Monaco.
This article provides general information based on the cited texts and does not constitute legal advice: consult a lawyer or the APDP.
Frequently asked questions
Does employing French or Italian residents bring an HR tool under the GDPR?
No: under EDPB Example 15 (3/2018), payroll by a Monaco employer is not offering services (Art. 3(2) GDPR). Only Law No. 1.565 applies, absent monitoring in the EU.
Does Monaco benefit from an EU adequacy decision?
No: Monaco does not appear among the countries listed on the Commission’s adequacy decisions page and is not recognised as adequate; from the EU to Monaco, the GDPR requires, outside derogations (Art. 49), Article 46 safeguards such as SCCs, whereas Monaco to the EU is free (Art. 97).
Is a US vendor certified under the Data Privacy Framework sufficient from Monaco?
No: the United States do not appear on the list in Order No. 2026-548, so DPF certification alone does not suffice from Monaco, which requires an Article 98 safeguard (for example the Standard Protection Clauses adopted on 11 November 2026), explicit consent (Art. 99) or authorisation (Art. 100).
How do fine ceilings differ between the APDP and the GDPR?
Law No. 1.565 caps fines at €5M or 2% (Art. 53) and €10M or 4% (Art. 54), compared with €10M or 2% and €20M or 4% under the GDPR (Art. 83).
Are two separate impact assessments required when both laws apply?
Nothing in the cited texts prohibits drafting a single file; verify that it meets the requirements of each text (Law No. 1.565, Art. 35; Ordinance No. 11.327, Art. 18; Order No. 2025-361; GDPR, Art. 35).
Describe your tools in the contact form for a free initial audit.
Request the free audit and prototype
Sources
- Legimonaco, Loi n° 1.565 du 3 décembre 2024 relative à la protection des données personnelles,
- EUR-Lex, Règlement (UE) 2016/679 du Parlement européen et du Conseil du 27 avril 2016 (RGPD),
- EDPB, Guidelines 3/2018 on the territorial scope of the GDPR (Article 3), Version 2.1,
- APDP, Les formalités à accomplir auprès de l'APDP,
- Legimonaco, Arrêté ministériel n° 2025-361 du 14 juillet 2025 portant application de l'article 35 de la loi n° 1.565 du 3 décembre 2024,
- EDPB, Guidelines on Automated individual decision-making and Profiling (WP251rev.01),
- European Commission, Adequacy decisions: How the EU determines if a non-EU country has an adequate level of data protection,
- Legimonaco, Arrêté ministériel n° 2026-548 du 30 septembre 2026 fixant la liste des pays, territoires et organisations internationales disposant du niveau de protection adéquat,
- Legimonaco, Ordonnance Souveraine n° 11.327 du 10 juillet 2025 portant application de la loi n° 1.565 du 3 décembre 2024,
- EUR-Lex, Règlement (UE) 2024/1689 du 13 juin 2024 établissant des règles harmonisées concernant l'intelligence artificielle (AI Act),
- APDP, Obligations des professionnels,
- APDP, Fiche métier du Délégué à la Protection des Données,
- European Commission, Standard Contractual Clauses (SCC),
- APDP, Publication de la liste des pays, territoires et OI disposant du niveau de protection adéquat,
- APDP, Transferts de données : Clauses Types de Protection,
- CNIL, Développement des systèmes d'IA : les recommandations de la CNIL pour respecter le RGPD,