Skip to content

The terms we work under

These cover the site itself and the shape of an engagement. A signed statement of work takes precedence over anything here, and where the two disagree, the statement of work wins.

Last updated 30 September 2026

Who you are contracting with

devsforfun Studio (OPC) Private Limited, registered in India, trading as Stafflo. Engagements are governed by Indian law unless a signed statement of work says otherwise.

What these terms cover

The site, and our five services: the audit, the private AI readiness check, the pilot, enablement, and the Run and improve plan. Each engagement’s scope, price and dates are set in its own statement of work. What each service includes and leaves out is on the services page.

Data protection

For a pilot we sign a data processing agreement, with Standard Contractual Clauses for clients in the EU, and for US healthcare work a business associate agreement. Both are available before any work starts.

What you own

On full payment, you own the source we write for you outright, in your repository, with the commit history intact. We keep no licence back over it and we do not resell your build to anyone else.

We do reuse our own general tooling and patterns across engagements — the engines themselves, the evaluation tooling, the queueing and rate-limiting approach. Those predate your project and remain ours. Nothing specific to you, your data, or your business rules is carried anywhere else.

What we warrant, and what we do not

We warrant that the work is performed with reasonable skill and care, and that at handover the tool does what the statement of work says it does.

We do not warrant that third-party systems will stay available, that a vendor will not change an API, or that a model provider will keep behaving as it did on the day we evaluated it. A large part of what we build exists precisely because those things happen, but they remain outside our control.

Nothing here limits liability for fraud, or for anything that cannot lawfully be limited. Otherwise our aggregate liability on an engagement is capped at the fees paid for it.

Your responsibilities

Timely access to the systems the tool has to reach, a named person who can answer questions about the process, and your own cloud, hardware and model spend. We cannot build against a system we are not given access to, and delay there moves the dates.

Support

We reply within one working day, during business hours in India, with a named escalation contact from kickoff. We don't run a 24/7 on-call rota.

Demos and evidence

The demos on this site run on synthetic data, and the figures on it describe our own tests on our own datasets, not results for any client. They are not a performance guarantee for your systems, and nobody outside this studio has checked them.

Changes

We may update these terms; the date at the top tells you when we last did. Changes do not apply retroactively to an engagement already underway.