# A software development NDA covers the contract. Ask what happens after it

> An NDA binds a development team on paper. Where client names still leak from an agency's own website, and five questions to ask before you sign.

Source: https://lastdoorsolutions.com/blog/software-development-nda

**A software development NDA binds the team on paper. A leak can still come later, from the team's own website.** A case study, a portfolio card or a line in a page's search data can name a client that never agreed to it.

So read the NDA with your lawyer, then ask what the team does about its own pages. This post is not legal advice. It is what we do, and what we would ask a supplier.

## What to settle in the agreement

- **Which information is confidential:** code, plans, data and any other material covered by the agreement.
- **Whether the team may name you or show the work:** agree what, if anything, may appear in a portfolio.
- **How that permission is applied:** check page descriptions, search data and plain-text copies as well as visible text.
- **Who checks before publication:** a signed agreement still needs someone to apply it.

The [UK Intellectual Property Office's NDA guidance](https://www.gov.uk/government/publications/non-disclosure-agreements/non-disclosure-agreements) explains why the permitted purpose and disclosure terms need to be agreed.

## Our rule: protected client identities stay private

Much of our government, pharmaceutical and nonprofit work was built through a partner agency. **Where permission to name a client has not been granted, we keep its identity off our public pages.**

We name our partners. Protected client identities stay private, and we hold that line in two ways: a release check, and a rule about details.

![Where a client's name can leak: page text, the meta description that search results show, the structured data search engines read, and the plain-text copy AI tools and teams read. A release check reads the public pages listed in the sitemap and their plain-text copies for listed protected names. The full story sits behind the access form, approved by a person, with a confidentiality undertaking.](/images/blog/where-a-name-leaks.png)

*Four places a name can leak, one check over all of them.*

## A check, not a habit

**A list of the names we may not publish sits in our code. Our release checks read the public pages listed in the sitemap and their plain-text copies. The check fails if a listed protected name appears.**

It reads the built site, not the text we wrote. A name that arrives through a page's description, its data for search engines or its plain-text copy is checked alongside names in paragraphs. Until that check existed, the rule was held by nothing but care.

## No detail that points to one client

A name is the obvious leak. **A detail can be just as clear.** A funding figure, a team size, a city or a named bank can narrow a description to one client. So can a product type that fits one drug.

So our public pages describe the work and keep the numbers, and leave out the detail that would identify the client. Further detail is shared only through the access review.

## Where the detail lives

Some readers need the detail to judge the work. For them, the full story sits behind [our access form](/access). **A person on our team reviews each request, and everyone who asks agrees to keep the contents confidential.**

## Five questions to ask before you sign

1. **Will you name us, or show our screens, anywhere?** Get the answer in writing, whatever it is.
2. **How do you stop a name reaching your site by accident?** A check beats a promise.
3. **Which details would identify us?** Agree them, not only the name.
4. **Who can see the full case study,** and what do they agree to first?
5. **What happens when the project ends?** Confidentiality should outlast the contract.

A software development NDA is where confidentiality starts. The supplier's own website is where it is tested, every time they publish.

## Is your project one you cannot talk about yet?

Tell us what has to stay private, and from whom. We will say how we would keep it off our own pages, and what we would show instead.

[Talk to us in confidence](https://lastdoorsolutions.com/contact?service=consulting)