A freelancer from Pune received an order from a long-time acquaintance in Jaipur, to develop a mobile Ludo game with real-money wagering and cash winnings.
The advance payment was already in the account and work was in full swing, but the developer's instincts suggested the project looked dangerously close to illegal gambling. An attempt to consult a local attorney yielded no clear answer. Only after turning to a specialized lawyer did it become clear that India's new criminal law provisions extend liability not only to the organizer but to anyone aiding the operation of a gambling platform. The outcome was favorable, but required swift decisions. The developer immediately halted work, terminated the contract, and did not hand over a single line of source code to the client.
How the Order Was Structured
The contract amount was 60,000 Indian Rupees, of which 20,000 Indian Rupees had been paid as an advance payment. The developer acted solely as a contractor and had no plans to handle hosting, payment processing, or administration. However, the functionality outlined in the technical specification (TOR) included mechanisms for real-money deposits and withdrawal of winnings. The client was the sole initiator and future project operator.
Key Facts That Determined the Legal Assessment
- Parties involved: the developer (Pune), the client (Jaipur), and the lawyer the developer consulted.
- Subject of development: Ludo with real-money wagering and cash winnings mechanics.
- At the time of the legal consultation, the project was in active development and no source code had been handed over.
- An advance payment of 20,000 Indian Rupees had already been received by the developer.
- The developer planned to "disconnect" immediately after delivering the project, believing this would eliminate any risks.
- The legal assessment revealed that developing software for wagering could be classified as aiding the operation of a gambling platform.
- Decision taken: cease work and not transfer the source code.
A Clean Exit and What Made It Possible
The developer took several steps, each of which played its part. Work was stopped immediately. An official notice of contract termination was sent to the client. The matter of the advance payment was handled within the legal framework advised by the attorney. Most importantly, the source code, builds, and access credentials were never transferred. This was precisely what deprived the investigative authorities of grounds to consider the developer a person who had effectively aided the launch of a gambling platform.
Why the Platform Owner Is Not the Only One at Risk
Bharatiya Nyaya Sanhita (BNS) defines liability far more broadly than previous legislation. Punishment applies not only to those who "run" a gaming house but also to those who help it function. Courts interpret the word "aiding" expansively: writing code that enables the acceptance of wagers and the payment of cash winnings falls squarely within that definition, even if the programmer never touched a player's money.
It is precisely because of such risks that freelancers rarely take on gambling game development, and when they do participate in such projects, it is mostly as part of a team. This segment has long been dominated by studios and providers that have in-house lawyers, compliance specialists, and experience working with regulators across different jurisdictions. As experts from Jili Games — a developer of slots, crash games, and instant games for online casinos — explained to us, legal nuances arise constantly and touch every aspect of the process: from drafting the technical specification (TOR) before development begins to obtaining a license. A solo contractor can provide neither legal expertise nor licensing compliance for a client's product, which is why such a contractor is simply not competitive in this market.
Moreover, without an understanding of these nuances, a freelancer risks ending up in a situation from which there is no way out without a lawyer's help — much as nearly happened to the developer from Pune.









