Dashboard
On this page

Agreements and NDAs

Fill a work agreement or an NDA from a template, attach an NDA to a contract, sign one on its own, and print the record.

Every contract has scope and terms that both sides accept. DevNet offers two plain-language templates to start from, and keeps an exact record of what each side accepted.

A plain-language template, not legal advice. DevNet is not a party to it. Read what you accept, and ask a lawyer when a lot is at stake.

Templates

When you write a contract, open Start from the work agreement template, answer a few questions and press Fill in the terms. The text lands in the terms box, where you can change anything. The work agreement (template version 1) asks:

  • What will be delivered, and an optional target date
  • How many rounds of changes each milestone includes
  • Who owns the work:
  • The client owns the work once it is paid for in full
  • The developer keeps ownership and gives the client a license to use it
  • Something else (write it yourself)
  • Whether the developer may be credited and show the work in their portfolio
  • Whether to add a short confidentiality clause

The NDA template (version 1) asks who shares information, why, what counts as confidential, and how long it lasts (6 months, 1 year, 2 years, 3 years and 5 years):

  • One-way: I share, they keep it confidential
  • Mutual: both sides share and keep it confidential
  • One-way: they share, I keep it confidential

It lists the usual things that are not confidential, each of which you can untick or add to:

  • Information that is or becomes public through no fault of the receiving side
  • Information the receiving side already had before it was shared
  • Information the receiving side develops on their own, without using what was shared
  • Information the receiving side gets lawfully from someone else who may share it
  • Sharing that a law, court or authority requires, after telling the other side where allowed

Templates are kept in DevNet's code with a version number. A changed template gets a new version, and the text you accepted always says which version it came from.

An NDA with a contract

Tick Add an NDA on the contract form to attach one. It is accepted together with the scope and terms when the developer accepts the contract, and shows beside the terms on the contract page.

An NDA on its own

Before you share a build with a tester or a pitch deck with an investor, you can ask them to sign an NDA without any contract or payment: New NDA on Contracts, or:

The other side reads it and signs or declines. A signed NDA stays in force for as long as it says; it has no milestones and nothing to complete. Signed NDAs are listed under the NDAs tab.

Changes need a new acceptance

Once sent, every change to the terms, the NDA or the unfunded milestones makes a new version. The other side has to accept the new version; on a work contract, no more milestones can be funded until they do. Earlier versions and their acceptances stay on record.

The record

Each acceptance records:

  • which side accepted (the account, which can be a studio) and the person who clicked
  • the version and the time (UTC)
  • the network it came from, shortened so it never shows a full address: an IPv4 address keeps its first three parts (203.0.113.0/24), an IPv6 address its first three groups
  • the SHA-256 fingerprint of the exact text accepted: the parties, title, terms, milestones and any NDA

Agreement record on the contract page shows it. Print or save as PDF opens a page made for printing; use your browser's print dialog to save it as a PDF. Download text gives the exact accepted text as a file: running sha256sum on it gives the same fingerprint as the record, which shows the text wasn't changed.

DevNet is not a party to these agreements and doesn't enforce them. If an NDA is broken, the sides settle it between themselves. Disputes about milestone payments follow the dispute process.

If the terms change while you're reading

Accepting records the exact version you had on your screen. If the other side edits the contract after you opened the page, your Accept is refused with "The terms changed since you opened this page", and the page reloads with the new text. Read it again, then accept. Nobody is ever recorded as accepting text they didn't see.

Still stuck? Ask in the support channel on the DevNet Discord, or see how support works on your plan.