Where to host an AI tool in Monaco: Principality, European Union or non-EU

Where can a Monaco company host an AI tool?
It may host in Monaco or inside the EU without prior transfer formalities under Article 97 of Law No. 1.565. Calling a US provider requires Article 98 safeguards, such as the Standard Protection Clauses adopted by the APDP on 11 November 2026. The choice also hinges on inference mode, keys and AMSN rules.
Key points
- Hosting in Monaco is not a transfer, and the EU is presumed adequate (Article 97 of Law No. 1.5651); a GDPR2 flow from the EU to Monaco requires an Article 46 safeguard, or an Article 49 derogation.
- Towards the United States, absent from Order No. 2026-5483, transfers require an Article 98 safeguard (APDP standard clauses4 or other), explicit consent (Article 99) or authorisation (Article 100), under penalty of a fine of up to €10M or 4% of turnover.
- Because inference reads clear text in memory, encryption is insufficient where a third-country processor holds the keys under disproportionate access laws (EDPB 01/20205, for GDPR exporters, relevant by analogy in Monaco).
- Vital operators fall under Law No. 1.4356, and the PINH standard7 restricts qualified cloud data and logs to Monaco or its e-Embassy in Luxembourg.
Connecting an AI agent to email, a CRM or contracts commits the location of servers, indexes and backups under Law No. 1.565 of 3 December 20241. This article extends our guides on data sovereignty and AI in Monaco and AI and personal data in Monaco.
Monaco, European Union, non-EU: three legal regimes
Under Article 3 of Law No. 1.5651, any controller or processor established in Monaco falls under Monegasque law regardless of server location. For the APDP (transfer scenarios8), a transfer covers foreign hosting and remote access (maintenance included): staying in Monaco without foreign remote access avoids it.
Article 97 of Law No. 1.5651 deems all twenty-seven EU Member States adequate, confirmed by Order No. 2026-548 of 30 September 20263 alongside, notably, Andorra, Argentina, Brazil, Canada, Iceland, Liechtenstein, Norway, Switzerland and the United Kingdom: flows from Monaco require no prior formality. As Monaco is absent from the European Commission adequacy list9, GDPR2 flows from the EU to Monaco require Articles 45 and 46.
For the United States, absent from Order No. 2026-5483, the EU-US framework does not apply from Monaco. Article 98 applies via the five sets of Standard Protection Clauses adopted on 11 November 2026 by APDP Deliberation No. 2026-244, including four inspired by the EU standard contractual clauses and one complete model, together with addendum clauses to the EU clauses, failing which Articles 99 or 100, backed by fines up to 10 million euros or 4% of global turnover (Article 54 of Law No. 1.5651; see transfers outside Monaco for AI).
External API vs controlled servers: what changes
Calling a third-party API makes that vendor a processor under Article 26 of Law No. 1.5651 and Article 8 of Sovereign Ordinance No. 11.327 of 10 July 202510: written contract, documented instructions, deletion of data and copies at contract end, audit, prior written authorisation for any sub-processor and information on any change under general authorisation. The CNIL11 stresses checking the entire chain.
A language model reads prompts in clear text in memory. Under EDPB Recommendations 01/2020 (Use Case 6, paragraphs 94 and 95)5, TLS and at-rest encryption do not suffice against cleartext processing where the provider holds the keys and third-country legislation allows disproportionate access; this recommendation for GDPR exporters is useful by analogy in Monaco.
A dedicated model on controlled servers in Europe or Monaco keeps prompts and indexes in-house. Article 32 of the Data Act (Regulation (EU) 2023/2854)12 obliges providers of data processing services to take all adequate measures to prevent third-country authorities from accessing non-personal data held in the EU where such access risks conflicting with Union or national law.
Encryption, access, logs and backups
Article 31 of Law No. 1.5651 requires pseudonymisation, encryption and resilience (fines up to 5 million euros or 2% of turnover, Article 53). The EDPB (paragraph 84)5 recommends keys retained under the sole control of the exporter. The PINH annexed to Order No. 2026-597 (10.1, 10.2, 10.5) requires protecting keys with a security container or disjoint medium, cites one key per client as an example and governs flow encryption; Chapter 3.3.2 specifies that the client must add its own encryption.
Article 13 of Ordinance No. 11.32710 restricts processing to instructions and provides, among possible security measures for sensitive data, for being able to verify which data were entered, when, by whom and to which recipients they were transmitted. The PINH7 (12.6 to 12.8) sets six months of time-stamped logs on a separate physical machine.
Under Chapter 12.5 of the PINH7, daily backups sit at safe distance, obey production rules and use encrypted inter-site links; backup access traces are reviewed monthly and restoration is tested regularly. Where backups sit outside Monaco, the destination country and Article 98 safeguards must appear in the Article 27 register under Law No. 1.5651.
AMSN framework, vital operators and PINH qualification
Operators of Vital Importance (OIV), governed by Articles 26 to 29 of Law No. 1.4356 and Order No. 2018-105313, declare vital systems to the AMSN before commissioning, apply its rules, undergo inspections and report major incidents without delay (fines of 150,000 and 750,000 euros).
Under Article 6 f) of Ordinance No. 8.50414, the AMSN qualifies PINH providers via Order No. 2026-5915 (IaaS, CaaS, PaaS, SaaS): under its annex7 (19.2, 19.6), data and logs stay in Monaco or the Luxembourg e-Embassy, administration runs from Monaco, France or Italy, and non-Monaco/non-EU capital is capped at 24% and 39%.
Monaco Cloud16 operates the State sovereign cloud with Monegasque capital, local storage and AMSN homologation (Monaco Cloud and sovereign cloud). Appendix 2 of the PINH annex7 recommends that the client require qualification in the contract.
Five practical criteria to choose your hosting
Five checks drawn from Law No. 1.5651 and the PINH7 guide the decision.
- Status: OIV status (Law No. 1.4356), professional secrecy or contractual residency in Monaco.
- Flows: free flow to the EU (Article 97 of Law No. 1.5651), versus GDPR2 rules from the EU to Monaco.
- Model: controlled servers to avoid cleartext processing by a third party holding keys (EDPB 01/20205).
- Scope: hosting and remote access, maintenance included (APDP guide8), plus backups, logs and support (PINH7, 12.5, 12.6, 19.2).
- Impact: assessment required before high-risk processing (Article 35 of Law No. 1.5651 and Article 18 of Ordinance No. 11.32710).
An AI audit in Monaco settles these choices before production deployment.
How PRAGMA applies these rules
PRAGMA designs custom software and AI agents within the framework of Law No. 1.5651.
- Your tools run today on European servers that we administer ourselves. Hosting in Monaco is available on request, subject to technical and contractual validation.
- Every outgoing message is approved by a person before anything is sent.
- Each agent’s access is restricted solely to the required tools and files.
- Every action is logged so operations remain verifiable.
- Client data never trains an external model.
See also AI for family offices and firms in Monaco and AI in Monaco with PRAGMA.
This article provides general information drawn from the official texts cited and does not constitute legal advice: for your specific situation, consult a lawyer or the APDP.
Frequently asked questions
Can a Monaco company host an AI tool in the European Union?
Yes. Article 97 of Law No. 1.565 and Order No. 2026-548 recognise the EU as adequate without prior formality, subject to a contract (Article 26), register (Article 27) and security (Article 31).
Is the EU-US Data Privacy Framework enough from Monaco?
No. With the United States absent from Order No. 2026-548, a US API requires Article 98 safeguards, including the APDP Standard Protection Clauses of 11 November 2026.
Why is encryption not enough with an API outside Europe?
Inference reads clear text in memory: under EDPB 01/2020 (Use Case 6, for GDPR exporters, useful by analogy in Monaco), TLS and at-rest encryption fail if the provider holds keys under disproportionate access.
Who is subject to AMSN security rules in Monaco?
Vital operators (Law No. 1.435 and Order No. 2018-1053) declare vital systems and incidents to the AMSN, which also qualifies PINH cloud providers (Order No. 2026-59).
Where do AI tools built by PRAGMA run?
Your tools run today on European servers that we administer ourselves. Hosting in Monaco is available on request, subject to technical and contractual validation. A person approves every outgoing message, access is scoped, every action is logged and client data never trains an external model.
Describe your tools in the contact form to review your hosting setup.
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 27 avril 2016 relatif à la protection des personnes physiques à l'égard du traitement des données à caractère personnel (RGPD),
- 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,
- Autorité de Protection des Données Personnelles (APDP), Transferts de données : Clauses Types de Protection (délibération n° 2026-24 du 11 novembre 2026),
- Comité européen de la protection des données (EDPB), Recommendations 01/2020 on measures that supplement transfer tools to ensure compliance with the EU level of protection of personal data (Version 2.0),
- Legimonaco, Loi n° 1.435 du 8 novembre 2016 relative à la lutte contre la criminalité technologique,
- Journal de Monaco / AMSN, Référentiel d'exigences concernant la qualification des prestataires d'informatique en nuage et d'hébergement (PINH), annexe à l'arrêté ministériel n° 2026-59,
- Autorité de Protection des Données Personnelles (APDP), Les transferts de données hors Principauté : les scénarios à envisager,
- Commission européenne, Data protection adequacy for non-EU countries,
- Legimonaco, Ordonnance Souveraine n° 11.327 du 10 juillet 2025 portant application de la loi n° 1.565 du 3 décembre 2024,
- CNIL, Sécurité : Gérer la sous-traitance,
- EUR-Lex, Règlement (UE) 2023/2854 du 13 décembre 2023 concernant des règles harmonisées portant sur l'équité de l'accès aux données et de l'utilisation des données (Data Act),
- Legimonaco, Arrêté ministériel n° 2018-1053 du 8 novembre 2018 fixant les règles de sécurité des systèmes d'information des opérateurs d'importance vitale,
- Legimonaco, Ordonnance Souveraine n° 8.504 du 18 février 2021 portant application de l'article 24 de la loi n° 1.435 du 8 novembre 2016,
- Legimonaco, Arrêté ministériel n° 2026-59 du 5 février 2026 définissant le référentiel d'exigences pour la qualification des prestataires d'informatique en nuage et d'hébergement,
- Monaco Cloud, Monaco Cloud, opérateur du Cloud Souverain d'État de Monaco,