JavaScript is off, so parts of this page are not showing. The written analysis is in the HTML and reads normally without scripting. What will not appear: the site navigation in the header, the state-of-play ledger, the regulatory status strips, the compliance calendar, the evidence markers and their drawer, the comparison tables, the interactions view, search and the glossary panel — all of which are rendered from data/*.json at runtime.

Every figure behind them is in that directory and can be read directly. The destinations the header would carry are linked here instead:

What applies to me?

Three questions, answered against — rules held as data. Every answer shows the rule that produced it, what that rule turns on, and where it comes from. Where nothing covers your combination, the tool says so rather than guessing.

Read this before you read a result

This is a map of the rulebook, not legal advice, and it cannot become legal advice however many boxes you tick. It asks three questions where a lawyer would ask fifty, and applicability in the real cases usually turns on the facts it does not ask for: your exact service architecture, your contracts, your sector, your Member State, your size over three financial years, and whether a Commission decision has actually been taken about you.

So the answers are graded, and every one of them still needs a case-specific assessment. Likely applies means a rule fires on the facts you gave. Potentially applicable means it turns on something unestablished — and the result tells you what. Likely not applicable is the weakest of the three: an obligation absent here is not a safe harbour. And where no rule matches at all you get Not determined — there is not enough information here to say — never a negative finding. Each result shows its reason, its legal basis and what it did not ask you.

Loading the rule set…