What it is
A non-disclosure agreement โ a legal obligation not to reveal project details and client data to third parties.
How we use it
We sign one on request โ which is why some case studies in the portfolio show no company name, only the substance and the stack.
Where an NDA helps a business
- A contractor sees your inner workings: the network, passwords, the customer base, processes.
- You do not want competitors to learn what your systems run on and how.
- The project touches security: access to services, video surveillance, record-keeping.
How we use it
- We sign on request. That is why some portfolio cases show no company name: "a museum complex in Moscow", "a cardboard packaging manufacturer", "an IT company". The substance, stack and result are visible; the client is not.
- A client's request is reason enough. The corporate gateway is described without the company name because the client asked us not to disclose it.
- Secrets stay out of documents. In the network survey of a museum complex service passwords are described in words, never as values, and
.gitignore keeps keys, access configurations and dumps out of the repository. - Passwords are encrypted. In the IT help desk the credential registry stores ciphertext rather than passwords, and every view of a password is logged.
We name only those who allowed it: for example, the ยซะัั
ะฐะฝะธะต ะะพะฒะพะปะถััยป brand and engineer Valery Afanasiev.
What happens without one
- Project details in someone else's portfolio. Screenshots of internal systems and company names end up in public.
- No grounds for a claim. If information leaks, there is no signed agreement to rely on.
When you do not need it
If the project is public, such as a business-card site or open guides, and the client wants to be named in the case, no NDA is needed. We do not publish passwords, keys or the client's customer data anyway.