EdTech IP in Nepal: Protecting an Education App Beyond Its Name
EdTech IP in Nepal: the protection stack for education apps — trademark classes 9, 41 and 42, copyright on content and code, and the ownership traps growth creates.
A Nepalese edtech app is two businesses in one product: a brand students search for, and a content library someone spent years building — courses, videos, question banks, explanations. Most founders protect the first and assume the second.
The assumption costs money at the worst moments: a co-founder leaves with the content, a competitor clones the course structure, an investor's diligence finds no one owns the code. The edtech IP stack is short; the mistakes are predictable.
In short
An edtech business in Nepal protects itself with trademarks in Class 9 (the app), Class 41 (education services) and Class 42 (software development and hosting) — NPR 1,000 to file and NPR 5,000 to register per class — plus copyright, which arises automatically on creation for the course content, code and design, with voluntary registration at the Copyright Registrar's Office as the dated evidence investors and licensees ask for. Software itself is not patentable subject matter in Nepal in the ordinary case; the protection runs on copyright, contracts and secrecy. The traps are ownership ones: every developer's and content-writer's work needs written assignment terms from day one.
The edtech trademark layer: three classes, not one
Nepal's single-class rule turns that map into separate Schedule 1(c) applications — NPR 1,000 each at filing, NPR 5,000 at registration, each renewed on its own 7-year clock at NPR 3,500 per class. Clear the name in both scripts before adopting: an education brand serves a bilingual market, and cross-script sound-alikes are treated as conflicting marks. File before the launch campaign — first-to-file rewards the application date, not the marketing date.
| Class | Covers | Why it matters |
|---|---|---|
| 9 | Recorded software, downloadable apps | The app as a product |
| 41 | Education, training, e-learning services | What the app actually delivers |
| 42 | Software development, hosting, SaaS | The technology services underneath |
| 35 | Advertising and platform services | Where marketplace-style operations run |
The content layer: copyright does the work
Course videos, question banks, explanations, illustrations, the app's code — all protected automatically on creation under the Copyright Act, 2059. No filing creates the right; what filing (voluntary registration at the Copyright Registrar's Office) creates is the dated, official ownership record that investors, school clients and licensees ask for, and that a dispute consumes first.
The strategic note founders miss: software is not patentable subject matter in Nepal in the ordinary case, so the technology's protection runs on copyright + contracts + secrecy — copyright on the code and UI assets, licence terms on the contracts, and confidentiality around the parts worth keeping closed. The site's software protection guide maps the split; the app registration guide walks the filing.
The ownership traps that actually hurt
Three recur in Nepalese edtech. The freelancer's syllabus: content written by contractors without written assignment terms belongs to the contractors — the company licensed nothing it can enforce. The departing developer: code written before a proper employment IP clause exists leaves with its author. The co-founder's library: the question bank one founder brought in, never assigned to the company, becomes the dispute when the founder exits.
All three have the same cure, and it is cheap: employee IP clauses in every contract, written assignments with every freelancer and content partner, and a founder-level contribution agreement before any funding round. The fix costs an afternoon per person; the omission costs the diligence round — the site's employee assignment guide provides the clauses.
The school-client contract
- Licence, not sale — institutional deals grant the school a defined right to use the platform and content, scoped by users, campuses and term
- Content stays yours — the agreement states that courses, question banks and materials remain the company's property, whatever the school does with its own data
- Student data and privacy — schools will ask; the contract should say who holds what and what happens to it at expiry
- Exit terms — what the school keeps, what it deletes, and whether its teachers' accounts survive the contract's end
Growth, clones and the funding file
Watch for the clones
A copied course or a lookalike app name surfaces on the Bulletin at publication (90-day opposition window) and on the app stores immediately — document, demand, escalate.
Licence expansion on paper
New districts, new languages, white-label versions for other institutions — each expansion is a written licence, not an email understanding.
Prepare the IP file for funding
Registrations, assignments, licences and the cap table of who owns what — the diligence pack that turns 'we built everything' into a verifiable claim.
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.