Legal Monaco

Digital sovereignty is not optional.

“Regulatory compliance does not guarantee control over data, infrastructure or technology dependencies.”

Monaco's financial centre must be able to control the infrastructure, the providers and the access rights to which it entrusts its most sensitive data and processes.

Stylised architectural view of Monaco — the Rock, the Palace, the harbour and Monte-Carlo — with data flows leaving for infrastructure in Switzerland, the EU, the UK and the United States. CH EU UK US 43°44′ N · 7°25′ E Jurisdiction?
Flows, infrastructure, jurisdictions
  • Independence
  • Digital sovereignty
  • Board accountability
  • Risk control
  • Data protection
  • Transparent subcontracting chains

The problem

The paperwork is in order. The data is somewhere else.

Contract signed, certificate on file, impact assessment written: the audit will pass. One question remains that few institutions can answer within a week — who could log into the systems holding their clients' data tonight?

What the file shows

Regulatory compliance

  • An outsourcing contract and its schedules
  • A declared hosting country
  • The provider's certification report
  • An exit clause
  • An impact assessment

What you should be able to prove

Operational sovereignty

  • The list of subcontractors, down to those who touch the data
  • Which foreign laws may apply to each of them
  • Who holds administrator access and the encryption keys
  • How long an exit actually takes
  • What is sent to the provider, and why

Our position

Compliance data should stay in Monaco.

KYC files, beneficial ownership, screening results: the most sensitive data in the financial centre. Handing it in bulk to a provider built on a US cloud puts it within reach of the CLOUD Act and FISA Section 702 — a law designed to target non-US persons abroad. In other words, Monaco's clients. And if that data leaks or is seized at the provider, it is the bank that answers for it.

Read our position

Six editorial themes

The issues

Six ways in, one underlying question: who really controls the sensitive data and processes of Monaco's financial centre?

Digital sovereignty

Why a data centre's address says very little about who actually controls the data.

Bank outsourcing

A task can be handed to a provider. The responsibility cannot. The case of AML, KYC and screening tools.

Subcontracting chains

Hosting firms, managed-service providers, support centres: who is working behind the provider the bank chose?

Foreign jurisdictions

CLOUD Act, FISA, Patriot Act, GDPR, UK, Swiss and Monegasque law: what each text says, and who it applies to.

Accountability and governance

What is mandatory, what is recommended, what is good practice — and what ends up on the board's desk.

Systemic and reputational risk

When an incident at a shared provider, or a leak at an intermediary, hits the whole financial centre.

A bank cannot control a risk it has not mapped.

Analysis and publications

Latest analysis

Dated, sourced, and corrected when the law changes. All articles (10)

A · Digital sovereignty4 min

Compliance data should stay in Monaco.

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.

F · Systemic and reputational risk3 min

“Monaco Gate”: the scenario of a mass leak at the intermediaries.

The great leaks of the past decade came from law firms and service providers, rarely from banks. In a financial centre with so many high-profile clients, a leak of that kind would be a shock. The story of a scenario — a hypothetical one.

Methodology

You always know what you are reading.

A sourced fact, a statutory provision, our own reading and a hypothesis are not the same thing. In our articles, each one is labelled. Methodology

  • Documented factsPublic events, with their source.
  • Legal textsStatutes and guidelines, with the exact reference.
  • InterpretationOur reading, presented as such and open to debate.
  • Technical analysisArchitectures, data flows, access, encryption.
  • ScenariosHypotheses — never real events.
  • RecommendationsWhat we advise, kept separate from what the law requires.

Spotted an error, have a source, or disagree? Write to us.

contact@legal-monaco.com