Regulatory compliance is not digital sovereignty.
An institution can have every document in order and still not know who administers its systems, from where, and under which law. That gap is rarely measured.
Editorial theme A / F
“Our data is in Europe.” The sentence is reassuring, and often true. It says nothing about what matters: who runs the servers, who administers them, who holds the keys, and under which law.
Thesis — Sovereignty cannot be read off a data centre's address. It shows in access rights, keys, contracts and applicable law.
When a bank assesses a provider, the first question is almost always where the data is hosted. It is the easiest question to ask and the easiest to satisfy. Three others matter at least as much.
| Level | The question | What settles it |
|---|---|---|
| Physical | Where is the data, including backups and disaster-recovery sites? | A location guaranteed by contract, not just announced |
| Legal | Which laws apply to the operator, its parent and its subcontractors? | An analysis of the law applicable to each entity |
| Operational | Who administers the system, from where, and who holds the keys? | An inventory of access rights and bank-controlled key management |
| Contractual | Can the provider change its terms? Can the bank leave? | Enforceable clauses and an exit that has actually been tested |
Many of the tools banks use — office software, compliance, screening, document management — run on infrastructure from three US providers: Amazon Web Services, Microsoft Azure and Google Cloud. A vendor in London, Geneva or Paris can advertise a European hosting region while relying entirely on one of them.
The bank signs with the vendor. It has no contract with the host, no audit rights over it, and often no information on how encryption keys are handled between the two. Yet that is where its data sits.
Neither text grants automatic access. Both require a legal process, and the major providers say they challenge requests they consider excessive. But the criterion they use is the provider's nationality, not the server's address. For a Monaco client base — made up, by definition, of non-US persons — that is not a detail.
A server in Frankfurt can be administered from Dublin, Bangalore or Seattle, depending on support and monitoring teams. In some cases remote access can itself amount to a data transfer under data-protection law. At the very least it belongs in the risk assessment, which it rarely is.
This is not a legal requirement: Law No. 1.565 regulates transfers out of Monaco; it does not prohibit them. It is a choice about control, and one we believe is justified for this category of data.
An institution can have every document in order and still not know who administers its systems, from where, and under which law. That gap is rarely measured.
The information entrusted to Monaco's financial centre is one of its most valuable assets. Its gradual dispersal to foreign providers raises a question that goes beyond any single institution.
KYC files, beneficial ownership, screening results: the most sensitive data in the financial centre. Our position is that it should be hosted and processed in the Principality, not with a provider built on a US cloud. Here is why, and what it takes.