Contact

[email protected]

One address, for everything. State the subject at the top of your message; that is enough to route it.

Reporting an error — the most useful message

An inaccurate article reference, a wrong date, a dead link, a page whose last review date is too old.

This is the enquiry we handle first, by a wide margin. A legal error in a public reference spreads: it gets copied into internal notes, quoted in meetings, reused in tenders. Fixing it quickly matters more than anything else here.

Where you can, state: the page address, the passage concerned, what seems inaccurate, and your source. Corrections to The CRA framework go to the front of the queue.

Suggesting content

A scenario you have lived through, a frequent question that is missing, a distribution case the licence matrix does not cover, an incident worth documenting.

The worked scenarios, the FAQ and the reference incidents are driven by situations people actually encounter. That is what makes them useful.

Asking a question

Before writing, two reflexes answer most questions: the FAQ, which covers around forty, and the glossary.

If your question concerns something the site handles badly or not at all, we want to hear it — it will probably end up in the FAQ.

Reporting a vulnerability in this site

Do not use this page for that. Follow the procedure in Vulnerability disclosure, which states the scope, our response commitments and the safe harbour.

What this site does not do

Worth saying plainly, so nobody wastes their time.

We do not give legal advice. This site is a documentation resource; it is no substitute for counsel. For a question about a specific product, a qualification or litigation risk, speak to a lawyer or to your legal department.

We do not support compliance engagements. We carry out no audits, no classifications and no technical documentation on anyone’s behalf.

We do not answer on behalf of an authority. For anything concerning market surveillance, the designation of a notified body or the reporting of an actively exploited vulnerability, your counterpart is your national authority, not this site. The official entry points are listed in Regulatory watch.

We recommend no product. The tools cited illustrate technical categories, with no commercial relationship of any kind. See Tooling.