One hand was raised when I asked "Who has read or looked at the actual EU Inc legal proposal itself?" in a session where we discussed the EU Inc proposal and how after adoption it will come to significantly impact the day to day operations of the group of participants. That single hand was already a pleasant surprise, I usually can expect none.

Hardly anyone does read EU legal proposals, even when they already are in force and apply to them. We mostly go by whatever framing by others we’ve come across in the press (like letting Apple tell us that the DMA is not about monopoly busting but ‘security erosion’, or Musk that the DSA is about ‘censorship’, the general misconceptions BigTech have w.r.t. the EU, all the fear mongering around the GDPR), rather than seeing for ourselves.

Always read the actual text of a regulation you see mentioned that might impact you, not other people’s framing

My advice always is to read the actual text of a regulation or proposal you see mentioned or that might impact you. For two reasons, first to see if you may want to influence the final outcome in some way by following its timeline, and second to early on assess what its impact might be on your day to day operations in terms of both opportunities and compliance and plan your responses.

Timelines hold options for influence

The timeline of any law does not start with the publication of a proposal by the Commission, nor does it end with the adoption of the law.

You can already get informed and involved well before a regulation exists.
No European legislation suddenly appears as an immutable thing to comply with, all are the output of a predictable process you can see coming years away. And it is highly useful, and mostly welcomed, to get involved in those regulations that impact things you care about. There are very different ways of getting involved, all along the timeline of creating regulation, as well as after its implementation.

A timeline of how something came about is of course only fully visible in hindsight. But there are usually early signs a proposal will be made, and there are steps that are to be expected in every case.

A policy option might come from a regular impact assessment or review of an earlier law, or some report, or pop up in commissioned research, and all those are announced or tendered out predictably. As a stakeholder it is usually possible to provide your experience and insights in those studies, and if tendered out you might try to be one of the consortium partners executing the study (I e.g. was part of the 2020 study that became the High Value Data Implementing Regulation in 2023). Or there’s a public call for evidence, or consultation for stakeholders to provide input (e.g. with a group of public entities we formulated shared input for the European Data Union Strategy in June 2025).

Then, based on policy options, there will be a Commission proposal, which is the first time there is an actual legal text to look at. The Council (Ministers of Member States), and the Parliament will formulate their own position on the proposal. Both those two processes are a negotiation (between Member States in the Council, and between parties in Parliament) meaning through your national government or European representatives you can likely provide input. For instance in the ongoing INSPIRE directive revision, with a government client I helped formulate phrases for the national response, and participated in a Council meeting with experts from all Member States to discuss technical aspects of the proposed changes. At other times I have had contact with Parliament rapporteurs about their response to a Commission proposal.

Once those positions are established, negotiation happens between all three for a final text (the ‘trilogue’), a phase in which you may have an opportunity to give feedback to contacts you have within either the Council or Parliament. Generally this is I think the phase with the least opportunities to involve yourself.

Once a law is published the timeline does not end. It may become applicable in stages, and not immediately after publication. Reporting cycles will be part of a law, as will be regular reviews, setting future dates to potentially provide feedback.

Early input and practical substance versus political influence
Earlier input has I think a bigger likelihood of ‘sticking’ as the early phases are not about negotiation or who is more powerful at the table, but more about setting the scene and formulating general aspects. For instance, towards the end of 2026 a Commission proposal for new High Value Data themes is expected. Already in May of 2022 in a workshop exploring possible new themes I introduced a topic that I think is relevant, and knew that at the time also was important to the Commission, albeit for different reasons. It ended up in the study report, and got mentioned by the EC civil servants afterwards on multiple occasions. As far as I can tell it will be in the list of themes proposed later this year, four years after I brought it up.

In general I much prefer to ‘talk shop’ outside the political part of the process, also after a law comes into force, e.g. to provide examples of working implementations. Good examples may well have a normative effect on how people think a law needs to be implemented in practice. And then, laws may lead to standards, and helping write those standards is a completely different place to take influence once again. I am for instance involved in the work on standards that are announced in the Data Act.

Where in such a timeline you might be able to provide feedback depends a bit on who you are of course, and where you feel you can be heard based on your expertise or role. Getting involved isn’t always possible for yourself in terms of time and effort, and also isn’t always needed, if you can connect to those who are. Checking who is getting involved in a process is therefore your minimal step to take.

The EU Inc timeline as example

A timeline for a regulation spans years. Although some steps may need very fast responses, there is always time to anticipate, prepare and organise. The EU Inc proposal I mentioned at the top concerns the creation of an EU level business entity that is easy to establish online and recognised in all Member States (in contrast to being e.g. a Dutch entity that still needs to register separately for having a location in Belgium). Here, as an illustration, is the timeline as I see it, for the EU Inc proposal, spanning from early 2024 to 2033:

  • First mention that I encountered: the Letta report on modernising the EU internal market (pdf), April 2024
  • Announced in the Political Guidelines 2024–2029 for the EC (pdf), 18-07-2024
  • Set as deliverable in the Mission letter of the Commissioner for Democracy, Justice and the Rule of Law (pdf), 17-09-2024
  • European Commission’s January 2025 Competitiveness Compass announced the creation of a “28th regime” meaning the start of planning for EuroInc, 29-1-2025
  • Single Market Strategy & Start-up/Scale-up Strategy both mention it as a building block, May 2025
  • Online workshop European Parliament, June 2025
  • Public consultation, and a Call for evidence, July-September 2025
  • Published Proposal for an EU Inc. corporate legal framework in parallel with an EC Communication on it, 18-03-2026
  • Council of Ministers discussions, May-July 2026, Dutch government published a position with Belgium and Luxembourg.
  • Parliament rapporteur draft report (pdf), 29 June 2026, debated mid July 2026
  • Council general position expected September 2026
  • Parliament commission decision expected September 2026, in plenary Q4 2026
  • Trilogue between Commission, Council and Parliament to start in Q4, political agreement perhaps at the end of December 2026, if so:
  • Publication final text, Q1 2027
  • Regulation in force, Q1 2027
  • Regulation applicable, Q1 2028 (to give MS time to adapt national laws, which likely will take more than the allowed year)
  • First reporting by Member States on uptake, 2033
  • Regulation Evaluation, 2033

Choosing your responses

In a second post I will say more about reading a (proposed) law and formulating your responses to it, but a few general words about why that is important when it comes to taking an influence.

EU law is about regulating aspects of the EU single market, and regulations are often aimed at creating new instruments for doing things, removing barriers and differences between national rules, not just, as seems a common assumption, to disallow things. Compliance with EU law is often mostly about making transparent how you operate and that the things you do are prepared and decided in line with regulation. A lot of the data and digital regulation I work with to me seem more akin to quality assurance instruments, a basis to build your own operations on.

This means that forming your opinion about any new regulation means thinking about your specific lens on a topic, what novel affordances you think useful, what barriers you encounter that you’d like to see removed, and what new demands would be placed on you and your organisation’s environment. What is so key to you you want to help actively shape it? What is important to you but you trust other involved actors to come up with the right things? Where do you think you might not be able to influence something important, nor be able to adopt what others will come up with, and how can you prepare for accommodating that?

European Data Protection makes it illegal to transfer person identifiable data to outside the EU. Unless there is equivalence in data protection, or an agreement with guarantees and oversight deemed adequate. For the USA this is the EU-US Data Privacy Framework (DPF). This framework depends on the existence of the independent oversight body FTC, and the Data Protection Review Court (DPRC) which serves as redress mechanism. The arrangement is in place since 2023.

Earlier agreements, the Safe Harbor Agreement (until 2015) and the Privacy Shield Agreement (until 2020), both were struck down in European courts as inadequate (the Schrems I and Schrems II cases).

The DPF always has been a sham. Because in reality it was clear that there was no practical adequacy in any way, let alone that it could be properly enforced. “But there’s independent oversight! The FTC!” has been used as plausible reason to change nothing in practice. Notions of data protection in the USA never aligned with the very different premises of the EU GDPR, and wrapping it in the DPF does not change that. Not even when paying no attention to the intelligence elephant in the room.

The semblance of a functional redress mechanism was already gone when the Trump regime fired most of the DPRC members in early 2025, leaving a single Republican in place where three people are needed for a decision. This placed the framework ‘in doubt’. Harsh words, I know.

The death of the DPR has now been made official by the Supreme Court as it destroyed the independence of the FTC by declaring statutory removal protections unconstitutional. That will wreak havoc in the USA itself no doubt, giving the executive control of all heretofore independent oversight bodies (except for the Federal Reserve to add a bit of inconsistency).
Doing away with the FTC’s independence removes the last pretence of a functioning EU – US Data Privacy Framework.

NOYB, the NGO run by Max Schrems (of the epynomous Schrems I and II verdicts) has called upon the European Commission (PDF) to face the facts and withdraw the adequacy decision about the DPF. It has also announced another lawsuit to ensure the DPF will not remain in place if the EC does not choose to act.

Technology, working in technology, is inherently impacting society, and must concern itself with the democratisation of access and use, and the flow of information. My focus has always been the agency technology can provide, specifically to those who don’t have such agency without it. How it can strengthen community and autonomy. Unintended consequences and externalised effects of creating and using technology do always exist and impact different groups too, and need to be considered in any technology choice. My work in government data is about information and power asymmetries, my work in digital ethics more generally seeks to incorporate a wide range of other values and considerations, my work in tech regulation and standards similarly is to enable agency and confirm and embed values. Ethics is not about saying no to things, it’s about shaping our actions towards each other. Seeing each other as part of every question, not othering others to cut them out of deliberations. Democracy is at its core.
My day to day work in my company is carried by it and my voluntary board work reflects it as well.

My work in technology has always been what I’ve come to call constructive activism. It’s an often less visible way to enable change though than through e.g. overtly campaigning for such change. You can work in relative quiet. There are times however when it becomes needed to more visibly get involved, to be seen to get involved. I increasingly feel we’ve been sliding into such a situation in the past years here in the West.

Defend Democracy is a young civil society organisation, working in Brussels, to strengthen democracy, and defend it against eroding forces from here, elsewhere and from technology. Like my other voluntary board memberships enabling agency is key here. At the Open State Foundation it’s about citizen’s agency based on increased government transparency and better information. At the Open Nederland association of Dutch makers in support of Creative Commons licensing, it’s about makers’ autonomy in what happens to what they make and how it can contribute to society. At the ActivityClub foundation it’s enabling public discourse through a non-toxic common infrastructure (mastodon.nl a.o.). At Defend Democracy it’s about what those other three organisations have in common. Strengthening and defending democracy.

I am joining the board of Defend Democracy as its treasurer.

Bookmarked Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence

Finalised in June, the AI Act (EU 2024/1689) was published yesterday 12-07-2024 and will enter into force after 20 days, on 02-08-2024. Generally the law will be applicable after 2 years, on 02-08-2026, with. a few exceptions:

  • The rules on banned practices (Chapter 2) will become applicable in 6 months, on 02-02-2025, as will the general provisions (Chapter 1)
  • Parts such as the chapter on notified bodies, general purpose AI models (Chapter 5), governance (Chapter 7), penalties (Chapter 12), will become applicable in a year, on 02-08-2025
  • Article 6 in Chapter 3, on the classification rules for high risk AI applications, will apply in 3 years, from 02-02-2027

The purpose of this Regulation is to improve the functioning of the internal market by laying down a uniform legal framework in particular for the development, the placing on the market, the putting into service and the use of artificial intelligence systems (AI systems) in the Union, in accordance with Union values, to promote the uptake of human centric and trustworthy artificial intelligence (AI) while ensuring a high level of protection of health, safety, fundamental rights as enshrined in the Charter of Fundamental Rights of the European Union (the ‘Charter’), including democracy, the rule of law and environmental protection, to protect against the harmful effects of AI systems in the Union, and to support innovation. This Regulation ensures the free movement, cross-border, of AI-based goods and services, thus preventing Member States from imposing restrictions on the development, marketing and use of AI systems, unless explicitly authorised by this Regulation.

A little over a decade ago I was at a small conference, where I happened to share the stage with a British lawyer, Polly Higgins, seeking to internationally criminalise ‘ecocide’, alongside various other speakers. One of those others was a self declared rationalist running a data driven research start-up with billionaire funding. He believed the trickle down innovation trope that usually ends in pulling up the ladder behind them, which can be readily found around all things tech-singularity. And he called himself a futurist. After the talks we as speakers stood on and in front of the stage chatting about the things that had been presented. The futurist, addressing me and one other speaker, chuckled that ‘that eco-lady’ had a nice idea but a naive unrealistic and irrational one that obviously had zero probability of happening. At the time I found it jerkish and jarring, not least given the guys’s absence of expertise in the fields concerned (environment and international law). It’s one of the key moments I remember from that conference, as the condescending remark so strongly clashed with the rest of the event and atmosphere.

Meanwhile we’re some 10 years into the future of that conference. The futurist’s efforts collapsed soon after the conference it seems and there are no recent online traces of him. Polly Higgins is no longer alive, but her cause has very much outlived her. On 26 March the final step in the legislative path of a renewed Directive on the protection of the environment through criminal law has been taken, when the Council of the EU formally approved the text agreed (last November) with the European Parliament. In that new ecocrimes directive preamble 21 uses the phrase ecocide to describe specific crimes covered in the Directive (PDF).

Criminal offences relating to intentional conduct listed in this Directive can lead to catastrophic results, such as widespread pollution, industrial accidents with severe effects on the environment or large-scale forest fires. Where such offences cause the destruction of, or widespread and substantial damage which is either irreversible or long-lasting to, an ecosystem of considerable size or environmental value or a habitat within a protected site, or cause widespread and substantial damage which is either irreversible or long-lasting to the quality of air, soil, or water, such offences, leading to such catastrophic results, should constitute qualified criminal offences and, consequently, be punished with more severe penalties than those applicable in the event of other criminal offences defined in this Directive. Those qualified criminal offences can encompass conduct comparable to ‘ecocide’, which is already covered by the law of certain Member States and which is being discussed in international fora.

Good work barrister Higgins, and the Stop Ecocide organisation.


A photo taken by Polly Higgins of me as we had fun together driving an all electric ‘motor bike’ around the venue’s hallways at that conference in 2013.

Polly Higgins about to take the e-chopper for a spin through the venue.

Bookmarked Commission opens non-compliance investigations against Alphabet, Apple and Meta under the Digital Markets Act (by European Commission)

With the large horizontal legal framework for the single digital market and the single market for data mostly in force and applicable, the EC is initiating first actions. This announcement focuses on app store aspects, on steering (third parties being able to provide users with other paths of paying for services than e.g. Apple’s app store), on (un-)installing any app and freedom to change settings, as well as providers preferencing own services above those of others. Five investigations for suspected non-compliance involving Google (Alphabet), Apple, and Meta (Facebook) have been announced. Amazon and Microsoft are also being investigated in order to clarify aspects that may lead to suspicions of non-compliance.

The investigation into Facebook is about their ‘pay or consent’ model, which is Facebook’s latest attempt to circumvent their GDPR obligations that consent should be freely given. It was clear that their move, even if it allows them to steer clear of GDPR (which is still very uncertain), it would create issues under the Digital Markets Act (DMA).

In the same press release the EC announces that Facebook Messenger is getting a 6 month extension of the period in which to comply with interoperability demands.

The Commission suspects that the measures put in place by these gatekeepers fall short of effective compliance of their obligations under the DMA. … The Commission has also adopted five retention orders addressed to Alphabet, Amazon, Apple, Meta, and Microsoft, asking them to retain documents which might be used to assess their compliance with the DMA obligations, so as to preserve available evidence and ensure effective enforcement.

European Commission