A colourful app in action: one screen bringing together branding, product imagery, ratings and reviews – with layers of IP, privacy and legal terms quietly working in the background.
So You’ve Come Up With a New App Idea? What next?
The legal issues that you need to think about as well
One thing we can all agree on is that Apps are everywhere – from how we bank and shop to how we date, exercise and order dinner.
In Australia, millions of us use apps every day, and Australian‑founded apps now range from tradie tools and booking platforms to wellness, education and niche B2B software. It’s exciting territory, but in the rush to build a prototype and get it into the app stores, the legal foundations are often left until “later” – or not done at all.
At Sharon Givoni Consulting, we see this pattern all the time.
A founder has a great idea, finds a developer and a designer, and suddenly there’s a working app… but no clear paperwork about who owns what, no Terms of Use or Privacy Policy, and no disclaimers even though users are relying on the app’s output in their daily lives.
We’ve advised on apps and custom software for a wide variety of clients – from tradies building job‑management tools, to creatives running booking platforms, to professionals offering calculators and assessment tools through an app.
This article doesn’t give you legal advice, and it certainly won’t turn you into a lawyer. Instead, it walks through the issues that usually trigger legal steps for app founders: branding and trade marks, copyright and ownership of the code and design, Terms of Use, Privacy Policies, and disclaimers.
The goal is to help you see what needs to be thought about early, so you can have a proper conversation with your developer – and with your lawyer – before problems arise.
1. “Is the app actually mine?” – IP ownership
A very common assumption is: “It’s my idea, so I own the app.” Unfortunately, that’s not how the law automatically works. As a general rule in Australia, the person or company that creates the code, designs and other materials owns the copyright – unless there is a clear contract or IP assignment saying otherwise.
If you’ve engaged a freelance developer or an external agency, and a graphic designer for the logo and interface, then without the right documents:
- the developer may own the code and database structure;
- the designer may own the logo, icons and UI artwork;
- you may only have an implied licence to use those things, not full control.
That can become a major problem if you ever want to change developers, raise investment, sell the business or enforce your rights.
Typically, the legal building blocks here are:
- A software development or services agreement where the developer agrees that all IP they create for the project is assigned to your company on payment, with a licence back to them for any pre‑existing tools they bring to the project.
- Short, clear IP assignment clauses for your graphic designer (logo, icons, screen designs, marketing graphics) and any other contributors, so you don’t have separate ownership sitting with different freelancers.
2. Protecting the brand – trade marks
Your app name and logo are often the first thing users notice. Many founders register a domain name and an app store listing and assume that’s “protection”. It isn’t. Domain names and app store listings can be important, but they don’t give you the same exclusive rights as a trade mark.
Common issues we see include:
- App names that are descriptive (“Job Planner”, “Budget Buddy”) and hard to protect.
- Names that are already used or registered by someone else in a related field.
- Logos and names used for years without any registration, making enforcement much harder.
The usual legal step is to consider registering your app name and key logo as trade marks in the relevant classes (e.g. software, online services) and territories, so you have a stronger platform if you ever need to object to copycats or licence the brand.
3. Terms of Use – the “rules of the game”
Users expect to see Terms of Use when they sign up to an app or online platform. These aren’t just box‑ticking; they are the contract between you and your users.
For an app, the Terms of Use typically cover:
- who can use the app (age, location, account requirements);
- what users are allowed to do with the app content and tools;
- what they must not do (misuse, reverse‑engineering, illegal content);
- how you can suspend or terminate access;
- how user‑generated content is handled; and
- which law applies and where disputes are resolved.
If your app involves users uploading photos or other content for you to review – for example, images of a product, a skin condition, a document or a site – the Terms also need to deal with things like:
- what you will and will not do with those photos;
- how long you keep them; and
- what the user is promising about the photos (that they own them, that they don’t show illegal content, etc.).
4. Privacy and data – what are you doing with user information?
Most apps collect some form of personal information: names, emails, login details, usage data, and sometimes more sensitive information. In Australia, if your business meets certain thresholds or handles particular kinds of data, you’ll need to comply with the Privacy Act and the Australian Privacy Principles.
Users now expect a clear Privacy Policy that explains:
- what personal information you collect and why;
- where you store it and how you secure it;
- who you share it with (hosting providers, payment gateways, analytics tools); and
- how users can access, correct or delete their data.
Even if you’re under the formal legal thresholds, having a transparent Privacy Policy can help build trust and reduce complaints
5. Disclaimers – managing expectations and risk
If your app does anything that might influence decisions – for example, health, finance, legal‑style guidance, risk ratings, or automated assessments – users can easily over‑rely on it. A good set of disclaimers in your Terms of Use and within the app itself can help manage that risk.
Typical disclaimer themes include:
- the app is a tool or guide, not a substitute for professional advice;
- information may be general or indicative only;
- users remain responsible for their own decisions; and
- limits on liability where users rely on incomplete, inaccurate or poor‑quality information (for example, unclear photos they upload).
Fun Legal Facts
- Your app’s code is protected like a book – but only if ownership is clearly documented.
- Most app fights aren’t about the idea, but who owns the code and visuals when things fall apart.
- If you don’t lock down IP in your dev contract, you may not actually own your own app.
- App store approval ≠ legal compliance – no one there is checking your contracts or IP.
- Apple and Google won’t fix your privacy or disclaimers; that’s on you and your lawyer.
How we usually help app founders
With app and software clients, our role is to pull all these threads together in a way that fits the size and stage of your business.
Typically, that means:
- Reviewing what you already have (developer proposals, emails, any existing terms, privacy wording or NDAs).
- Workshopping everything with you in a focussed meeting so we understand your model, your priorities and your risk tolerance.
- Then drafting or updating the core documents: the development/IP ownership agreement, IP assignments for your designer and other contributors, Terms of Use, Privacy Policy and key disclaimers.
You don’t have to arrive with all the answers.
If you have a prototype launching soon and you know these legal pieces haven’t been sorted yet, that’s usually the best time to sit down, map it out and put proper protections in place before you scale.
At a glance
Here are a handful of Australian laws that affect apps
- Copyright Act 1968 (Cth), ss 10, 31, 35 – Protects your app code, text and graphics as copyright and sets who owns them.
- Trade Marks Act 1995 (Cth), ss 17–20, 27–41 – Protects your app name, logo and brand as trade marks and lets you stop confusingly similar branding.
- Australian Consumer Law (CCA 2010 (Cth) Sch 2), ss 18, 29, 60–62 – Bans misleading app claims and builds in quality and “fit for purpose” guarantees.
- Privacy Act 1988 (Cth) and APPs 1–13 – Controls how apps collect, use and secure personal information and what you must tell users.
- Spam Act 2003 (Cth), ss 16–18 – Regulates marketing emails, SMS and some in‑app messages, including consent and unsubscribe rules.
Electronic Transactions Act 1999 (Cth) – Makes in‑app clicks and electronic acceptances legally effective in many cases.
Further reading
How to Protect Your Ideas: A Step-by-Step Guide –
https://sharongivoni.com.au/how-to-protect-your-ideas-a-step-by-step-guide/
Protecting Your Business Ideas under the law
https://sharongivoni.com.au/protecting-your-creative-business-ideas-legally-from-lego-to-logos/
A Short Guide to Copyright Law in Australia
https://sharongivoni.com.au/short-guide-copyright-law-australia/
Protect Your Business Idea and Stop Others from Copying You
https://sharongivoni.com.au/first-to-market-heres-how-to-stop-others-from-copying-your-idea/
Please note the above article is general in nature and does not constitute legal advice.
Please email us info@iplegal.com.au if you need legal advice about your brand or another legal matter in this area generally.

