Source Code Handover Policy

This Policy describes the handover of source code and related materials for a TECH360 project. The approved SOW and agreement define the specific deliverables and ownership or licence terms.

Depending on the SOW, handover may include custom source code, agreed assets, documentation, configuration templates without secrets, a dependency/licence inventory, and agreed deployment or build instructions. No item is included solely because it is listed as a possible example here.

Unless otherwise agreed in writing, final source-code handover takes place after all required project payments have been received and cleared. Any suspension or withholding of work or delivery must follow the approved agreement and applicable law.

Custom code and materials made specifically for the Client are treated according to the ownership, assignment, and licence terms in the approved agreement and applicable law. Payment does not expand ownership beyond those agreed terms. TECH360 will record the agreed treatment in project documents.

TECH360 retains its pre-existing tools, libraries, know-how, templates, general methods, and reusable components unless the agreement expressly provides otherwise. Where such material is incorporated into a deliverable, the Client receives only the licence or rights specified in the agreement, sufficient for the agreed use where stated.

Handover may include Client-owned credentials specifically identified in the approved SOW, using a suitable secure method. Credentials should be rotated after transfer where appropriate. If a provider does not permit an account or credential to be transferred, the parties may create a Client-owned account, rotate credentials, or grant authorized access as appropriate.

Handover does not include TECH360 API keys, private tokens, passwords, shared infrastructure credentials, internal administrative secrets, other Clients' credentials, or unrelated operational systems. Source packages should use configuration templates or variable names rather than embedding private credentials. TECH360 will not disclose unrelated confidential information.

Where the Client owns an account, the SOW may identify the account or access required for delivery. TECH360 will not promise transfer of accounts that are controlled by a third-party provider or cannot lawfully be transferred. An agreed alternative may include a new Client-owned account, credential rotation, or scoped access.

The parties may agree on a repository transfer, secure file delivery, portal, or other suitable method. The method depends on project configuration and security. Handover records should identify the package and recipient without recording passwords, keys, or tokens in the evidence itself.

TECH360 may retain a handover manifest, delivery date, recipient, channel or repository reference, package identifier, and acknowledgement as evidence of delivery. Evidence is maintained subject to applicable retention, confidentiality, and privacy requirements.

The Client should verify receipt and report missing agreed items or material non-conformity through the agreed support or project channel. Review does not automatically waive remedies under the agreement or applicable law. Source-code handover alone is not proof that every production account, integration, or third-party licence was transferable.

Third-party software, open-source components, fonts, assets, and services remain governed by their own terms and licences. TECH360 does not claim ownership of third-party components or promise every licence is transferable. Where included in the SOW, TECH360 may provide an inventory or relevant licence information.

Support, maintenance, hosting, backup, and continued access are provided only as stated in the SOW or a separate written agreement. The Client is responsible for its own secure backups and account administration unless those services are expressly included. Applicable warranty and legal rights remain unaffected.

The handover is limited to Client deliverables and authorized Client-owned materials. It excludes other Clients' data, source code, credentials, and confidential information, as well as TECH360 confidential operational material, except for any right expressly granted in writing.

Handover status, records, and payment verification may be relevant to a refund or payment dispute, but do not determine the outcome by themselves. See the Refund Policy and Payment Policy. For a payment dispute, TECH360 may preserve and submit relevant evidence to the applicable payment provider or financial institution, including the approved SOW and terms, HTML Preview approval, authorization records, invoices and transaction references, milestone records, revision history, testing and delivery records, source-code handover evidence, and project communications. A provider or financial institution makes its own decision; TECH360 cannot override it or guarantee a dispute outcome. Any recovery of unpaid amounts or documented losses must be permitted by the agreement and applicable law; no blanket penalty applies.

Contact TECH360 LLC at info@bdtech360.com. Please include the relevant project or invoice reference, but do not email passwords, full payment-card details, or card security codes.