White Oryx
Client IP &
Ownership
Guide

How White Oryx protects your business, our work & a fair partnership. What you own, what we own & how the Australian Consumer Law views fair contract terms. Clear expectations, no surprises.

Section 1

What intellectual property means in software development

In the tech & software industry, intellectual property refers to the technical assets, code, logic, architecture, tools & methods created by a developer or development team. At White Oryx, our intellectual property includes:

  • System architecture & solution design
  • Coding frameworks & reusable components
  • Automation logic & workflows
  • Database structures & integration patterns
  • Developer tools, templates & libraries
  • Methodologies & problem-solving approaches

These elements are the result of many years of experience, research & refinement. They allow us to work efficiently and deliver custom systems at a competitive price.

Section 2

What you, the client, own

Anything that originates from your business remains your property. This includes:

  • Your data & records
  • Your business processes & workflows
  • Your pricing formulas & operational methods
  • Your branding, text, images & media assets
  • Any content, documentation or materials you provide to us
  • The specific configuration of the software tailored to your business

You also have full rights to use the system we build for you in your business as intended, within the agreed licence & terms of engagement.

Section 3

What White Oryx owns

To continue delivering high quality solutions & operate as a sustainable business, White Oryx retains ownership of:

  • The underlying codebase
  • System logic, architecture & core frameworks
  • Reusable modules, components & integration patterns
  • Backend automation workflows & technical connectors
  • Internal development tools, templates & libraries
  • Our overarching system design principles & methodologies

These items are not specific to a single client. They are the technical foundation that allows us to build solutions quickly, reliably & cost-effectively. Protecting this foundation means we can continue to support you over the long term, while also serving other clients without legal conflict or excessive project costs.

Section 4

Why this distinction matters

There are two key reasons why clear IP boundaries are important.

1. Protecting your business. We treat your data, formulas & processes as confidential. We do not reuse client-specific information in other projects. Each system is constructed around the information you provide & the needs of your business.

2. Protecting White Oryx & the industry. Developers must retain ownership of their frameworks, tools & methods so they can continue working and supporting multiple clients. Asking a developer to hand over all of that for a single project fee would significantly increase costs & make the work commercially unsustainable.

Section 5

Common misunderstandings about ownership

Most clients are reasonable, but some assumptions can create tension if not clarified early. Examples include:

  • "We want full ownership of all your code and technical frameworks." This would amount to a full IP buy-out, which is a separate and often very significant commercial transaction. It is not included in a standard project fee.
  • "You must agree not to work with anyone in our industry again." Industry-wide non-compete clauses restrict a developer's future earning capacity & are generally not reasonable or enforceable without substantial compensation.
  • "Because the system reflects our workflow, the entire app belongs to us." Your workflow is yours. The technical system that enables it remains the developer's intellectual property.
  • "We paid a project fee, so we own everything." Project fees cover the delivery of a solution & the right to use it, not the purchase of exclusive rights over the developer's entire technical foundation.

To avoid misunderstandings, White Oryx is clear from the outset about what is included in the project fee & what would require a separate IP or exclusivity agreement.

Section 6

Similarities between systems without IP conflict

We do not reuse client-specific methods, formulas, data or proprietary processes. Every system we build is constructed uniquely around the information that client provides.

However, we cannot control what other clients independently share with us about their own processes, or what is already publicly available through industry knowledge, online research or standard commercial practice.

As a result, it is possible for similarities to arise between systems, especially in industries where many businesses use comparable workflows. These similarities can occur by coincidence & do not represent an IP breach.

Section 7

ACCC guidance on fair & unfair contract terms

Under the Australian Consumer Law, certain contract terms may be considered unfair if they create an unreasonable imbalance between the parties or cause harm. Under ACL section 24, a term may be unfair if it:

  • Creates a significant imbalance between the rights & obligations of the parties
  • Is not reasonably necessary to protect one party's legitimate interests
  • Would cause financial or operational detriment to the other party

Examples that may fall into this category include:

  • Demanding full transfer of developer IP without reasonable compensation
  • Imposing broad, long-term, industry-wide non-compete clauses
  • Withholding payment to pressure a party into signing an unfair agreement
  • Requiring a developer to surrender tools, methods & frameworks built over many years as part of a standard project

White Oryx does not engage in coercive or unconscionable conduct. We aim for agreements that are balanced, transparent & aligned with Australian Consumer Law so that both parties are protected.

Section 8

What a healthy partnership looks like

A successful project is a collaboration between your business & our team.

Your responsibilities. As the client, you are responsible for:

  • Providing accurate information, content & requirements
  • Engaging with the system & giving clear feedback
  • Marketing & promoting the solution to your audience
  • Maintaining access to your own accounts, such as Softr, Make, Airtable & related tools

White Oryx's responsibilities. We are responsible for:

  • Delivering a solution in line with the agreed scope
  • Protecting the confidentiality of your data & processes
  • Maintaining & improving our technical frameworks
  • Communicating clearly & supporting you as outlined in our agreements

We genuinely want to see your business succeed with the systems we build. Long-term success relies not only on the technology itself, but also on ongoing marketing, awareness & user engagement. The businesses that win in this space are the ones that keep giving their users real value & reasons to come back.

Need
clarification?

If you have questions about ownership, licensing or how these principles apply to your project, we welcome the conversation. Clear expectations & mutual respect sit at the heart of every successful White Oryx partnership.