Are Computer Program Algorithms Protected by Copyright in New Zealand?

If you are building software in New Zealand, one of the easiest mistakes to make is assuming your algorithm is automatically protected just because you wrote it down in code. Another common error is copying the structure or logic of a competitor’s system and thinking it is safe because the wording is different. A third is relying on copyright alone, without sorting out contracts, confidentiality, ownership clauses, and trade mark protection around the product.

The short answer is that copyright can protect the source code and other original expression connected to a computer program, but it does not usually protect the underlying idea, method, or mathematical logic of an algorithm in the abstract. That distinction matters before you sign a developer agreement, share your technical documents with investors, or spend money on building a platform around a supposedly exclusive process. This guide explains what New Zealand businesses need to know, where founders often get caught, and what to do if your value sits in software logic rather than branding alone.

Overview

In New Zealand, copyright generally protects the way software is expressed, not the bare idea or function behind it. For most businesses, that means code, architecture documents, user interface text, diagrams, and technical material may be protected if they are original, while the underlying algorithmic concept may not be protected by copyright on its own.

This becomes a practical issue when you are outsourcing development, pitching your product, entering a collaboration, or trying to stop a competitor from producing a similar tool with different code.

• Copyright usually protects original source code and object code as literary works.
• Copyright does not generally protect ideas, procedures, systems, or mathematical methods by themselves.
• An algorithm described at a high level may be hard to protect unless it is tied to original written expression or code.
• Confidentiality terms and IP ownership clauses are often just as important as copyright.
• Patents may be relevant in limited cases, but software patentability in New Zealand has special rules and needs tailored advice.
• Trade marks protect branding, not the software logic itself.
• Clear contracts matter before you engage developers, contractors, agencies, or technical co-founders.

What Are Computer Program Algorithms Protected by Copyright Means For New Zealand Businesses

For New Zealand businesses, the real answer is this: copyright can help protect your software, but it is not a blanket monopoly over how the software works.

That is why founders get a nasty surprise when they discover a rival can sometimes build something functionally similar without copying their actual code. If the competitor independently writes its own code and does not reproduce your original expression, copyright may not stop them just because the result performs a similar task.

What copyright can protect

Under New Zealand copyright principles, computer programs are generally treated as literary works. That means copyright can potentially protect the original expression in materials such as:

• source code
• object code
• software documentation
• technical specifications
• flowcharts and architecture diagrams
• database structure or compilations, in some circumstances
• screen text, help content, and original written materials

If someone copies a substantial part of that original expression, there may be infringement. The analysis is not only about whether they copied line for line. In some cases, copying significant structure, sequence, or arrangement can matter, but the details are highly fact-specific.

What copyright usually does not protect

Copyright usually does not protect the underlying concepts behind your software. That can include:

• the idea for the product
• the business method behind it
• the logic of an algorithm in abstract form
• mathematical formulas
• general functionality
• systems or processes described only at a conceptual level

This idea versus expression distinction is the key point. A fraud detection engine, recommendation model, scheduling formula, or pricing logic may be commercially valuable, but copyright does not automatically stop others from developing their own version of the same concept.

Why this matters commercially

This matters most when your business value sits in hidden technical know-how rather than customer-facing branding. If your competitive edge is your matching logic, data weighting, optimisation process, or machine-learning workflow, you need to think beyond copyright.

For example, a SaaS startup may spend months refining an allocation algorithm for service bookings. If it only relies on copyright, it may find that a competitor can lawfully create a similar booking engine using different code. The startup’s stronger protection may come from confidential treatment of the logic, carefully drafted contractor agreements, restricted access to technical documents, and clear ownership of all development work.

Copyright ownership is not always obvious

Even where copyright exists, your business may not own it unless ownership has been properly addressed. This is where founders often get caught before they sign a contract or engage an overseas developer.

Questions to resolve early include:

• Was the software created by an employee, contractor, agency, or co-founder?
• Does the development agreement clearly assign intellectual property to the business?
• Were any open source components used, and on what terms?
• Did a third party contribute code, documentation, or design work without a signed IP assignment clause?
• Has anyone reused code from an earlier employer or another client project?

If ownership is messy, enforcing copyright becomes much harder, even if copying has occurred.

When This Issue Comes Up

This issue usually comes up when a business is about to share, buy, build, or challenge software.

It is rarely just an academic question. Most founders run into it in real commercial moments, often before they spend money on company setup or before they invest in branding and launch.

When you are building custom software

If you hire a freelance developer or software studio to build your platform, app, or internal tool, you need to confirm who owns the code and related IP. Paying for development does not always mean you automatically own everything that was created.

This is especially important if the value of your business is tied to backend logic. Without a strong written agreement, you may end up with a licence to use the software rather than full ownership.

When you are working with a technical co-founder

Plenty of early stage businesses start with an informal arrangement between founders. One founder writes the code, the other handles operations or sales, and no one documents ownership properly.

That works until someone leaves. If the core algorithm was created before the company was formed, or outside a proper assignment document, disputes can arise over who actually owns the software assets.

When you are pitching to investors, customers, or collaborators

Before you disclose your technical method to potential partners, enterprise customers, or investors, think carefully about what you are sharing. A polished product demo is one thing. Handing over detailed technical logic, code snippets, or architecture documents is another.

If your edge lies in confidential know-how, non-disclosure terms and controlled disclosure processes can matter more than copyright alone.

When you think a competitor copied you

You may suspect copying because a competing product behaves in a very similar way. Similar functionality, however, is not enough on its own to prove copyright infringement.

You need to ask more targeted questions, such as:

• Did they have access to your code or documentation?
• Have they copied material from your repositories, technical documents, or interface text?
• Is the similarity in the protected expression, or only in the idea and output?
• Did a former contractor or employee move across with your material?

Those details affect whether you may have a copyright claim, a confidentiality claim, a contractual issue, or a mix of all three.

When you are acquiring or licensing software

If you are buying a software business, licensing a platform, or white-labelling a product, you need to understand what IP rights actually exist. Sellers sometimes say their “algorithm is copyrighted” when they really mean they have written code and internal documentation.

Before you sign, due diligence should cover:

• who created the software
• whether ownership has been assigned properly
• whether there are any open source licence risks
• whether confidential information has been adequately protected
• whether branding, trade marks, domain names, and customer-facing assets are also owned by the right entity

Practical Steps And Common Mistakes

The most practical approach is to treat copyright as one part of an intellectual property plan, not the whole plan.

If your business relies on software logic, you need to line up ownership, confidentiality, branding, privacy policy considerations, and commercial contracts early. That is especially true before you launch online, before you register a domain or print packaging, or before you let third parties build on your platform.

1. Lock down IP ownership in writing

Your first step is to make sure the company owns what it thinks it owns. Employment contracts, contractor agreements, co-founder arrangements, and agency contracts should deal clearly with intellectual property created during the relationship.

Key clauses often cover:

• assignment of present and future IP rights
• moral rights consents where relevant
• confidentiality obligations
• warranties that work is original and does not infringe others’ rights
• restrictions on reusing confidential materials
• obligations to sign further documents if needed

A handshake arrangement is not enough if ownership becomes valuable later.

2. Protect confidential know-how properly

If your algorithm is commercially sensitive, confidentiality may be one of your strongest protections. Once confidential material is widely disclosed without safeguards, your practical leverage can shrink quickly.

Good habits include:

• limiting access to code repositories and technical documentation
• using confidentiality clauses in employment and contractor agreements
• having tailored non-disclosure terms before sharing sensitive technical details
• recording what was disclosed, to whom, and for what purpose
• separating customer-facing marketing from secret technical methods

Many businesses talk publicly about being “AI-powered” or “algorithm-driven” while keeping the actual logic private. That can be a sensible middle ground.

3. Do not confuse copyright with patents

Some founders assume that if copyright does not protect the underlying algorithm, there is no other option. That is too simplistic. Patent protection may be relevant in some circumstances, but software-related inventions in New Zealand sit under specific rules and should be assessed carefully.

You should not assume a software idea is patentable, and you should not rely on a casual online summary. Patent strategy needs specialist advice early, especially before public disclosure.

4. Check your use of open source software

Open source code can be useful, but it can also create licence obligations that affect how you distribute your software. The issue is not that open source is bad. The issue is failing to track what has been used and on what terms.

Before you commercialise your product, check:

• which open source components are included
• what licences apply to those components
• whether you need to provide attribution or notices
• whether any copyleft-style obligations could affect distribution
• whether third party developers have documented dependencies properly

This is particularly important if you are selling online, seeking investment, or preparing for a due diligence review.

5. Protect the brand separately

Your software logic and your brand are different assets. Even if competitors can lawfully develop similar functionality, they should not be able to trade off your brand identity if you have protected it properly.

Trade mark strategy often gets left too late. Before you invest in branding, choose a product name, business name, or register a domain, it is worth checking whether the brand is available and whether a trade mark application makes sense.

6. Match your customer contracts to your product model

Your terms with customers should reflect what you are actually providing. A SaaS business, software development shop, API provider, or data analytics platform will all have different commercial risk points.

Your customer terms may need to address:

• licence scope
• restrictions on reverse engineering, copying, or resale
• service levels and support boundaries
• ownership of customer data and platform data
• acceptable use rules
• liability limits and exclusions, to the extent permitted by law
• privacy disclosures if personal information is involved

Those documents will not create copyright in an abstract algorithm, but they can reduce disputes and set clear limits on how your product may be used.

7. Avoid these common mistakes

The most common mistakes are practical, not technical. They tend to happen in the rush to launch.

• Assuming “I paid for it” means “I own the IP”.
• Thinking an idea is protected before it is expressed in original material.
• Sharing sensitive technical details without confidentiality protections.
• Waiting too long to document founder ownership.
• Ignoring open source licence obligations.
• Focusing on code and forgetting trade marks, privacy, and customer contracts.
• Accusing a competitor of infringement based only on similar functionality.

These mistakes can usually be reduced with early legal documentation and a clear internal process for software development and disclosure.

FAQs

Can copyright protect my algorithm itself?

Usually not in the abstract. Copyright generally protects the original expression of the algorithm, such as code or written documentation, rather than the underlying idea, logic, or method by itself.

If someone rewrites my software in different code, is that infringement?

Not necessarily. If they independently create their own code and only adopt the same idea or functionality, copyright may not be infringed. If they copied a substantial part of your original expression, the position may be different.

Do I own code written by a contractor for my business?

Not automatically in every case. You should have a written agreement that clearly assigns intellectual property to your business and deals with confidentiality and original work warranties.

Should software businesses in New Zealand also think about trade marks and privacy?

Yes. Trade marks can protect your brand, while privacy compliance matters if your software collects, stores, or uses personal information. These issues sit alongside copyright, not instead of it.

Is patent protection available for software in New Zealand?

Sometimes, but the rules are specialised and software-related inventions need careful assessment. You should get tailored advice before public disclosure or filing decisions.

Key Takeaways

• In New Zealand, copyright can protect original software code and related expression, but it does not usually protect an algorithm as a bare idea or method.
• If your business value sits in software logic, confidentiality measures and strong IP ownership clauses are often just as important as copyright.
• Before you sign a contract with developers, co-founders, or agencies, make sure ownership of all code, documentation, and related IP is clear in writing.
• Similar software functionality does not automatically mean copyright infringement, because the law distinguishes between ideas and expression.
• Trade marks, privacy compliance, customer contracts, and open source licence management all matter around a software product.
• Patent questions can arise in limited cases, but software patentability in New Zealand needs specific advice.

If your business is dealing with are computer program algorithms protected by copyright and wants help with software development contracts, intellectual property ownership, confidentiality terms, and trade mark strategy, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.