Data Processing Agreement (Australia)

Create a compliant Australian Privacy Policy for your business or website. Our template is drafted in accordance with the Privacy Act 1988 (Cth) and covers all 13 Australian Privacy Principles (APPs), including APP 1 (open management), APP 5 (notification), APP 6 (use and disclosure), APP 7 (direct marketing), APP 8 (cross-border disclosure), APP 11 (security), APP 12 (access), and APP 13 (correction). Includes the Notifiable Data Breaches scheme, OAIC complaint process, and the $3 million turnover threshold explanation.

A Software as a Service (SaaS) agreement is the foundation of every cloud-based software subscription business. Whether you are an Australian startup offering your first B2B platform or an established provider expanding your customer base, having a professionally drafted SaaS agreement is essential to protect your intellectual property, manage your liability, ensure privacy law compliance, and set clear expectations with customers about service levels, payment, and data handling. An Australian SaaS Agreement differs in important respects from equivalent agreements used in the United Kingdom or the United States. Australian law imposes obligations that cannot be contracted out of, particularly under the Australian Consumer Law (ACL), the Privacy Act 1988 (Cth), and the Spam Act 2003 (Cth). A SaaS agreement that simply adopts a US or UK template without adapting it for the Australian legal environment may be unenforceable in key respects and may expose the provider to regulatory risk. The Australian Consumer Law (ACL), being Schedule 2 to the Competition and Consumer Act 2010 (Cth), is one of the most significant considerations for SaaS providers. Sections 23 to 28 of the ACL prohibit unfair contract terms in standard form contracts with consumers and, since November 2023, with small businesses. A term in a SaaS agreement is unfair if it would cause a significant imbalance in the parties' rights and obligations arising under the contract, is not reasonably necessary to protect the legitimate interests of the party advantaged by the term, and would cause detriment to a party if it were relied on. Commonly challenged terms include broad indemnities, unilateral variation rights, and automatic renewal clauses with short cancellation windows. Under the Treasury Laws Amendment (More Competition, Better Prices) Act 2022 (Cth), unfair terms in standard form contracts are now void and attract significant civil penalties. The Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs) govern how personal information is collected, used, disclosed, and secured by APP entities. A SaaS provider who collects personal information from customers or who processes personal information on behalf of customers must comply with the APPs. Of particular importance are APP 1 (open and transparent management of personal information), APP 3 (collection of personal information), APP 6 (use or disclosure of personal information), APP 8 (cross-border disclosure of personal information), APP 11 (security of personal information), and APPs 12 and 13 (access to and correction of personal information). The agreement should address who owns customer data, how the provider will secure it consistent with APP 11, and what happens to the data on termination. The Spam Act 2003 (Cth) prohibits the sending of unsolicited commercial electronic messages to Australian accounts. SaaS providers who send marketing emails or in-app notifications to customers must have explicit or inferred consent and must include a functioning unsubscribe mechanism. The agreement should confirm that the provider will comply with the Spam Act 2003 in relation to any electronic communications sent in connection with the service. Australia does not have an equivalent of the EU GDPR's data processing agreement regime. However, where a SaaS provider processes personal information on behalf of a customer, it is best practice to include equivalent contractual protections addressing handling instructions, security obligations, sub-processor disclosure, breach notification, and data return or deletion on termination. Service level agreements (SLAs) specifying uptime commitments are a standard feature of SaaS agreements. A meaningful SLA will specify the uptime percentage, how downtime is measured, what events are excluded (such as scheduled maintenance and factors beyond the provider's control), and what remedy is available to the customer for a breach of the SLA. A service credit regime — where the customer receives a credit against future invoices for periods of downtime exceeding the SLA threshold — is the most common remedy. Subscription pricing in AUD, GST provisions complying with the A New Tax System (Goods and Services Tax) Act 1999 (Cth), auto-renewal with appropriate notice periods, and the right to increase fees on renewal are all standard commercial terms in Australian SaaS agreements. The agreement should also address what happens to customer data on termination, including a grace period for data export before deletion. This Australian SaaS Agreement template addresses all key commercial and legal issues: ACL compliance including unfair contract terms considerations, Privacy Act 1988 (Cth) and APP obligations, Spam Act 2003 compliance, customer data ownership and security, SLA uptime commitments, AUD subscription pricing with GST, auto-renewal and cancellation, IP protection, limitation of liability, confidentiality, and governing law.

Create a comprehensive Australian Service Agreement compliant with the Australian Consumer Law (Schedule 2 of the Competition and Consumer Act 2010 (Cth)) and the common law of contract. Covers scope of services, GST-inclusive or exclusive fees, payment terms, consumer guarantees, intellectual property ownership, confidentiality, Privacy Act 1988 obligations, limitation of liability, and termination rights. Suitable for consultants, freelancers, agencies, and businesses providing services to other businesses or consumers across all Australian states and territories.

Commissioning bespoke software is one of the most significant investments a business can make, and getting the legal foundations right from the outset is essential. An Australian Software Development Agreement is a bespoke contract between a client and a developer that governs the creation of custom software — whether a web application, mobile app, enterprise platform, or integrated system. This agreement sets out each party's rights and obligations in legally precise terms, reducing the risk of disputes over intellectual property, payment, scope creep, and delivery timelines. In Australia, the starting point for intellectual property in software is the Copyright Act 1968 (Cth). Section 35(6) of that Act provides that where a work is made by an independent contractor (rather than an employee), copyright is owned by the contractor — not the client — unless there is a written agreement to the contrary. This default rule surprises many clients who assume they automatically own what they have paid to have built. A well-drafted software development agreement expressly addresses copyright ownership and, where the parties intend for the client to own the finished software, includes a valid assignment of copyright pursuant to s 196 of the Copyright Act 1968 (Cth). Without such a written assignment, the client receives only whatever licence the developer is willing to grant. Patentable inventions arising from software development are governed by the Patents Act 1990 (Cth). Where the software may give rise to a novel technical process or system that could be patentable, the agreement should address how any patent rights will be owned and licensed, either by express assignment or by a commitment to negotiate in good faith. The Australian Consumer Law (ACL), being Schedule 2 to the Competition and Consumer Act 2010 (Cth), imposes consumer guarantees on the supply of services in trade or commerce. A developer supplying software development services to a consumer or small business cannot exclude guarantees that the services will be rendered with due care and skill and that the result will be fit for the disclosed purpose. A professionally drafted agreement acknowledges these non-excludable rights and structures any additional limitation of liability around them. Payment disputes are one of the most common causes of conflict in software projects. An effective payment structure ties payments to defined milestones — for example, 30% on signing, 40% on design approval, and 30% on final acceptance — so that the developer is incentivised to deliver and the client does not pre-pay for work that may not be completed. The agreement should also address the developer's right to suspend work for non-payment and to charge interest on overdue amounts. Scope creep — where the client requests additional features or changes beyond what was originally agreed — is another major source of disputes. The agreement should specify that changes to scope require a written change order signed by both parties and may attract additional fees. This protects the developer from being expected to deliver a materially different product for the same fixed price. Confidentiality is critically important in software development engagements. Clients frequently share proprietary business logic, trade secrets, and sensitive commercial data to enable the developer to build the system. The agreement should impose reciprocal confidentiality obligations on both parties and should specify that these obligations survive termination. Where the software will collect, store, or process personal information about individuals, the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs) will apply. Australian Privacy Principle 11 requires APP entities to take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access. The software development agreement should address how the developer will handle any personal information encountered during the project and should require the developer to implement appropriate security measures. User acceptance testing (UAT) and a formal acceptance process protect both parties by providing a defined mechanism for the client to review the software against the agreed specification before final payment is released. Without a clear acceptance process, disputes commonly arise about whether the software meets requirements. This Australian Software Development Agreement template covers all key aspects: copyright assignment under the Copyright Act 1968 (Cth), patent provisions under the Patents Act 1990 (Cth), ACL consumer guarantee acknowledgment, milestone-based payment, scope change control, background IP protection, user acceptance testing, confidentiality, privacy compliance, limitation of liability, and termination rights. It uses Australian business terminology (Pty Ltd, ABN, AUD, DD/MM/YYYY) and is governed by the laws of the relevant Australian state or territory.

Protect your confidential business information under Australian common law with a legally sound Non-Disclosure Agreement (NDA). Whether you are sharing trade secrets with a prospective partner, disclosing proprietary technology to a developer, or presenting financial projections to a potential investor, a properly drafted Australian NDA keeps your sensitive information under strict legal protection. Our template complies with Australian contract law principles and includes provisions addressing the Privacy Act 1988 (Cth) and the Australian Privacy Principles.