Black FridayUp to $500 off your legals

IT Non Disclosure Agreement: What To Include

byAlex Solo9 min read

Priya is building a SaaS platform and wants a developer to quote on a new feature. To get an accurate estimate, she needs to share user flows, product specs, API details and a test environment login. She trusts the developer, but she also knows that one forwarded email or reused code snippet could cause real problems.

This is where an IT non disclosure agreement can be very useful. A standard NDA might cover confidential information generally, but software and IT projects have extra risks: source code, credentials, production access, subcontractors, security incidents and technical know-how that's hard to unlearn.

The goal isn't to make the project harder. It's to let you share what needs to be shared, while making the rules clear from day one.

Do You Need An IT Non Disclosure Agreement Before Sharing Technical Information?

Yes, you should usually have an IT non disclosure agreement before sharing sensitive technical or commercial information with a developer, agency, contractor, consultant or potential technology partner.

An NDA is especially useful before you share things like:

  • source code, repositories or technical architecture
  • product roadmaps, feature specs or wireframes
  • API keys, credentials, staging logins or admin access
  • customer lists, pricing, revenue data or investor materials
  • security processes, penetration test results or vulnerability reports
  • datasets, algorithms, models or training data

In Australia, confidential information can sometimes be protected even without a signed NDA, but proving what was confidential and what the other person agreed to can be difficult. A written NDA helps because it sets out the information covered, the permitted use, who can access it, and what happens when the project ends.

For example, say Priya shares a GitHub repository and staging credentials with a freelance developer to quote on a payment integration. If there's no NDA, the developer might later argue that the code structure, comments or product logic weren't clearly confidential. If the NDA says repository access, credentials, product logic and related communications are confidential, Priya is in a much stronger position.

If the other party will also share confidential information with you, such as their own frameworks or internal tools, you may need a mutual non disclosure agreement instead of a one-way NDA.

What Should An IT Non Disclosure Agreement Cover?

An IT non disclosure agreement should cover the specific technical, commercial and security information you're sharing, and it should say exactly what the recipient can and can't do with it.

A good starting point is to define Confidential Information broadly enough to include both business and technical material. For an IT or software project, this often includes:

  • code, scripts, libraries, configurations and deployment information
  • system architecture, database structures and technical diagrams
  • product specs, user stories, designs and prototypes
  • trade secrets, algorithms, formulas, prompts or workflows
  • security controls, incident reports and vulnerability information
  • customer, supplier, employee and user data
  • pricing, budgets, commercial strategy and investor information

The NDA should also make the permitted purpose clear. This is the reason the information is being shared. For example, it might be: assessing and quoting on a software development project, providing managed IT support, carrying out a security review, or negotiating a technology partnership.

This matters because you don't just want the recipient to keep the information private. You also want to stop them from using it for another purpose, such as building a competing product, training their internal team, or reusing your customer data for marketing.

The agreement should also cover permitted disclosures. There may be sensible situations where disclosure is allowed, such as to an employee who needs the information for the project, to a professional adviser, or where disclosure is required by law. The key is to make sure those disclosures are limited and controlled.

If personal information is involved, you may also need to think about the Privacy Act 1988, the Australian Privacy Principles and the Notifiable Data Breaches scheme. An NDA won't replace a privacy policy for sensitive information, data processing terms or cyber security processes, but it can sit alongside them.

How Should Your NDA Handle Source Code, Credentials And Security Access?

Your NDA should treat source code, credentials and security access as especially sensitive information, because misuse or poor handling can affect your whole business.

For source code, the agreement should say that access is only for the agreed project and doesn't transfer ownership. Copyright in software is protected under the Copyright Act 1968, but ownership and licensing can still become messy if your documents aren't clear. If the developer is creating new code for you, you'll usually also need a software development agreement that deals with IP ownership, deliverables, testing, payment and support.

Your NDA can support this by saying the recipient must not:

  • copy, fork or download repositories except as needed for the project
  • reuse your code in other projects
  • reverse engineer, decompile or analyse your systems beyond the agreed scope
  • remove copyright notices, watermarks or audit logs
  • share repository access with anyone else without written approval

Credentials need their own treatment. If you give someone a shared admin login, it can be hard to work out who did what later. Where possible, give each person a unique login, limit access to what they need, and turn access off as soon as it's no longer required.

A Practical Example

Priya gives a contractor read-only access to one repository for 14 days so they can quote on a feature. The NDA says the contractor can only use the code to prepare the quote, can't download the full codebase unless approved, and must confirm deletion of any local copies within 48 hours after access ends.

Those 48 hours aren't a legal rule. They're a practical deadline Priya chose for her business. The point is to make the expectation clear, measurable and easy to enforce.

For higher risk projects, you may also want the NDA to require basic security controls, such as multi-factor authentication, encrypted devices, secure password storage, and prompt notice if credentials are lost or compromised.

Should Your NDA Cover Contractors, Subcontractors And Offshore Developers?

Yes, your NDA should clearly deal with contractors, subcontractors and offshore developers if anyone outside the main recipient might access your information.

This is one of the most common gaps in technology NDAs. You may sign an agreement with a local agency, but the work is then done by freelance developers, offshore teams, support staff or specialist contractors. That can be completely fine, but you need the rules in writing.

Your NDA should say whether the recipient can disclose your confidential information to its personnel and subcontractors. If they can, the agreement should usually require that:

  • only people who genuinely need the information can access it
  • those people are bound by confidentiality obligations at least as protective as the NDA
  • the main recipient remains responsible for their actions
  • you can ask for details of who has access, especially for sensitive systems
  • access must be removed when the person stops working on the project

If information may be sent overseas, privacy and data security need closer attention. Under the Privacy Act, Australian businesses that disclose personal information overseas may need to take reasonable steps to make sure the overseas recipient doesn't breach the Australian Privacy Principles, unless an exception applies.

This can matter for software projects involving customer records, health information, employee data, payment information or analytics data. Your NDA may need to work together with a data sharing agreement, information security policy or service agreement.

You should also think about residual knowledge. This means knowledge someone remembers after working on your project, without taking documents or code. A fair clause might allow general skills and experience to be used later, but not your specific confidential information, source code, architecture, customer data or product strategy. Getting this balance right can help avoid arguments with developers who work across similar projects.

IT Non Disclosure Agreement Template: What To Include

An IT non disclosure agreement template can be a helpful starting point, but it should be tailored before you use it. Generic templates often miss the technical details that matter most in software and IT projects.

Here is a fill-in outline you can use to plan what your agreement needs to cover:

  1. Parties: Write the legal names, ABNs or ACNs, and contact details of the business sharing information and the recipient.
  2. Background: Briefly describe the project, such as a software build, quote, security review, IT support arrangement or partnership discussion.
  3. Confidential Information: List the technical and commercial information covered, including code, credentials, specs, customer data and security information.
  4. Permitted Purpose: State exactly why the recipient can use the information, such as preparing a quote or delivering agreed development services.
  5. Confidentiality Obligations: Say the recipient must keep the information confidential, protect it properly and only use it for the permitted purpose.
  6. Access Controls: Set rules for repositories, admin accounts, test environments, production systems, devices and password management.
  7. Personnel And Subcontractors: Explain who can access the information, when subcontractors are allowed, and who is responsible if they misuse it.
  8. Permitted Disclosures: Allow limited disclosures where needed, such as to advisers or where the law requires it, while keeping those disclosures controlled.
  9. Exclusions: Carve out information that's already public, already known by the recipient, or independently developed without using your confidential information.
  10. Residual Knowledge: Clarify what general know-how can be used later and what specific confidential information can't be used or disclosed.
  11. Return Or Deletion: Set a deadline for returning or deleting files, local copies, credentials, backups and project materials when the NDA ends.
  12. Term: State how long the NDA lasts and how long confidentiality obligations continue after the project or discussions end.
  13. Remedies: Explain what can happen if the NDA is breached, such as injunctive relief, damages, account suspension or termination of related services.
  14. Governing Law: Choose the Australian state or territory law that applies to the agreement.

This outline isn't a finished legal document. A lawyer should tailor it to your project, especially if you're sharing source code, personal information, trade secrets, regulated data or access to live systems.

You should also check how the NDA fits with your other documents. For a software build, you may need a software development agreement. For an IT contractor, you may need a contractor agreement with confidentiality, IP, non compete and privacy clauses. For a customer-facing platform, your terms of use and privacy policy may also need to line up.

What Happens If Someone Breaches Your IT NDA?

If someone breaches your IT NDA, act quickly to contain access, preserve evidence and work out the practical damage before deciding your next step.

Start with the operational side. Depending on what happened, you may need to:

  • disable repository access, admin accounts and API keys
  • rotate passwords, tokens and credentials
  • check audit logs, download history and access records
  • ask for written confirmation that files have been returned or deleted
  • record what was accessed, copied, shared or changed
  • notify affected customers or regulators if personal information is involved

If the breach involves personal information and is likely to result in serious harm, the Notifiable Data Breaches scheme under the Privacy Act may require you to notify affected individuals and the Office of the Australian Information Commissioner. Whether that threshold is met depends on the facts, including the type of information, who accessed it, and what steps have been taken to reduce harm.

Keep communications clear and calm. You may ask the recipient to stop using the information, return or delete it, identify who received it, and give written undertakings. If the issue is serious, get tailored legal help before sending strong demands, because the wording can affect your options later.

Without a well-drafted NDA, you may still have rights under confidentiality law, copyright law, privacy law or your service agreement. The problem is that it can be harder, slower and more expensive to show exactly what the recipient promised to do. That's why getting the NDA right early can save a lot of stress down the track.

Key Takeaways

  • An IT non disclosure agreement should be tailored to software and technology risks, not just general business confidentiality.
  • Source code, credentials, security information, customer data and product specs should be clearly covered.
  • Your NDA should say who can access confidential information, including subcontractors and offshore developers.
  • Residual knowledge clauses need care, so developers can use general skills but not your confidential information.
  • An NDA works best alongside the right software development, contractor, privacy and IP documents.
  • If something goes wrong, lock down access, preserve records and get help before the issue escalates.

If you'd like help with your IT confidentiality documents, software development arrangements, contractor terms or privacy and data protection clauses, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.

Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Keep reading

Related Articles

What Is an NDA and How Does It Work?

What Is an NDA and How Does It Work?

If you’re sharing ideas, pricing, customer lists or prototypes with people outside your business, you’ll want a simple way to keep that information under wraps. That’s where a Non‑Disclosure Agreement (NDA) comes...

2 Jan 2026
Read more
What Is a Non-Disclosure Agreement (NDA) And When Should You Use One?

What Is a Non-Disclosure Agreement (NDA) And When Should You Use One?

Sharing ideas drives growth - whether you’re pitching to an investor, onboarding a contractor, or exploring a partnership. But whenever you share confidential information, you take on risk. A Non-Disclosure Agreement (NDA)...

13 Oct 2025
Read more
NDA Agreement Format: A Guide to Drafting Effective Non‑Disclosure Agreements for Australian Businesses

NDA Agreement Format: A Guide to Drafting Effective Non‑Disclosure Agreements for Australian Businesses

Protecting your business information is critical - the right NDA agreement format helps you share ideas confidently while keeping your competitive edge safe. Whether you’re pitching to investors, onboarding a contractor, or...

28 July 2025
Read more
NDA Checklist For Talking To Manufacturers

NDA Checklist For Talking To Manufacturers

Sharing product details with a manufacturer can feel risky. Here's what your NDA should cover before you send designs, samples, formulas or specifications.

6 Nov 2026
Read more
NDA Contracts: Protecting Your Business Legally

NDA Contracts: Protecting Your Business Legally

Confidentiality underpins trust in business. Whether you’re pitching a new idea, onboarding a contractor, or exploring a joint venture, there are moments when you need to share sensitive information-without losing control of...

20 May 2025
Read more
Non-Disclosure Agreement Meaning: What It Is, When To Use, Essentials

Non-Disclosure Agreement Meaning: What It Is, When To Use, Essentials

Sharing ideas is essential to doing business - but sharing the wrong details without protection can cost you your competitive edge. That’s where a Non-Disclosure Agreement (NDA) comes in. If you’re wondering...

6 Nov 2025
Read more
Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.