White-Label Software IP Terms in Nepal: Who Owns What When Your Platform Wears Another's Brand

White label software IP: the ownership baseline

The first clause to get right is also the one most often fudged: the platform owner retains ownership of the platform — code, architecture, road map — and the reseller receives a licence to operate a branded instance. Nepal's Copyright Act gives the builder automatic copyright in the code from creation; the white-label agreement's job is to state the licence's scope, not to transfer the asset.

The fight this clause prevents arrives at termination, when the reseller who believed they 'bought the system' discovers the contract says licence. Drafting the distinction explicitly — ownership vs. licence, platform vs. instance — is the whole first page of the agreement.

The trademark layer: whose brand is on the product

White-label branding runs in both directions, and both directions need paper. Where the reseller's brand fronts the product, the reseller should own that mark — registered at the DOI (NPR 1,000 per class to file, Classes 9 and 42 for software) — because a brand built on someone else's platform still needs to be theirs when the deal ends. Where the platform owner's marks appear (in the interface, documentation, or co-branding), the licence should define the display and quality-control terms — the standard trademark-licence questions.

Formal, ongoing trademark licences between Nepalese businesses are recordable at the Department of Industry — the licence recordal runs NPR 2,000 per mark — and for royalty-bearing or long-term arrangements the recordal is what makes the arrangement legible to the register, to banks processing royalties, and to diligence later.

Customisations, data and the integration question

White-label deals generate hybrid assets, and the agreement should name each. Customisations — the reseller-funded features built into the instance: default answer is platform ownership with a licence back, or ownership of the custom layer only; silence produces the termination fight. Data: the reseller's customers' data usually belongs to the reseller with defined export and deletion rights; the platform owner's aggregation and improvement rights need their own clause. Integrations: third-party components (payment gateways, SMS providers, map APIs) carry their own licence terms the agreement should not contradict.

Indemnities: who pays when the product infringes

The infringement indemnity is the clause that prices the deal's risk. The standard split: the platform owner indemnifies against claims that the platform itself infringes third-party IP — the code, the bundled libraries, the design assets; the reseller warrants its own brand and content. Both sides should care about the paper underneath: an indemnity is only as good as the chain of title behind the code, which is why employee and contractor assignments are a diligence item in white-label deals, not a formality.

The escrow clause belongs in the same conversation: enterprise resellers (banks, insurers) often demand source-code escrow as the price of dependence on a small platform vendor — a separately negotiated arrangement with a release-trigger framework, not a ToS afterthought.

Termination: the clause the deal is remembered by

White-label relationships end — resellers are acquired, platforms pivot, terms lapse. The termination clause decides whether the ending is administrative or existential: the branded instance's wind-down period, data export and deletion, the fate of customisations, cessation of the mark licences, and survival of confidentiality and indemnity terms. The drafting test is simple: can both sides walk away with what they own and nothing they do not?

For the reseller, one negotiating point is worth the fight: a transition assistance obligation — the platform owner supports migration to a new vendor for a defined period at defined rates. It converts the lock-in fear into a priced service instead of a hostage situation.

The Nepalese drafting reality

Two local notes close the guide. Foreign-platform white-label deals (a Nepalese reseller running a foreign SaaS) add the cross-border layer: royalty payments raise NRB repatriation procedure, and the platform owner's documents arrive needing certified Nepali translations where they reach regulators or courts. And the contract stack should match the registration stack: the agreement's licence and indemnity clauses assume the marks are actually registered — the NPR 1,000-per-class DOI filing is the cheapest clause-support in the whole deal.