In one paragraph. 18 U.S.C. § 2713, the CLOUD Act, obliges a provider to "preserve, comply with, and produce" any data in its possession, custody or control, regardless of whether that data physically sits in the EU or abroad. GitHub is a wholly-owned subsidiary of Microsoft Corporation: a US company in a US jurisdiction. That makes every repository on github.com reachable by US process, even one whose files are served from Frankfurt. Codeberg, at the other end, is operated by Codeberg e.V., a registered non-profit association under German law, headquartered in Berlin. It is not a provider in the jurisdiction of the United States, so the Act never reaches it. For us, nine repositories on codeberg.org/PrivateLocalAI, an inference stack that runs in our own engine room, that is not ideology, it is a compliance decision with a file location.
A repository is personal data, full stop
People treat source code as if the GDPR did not apply to it. It does. A repository carries contributor names and email addresses (git author metadata is baked into every commit), branch and issue discussions, access logs, membership rosters. Under Article 4(1) of the GDPR most of that is personal data about identifiable people, maintainers, contributors, candidates, and once a US provider holds it, Chapter V of the GDPR says a third-country transfer has taken place. After Schrems II (C-311/18), the organisation using the service carries the homework: standard contractual clauses alone are not enough; you need a transfer impact assessment and, where needed, supplementary measures that actually deliver essentially equivalent protection. We wrote the mechanics of this in an earlier post, "Your data, your jurisdiction", nothing changes because the data happens to be C++ and Rust.
What the CLOUD Act actually compels
The statute is unusually plain, which is why it bites. § 2713(a) requires a provider service to "preserve, comply with, and produce any communication, call, or other recording or other information in its possession, custody, or control regardless of the location of such communication, call, record or information." The old argument that US process only reaches data stored on US servers was specifically cancelled by the 2018 Act, Microsoft Corp. v. Microsoft, the case the Act partly codifies, had died on exactly that question: a provider in Washington could be compelled to produce email stored in Ireland.
The test is not "where does the file sit". The test is whether the provider is an entity "in the jurisdiction of the United States." Microsoft, and therefore GitHub, plainly is. An EU-mirrored git host does not change that: Azure-hosted enterprise endpoints, Frankfurt regions, a sub-page served from Europe, all cosmetic against § 2713. The obligation attaches to the company, not the data centre.
Why Codeberg e.V. is different in kind, not in promise
Codeberg is not a company that found a friendlier cloud; it is an association, an eingetragener Verein registered under German law, based in Berlin, non-profit by construction, run democratically by its members. The forge itself (codeberg.org) runs on Forgejo software, maintained by the community and hosted for the community by the association. The difference between Codeberg and GitHub is therefore not a difference of promises, it is a question of whose law governs the provider at all:
- For GitHub: US jurisdiction first. US process reaches our repositories in Berlin, Tokyo or San Francisco; then GDPR becomes our headache to paper over with SCCs and assessments.
- For Codeberg e.V.: German law and the GDPR apply directly, as domestic processing. Chapter V never even opens, because there is no third-country transfer to assess. No § 2713 obligation exists on the provider side for anyone to invoke.
This is what "moving away from US-hosted services" actually accomplishes, stated honestly: not that American law disappears, but that it stops having any route into your systems at all. A company that keeps its inference on its own hardware and now keeps its source history with a Berlin non-profit has simply removed the transatlantic conflict from its compliance register, there is nothing left to assess, no SCC module to pick, no TIA file to keep updated, because the provider never falls within reach of US compelled disclosure.
The honest caveats
Two, so this stays a serious post and not marketing:
- Jurisdiction follows the provider, but so does pragmatism. We still mirror everything; git is a distributed tool by design, and forks are free as in forkable. Moving to Codeberg does not mean locking anything away, codeberg.org/PrivateLocalAI stays open, and a mirror is one
git pushaway from anywhere it used to be. - One forge does not make the stack compliant. Our inference engines, llama.cpp, Strata, Avalon, FreeToken, Xolotl, run on hardware in our own building for exactly the same reason the repositories moved: an air-gapped or on-prem deployment never leaves the jurisdiction either. The git host change is one line in a register; the inference stack being physically ours is the big one. Both live or die by the same principle: whatever you cannot transfer out of the jurisdiction cannot be compelled into it.
If your compliance team keeps asking whether your US AI or git vendor "tramples" European privacy law, and after Schrems II they must ask, there is a quieter answer than an assessment file. It lives in Frankfurt, Berlin, or your own rack. We put ours on the internet as codeberg.org/PrivateLocalAI.
Related reading: Code on EU soil: why nine repositories moved to a Berlin non-profit and Your data, your jurisdiction.

Leave a Reply