Confidentiality
NDA
ARKSOFT understands that project conversations may involve confidential software, product, business, architecture, security, data, and operational information. A written NDA can be used before deeper discovery when the engagement requires it.
Purpose
This page explains ARKSOFT's general approach to confidentiality discussions. It is not itself a signed NDA. Confidentiality obligations are created by a written agreement signed or otherwise accepted by the parties.
Confidential Information
- Source code, product plans, architecture diagrams, technical specifications, credentials, datasets, and deployment details.
- Business plans, customer information, pricing, financial details, vendor information, and operational workflows.
- Security findings, vulnerability details, incident information, and proprietary automation or AI workflow designs.
Exclusions
Typical NDA exclusions include information that is already public, independently developed without using confidential information, lawfully received from another source, previously known without restriction, or required to be disclosed by law.
Permitted Use
Confidential information should be used only to evaluate, plan, deliver, support, or manage the specific business relationship or project for which it was shared.
Safeguards
- Share sensitive files through an approved secure channel, not through public forms.
- Limit access to people and systems with a legitimate project need.
- Mark confidential documents when your internal policy requires it.
- Do not send passwords, private keys, live tokens, or production secrets unless a secure transfer method has been agreed.
Return or Destruction
A signed NDA or project agreement should describe how confidential materials are returned, deleted, archived, or retained after the project ends, including any backup, legal, accounting, or audit exceptions.
No License
Sharing confidential information does not grant ownership, license, or intellectual property rights unless a written agreement says so.
Term
The duration of confidentiality obligations should be defined in the signed NDA or project agreement. Some obligations may survive project completion when required by the agreement or applicable law.
Before Sharing Sensitive Details
- Use the website contact form to request an NDA before sending confidential files or proprietary details.
- Identify any export-controlled, regulated, restricted, or third-party confidential material before disclosure.
- Do not submit passwords, private keys, live credentials, or production secrets through the website form.
Project Confidentiality
Confidentiality obligations, permitted use, exclusions, retention, return, deletion, ownership, and disclosure requirements should be documented in the signed NDA or service agreement for the engagement.
Existing NDA
If your company has a preferred NDA, ARKSOFT can review it before project discovery. If not, ARKSOFT can discuss a mutual confidentiality agreement suited to the engagement.
Requesting an NDA
Use the contact form to request NDA review and include the general project category, company name, and preferred contact method. Do not include confidential technical files or secrets in the initial website message.
Contact
NDA and confidentiality questions may be sent through the website contact form or by email to info@arksoft.dev.