iGaming software IP ownership: establish the rights chain
A gaming company should be able to show how it obtained the rights needed to use, modify and license its software. Paying an invoice or possessing the source code does not by itself answer every ownership question. Review the complete rights chain.
iGaming Cyprus · Last updated:
Who created the software?
Identify employees, founders, contractors and third-party contributors. The EU computer-program directive addresses economic rights in software created by employees in the course of their duties, subject to contractual provisions. Contractor and cross-border situations need their own analysis.
Do not assume that every contributor falls under the same rule. Record the relevant employer or commissioning entity, contract, jurisdiction and work. A group may discover that code was commissioned by a different company from the one now claiming to license it.
What should the rights register contain?
Create a practical inventory connected to the software components.
| Component | Evidence question |
|---|---|
| Employee-developed code | Which employment and applicable-law provisions govern rights? |
| Contractor work | What assignment or licence was agreed? |
| Purchased software | Which rights and restrictions were acquired? |
| Open-source components | Which licence conditions apply? |
| Third-party assets and content | Are the required uses and sublicensing rights covered? |
What should an assignment or licence clarify?
The agreement should identify the relevant work and permitted uses, with appropriate treatment of modification, distribution, sublicensing and future development. The exact drafting depends on the governing law and commercial arrangement.
Check the chain in both directions. The company must have sufficient rights from contributors and must not promise customers broader rights than it owns. A platform agreement allowing unlimited sublicensing is problematic if a critical component is licensed only for internal use.
How should open-source and supplier dependencies be reviewed?
Maintain a component inventory and review the actual licence terms for the intended use. Do not label all open source as prohibited or assume that every licence is permissive in the same way.
Connect the legal inventory to release management so newly added components are assessed. Preserve notices and other required materials where applicable. Ask technical staff to identify dependencies that may not appear in procurement records.
Why does this matter for a Cyprus IP structure?
The entity receiving IP income should have a supported explanation of its rights and activities. Ownership evidence, tax eligibility and transfer-pricing analysis are separate but connected workstreams.
Before moving or licensing IP within the group, reconcile the rights register, development history and contracts. Resolve missing assignments and restricted components with appropriate advice. Do not create a tax narrative around ownership that the underlying documents cannot establish.
Frequently asked questions
Do not assume so. Review the contract, governing law and rights actually transferred.
No. IP rights and regulated gambling permissions are separate questions.
Sources and scope
- EU Directive 2009/24/EC — computer-program protection and authorship
- Cyprus Ministry of Finance — IP incentive scope
This guide was prepared with AI assistance using the linked sources. It provides general information and practical preparation suggestions, not a legal opinion for a particular business. No personal professional review is claimed.
Get the right structure for your case
Book a free, no-obligation consultation. We’ll confirm the right Cyprus company + licence setup and a fixed fee for your business.