Skip to content

The US CLOUD Act and Swiss board data: the real risk

—10 min read

A key and a locked document box on one side of a dark background and a distant government building outline on the other, joined by a thin dashed line

The US CLOUD Act obliges providers subject to US jurisdiction to comply with valid US orders for data in their possession, custody or control, even if the data is stored outside the United States. For Swiss board data, the risk depends on whether any provider in the chain is reachable by US law and on who holds the encryption keys. It is real but narrow: according to the Swiss Federal Office of Justice it serves criminal investigations, not general surveillance, and adds no duties for providers without a US connection.

What does the CLOUD Act actually say?

The Clarifying Lawful Overseas Use of Data Act was passed in March 2018. Its core provision, 18 U.S.C. § 2713, requires providers of electronic communication services and remote computing services to comply with their obligations under US law to preserve, back up or disclose communications and records in their possession, custody or control, regardless of whether the data is located within or outside the United States. A remote computing service is the provision to the public of computer storage or processing services (18 U.S.C. § 2711(2)): that covers cloud storage, hosted email and most SaaS tools, which can include board portals.

The Act answered the Microsoft case. In 2013 a US court ordered Microsoft to hand over emails of an account; Microsoft produced what sat on US servers but refused the emails stored in Ireland. It won on appeal, the government took the case to the Supreme Court, and Congress passed the CLOUD Act before the Court decided. According to the Swiss Federal Office of Justice, the Act applies only in criminal proceedings.

The Act also allows the US to conclude executive agreements with other countries. The US Department of Justice lists agreements with the United Kingdom (signed 2019) and Australia (2021), negotiations with Canada announced in 2022, and the resumption of EU-US negotiations on electronic evidence in March 2023 (checked 29 October 2026). Switzerland has no such agreement.

Which providers does it reach?

Providers subject to US jurisdiction. In its 2021 report, the Federal Office of Justice explains that this covers companies under US law and requires a minimum connection to the United States (“minimum contacts”), whose interpretation lies with US courts. Companies with US holding companies, subsidiaries or branches can be covered, under some circumstances even foreign cloud providers that advertise their services in the US. Foreign providers without such a connection get no new obligations.

Who could be ordered to disclose board data?
ProviderReached by the CLOUD Act?What it means for you
US company, data in the USYesThe classic case
US company, data in a Swiss data centreYesStorage location does not change it
Swiss company with US parent, subsidiary or branchPossibly, as decided by US courtsAsk about the group structure
Swiss company marketing actively in the USPossibly, as decided by US courtsAsk where it sells and operates
Swiss or EU company with no US connectionNo new obligationsCheck its sub-processors too
Any provider that never holds the keysCan only hand over encrypted dataKey management is decisive

Why is the chain of sub-processors the real question?

Because a board portal is rarely one company. Behind the vendor there is usually a hosting provider, sometimes a separate database or storage service, an email service for notifications, an SMS service for sign-in codes, a monitoring tool and, increasingly, an AI model provider. Each one that holds readable board data is a possible addressee of an order.

So the question is not where the vendor is based, but which companies in the chain hold readable data, and which of them have a US connection. A Swiss vendor with a US-owned database host has the same exposure for that data as a US vendor. A vendor whose US email service sees only names and meeting titles has a much smaller one. Our guide to reading a sub-processor list shows how to check this entry by entry.

How much do encryption and key management help?

A lot, if the provider cannot decrypt. The Federal Office of Justice notes that the CLOUD Act contains no duty to decrypt data that providers hold for their customers, so they cannot be forced to decrypt data the customer encrypted. Whether the provider can decrypt depends on who manages the keys.

Key management and CLOUD Act exposure (after the Federal Office of Justice report, 2021)
Set-upWho can decryptExposure
Client-side encryption, key stays with the customerOnly the customerLargely protected without the customer's cooperation
Server-side, provider manages the keyThe providerProvider can make readable data available
Server-side, customer's own key stored in the cloud (BYOK)The provider, technicallyReadable data can be disclosed
Server-side, key only on the customer's own hardwareOnly the customerSame protection as client-side encryption

The catch for board portals: a web application that displays, annotates and searches documents needs to read them, so the provider or its host usually manages the keys. Encryption at rest then protects against theft from the data centre, not against an order to the provider. Customer-held keys are possible, but they come with costs in functionality and key management that most boards do not want to carry for every paper.

Can a provider resist an order?

Only the provider can, not the customer and not a foreign state, according to the Federal Office of Justice. The CLOUD Act gives providers a specific motion to quash or modify an order for the contents of communications, filed within 14 days, where the customer is not a US person and does not reside in the US, and disclosure would create a material risk of violating the laws of a “qualifying foreign government” (18 U.S.C. § 2703(h)(2)). A qualifying foreign government is one with an executive agreement in force whose laws give providers similar rights to challenge orders (§ 2703(h)(1)).

Because Switzerland has no such agreement, this route is not available for conflicts with Swiss law. Other grounds to challenge an order, such as a common-law comity argument, may still be raised. Contracts can add a layer: a provider can commit to notify you of requests where it is allowed to, to challenge overbroad orders and to disclose only what is required. Ask whether those commitments are in the data processing agreement, not only in a blog post.

Would Swiss law stop a provider in Switzerland from complying?

It may put the provider in a conflict. Under Swiss criminal law, anyone who carries out acts on Swiss territory for a foreign state that are reserved to a public authority, without authorisation, is punishable (Art. 271 StGB), and so is anyone who makes a manufacturing or business secret available to a foreign authority, organisation or private business (Art. 273 StGB). Disclosing personal data abroad must also meet the FADP's transfer rules (Art. 16 and 17 FADP).

The Federal Office of Justice concluded in 2021 that disclosure under a CLOUD Act order is compatible with Swiss and European data protection law only in specific exceptional cases. For providers in the EU, a third-country court order requiring disclosure is only recognised or enforceable if based on an international agreement such as a mutual legal assistance treaty (Art. 48 GDPR). How a particular provider would resolve such a conflict is a question for a lawyer, and one worth asking your vendor directly.

How big is the risk for a Swiss board, really?

For most boards, small but not zero. The CLOUD Act serves criminal investigations, and an order targets data relevant to a specific case. A Swiss company that is not itself involved in a US investigation is unlikely to see its board papers requested. The risk rises with US business, sanctions exposure, or disputes in which US authorities take an interest.

Do not confuse two separate questions. Since 15 September 2024 the United States is on the Swiss list of countries with adequate protection, but only for organisations certified under the Swiss-US Data Privacy Framework (Annex 1 DPO). That concerns whether you may transfer personal data to such a company. It does not change what US authorities may order that company to disclose under US law.

What should the board decide?

A short decision, recorded in the minutes, is better than a vague worry. Classify first, then match the set-up to the class.

Matching board data to the set-up (example classification)
Class of board dataExampleAcceptable set-up
RoutineAnnual calendar, approved minutes of routine itemsAny provider with a sound contract
ConfidentialStrategy, budget, executive payProviders whose chain holds readable data only in Switzerland or the EU, or documented acceptance of a US link
Highly sensitiveAcquisition target, internal investigation, sanctions matterNo US connection anywhere in the chain, or encryption with keys only the company holds, or kept out of cloud tools
  1. Ask every vendor for the jurisdiction of each provider in the chain, not only the hosting location.
  2. Decide whether a US connection anywhere in the chain is acceptable, and for which class of data.
  3. Switch off features that send content to further providers, such as AI or content-bearing email notifications, where the class requires it.
  4. Record the decision and review it when vendors or sub-processors change.

Possible minute entry: “The board takes note of the analysis of the CLOUD Act. It accepts a US connection in the provider chain for routine and confidential papers, provided content-free email notifications are used. Papers on transactions and internal investigations are not uploaded to cloud services; the board office distributes them in the meeting and collects them afterwards.” For the wider picture, see our post on Swiss vs EU hosting for board data.

Konsaro does not claim that Swiss storage alone answers the CLOUD Act question. Board data is stored in Zürich and the application servers run in the EU; every provider involved, with its purpose and location, is listed on the sub-processors page, so you can apply the questions above to us as to any vendor. The information security page shows how IT teams review board tools.

Frequently asked questions

Does the CLOUD Act apply to Swiss companies?

Only if they are subject to US jurisdiction, for example through a US parent, subsidiary or branch, as decided by US courts. Swiss companies without such a connection get no new obligations under the Act.

Does storing data in Switzerland protect against the CLOUD Act?

Not if the provider is subject to US jurisdiction: the Act applies regardless of where the data is located. Storage location matters for providers without a US connection.

Can a US provider refuse to hand over data?

It can challenge an order in court. The specific motion under the CLOUD Act requires a conflict with the laws of a country that has an executive agreement with the US, which Switzerland does not have. Other grounds remain possible.

Will we be told if our board data is requested?

Not necessarily. Notification depends on the order and on what the provider is allowed to disclose. Ask your vendor to commit in the contract to notify you where the law permits it.

Does the Swiss-US Data Privacy Framework solve the CLOUD Act question?

No. The framework lets Swiss companies transfer personal data to certified US organisations without further safeguards. It does not limit what US authorities can order those organisations to disclose.

Would Swiss law forbid a provider in Switzerland from complying?

Disclosure to foreign authorities can conflict with Art. 271 and 273 StGB and with Swiss data protection law. The Federal Office of Justice discusses these conflicts in its 2021 report. Whether a specific disclosure would be lawful is a question for a lawyer.

Sources

  1. 18 U.S.C. § 2713: required preservation and disclosure of communications and records, Legal Information Institute (checked 29 October 2026)
  2. 18 U.S.C. § 2703(h): comity analysis and motions to quash, Legal Information Institute (checked 29 October 2026)
  3. 18 U.S.C. § 2711(2): definition of remote computing service, Legal Information Institute (checked 29 October 2026)
  4. US Department of Justice: CLOUD Act Resources (checked 29 October 2026)
  5. Federal Office of Justice: Bericht zum US CLOUD Act, 17 September 2021 (German) (checked 28 October 2026)
  6. Swiss Criminal Code (StGB, SR 311.0), Art. 271 and 273 (checked 29 October 2026)
  7. Federal Act on Data Protection (FADP, SR 235.1), Art. 16 and 17 (checked 29 October 2026)
  8. Data Protection Ordinance (DPO, SR 235.11), Annex 1 (checked 29 October 2026)
  9. General Data Protection Regulation (EU) 2016/679, Art. 48, EUR-Lex (checked 29 October 2026)
Book in under a minuteSee open times instantly

Interested? Let's talk.

We'll walk you through one full board cycle in Konsaro, from the first board book to signed minutes and assigned actions, and answer your questions live.

Book your demo

30-min video call · Phone call · Email