TFH Software is comfortable signing a mutual non-disclosure agreement before sensitive project discussions. We want founders and teams to share the context needed for good technical decisions without worrying that confidential information will be reused or disclosed improperly.
We sign NDAs
When a conversation involves confidential product plans, internal systems, customer information, business strategy, security details, source code, financial information, or unpublished intellectual property, TFH will sign an appropriate NDA before detailed disclosure.
We usually prefer a mutual NDA because both parties may share confidential information during discovery and delivery.
Why an NDA matters
Good software decisions require honest context. An NDA creates a clear legal boundary around that context, helping both sides discuss the real constraints, risks, architecture, commercial plans, and opportunities without relying on informal expectations.
- It defines what information is confidential.
- It limits confidential information to the agreed purpose.
- It restricts unauthorised disclosure to third parties.
- It clarifies who may access the information and what safeguards are expected.
- It explains how long confidentiality obligations continue.
- It records common exclusions, such as information already public or independently developed.
How it protects you
A properly written NDA helps protect product concepts, technical designs, customer data, research, pricing, go-to-market plans, credentials, security findings, and other non-public material. It also gives both parties a documented remedy if confidential information is misused.
Confidentiality in practice
Signing an NDA is only one part of protecting information. TFH also limits access to people who need the information for the engagement, uses appropriate account and device controls, avoids placing client secrets in public tools, and discusses project-specific security requirements during discovery.
Our NDA process
The process is designed to be simple and should not delay useful conversations.
- Tell us that you would like an NDA before the detailed discovery call.
- Send your organisation’s standard mutual NDA, or ask TFH to provide a starting document.
- Both parties review the names, purpose, confidential-information definition, exclusions, duration, governing law, and signature details.
- Authorised representatives sign the agreed version.
- Once signed, the detailed project conversation begins.
The signed agreement controls
This page explains TFH’s general approach and is not itself a non-disclosure agreement. The final signed NDA will contain the binding obligations for the specific parties and conversation. If your organisation has legal, regulatory, procurement, or security requirements, those can be reviewed before signing.