Terms
How engagements work, in plain language. The binding version lives in each statement of work — this is so you know what is in it before you sign one.
This page is a summary
The binding terms for any engagement are in its statement of work, signed by both sides. This page describes how we normally operate so you know what to expect before anything is signed. Where the two differ, the signed document governs.
Scope and changes
Every engagement has a written scope agreed before work starts. Changes are quoted in writing and agreed before they are built, and they are treated as new work rather than absorbed silently. That is what makes a fixed price and a fixed date meaningful.
Payment
Fifty per cent advance before the build begins, fifty per cent before go-live on your domain. Work does not start until the advance clears. Invoices are payable within seven days unless the statement of work says otherwise. Prices exclude GST.
Ownership
On final payment, all code, design files, repositories, credentials and infrastructure created for the engagement are yours. We work inside your GitHub organisation and your cloud account from the first commit, so there is nothing to migrate. We retain no licence over your product and claim no rights in your data.
Our reusable components
Some builds include components from our internal registry. Those are delivered to you as editable source under a perpetual, irrevocable licence to use, modify and distribute them as part of your product. We keep the right to continue using the same components elsewhere — they predate your project and will outlive it.
Warranty
Six months from go-live, we fix defects in what we built at no cost. That covers our work not doing what the scope said it would. It does not cover new features, changes to third-party services, or issues caused by modifications made by others after handover.
Confidentiality
We treat everything you share as confidential and will sign your NDA rather than insisting on ours. Where an engagement touches personal data we work under a data-processing agreement. Access to your systems is limited to named people, time-boxed to the engagement, and revoked at handover.
Portfolio rights
We would like to describe the work publicly, but we ask first and we accept no. Nothing appears on this site, in a proposal or in a pitch without your agreement, and anything you mark confidential stays that way indefinitely.
If it goes wrong
Either side can end an engagement in writing. You pay for work completed to that point and we hand over everything produced so far — code, credentials and documentation — in the same condition as a normal handover. We do not hold deliverables to force a renegotiation.
Governing law
Engagements are governed by the laws of India, with courts in Uttar Pradesh having jurisdiction, unless the statement of work agrees otherwise.
Anything here you would want changed for your engagement? Say so before we draft the statement of work — hello@valentir.in.
Valentir Technologies Private Limited · Noida, Uttar Pradesh, India