Terms of service
These terms apply to the project work AI SpeedForce does for business clients: AI agent engineering, retrieval (RAG) systems and automations.
Who we are
AI SpeedForce is not a company. It is the trading name of Poonam Devi, an individual who runs the business as a sole proprietor from India. In these terms, "we", "us" and "our" mean Poonam Devi, trading as AI SpeedForce. "You" means the business that hires us, called the client.
What we do
We deliver scoped project work for business clients: AI agent engineering, retrieval (RAG) systems and automations. We do not sell a software subscription or an off-the-shelf product. Each project covers the work described in its proposal or statement of work, and nothing more unless we both agree in writing.
How an engagement is formed
An engagement starts when both of us sign a written proposal or statement of work (SOW). It sets out the task, the deliverables, the eval suite the work will be tested against, the timeline, the fees and the payment schedule.
These terms apply to every engagement. If the signed proposal or SOW says something different from these terms, the signed proposal or SOW wins for that engagement.
Changes to scope are agreed in writing, by email or an updated SOW, before we do the extra work.
What we need from you
AI systems are only as good as the examples and access behind them. To do the work, you agree to provide:
- Real task examples. Genuine examples of the task, including awkward cases and ones that went wrong. We write the eval cases from them.
- System access. Access to the systems the work touches, with the narrowest permissions the task needs, on time.
- A named point of contact. One person who can answer questions, make decisions and approve deliverables.
You confirm that you have the right to share the data and grant the access you give us. If you are late with any of these, the timeline moves by the same amount, and we are not responsible for the delay.
What we commit to
- Do the work described in the proposal or SOW with reasonable skill and care.
- Test the work against the eval suite agreed with you, and show you the results and run traces.
- Keep write actions behind human approval by default.
- Tell you plainly when we think a task is a poor fit for an AI agent, or when a simpler approach would do.
- Keep your information confidential, as set out below.
Fees and payment
Fees, deposits, milestones and payment dates are set in the signed proposal or SOW. We invoice in line with that schedule, and you pay each invoice by the date it shows.
Our fees do not include third-party costs. See third-party costs.
Late payment
If an invoice is not paid by its due date, we will remind you in writing. If it is still unpaid after that, we may pause work on the engagement until it is paid, and the timeline moves by the length of the pause. Any interest or charges on late payment are those stated in the signed proposal or SOW.
Ownership of deliverables does not pass to you until they are paid for in full. See ownership.
Third-party costs
The AI systems we build run on services from other providers. These include AI model and API usage, hosting, databases and software licenses. They are set up in your own accounts, and you pay those providers directly. These costs are separate from our fees.
Before we build, we agree a cost budget with you for model and API usage. We cannot control the prices or terms of third-party providers, and they may change them.
Costs already incurred with third parties are not refundable by us. See the refund and cancellation policy.
Ownership and intellectual property
On full payment for an engagement, you own the deliverables we made for you in it. That includes:
- the code;
- the prompts;
- the tool definitions;
- the MCP servers; and
- the eval cases.
They live in your repository and your accounts. Nothing in them depends on us continuing to work with you.
We keep ownership of our general know-how, skills, methods and working practices, and any reusable internal libraries we had before the engagement or build for use across projects. Where a deliverable includes one of our reusable libraries, you get a permanent, non-exclusive, royalty-free license to use, change and run it as part of that deliverable.
Open-source components stay under their own licenses. Your own material, data and systems stay yours at all times.
How AI systems behave
The systems we build use AI models. Please read this section carefully, because it explains what you are buying.
- Output is probabilistic. AI models can give different answers to the same input. An AI system can be wrong, misread a record, or take an action that looks correct but is wrong for your business. This is a property of the technology, not a defect we can remove.
- Testing is against an agreed eval suite. Before handover we test the system against the eval suite agreed with you and share the results and run traces. Passing the eval suite shows the system handles those cases. It does not prove the system will be right on inputs nobody anticipated.
- Write actions need human approval. By default, any action that changes a record, sends a message or moves money waits for a person to approve it. That approval step stays in place unless you ask us, in writing, to remove or narrow it. If you do, actions in that path run without review, and you are responsible for their results.
- Providers can change. AI systems depend on model providers and platforms we do not control. Their changes to models, APIs, limits or prices can affect how a system performs.
- Use after handover is your responsibility. Once a system is handed over, you decide how it is used, who uses it, what data it sees and what it is allowed to do. You are responsible for that use, and for complying with the laws that apply to it.
The disclaimer says more about what we do and do not promise.
Confidentiality
Each of us will keep the other's confidential information private and use it only for the engagement. Confidential information includes business plans, data, system details, credentials, code and the terms of the proposal.
This does not cover information that is already public, that the other side already knew, that it received lawfully from someone else, or that the law or a court requires it to disclose. This duty continues after the engagement ends.
How we handle personal data is set out in the privacy policy.
Warranties
We will do the work with reasonable skill and care, and the deliverables will materially match the proposal or SOW when handed over.
Apart from that, and to the extent the law allows, the work is provided without any other warranty or promise, express or implied. In particular we do not promise that an AI system will be error-free, will run without interruption, or will produce any specific business result.
Limitation of liability
Our total liability to you for all claims arising from or connected with an engagement, whether in contract, tort (including negligence) or otherwise, is limited to the fees you actually paid us for the affected engagement.
We are not liable for indirect or consequential loss, or for loss of profit, revenue, business, goodwill or data, even if we were told it was possible.
We are not liable for loss caused by:
- actions an AI system took in a path where you removed or narrowed the human approval step;
- how you use a system after handover;
- changes or failures of third-party providers, models or platforms; or
- inaccurate or incomplete information, examples or access you gave us.
Nothing in these terms limits liability that cannot be limited under Indian law, such as liability for fraud.
Indemnity
You agree to cover us against losses, claims and reasonable costs, including legal costs, that arise from:
- data, material or access you provided that you did not have the right to share;
- your use of a system after handover, including any breach of law by that use; or
- actions taken in a path where you had the human approval step removed or narrowed.
We will tell you promptly about any such claim and let you take part in handling it.
Termination
Either of us can end an engagement by giving written notice as set out in the proposal or SOW.
Either of us can end an engagement straight away by written notice if the other side seriously breaks these terms or the SOW and does not fix it within a reasonable time after being told in writing.
When an engagement ends:
- you pay for the work completed up to the end date, and any third-party costs already incurred;
- we hand over the work completed to date, and it becomes yours once paid for; and
- each of us returns or deletes the other's confidential information, except where the law requires a record to be kept.
The refund and cancellation policy explains how this works in practice.
Events outside our control
Neither of us is responsible for a delay or failure caused by events outside our reasonable control, such as natural disasters, epidemics, war, government action, power or internet failure, or an outage at a major provider. The affected side will tell the other promptly and resume as soon as it can. If the event lasts long enough to defeat the purpose of the engagement, either of us can end it by written notice.
Governing law and jurisdiction
These terms, and every engagement under them, are governed by the laws of India. The courts of Delhi, India have exclusive jurisdiction over any dispute arising from them.
Before going to court, we will each try in good faith to settle the dispute by talking to each other.
General
- Entire agreement. These terms and the signed proposal or SOW are the whole agreement for an engagement.
- Notices. Notices under these terms are given in writing by email to the contact addresses we each use for the engagement. Ours is in the contact section.
- Transfer. Neither of us can transfer an engagement to someone else without the other's written agreement.
- Severability. If a court finds part of these terms unenforceable, the rest still applies.
- Independent parties. We work as an independent contractor. Nothing in these terms makes us your employee, partner or agent.
Changes to these terms
We may update these terms. The version in force when you sign a proposal or SOW applies to that engagement, unless we both agree in writing to use a newer version. Changes are shown by the "Last updated" date and the version history.
Related policies
Read these terms with our privacy policy, refund and cancellation policy, cookie policy and disclaimer.
Contact
AI SpeedForce is run by Poonam Devi as a sole proprietor. Questions about this document, or any of our policies, go to:
- Name: Poonam Devi, proprietor, trading as AI SpeedForce
- Email: support@aispeedforce.com
- Phone: +91 7669002473
- Address: New Delhi 110063, India
Effective date: 22 September 2026
Last updated: 22 September 2026
Version history
| Version | Date | Change |
|---|---|---|
| 1.0 | 22 September 2026 | First published version. |
| 1.1 | 22 September 2026 | Cookie and privacy policies: added the light or dark theme choice saved in your browser. |
| 1.2 | 22 September 2026 | Privacy policy: the inquiry email also records the time, IP address and user agent of the submission. |
| 1.3 | 22 September 2026 | Privacy policy and disclaimer: added the agent-readiness scanner. |
| 1.4 | 22 September 2026 | Disclaimer: platform logos are trademarks of their owners. |