Delivery,
made clear.

01What delivery means

Our services are primarily digital. Delivery may be an accessible staging link, design file, repository invitation, deployed application, configured account, workflow, documented IT task, catalogue update, campaign setup or service report, as specified in the accepted Scope. Physical goods, courier charges and onsite attendance are not included unless separately agreed.

A milestone review delivery, production launch and final source-file handover are different events. Delivering one does not represent that all others are complete. No contract arises merely because you submit the enquiry form.

02When the delivery schedule starts

We confirm a start date after accepting the Scope, receiving the agreed booking payment, appointing the decision-maker and receiving the necessary content, access and approvals. A payment alone cannot start a task that depends on missing information.

The Scope identifies delivery milestones, dependencies, responsible people and any fixed deadline. Published examples and verbal timing discussions are estimates unless included as a binding commitment. A delivery date is not an unconditional promise of third-party approval or commercial results.

03Delivery channels and proof of delivery

We use the agreed email, project workspace, secure file-sharing service, repository or account invitation. A delivery message should identify the milestone, what is ready, how to access it, what remains, the review deadline and any action required from you. Logs, version history and written approvals may be used to establish what was delivered.

Keep nominated contact details current and tell us promptly if a link, invitation or attachment is inaccessible. We will provide a reasonable alternative or reissue access. An inaccessible deliverable does not start the review period until reasonable access is available. Downloadable links may expire; we will identify an expiry where applicable.

04Milestones, part delivery and delays

Projects may be delivered in phases so you can review work before the next stage. Only the completed phase is submitted for acceptance. A partial delivery does not make an unfinished final milestone complete or automatically entitle us to its full fee.

Client-side delays in content, approvals, licences, access or payment can move later milestones. Changes in scope require a revised estimate. Provider outages, API changes, KYC, marketplace reviews, app-store decisions, DNS propagation and email filtering can affect external completion dates. We will explain material impacts, offer a revised plan and remain responsible for the work we agreed to perform with reasonable care.

Rush delivery must be expressly accepted, may carry a quoted fee and remains subject to technical and external constraints. A delayed project is not automatically a cancellation; rights arising from a binding deadline or deficient service remain available.

05Review and acceptance

Unless the Scope states otherwise, you have 5 business days from an accessible milestone delivery to review it against the agreed requirements. Send one consolidated list of material mismatches, with the relevant page or workflow, steps to reproduce, environment and screenshots where useful.

• In-scope defect: a failure to meet an agreed requirement or an implementation error. Verified defects are corrected without using a paid revision round.
• Included revision: a refinement within the original approved brief and remaining revision allowance.
• Change request: a new requirement, changed direction or addition outside the accepted Scope. Price and timing are agreed before work starts.

We will address a valid material objection and resubmit the affected work for a further 5-business-day review, unless another reasonable period is agreed. Minor defects that do not materially prevent the agreed use can be listed with a correction plan; they do not excuse payment for unrelated accepted work.

Written sign-off, an instruction to launch or intentional ordinary production use may evidence acceptance. Testing is not production use. For business clients, after the initial review period we may send a reminder allowing a further 5 business days; if no material objection is received, the milestone may then be treated as accepted for scheduling and billing. Silence does not authorise launch, new fees or scope changes, and does not remove latent-defect, statutory or agreed support rights.

06Production launch and release authority

A production launch requires your authorised written instruction, completion of agreed pre-launch checks and the payment due for that stage. We will not treat an unanswered staging link as permission to launch. You approve final content, product information, prices, tax settings, customer-facing policies and campaigns before publication.

Before a material migration or change to live data, agree who creates the backup, confirms it can be restored, schedules downtime and performs rollback if required. Existing analytics and integrations are retained only where listed in the migration Scope. Unauthorised changes by other providers can invalidate a planned release window.

A live website, approved ad campaign or configured payment gateway is not a guarantee of sales, ranking, inbox placement, platform approval or uninterrupted third-party service.

07Final handover and account access

After the relevant agreed fees are paid, the handover checklist should identify the delivered files and accounts, source or editable assets included in the Scope, repository access, deployment instructions, licence dependencies, known issues, renewal responsibilities and any training included.

Client-owned accounts and domains remain yours. We transfer available owner access for accounts we administer on your behalf, subject to provider verification and security checks. Third-party credentials, another client’s assets, our internal tools and unlicensed commercial software cannot be transferred as part of your deliverable.

Download your handover package and keep an independent copy. Tell us promptly about a missing agreed item. A new provider’s onboarding, a different hosting platform, extra training or a new export format may require separately agreed work.

08Delivery of recurring and operational services

Retainers deliver the agreed activities, capacity, response windows or reports for a stated period. They are not a promise of an unlimited number of tasks or a particular commercial result. The Scope should state the task cap, covered accounts or users, priority system, reporting cycle and what happens to unused capacity.

Unless expressly agreed, unused reserved capacity does not roll over to a later period, provided the agreed capacity was genuinely available and we were ready to perform. Capacity we did not provide is not deemed earned merely because a month ended. Emergencies and out-of-hours requests require a separate arrangement.

09Post-delivery defects and support

Unless a different period is agreed, bespoke-development defects reported within 30 calendar days after delivery of the completed deliverable are assessed under the defect-correction terms. The request should identify a reproducible mismatch with the agreed Scope.

Ongoing content edits, provider updates, new integrations, new regulations, compromised client credentials or third-party changes are separately scoped to the extent they did not arise from our breach. Service-level response and resolution targets apply only if included in a written support agreement. A defect-reporting window does not extinguish a statutory claim or shorten its legal filing period.

10Paused projects and delivery archives

If required client inputs remain outstanding for more than 10 business days, we may pause after notice. After 30 calendar days of client-caused inactivity, we may give at least 5 business days’ final notice before archiving. The original delivery slot may no longer be available, and a restart plan must be agreed.

Archiving is not automatic cancellation or forfeiture. We reconcile the work if the engagement ends. We are not a permanent file-storage provider unless contracted as one. We will communicate a practical collection or export window before routine removal of project files; legal records and necessary security logs may be retained separately.

11Delivery concerns and remedies

Report missing access, a missed milestone or an incomplete item to hello@vorohq.com with your project reference. We acknowledge complaints within 48 hours and aim to resolve them within one month, subject to a shorter legal requirement. For time-sensitive launch issues, also call +91 11 6929 6665.

Where we materially fail to deliver, correction, re-performance, an agreed revised plan or a refund for the affected undelivered work may be appropriate under the Refund and Cancellation Policy and applicable law. Nothing in this policy removes a mandatory remedy. Read it with the Terms & Conditions.

12Indian law and exclusive Delhi jurisdiction

Indian law governs this policy and the contractual relationship. Subject to mandatory law, the courts of competent jurisdiction situated in the National Capital Territory of Delhi, India, shall have exclusive jurisdiction over all disputes, claims and proceedings arising out of or relating to this policy, our website or our services, including their formation, interpretation, performance, breach or termination. The parties agree to exclude the jurisdiction of other courts to the extent legally permitted.

This clause selects Delhi courts that otherwise have jurisdiction; it does not create jurisdiction where none exists. It does not exclude a consumer commission, statutory authority, tribunal or other forum whose jurisdiction cannot lawfully be excluded, or prevent a person from exercising a non-waivable statutory remedy. Any separate arbitration agreement must be expressly agreed in a signed writing; these policies do not impose compulsory arbitration.