Legal & policy centre

Service Delivery Policy

This policy explains how our digital services and deliverables are planned, reviewed, delivered, deployed, accepted, and supported. We do not ordinarily ship physical products.

Last updated12 July 2026
Please read this with your project documents.

A signed agreement, statement of work, approved proposal, or invoice may contain additional service-specific terms.

01

Digital deliverables

  • Deliverables may include strategy, reports, audits, creative assets, content, campaign structures, code, websites, stores, software, dashboards, APIs, databases, configurations, documentation, training, deployment, or support.
  • Delivery may occur through email, shared documents, approved messaging channels, meetings, repositories, cloud dashboards, staging links, production links, project-management tools, or client-controlled systems.
02

Schedules and estimates

  • Estimated schedules depend on scope, complexity, team availability, client inputs, content, approvals, payment milestones, integrations, platforms, and third-party response times.
  • Schedules may change where requirements change, dependencies are delayed, approvals are not received, third-party systems fail, or unforeseen technical work is discovered.
  • Rush or fixed-date delivery requires written confirmation and may involve additional fees or reduced scope.
03

Milestones and reviews

  • Projects may be divided into discovery, strategy, design, content, development, campaign setup, testing, deployment, and handover milestones.
  • Clients must review each milestone within the stated review period and provide consolidated, authorised feedback.
  • If no clear objection is received within the review period after reasonable follow-up, the milestone may be treated as accepted for scheduling and billing purposes, subject to applicable law and written project terms.
04

Client dependencies

  • The client must provide accurate content, brand assets, product data, legal notices, offers, account access, credentials, API information, domain or hosting access, payment details, approvals, and business rules on time.
  • We are not responsible for delay caused by missing or incorrect information, unavailable stakeholders, late payment, delayed approval, platform review, DNS propagation, third-party outage, or external vendor action.
05

Deployment and handover

  • Deployment may be made to staging, production, or client-controlled infrastructure according to scope and access availability.
  • Handover may include repository access, deployment links, accounts, documentation, environment guidance, agreed credentials, reports, files, and walkthroughs.
  • Source files, production release, administrative ownership, or final handover may be withheld while agreed payments remain overdue, to the extent permitted by law and contract.
  • Clients should change shared passwords, review users, preserve backups, and confirm ownership after handover.
06

Revisions and change requests

  • Included revisions are limited to the agreed scope and review rounds.
  • New pages, features, workflows, integrations, redesigns, campaign requirements, migrations, data work, or material changes may require a written change request, revised fee, and updated schedule.
  • Corrections to agreed functionality during a stated warranty period are distinguished from enhancements or third-party changes.
07

Support and maintenance

  • Post-delivery support is provided only where included in the project, warranty, retainer, or maintenance agreement.
  • Support may exclude new features, client or third-party edits, platform policy changes, hosting outages, compromised accounts, content changes, or incidents outside the agreed scope.
  • Ongoing maintenance, monitoring, backups, updates, campaign optimisation, analytics review, and support may be quoted separately.
08

Acceptance

  • A deliverable may be considered delivered when it is shared through the agreed channel, deployed, handed over, approved, or used commercially.
  • Clients should report defects with clear reproduction information during the agreed review or warranty period so that they can be assessed promptly.
09

Governing law, dispute resolution and Delhi jurisdiction

  • These terms and any service engagement are governed by the laws of India.
  • The parties should first attempt to resolve a dispute through written communication and good-faith discussion for at least 30 days after a written dispute notice, unless urgent interim relief is reasonably required.
  • If a commercial dispute remains unresolved, it may be referred to arbitration under the Arbitration and Conciliation Act, 1996. The tribunal will consist of a sole arbitrator mutually appointed by the parties, the seat and venue will be New Delhi, India, and proceedings will be conducted in English.
  • Subject to the arbitration clause, applicable law, and any non-waivable consumer remedy, courts at New Delhi, Delhi will have exclusive jurisdiction.
  • Nothing in these policies limits any right or remedy that cannot lawfully be excluded, including rights available under applicable consumer-protection law.