620: Compromis

But erasure is not the same as non-existence.

The question isn’t whether it was real. The question is: What did it almost let happen? If you have primary source documentation or a verified EU document reference for Compromis 620, contact this blog via encrypted channel. Until then, treat every “leak” with skepticism—but keep watching the footnotes. compromis 620

Whether it was a migration clause too harsh to defend, a military annex too dangerous to admit, or a digital sovereignty measure too effective for industry to allow—something called Compromis 620 was drafted, debated, and destroyed. But erasure is not the same as non-existence

One former MEP aide (speaking on condition of anonymity) told me: “Compromis 620 was real. It was an eleventh-hour compromise on data residency. But it was never published because three member states threatened to walk unless the language was stripped entirely—and then they demanded the original draft be deleted, not just revised.” What makes Compromis 620 genuinely strange is the metadata. Searching the EU’s PreLex and Consilium databases returns exactly zero results. But searching internal email domains from 2024 shows several references to “620 comp” in calendar invites. Those meetings? All marked “LIMITE” (restricted) or “ÉUREKA” (an informal EU classification for documents that exist but are not to be listed publicly). If you have primary source documentation or a

I believe “620” became a shorthand within the EU Council’s legal service for a family of last-minute, politically toxic edits that were never meant to survive in final law. They were trial balloons, back-channel concessions, or worst-case contingencies—written, negotiated, and then erased from the formal record to preserve the illusion of clean legislation.