Protecting copyright in software has stopped being a purely legal question. The law exists, it is reasonably consistent across the region, and it has been settled for decades. What changed is scale: a publisher can have thousands of unauthorised installations spread across a dozen countries, and no traditional legal structure is sized to handle that case by case.
Data first, law second
A programme that works begins with product telemetry and turns it into a list of identified organisations. That conversion is not trivial. One company appears under several registered names, one machine under several IP addresses, and a share of all detections belongs to customers who already pay.
Clearing that up before anyone is contacted prevents the most expensive mistake in this sector: treating a paying customer as an infringer.
Jurisdiction decides
Once the organisation is identified, the ground becomes legal again — and the differences between countries matter a great deal. Limitation periods, burden of proof, the availability of interim measures and the existence of a criminal route all change at the border.
That is why a programme needs genuine legal capacity in every country where it acts. Not the theoretical option of hiring a firm if negotiation fails, but an admitted firm that has known the file since it was opened.
The objective is regularisation
The measure of a compliance programme is not how many legal actions it starts. It is how many companies end up compliant and remain customers of the publisher. Everything else is the mechanism that makes that conversation credible.