Clear contracts.
Controlled access.

We can discuss your NDA and confidentiality requirements before confidential access. Acceptance depends on the scope and final agreement.

Any engineer receiving confidential information needs suitable obligations covering permitted use, disclosure, and return or deletion. An NDA and deliverable ownership terms serve different purposes.

Specify deliverable ownership and assignment terms in signed client and developer agreements. Separate new client work from pre-existing tools, open-source dependencies, and other third-party components.

Discuss your rules for dependencies and AI coding tools before work starts. Do not assume the engagement itself transfers every right.

The engagement should define authorized systems and a named engineer. Agree the controls appropriate to the work:

• Individual accounts, limited permissions, and MFA where supported.
• Client-approved credential sharing through a suitable secret manager.
• Repository review and merge rules; production access only with approval.
• Explicit permission before substitution or additional personnel access.
• A named incident contact and access-removal checklist.

These are requirements to agree and confirm, not a claim that every client environment already has these controls.

Tell us about personal data, regulated systems, permitted locations, device policies, and any required certifications. Data-processing agreements or additional safeguards may be needed.

We do not advertise SOC 2, ISO 27001, or blanket regulated-data eligibility. Requested checks and controls must be confirmed for the specific assignment before access.

Please keep credentials, source code, and customer records out of the public enquiry form. Read our website privacy notice.