Terms

These terms are written in plain English on purpose. We ask clients for access to private repositories, so we want you to read them. Client work runs under a signed statement of work that refers to these terms; where the two differ, the statement of work wins. This page is also the terms of use for the website.

1. Who we are and who these terms cover

“Dravin AI”, “we” and “us” mean the engineering services firm operating at Gachibowli, Hyderabad, Telangana 500032, India, reachable at [email protected]. “You” means a visitor to dravin.ai, or a client who has signed a statement of work with us. The contracting entity is named in your statement of work. Dravin AI is a services firm. We do not sell a software product or a subscription.

2. Statements of work

Every engagement is described in a statement of work: the problem, the scope, the engineers, the kind of engagement (a project, embedded engineering, ongoing engineering, a code audit, vibe-code cleanup or consulting), the timeframes and the fees. Nothing in a proposal, a call or an email is binding until it is in a signed statement of work. Changes to scope are agreed in writing before the work changes.

3. Confidentiality

Anything you share with us that is not public is confidential: source code, data, documents, credentials, business information, and the fact of what you are building. We use it only to do the work, share it only with people who need it to do the work, and protect it with the practices on our security page. These obligations start when you first share something with us, whether or not a statement of work follows, and survive for three years after the engagement ends. Client names and work appear on this website only where the client has agreed in writing, or where the information is already public.

4. Intellectual property

You own the code from the first commit. All rights in the work we produce for you under the statement of work, including source code, models and model weights we train for you, prompts, configuration, infrastructure definitions, documentation and designs, are assigned to you as the work is created. If an invoice is unpaid past its due date, we may pause the work after written notice until it is paid; what you already own stays yours.

We keep what we brought. Tools, libraries, templates, methods and general know-how that existed before the engagement, or that we develop independently of your confidential information, remain ours. Where any of it is embedded in a deliverable, you receive a perpetual licence, with no royalty, to use it as part of that deliverable.

Open source stays open source. Third-party open-source components remain under their own licences, and we list them in the handover documentation.

We do not reuse your code, your data or your confidential information in work for anyone else.

5. Access to your systems

You grant access to the systems the work needs, and no more. We ask for the least privilege that will do the job: read-only for reviews, a named account of our own rather than a shared credential, and scoped tokens for deployment. You may revoke access at any time. Our practices for access, devices, secrets and offboarding are on the security page and form part of these terms.

6. Data protection

Where the work involves personal data of your users, you are the Data Fiduciary and we are a Data Processor under the Digital Personal Data Protection Act, 2023. We process that data only on your written instructions, only for the work, and only to the extent the work requires. We do not copy production personal data to our machines unless a statement of work says so, and we prefer anonymised or synthetic data for development. Our privacy notice sets out how we handle personal data in full, including subprocessors, retention and your rights.

7. Your obligations

Timely access, timely decisions and someone on your side who can make them. Feedback on demos within a working week, so the following week builds on it. Accurate information about the system, including any data it holds that is regulated. Payment of invoices on the terms in the statement of work.

8. Fees, invoicing and taxes

Fees are set out in the statement of work and nowhere else; we publish no rates. Invoices are issued on the schedule in the statement of work, and applicable Indian taxes, including GST, are added where they apply. Late payment may pause the work after written notice. Fees paid are not refundable, except where a statement of work says otherwise.

9. Use of AI tools

We use AI coding tools in our work and say so. Any tool that processes your code or data is used on terms that prohibit training on its input, is named to you before work starts, and can be vetoed by you. What such a tool produces reaches your repository only as a pull request on a branch, never directly on main, and one of our engineers checks it before it merges. Where your code is held during the work, including our agents’ isolated environments and preview deployments on our domain, is set out on our security page. We never use your code or data to train a model of our own or anyone else’s.

10. Warranties

We warrant that the work will be carried out with the care and skill of a competent senior engineer, and that to our knowledge the deliverables will not infringe anyone else’s rights. If a deliverable does not meet its statement of work, tell us in writing within 30 days of handover and we will correct it under the existing statement of work. We do not warrant business outcomes, user numbers, revenue, or the behaviour of third-party services and models we do not control.

11. Limits on liability

Neither side is liable to the other for indirect or consequential loss, including lost profit or lost data that you have not backed up. Our total liability under a statement of work is limited to the fees paid under that statement of work in the twelve months before the claim. Nothing here limits liability for fraud, for a breach of confidentiality, or for anything that cannot be limited under Indian law.

12. Ending the work

A project, a code audit, a vibe-code cleanup or a consulting engagement ends on the agreed end date or on delivery, whichever the statement of work says. Embedded or ongoing engineering can be ended by either side with 14 days’ written notice. Either side may end any engagement immediately for a material breach that is not fixed within 14 days of written notice. On ending: you pay for work done to that date; you receive everything produced to that date, with documentation; and we revoke our own access, delete local copies and confirm both in writing within seven days. Sections 3, 4, 6, 10, 11 and 13 survive.

13. Governing law and disputes

These terms are governed by the laws of India. If we cannot resolve a dispute by talking, either side may refer it to arbitration under the Arbitration and Conciliation Act, 1996, by a sole arbitrator, seated in Hyderabad, in English. Courts in Hyderabad, Telangana have exclusive jurisdiction for anything that cannot be arbitrated.

14. The website

The content on dravin.ai is ours or used with permission. You may link to it and quote it with attribution. The site is provided as-is; we may change it at any time. It uses Google Analytics to count visits; the privacy notice explains what that records and where it sets cookies.

15. Changes to these terms

We may update these terms; the date at the top changes when we do. For clients, the version in force is the one referenced by your statement of work.

16. Contact

[email protected] · Gachibowli, Hyderabad, Telangana 500032, India