Software licence compliance
Regularising in time costs less than arguing it in court.
We act on behalf of software rights holders. If a communication from us has reached you, the objective is to agree a regularisation: here is what that means and what to do next.
The communication
What it means that we contacted you
It is not an automated notice.
We have verified unlicensed software use associated with your organisation, and we act on behalf of the rights holder. Before writing to you there is prior verification of the company, of the use established and of the period it corresponds to.
The objective of the communication is to agree a regularisation. In the very large majority of the cases we handle, the matter closes with an agreement and the company carries on using the product under a valid licence.
What to do now
Three steps
The sooner the conversation opens, the simpler and cheaper it is to close.
Gather your licence records
Purchase invoices, subscription contracts, keys, and the inventory of machines where the product is installed.
Reply quoting the case reference
Write to us quoting the reference. We assign a contact who works in your country and your language.
We agree scope and regularisation
Actual use, the licences required and the timeline are established. The agreement closes the matter and leaves the company compliant.
Why it matters
What unlicensed software actually puts at risk
It is not only the invoice for the missing licences.
The company answers for it
Security exposure
Technical continuity
Tenders and procurement
The cost of waiting
Where we are
A local firm in your country, not a letter from another continent
Head office in Bogotá, with our own offices and associated firms across the region. We give local coverage across the Spanish-speaking countries, and the conversation always stays in the language and time zone of the company.
- Office
- Spanish-speaking countries
- Outside coverage
Insights
What we publish
The real cost of unlicensed software
Beyond the missing licences, unlicensed software brings security exposure, legal risk and lost time. What a company actually pays.
Subcontracting does not transfer liability for unlicensed software
If the work delivered to you was produced on uncertified licences, the company that commissioned it can answer alongside whoever installed. What the control test says, and what to require by contract.
Protecting software copyright at scale
Detecting unauthorised use is now a data problem before it is a legal one. How to build a programme that works across several jurisdictions at once.
Write to us
If you have a case reference, quote it in your message. We reply within one business day.
