Last updated: [August 2025]

Scope. This policy covers delivery of custom software and digital deliverables (source code, builds, documentation, configurations). No physical shipping is involved.

Delivery method. We deliver via secure channels such as Git repositories, shared drives, encrypted archives, or deployment to staging/production environments agreed in the contract.

Timelines. Delivery timelines, milestones, and dependencies are defined in the proposal/contract or project plan. Timelines may adjust if scope changes, third-party dependencies are delayed, or client inputs/approvals are late.

Client responsibilities. The client provides timely access, approvals, and content (e.g., credentials, environments, texts, images). Delays in these may postpone delivery.

Acceptance. Each deliverable/milestone is subject to User Acceptance Testing (UAT). Unless otherwise agreed, the client has 5 business days from delivery to report blocking issues in writing. If no material issues are reported within this period, the deliverable is deemed accepted. Reported issues will be triaged and addressed according to the agreed priority/severity.

Handover. Final handover (including transfer of repositories, credentials, and documentation) occurs after acceptance of the last milestone and settlement of due invoices, unless otherwise stated in the contract.

Support & warranty. Post-delivery support, warranty terms, and SLAs (if any) are specified in the contract or separate support agreement.

Contact. Delivery questions: [contact@lupx.ro].