How NDA works
A mutual NDA can be signed before any technical detail is shared. Here is what it covers, what we need from you, and how long it takes.
1. Why we sign an NDA
Most serious engagements start with information you would not want in the open: system architecture, a data model, a failing migration, or commercial terms. We are happy to sign a mutual (two-way) NDA before you share any of that — and we will do it before the first technical call, not after.
Because the agreement is mutual, your confidential information and ours are protected on the same terms. There is no fee, and signing one does not commit you to hiring us.
2. What a mutual NDA covers
Typically it covers:
- technical documentation, architecture diagrams, source code and database schemas;
- product roadmaps, business plans, pricing, margins and commercial terms;
- security findings, incident details and audit results you share with us;
- customer data samples, datasets and test accounts you make available.
The usual exclusions apply — information that is:
- already public, or becomes public without breach of the agreement;
- already lawfully known to the receiving party before disclosure;
- independently developed without using the other party's information;
- required to be disclosed by law or a regulator (with notice where permitted);
- general skills, know-how and experience — an NDA does not stop either side from doing similar work for other clients.
A standard mutual NDA also sets a confidentiality period — commonly three to five years after disclosure — and requires confidential material to be returned or destroyed on request. Our NDAs do not contain non-compete clauses and do not transfer intellectual property; IP ownership is dealt with in the Terms of Service (section 7), not in the NDA.
3. What we need from you
So the paperwork can be issued in one go, send:
- the exact legal entity name that will sign;
- its registered address;
- the signatory's name and title (or your procurement/legal contact);
- the governing law you prefer;
- your template, if your legal team requires your own paper.
4. How the process works
- You request it. Email turjo_t@yahoo.com with the details above, or use the contact form and tick "Send me a mutual NDA" — a plain "NDA first, please" in the message is enough to start.
- We send the document within one to two business days, usually the same working day. You receive it by email for electronic signature; no account or platform login is required.
- You sign. If your legal team wants changes to the wording, we handle the redlines directly rather than (as often happens) losing a week to email ping-pong.
- Discovery call. Once it is signed we schedule the technical discussion — typically 30–45 minutes — so nothing sensitive is discussed before the NDA is in place.
No confidential information should be sent with the NDA request itself. Send the entity and signatory details only; technical detail comes after signature.
5. Our template or yours
We keep a short mutual NDA that most organisations' legal teams accept without changes. If you prefer your own standard template, send it with the request — we will review and sign it provided it is mutual, contains no non-compete or IP-assignment obligation, and does not require us to indemnify unlimited liability.
6. Security reviews and certifications
Enterprise procurement often asks for certifications before talking to an independent engineer, so here is the honest position up front:
- No SOC 2 or ISO 27001 certificate is held. We will not imply otherwise.
- We will complete your vendor security questionnaire, and we answer questions about hosting, access control, encryption and data handling in writing.
- We can sign a data processing agreement (DPA) and rely on Standard Contractual Clauses for transfers where your jurisdiction requires it — see the Privacy Policy.
- Where your policy requires it, we work inside your own repositories, cloud accounts and ticketing systems, using credentials you issue and can revoke.
- The security expectations for an engagement (environments, access, incident notification) can be attached as an appendix to the SOW.
If your process requires a certificate rather than a questionnaire, say so early and we will tell you plainly whether we can meet it.
7. If you would rather not sign one
That is fine. Without an NDA we can still discuss:
- the general scope of work and the engagement model that fits;
- indicative budget ranges and timelines;
- technology preferences and public information about your stack;
- how we would approach the work at a high level.
We simply avoid detailed architecture, code, data samples and commercial terms until it is in place. Alternatively, a paid discovery or audit can be run under your own standard contractual terms without any NDA at all.
8. Request an NDA
Email the details from section 3 to turjo_t@yahoo.com (the subject line is pre-filled), or use the contact form and tick "Send me a mutual NDA". Expect the document within one to two business days.
Related documents: Terms of Service (confidentiality in section 8), Privacy Policy and Cookie Policy.