App Copyright Registration in Nepal: Registering Your App's Code and Creative Assets
App copyright registration in Nepal: what to register for a mobile app, what deposits look like, the assignments that come first, and how the certificate pays off.
A mobile app is a bundle of protected works: source code, screens, icons, illustrations, audio, the marketing site. Nepal's Copyright Act protects all of it automatically from creation — and app copyright registration is the voluntary step that turns that automatic right into provable ownership.
This guide sets out what an app team should register, what the filing involves, and the paperwork that has to be fixed before the certificate is worth anything.
In short
App copyright registration in Nepal is voluntary but strategic: protection is automatic under the Copyright Act, 2059 (2002), and registration at the Copyright Registrar's Office adds a dated, government-issued ownership record — the document diligence, platform takedowns and licensing all run on. Register the works that carry disputes and value: the core codebase, the flagship app client, the signature icon set. Fix assignments first — every developer, designer and freelancer signs — then file with code deposits and the prescribed fee per work. The app's name and icon as brand assets are trademark territory at the DOI; copyright covers the expression underneath.
What an app actually owns: the bundle of works
The table's last row is the boundary that matters: copyright protects the expression; the name and the icon's market-facing identity are trademark assets, registered at the Department of Industry on Schedule 1(c) — each class a separate NPR 1,000 application. The two systems stack; neither substitutes for the other.
| Layer | Protected as | Register? |
|---|---|---|
| Source code (front end, back end) | Literary work | Yes — the core codebase at minimum |
| UI screens and layout graphics | Artistic works | Selectively — signature screens |
| App icon and illustration set | Artistic works | Yes for the flagship icon set |
| Audio, animation, video | Respective work categories | Where licensed or at infringement risk |
| App name and logo as brand | Not copyright's job — trademark | DOI filing (Classes 9 and 42) |
Before registration: the assignment audit
Registration records ownership as filed — it cannot cure a broken chain, and app code is where chains break. Every contributor needs paper: employees under IP-clause-bearing contracts, freelancers and agencies under written assignments, and founders under contribution agreements (the cofounder who 'wrote the MVP' without an assignment is the classic Nepalese startup defect).
The audit is short: list the codebase's contributors, find the missing signatures, execute retroactive assignments now. The registration that follows is then a capstone on a clean chain — the document that holds under challenge rather than the one that exposes the gap.
App copyright registration: deposits, fee and certificate
The Registrar's process is light, and the online portal removes the queue. The application states the applicant (author and/or owner — different when rights are assigned), the work's title, type and creation or release dates. The deposits are the work itself: for code, representative source excerpts with version documentation — decide the excerpt scope deliberately, because the certificate describes what was deposited.
The prescribed fee is charged per work: a codebase and a website file as two registrations. The Registrar examines formal compliance — category, deposit, documents — which is a recordal with scrutiny, not an adjudication of originality. The certificate issues with the registration details; file it with the assignment papers in the chain-of-title folder.
What the certificate buys an app business
Four payoffs recur. Diligence: investors and acquirers examining the IP schedule accept the certificate without argument — unproven ownership is the most common Nepalese startup finding. Platform takedowns: clone-app complaints to app stores move on documented ownership. Licensing and publishing: counterparties, platform partners and publishers demand clear chains. Disputes: the presumptive validity of a government-issued record shifts the burden in any ownership argument — including the departed-contractor kind.
The clone problem: how the layers work together
When a clone app appears — lifted icon, copied screens, similar name — enforcement stacks the rights. The copyright certificates ground the takedown demand for the code and creative assets; the registered device mark grounds the icon and name claims; the DOI registration supports the domestic enforcement track. Platforms act fastest on documented ownership, and counterparties facing certificates rather than assertions settle.
The registration work is therefore preventive, not reactive: the afternoon spent registering the core code and the icon set is what makes the clone response a week long instead of a quarter.
The maintenance habit
Apps iterate — and copyright follows creation, so each significant release is new expression on top of the registered base. The pragmatic habit: register the crown jewels once (the core codebase, the flagship client, the icon set), keep the assignment paper flowing with every contributor, and add registrations when a specific work becomes commercially load-bearing. The automatic right covers everything in between; the certificates cover the works whose ownership must be beyond argument.
Want this handled for your brand?
IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.
This article is general information, not legal advice.