Terms of service

The content here is provided for information. Service descriptions, capabilities and service-level targets are indicative of how our programs are designed; they are not an offer and they do not create a contract. The binding terms for any engagement are the ones in the signed agreement and its SLA schedule.

You may read, print and share this material for your own evaluation. You may not reproduce it as your own, or use it to train a model that reproduces it as its own.

Figures published on this site describe what a program is designed and staffed to achieve. They are not guarantees. The contractual service level for your engagement is agreed in writing after we baseline your current performance, and only that number is enforceable.

Every engagement begins with a written scope listing what is in and what is out. Work outside the scope is quoted in a written change note, with its volume impact and price, before it begins. We do not absorb unquoted scope quietly — it is how programs degrade.

We work inside your systems under named individual accounts with least-privilege access. You retain ownership of your data at all times. We act as a processor on your documented instructions, under the data-processing terms attached to your agreement.

SOPs, runbooks, QA rubrics, process maps and architecture notes we produce for your engagement belong to you, and are handed over on request at any point during the engagement or at its end. This is a contractual term, not a courtesy.

Our own general methods, templates and internal tooling remain ours. Anything built specifically for you under a development engagement is assigned to you on payment, as set out in that agreement.

Confidentiality obligations are mutual and are signed at both company and individual level — every person assigned to your account signs their own undertaking, not just the company. They survive the end of the engagement.

Fees, invoicing cadence, minimum term and notice period are set out in your agreement. Minimum terms exist because training and shadowing are paid for before the first month produces anything; they are not a lock-in device.

On termination we hand over documentation, transfer or revoke access as you direct, and delete or return client data on the terms in the agreement. Exit should be an access change and a handover call. If a vendor makes leaving hard, that is the product working as intended, and it is not how we build.

Nothing here limits liability that cannot lawfully be limited. Beyond that, liability is capped and allocated in the signed agreement — and negotiated openly rather than buried in a schedule nobody reads.

These website terms are governed by the laws of India, with the courts of Uttar Pradesh having jurisdiction. Engagement agreements may specify a different governing law by mutual agreement, and frequently do for international clients.

The contracting entity is Wizthinkers Private Limited, CIN U74999UP2022PTC174011.