Terms of Service

01Who we are and what these terms cover

Hextor Labs is the trading name of Aakarshak Chauhan, sole proprietor, registered in India under Udyam Registration Number UDYAM-UK-05-0143392 as a Micro enterprise. Because a sole proprietorship has no separate legal personality, the contracting party is that individual trading under the Hextor Labs name.

By using this website you accept sections 2 and 3. The rest apply once we begin work together, and are read alongside the written scope for your engagement. Where a signed scope, statement of work, or master agreement says something different from these terms, that document wins for the engagement it covers.

These terms are for businesses. They are not a consumer contract.

02The website

Everything on this site is descriptive. The workflow summaries, timelines, and answers in the FAQ describe how we normally work; they are not a quote, a specification, or a guarantee of outcome for your particular operation. Nothing here is legal, tax, financial, or compliance advice.

We try to keep the site accurate and available, but it is provided as it is. Do not use it to break the law, to attack it, or to scrape it at volume.

03Enquiries and the free audit

Sending the enquiry form starts a conversation and nothing more. It creates no contract and no obligation on either side.

The first hour — the audit — is free, whether or not you go further. In it we look at where the time goes in your operation and what a workflow would have to handle to be worth building. What comes out of it is a view and, usually, a scope and a number. You are free to take that and do nothing, do it yourself, or take it elsewhere.

Both sides should treat what is discussed in the audit as confidential, on the terms in section 10, even though no contract has been signed.

04How an engagement works

Work begins when you approve a written scope. The scope names what is being built, what it connects to, what “done” means, the price, and the timeline. If it is not in the scope, it is not in the build — which is the point.

A bespoke build normally runs through four steps: audit, prototype, human-in-the-loop test, live deploy. We may move faster where a standard workflow fits with little change.

Changes

If you want something added mid-build, we will price it as a written change to the scope before doing it. Scope does not grow quietly and it does not grow by accident. Equally, if we discover partway through that the original scope will not do the job, we will tell you at once rather than at the end.

05Fees, payment, and costs that are not ours

• Priced per workflow. The price is agreed in the scope. No hourly billing.
• Payment schedule is set in the scope, typically part on signature and the balance on live deployment.
• Invoices are payable within 15 days unless the scope says otherwise. Overdue amounts may carry interest at 1.5% per month, and we may pause work while an invoice is outstanding.
• Taxes. Fees are exclusive of tax. We are not presently registered for GST, so no GST is charged on our invoices. Should that change, or should any other tax become applicable to a supply, it is added at the prevailing rate and shown separately on the invoice.
• Running costs are yours. Because the workflow lives in your accounts on your keys, the model API usage, cloud hosting, and any third-party licences are billed to you directly by those providers. We never mark them up, and we will estimate them before you commit. They can change if your volumes change or a provider changes its pricing.

06What you need to provide

A build depends on things only you can supply. You agree to give us, in reasonable time:

• Access to the accounts, systems, and API keys the workflow needs, at the scope of permission we agree.
• A person who can answer questions and make decisions.
• Accurate sample data, and the rules the workflow is meant to apply.
• Confirmation that you have the right to give us that access and that data, and that processing it the way we have described is lawful for you.

If any of that is late, timelines move accordingly. You are responsible for your own accounts, for revoking our access when the engagement ends, and for keeping backups of your systems.

07Who owns what

You own the deliverable

On full payment, the workflow we build for you — its configuration, its prompts, the code written specifically for it, and its documentation — is yours. It runs in your accounts and it keeps running if you never speak to us again. We assign to you whatever rights are needed to make that true.

We keep our own toolkit

We bring general methods, patterns, internal libraries, and know-how that existed before your engagement or that we develop generally across our work. Those stay ours, and we grant you a perpetual, non-exclusive licence to use them to the extent they are embedded in your deliverable. This lets us keep working in the same field; it does not let us reuse anything specific to you.

Your data stays yours

We claim nothing over your data, and we do not use it to train models of our own. The Privacy Policy sets out how it is handled.

Naming you

We will not name you as a client, use your logo, or describe your project publicly without your written permission. Ask us and we will happily stay anonymous.

08What AI systems can and cannot be relied on to do

This section matters more than the rest, so it is written plainly.

The systems we build use machine learning models that are probabilistic. They are extremely good at the work we point them at and they are not infallible. A model can extract a field incorrectly, misread an unusual document, or draft a reply that is confidently wrong. This is a property of the technology, not a defect in a particular build.

Everything we build is designed around that fact rather than in denial of it: confidence thresholds, validation rules, retries, and a review queue where anything uncertain goes to a person. That is what the human-in-the-loop step in section 4 is for.

So, clearly: you remain responsible for decisions your business takes on the output of a workflow. Where output feeds a consequential decision — a payment, a contractual commitment, a legal or regulatory filing, anything affecting an individual's rights — you agree to keep meaningful human review in the loop, and not to remove the review steps we build in. We are not liable for the consequences of output used without the review the design assumed.

We will tell you honestly, before you commit, when we think a task is at the edge of what these systems do reliably.

09Third-party services

Your workflow will depend on services neither of us controls — model providers, cloud platforms, the applications it connects to. Those services set their own terms, and they can go down, change an API, deprecate a model, or change their prices. We build with retries, fallbacks, and alerting so a wobble does not become a silent failure, but we cannot be responsible for a third party's own availability, acts, or pricing.

Where a provider retires something your workflow depends on, we will tell you what it takes to move.

10Confidentiality

Each side will keep the other's non-public information confidential, use it only for the engagement, and protect it at least as carefully as its own. This runs from the first conversation and continues for three years after the engagement ends — indefinitely for anything that is a trade secret or personal data.

It does not cover information that is already public, was already known without an obligation of confidence, or is independently developed. If either side is legally compelled to disclose something, it will give the other notice where it lawfully can.

11What we warrant, and what we do not

We warrant that we will perform with reasonable skill and care, in a professional manner, by people competent to do the work, and that the deliverable will materially do what the scope says on the date it goes live.

If something in the deliverable does not match the scope, tell us within 30 days of deployment and we will fix it at no charge. That correction is your remedy for a defect.

Beyond that, and to the extent the law allows, we exclude all other warranties, whether express or implied. In particular we do not warrant that a workflow will be uninterrupted or error-free, that model output will be accurate in every instance (see section 8), or that any specific commercial result, saving, or revenue will follow. Post-deployment support, monitoring, and maintenance are only included if the scope says so.

12Liability

Neither side is liable to the other for indirect or consequential loss, or for loss of profit, revenue, business, goodwill, anticipated savings, or data, however it arises.

Each side's total liability arising out of or in connection with an engagement is limited to the fees paid by you to us for that engagement in the 12 months before the claim arose.

Nothing here limits liability for fraud, fraudulent misrepresentation, death or personal injury caused by negligence, or anything else that cannot be limited under Indian law. The limits in this section do not apply to your obligation to pay fees properly due, or to either side's breach of section 10.

13Ending an engagement

Either side may end an engagement on 30 days' written notice, or immediately if the other commits a material breach and fails to fix it within 15 days of being told.

On termination you pay for work properly done up to that date, we hand over everything completed and paid for, and each side returns or destroys the other's confidential information. You should revoke our access to your accounts. Sections 7, 8, 10, 11, 12, and 15 survive.

14Events outside anyone's control

Neither side is in breach for a delay or failure caused by something genuinely beyond its reasonable control — natural disaster, war, a general failure of internet or power infrastructure, government action, or a prolonged outage at a major upstream provider. The affected side will tell the other promptly and both will act reasonably to work around it.

15Governing law and disputes

These terms and any engagement under them are governed by the laws of India. The courts at Dehradun, Uttarakhand have exclusive jurisdiction, and both sides submit to it.

Before either side goes to court, we both agree to spend 30 days genuinely trying to resolve the matter between senior people on each side. Most disagreements are a misunderstanding about scope, and most misunderstandings about scope survive one honest conversation.

16The usual closing clauses

• Whole agreement. These terms plus your signed scope are the whole of what is agreed, and replace anything said beforehand.
• Severability. If a clause is unenforceable, the rest still stands.
• No waiver. Not enforcing something once does not give it up.
• Assignment. Neither side may assign the engagement without the other's written consent, except to a successor of substantially the whole business.
• Independent contractor. We are your supplier, not your employee, agent, or partner.
• Changes. We may update these terms for future engagements; the effective date at the top will change. The version in force when your scope was signed governs that engagement.

17Contact

The full registered address is available on written request, and to any regulator entitled to it.