LLexfolio

Tag: copyright software

  • Do I Own the Code I Write? 8 IPR Myths for Coders, Engineers and Designers in India

    Last updated: 12 November 2026

    Short answer: if you write code, build hardware or design products in India, you automatically get copyright in your original code and artwork, but you do not automatically own what you build for an employer or a client without a written agreement, you cannot protect a bare idea, and you may lose the right to patent or register a design by showing it publicly too early. This guide goes through eight myths that engineers, developers and designers believe about intellectual property, with the correct position on each.

    Want the full picture? This is a self-paced certificate course on intellectual property rights for engineers, coders and designers, covering copyright, patents, designs and trademarks in the way you meet them at work. The course is IPR for Engineers, Coders and Designers, priced at Rs 499.

    Myth 1: “I must register my code or design to get copyright”

    Copyright arises the moment an original work is created and fixed, with no registration. A computer programme is treated as a literary work under the Copyright Act, 1957, and artwork is an artistic work. Registration with the Copyright Office is optional. It is still useful as evidence of authorship and of the date, and it helps when you have to prove ownership in a dispute, but its absence does not weaken the right itself. Keep your own dated records as well: version control history, design files with timestamps and signed drafts.

    Myth 2: “I can copyright my app idea”

    Copyright protects the way something is expressed, not the idea behind it. The concept of an app that matches tutors to students, or a game with a particular mechanic, is free for anyone to use. What is protected is your actual source code, your user interface artwork, your text and your original design files. If two developers write different code for the same idea, neither infringes the other. To protect an idea at the pitch stage, use a confidentiality agreement and keep the detail out of public view until you file the right application.

    Myth 3: “I wrote it, so I own it, even if my employer pays me”

    The author is generally the first owner of a copyright work, but section 17 lists exceptions. The one that matters to most engineers is that a work made in the course of the author’s employment under a contract of service or apprenticeship belongs to the employer, unless the parties agreed otherwise. The words “course of employment” matter. Code you wrote on your own time for a personal project, without using the employer’s resources and unrelated to its business, is a different case, but your employment agreement may include a clause that claims inventions or works related to the business. Read the IP clause before you start a side project, and ask for written clearance if the project is close to your employer’s work.

    Myth 4: “The client paid, so the client owns the code or the design”

    For a freelancer or an agency, the opposite is generally true unless the contract says so. An assignment of copyright is valid only if it is in writing and signed by the assignor (section 19(1) of the Copyright Act). It should identify the work and state the rights assigned, the duration and the territorial extent (section 19(2)). If the period is not stated it is deemed to be five years, and if the territory is not stated it is presumed to extend only within India (section 19(5) and 19(6)). So a payment alone does not move ownership, and a short assignment with no term can lapse after five years. The author also keeps moral rights under section 57, such as the right to claim authorship and to object to distortion that harms honour or reputation, which is why many contracts include a limited waiver or acknowledgment.

    Practical rule for freelancers: say whether you are assigning or licensing, for how long, for which territory and for which uses, and retain rights in your reusable tools and libraries. Practical rule for clients: ask for a full assignment for the whole term and the world, plus a warranty that the work is original.

    Myth 5: “Software cannot be patented in India” and its opposite, “any algorithm can be patented”

    Both are wrong. Section 3(k) of the Patents Act, 1970 says that “a mathematical or business method or a computer programme per se or algorithms” is not an invention. The key words are “per se”. A claim to code, a formula, or a bare business method is excluded. A claim to a technical solution implemented in software, which produces a real technical effect, has a better chance. The Patent Office published revised guidelines on computer related inventions in 2025 (a draft came out for comment in March 2025), and the draft listed technical effects such as higher speed, reduced memory access time, better control of a device and security enhancement, and said that an invention that improves how the computer itself works cannot be rejected merely as a programme per se. These are guidelines, not law, and examiners and courts decide case by case. If your invention has a hardware or process element, describe that element clearly.

    Myth 6: “Open source means free for any use”

    Open source software is licensed, not abandoned. The licence decides what you may do. A permissive licence usually lets you use and modify the code with attribution. A copyleft licence may require you to release your own code under the same terms if you distribute a combined work. Using a library without reading its licence can leave a company unable to ship a product or to pass an investor’s technical diligence. Keep a list of third party components and their licences. Code you find on a public site without a licence is not free to use, and copyright still belongs to its author.

    Myth 7: “I can show my invention at a demo day and still file a patent afterwards”

    A patent is granted for something new. If your invention has been disclosed to the public before you file, you may lose novelty. India does not have a general grace period for your own disclosure. The Act contains narrow situations in section 31, and the Patents (Amendment) Rules, 2024 added a procedure under Rule 29A, with Form 31, to be used within 12 months of the disclosure. Do not rely on it. File first, at least a provisional application, and present afterwards. The same logic applies to designs: under the Designs Act, 2000, a design is not registrable if it was disclosed to the public before the filing date, and novelty is assessed worldwide.

    Myth 8: “Copyright already protects my product design”

    For designs of articles made in quantity, copyright is limited. Section 15 of the Copyright Act says copyright does not subsist in a design that is registered under the Designs Act, 2000, and that copyright in a design capable of being registered but not registered ceases once the article has been reproduced more than fifty times by an industrial process by the owner. So a mass produced bottle, chair or casing design that you never registered may lose copyright protection once production crosses that line. Registration lasts ten years from the date of registration and can be renewed once for five years, for a maximum of fifteen. A design means the look of the article: shape, pattern, ornament or colour composition, judged by the eye. Purely functional features are not protected by design registration, and a trademark or an artistic work is dealt with under its own law.

    Quick reference

    If you madeMain rightRegistration needed?
    Source code, documentationCopyright (literary work)No, optional
    Logo, illustration, UI artworkCopyright (artistic work); trademark for a logo used as a brandCopyright no; trademark yes for full protection
    New technical process or devicePatent (20 year term from the filing date)Yes, and file before public disclosure
    Look of a manufactured productRegistered designYes, to keep protection beyond fifty articles
    Brand name or logoTrademark, valid ten years and renewableYes for statutory protection
    Confidential know howContract and confidenceNo

    Do not use the registered mark symbol before registration. The symbol ™ may be used once you have filed or even before, but the Trade Marks Act treats falsely representing a mark as registered as an offence.

    Know your rights before you sign. The Lexfolio course on intellectual property for engineers, coders and designers is a self-paced certificate course aimed at people who create things for a living. The course is IPR for Engineers, Coders and Designers, priced at Rs 499.

    Frequently asked questions

    Does my employer own side projects I build at home?

    Not automatically. Ownership of work made in the course of employment goes to the employer, but a personal project outside that course may be yours. Your employment agreement may claim more, so read the IP clause and take written clearance when in doubt.

    Is a software licence the same as an assignment?

    No. An assignment transfers ownership of the rights, while a licence gives permission to use them. A licence can be exclusive or non-exclusive and limited by time and territory, and the original owner keeps the underlying right.

    Can I reuse code I wrote for one client in another project?

    It depends on the contract. If you assigned all rights in the code, reuse can infringe the client’s rights. Keep your general purpose libraries out of the assignment, or license them to the client instead.

    How long does copyright in software last?

    For a literary work such as a programme by an identified author, the term is the author’s lifetime plus sixty years from the year after death. Other categories and joint works have their own rules.

    Is a design patent available in India?

    India has registered designs under the Designs Act, 2000, not design patents. Registration protects the visual appearance of an article for ten years, renewable once for five.

    This article is general information, not legal advice for a specific case. Laws, guidelines and fees change, so confirm current requirements with a registered patent agent, an advocate or the relevant registry. Lexfolio is a learning resource.