DELIVERY OCCURS WHEN THE RELEVANT FILE, ACCESS, DEPLOYMENT, CREDENTIAL, LICENCE OR OTHER DELIVERABLE IS MADE AVAILABLE THROUGH AN AGREED METHOD. A CUSTOMER'S FAILURE TO OPEN OR DOWNLOAD AN AVAILABLE ITEM DOES NOT, BY ITSELF, MEAN THAT DELIVERY HAS NOT OCCURRED.
Scope
This Policy applies to Digital Products, websites, applications, software, designs, documents, reports, source files, configurations, credentials, licences, repositories, integrations, deployments, subscription activation and other electronically supplied Deliverables.
Approved delivery methods
- (a)
secure customer dashboard or authenticated workspace;
- (b)
private, signed or time-limited download link;
- (c)
email to the purchasing or authorised account;
- (d)
repository, cloud-storage, hosting-panel or server transfer;
- (e)
deployment to an agreed staging or production environment;
- (f)
administrative credentials, licence key, activation or account access; and
- (g)
handover demonstration or written notice that the Deliverable is available.
Point of delivery
A Deliverable is delivered when it is made available through an approved or otherwise agreed method in a form reasonably capable of access or use for its agreed purpose.
A live deployment, transfer of administrative control, release of source files, provision of a usable download or activation of account access constitutes delivery of the relevant item or milestone.
Immediate Digital Products
A Digital Product described as immediately available is ordinarily released after successful payment, account verification and any fraud or sanctions checks.
Short processing or verification time does not alter its digital character or create a right to cancel after supply has begun where the applicable legal conditions have been met.
Custom-project timing
Custom Deliverables are supplied according to the accepted scope, dependencies, review cycles and milestone plan.
A target date may be extended by late payment, incomplete requirements, missing content, unavailable credentials, delayed approval, changed scope, app-store review, third-party outage or another dependency identified in the Order or Terms of Business.
Staged and partial delivery
An Order may be supplied in files, modules, milestones, environments or releases. Each identifiable part may be separately delivered and accepted.
Delivery of one part does not depend on delivery of every later part unless the Order expressly states that the Deliverables are indivisible.
Delivered parts remain chargeable and are assessed separately under the Refund and Cancellation Policy.
Security and release controls
We may require payment clearance, identity verification, authority confirmation, multi-factor authentication or secure-channel confirmation before releasing source code, high-value files, credentials or administrative control.
A security hold is not a failure to deliver where the Customer has not completed a reasonable verification requirement.
Customer access responsibilities
The Customer must maintain access to the registered email address and account, protect credentials and secure delivered links and files after release.
The Customer must notify us promptly if an authorised contact changes or an account may be compromised.
Download windows and retention
A signed or private download link may expire for security. Expiry does not mean that the item was not delivered. The Customer should download, verify and back up Deliverables promptly.
Unless continuing storage is expressly included, we do not guarantee indefinite retention of delivered files after the stated support or access period.
Review period
The Customer must test and review each delivery within the period stated in the Order or, if none is stated, seven calendar days.
A report should identify the affected item and environment, the steps to reproduce, the expected result, the actual result and supporting evidence.
Operational acceptance
For Business Customers, approval, production use, onward publication, instruction to continue or failure to issue a valid rejection within the review period may be recorded as operational acceptance.
For Consumers, acceptance and remedies remain subject to mandatory consumer law. Operational acceptance does not remove a mandatory remedy for a latent defect that could not reasonably have been identified during review.
Evidence of fulfilment
We may retain the accepted Order, applicable policy record, checkout consent, timestamps, emails, account notifications, delivery logs, IP and device records, download events, repository activity, deployment records, access grants, demonstrations and acceptance history as evidence of fulfilment.
Such records are retained in accordance with the Privacy Notice and applicable law.
Missing, expired or inaccessible delivery
A Customer should report a missing, expired, inaccessible or corrupted delivery promptly to support@involvecsolutions.com with the Order reference and details of the issue.
After verification, we may redeliver, renew access, restore a link or provide another secure method. A problem caused by a full mailbox, lost credentials, expired link or Customer security setting will ordinarily be resolved by redelivery rather than refund.
Deployment and third-party review
Where delivery requires an app store, marketplace, registrar, hosting provider or other third-party review, our obligation is to prepare and submit the agreed material with reasonable care; we do not guarantee the third party's approval or timetable unless expressly stated.
A rejection caused by Customer content, business model, account status or platform policy does not reverse delivery of work already performed.
Post-delivery changes
A change requested after delivery or acceptance is treated as support, maintenance, revision or new scope according to the contract. It may require a separate fee and does not invalidate the original delivery.
Relationship with refunds
After delivery, deployment, activation or access, no change-of-mind refund is ordinarily available for the delivered item. Partial and staged deliveries are assessed under the Refund and Cancellation Policy.
Mandatory remedies for non-conforming supply remain unaffected.
Where the Delivery Timeline Is Recorded
The delivery timeline is not ordinarily stated on the invoice. It is shown and maintained in the Customer account dashboard and may also be communicated by an official email sent by Involvec Solutions.
The dashboard or official email may state the requirements status, Service Commencement Date, estimated delivery window, current stage, dependencies, requested Customer action, pause status and revised estimate.
Commencement Confirmation
The delivery period begins only when Involvec Solutions confirms that the applicable requirements, content, access, payment, approvals and verification are complete and the Order is ready for production.
The commencement confirmation may be issued through the dashboard, by email or both. The date recorded in that confirmation is the Service Commencement Date unless an accepted Custom Project document expressly states another date.
An invoice, automated payment receipt or submission of an incomplete Requirement Form is not a commencement confirmation.
Service Details and Regular Updates
Involvec Solutions will provide the Customer with appropriate Service details through the Order confirmation, dashboard or email. Those details may include the purchased scope, selected options, required inputs, key exclusions, current stage and delivery arrangements.
During active performance, Involvec Solutions may provide regular progress updates at intervals appropriate to the Service, milestone or Subscription. The frequency and form of updates may differ according to the complexity and duration of the work.
The Customer must review requests and updates promptly. A lack of response may pause the affected work and extend the estimated delivery date.
Pause, Resumption and Revised Estimates
Where performance is blocked by a Customer dependency, the delivery period is paused from the time the dependency is requested or identified until complete and usable information, access, approval or payment is received.
After the dependency is resolved, Involvec Solutions may require reasonable time to validate the information, restore the production environment and reschedule the work. The dashboard or an official email may show a revised estimated delivery window.
A revised estimate issued because of Customer delay does not constitute a failure to deliver by Involvec Solutions and does not invalidate work already supplied or charges already earned.