Skip to content

Legal & policies

Source Code Handover Policy

When agreed source code, build assets, documentation, credentials, and other deliverables are transferred, and the responsibilities that follow.

Updated October 2026Applies as written; a signed engagement agreement prevails where it differs.

Source Code Handover Policy

When agreed source code, build assets, documentation, credentials, and other deliverables are transferred, and the responsibilities that follow.

1. The principle

Subject to the approved Final Scope of Work, engagement agreement, verified final payment, and applicable law, TECH360 delivers the agreed source code, applicable build assets, documentation, and other handover materials.

Before final payment, work in progress is available for review at the agreed preview and milestone stages. You are not required to pay for an undisclosed black box.

The agreed payment gate protects both parties: the client receives the deliverables covered by the agreement, and TECH360 releases the final handover package after the agreed payment condition is satisfied.

2. What is handed over

The handover package includes the applicable items specified in the approved scope, which may include: the custom source-code repository and application code; applicable build assets and custom files; configuration templates without embedded secrets; database schemas and migrations; installation, dependency, build, deployment, and maintenance documentation sufficient for a competent developer to rebuild and deploy the system; an environment-variable and credential-name inventory; a third-party dependency, version, and licence inventory; and a written handover manifest.

For systems hosted on TECH360-managed infrastructure, the package includes an infrastructure description and migration instructions or reasonable migration assistance only where that work is included in the approved scope or a separate written agreement.

Backups are excluded unless expressly included in the approved Final Scope of Work or a separate written agreement. A backup snapshot will be provided only where it has been expressly included and is available for delivery.

3. Credentials handover

Applicable credentials for systems created or managed on the client’s behalf are transferred through a suitable secure channel, not as unprotected passwords, API secrets, database passwords, private keys, or tokens in ordinary email.

For third-party accounts, TECH360 assists with ownership transfer or confirmation only where the provider permits it and the engagement includes that assistance.

Where applicable, handover documentation identifies the account or system, the access being transferred, relevant permission levels, transfer method, required password or key rotation, and remaining third-party restrictions.

4. Password changes and handover confirmation

Clients should rotate applicable transferred passwords, API keys, tokens, and other secrets promptly after handover. A period of 72 hours is recommended where practical.

The client may confirm the rotation in writing. That acknowledgement records the handover and does not waive any rights or obligations that cannot legally be waived.

After handover, TECH360 does not retain or use access to client-controlled systems except where separately authorized by the client or otherwise permitted under the engagement agreement and applicable law. Temporary access that is no longer needed should be revoked securely.

5. Client responsibilities after handover

After the agreed handover, the client is responsible for taking reasonable care of the delivered materials, including: keeping secure copies of source code and documentation; maintaining independent backups unless a backup service is expressly included; protecting credentials and confidential configuration; managing user access and permissions; reviewing and testing changes made by the client or subsequent developers; and maintaining client-managed hosting, databases, infrastructure, and third-party services.

TECH360 does not provide ongoing source-code storage or backup services after handover unless a separate written agreement expressly includes them. TECH360 does not guarantee that it will retain or be able to recover a copy of handed-over source code after delivery.

6. Issues arising after handover

Unless otherwise agreed, post-handover troubleshooting, restoration, maintenance, and recovery are separate services. Client or third-party modifications, lost source code, compromised client-controlled credentials, inadequate client-managed backups, and systems outside TECH360’s control may require separately agreed assistance.

TECH360 does not automatically classify every post-handover defect as the client’s responsibility. Responsibility for defects, breaches, warranties, or failures attributable to TECH360’s own work, and any obligation that cannot lawfully be excluded, remains subject to the applicable agreement and law.

7. Ownership and third-party materials

Subject to full payment, the approved engagement agreement, and applicable law, ownership or the agreed rights to custom deliverables transfer to the client as specified in the contract.

Third-party libraries, frameworks, fonts, software, and other licensed materials remain subject to their respective licences. Open-source and third-party components are not transferred as exclusive property where their licences do not permit that. Pre-existing TECH360 materials and reusable components are identified and licensed as agreed.

TECH360 will identify or display a client engagement or related materials publicly only with the client’s separate prior written permission and subject to applicable confidentiality terms.

8. Support after handover

Maintenance and support after handover are optional and may be provided only under a separate written agreement that identifies the scope, response targets, fees, support hours, covered systems, exclusions, renewal, and termination terms.

Hosting, monitoring, backups, restoration, recovery, and maintenance do not continue automatically after handover unless expressly agreed in writing.

9. Contact

For handover questions, contact TECH360 LLC at info@bdtech360.com or https://bdtech360.com. The public WhatsApp channel is optional: +8801327100297. Postal address: 117 S Lexington St Ste 100, Harrisonville, MO 64701, USA.

Include your Client ID and project reference when asking about a handover. Never send passwords, API secrets, online banking credentials, or card security codes through ordinary email or chat.

Questions about this policy?

Write to info@bdtech360.com or start a chat with our AI assistant (on any page) quoting your Client ID. Policy questions are answered by the team that wrote the policy.