BoundHQ — Founding Beta Partner Confidentiality Agreement (Draft Framework)

Note: This is a practical framework, not legal advice. Have a lawyer review before use.

Structure: Mutual NDA

Both parties disclose information. Both are protected.

What's Covered

Tester's Confidential Information:

Pricing structures, margins, markup models
Customer lists and client details
Job costing breakdowns
Supplier lists and pricing
Internal workflow documentation
Financial data and business performance
Any data entered into BoundHQ during beta

BoundHQ's Confidential Information:

Product roadmap and unreleased features
Source code and architecture
Business plans, pricing strategy
Other beta tester information
Internal development discussions

Duration

NDA term: 2 years from signing
Confidentiality obligations survive termination for a further 2 years
Data in BoundHQ systems returned or deleted within 30 days of beta end

Key Clauses Needed

Clause	Purpose
Definition of Confidential Information	Covers written/oral, clearly scoped
Exclusions from confidentiality	Public info, independently developed, received from third party
Permitted use	Only for beta testing purposes
Anonymised data carve-out	BoundHQ may use aggregated, de-identified data for product development
Data security obligations	Both parties maintain reasonable safeguards
Return/destruction of data	On termination or request
No reverse engineering	Tester won't decompile or copy BoundHQ
Non-solicitation	Neither party poaches the other's staff during term
Term and termination	2-year term, either party can terminate with 30 days notice
Jurisdiction	Queensland / Australia

The Anonymised Data Carve-Out (Important)

This is the clause that lets you actually use what you learn:

"Notwithstanding the above, BoundHQ may use Aggregated Data (data that has been anonymised such that it cannot be reasonably linked to the Disclosing Party or any identifiable individual) for product development, research, marketing, and business operations purposes."

This protects their specifics but lets you:

See common pricing patterns across testers
Build features based on real workflows
Use aggregate insights in marketing ("Our beta testers reduced quoting time by X%")
Just not attribute any of it to a named business

Practical Flow

Tester applies → Mutual NDA signed (DocuSign / HelloSign) 
→ Workflow mapping session (now protected) 
→ Onboarding begins → Data goes into BoundHQ
→ Beta runs → If either party leaves, data returned/deleted

Recommendation

Don't make the NDA heavy. A 2-page mutual NDA with the anonymised data carve-out is enough. If you front-load a 10-page legal document, you'll scare off tradespeople who aren't used to that. Keep it simple, practical, and honest.

One page summary to send with it:

"This NDA protects both of us. Your pricing, customer info, and business data stay yours and confidential. My roadmap and unreleased features stay mine. The only exception is anonymised data — stripped of anything that could identify your business — which helps me build better features. Fair?"

Draft framework — have a lawyer review before signing.

3.3 KiB Raw Permalink Blame History