Terms of Service

1. Who these terms are between

These terms cover engagements between you (the client) and MyDigiShell, a software practice based in India working with clients internationally. MyDigiShell is a registered trading name, not a separate limited company — you are contracting with the proprietor and the team working under that name, which is why this document says "we" throughout.

The people who will be on your project are named on the site, and you deal with them directly rather than through an account manager. Where you have your own contractor agreement or statement of work, that document governs and these terms fall away to the extent they conflict. We read what we sign.

2. What is offered

• API performance audit — a fixed-scope engagement producing a written report and an accompanying pull request.
• Backend rewrite or new service build — scoped per project against a written design document, delivered in milestones.
• Fractional backend lead — a monthly retainer for ongoing architecture, review and implementation.

Backend and infrastructure work is the core. Where a project needs adjacent work, we say so honestly and scope it, rather than pretending any one person covers everything.

3. Scope and quotes

Work begins from a written scope agreed by both sides. Audits are fixed price for a fixed scope. Builds are quoted after a design document exists, because quoting before that is guesswork billed to you. An online quote produced through this site is an estimate, not a binding offer — the agreed scope document is what governs. Changes to agreed scope are re-quoted in writing rather than silently absorbed or silently dropped.

4. Payment

• Audits are payable in full before the engagement starts.
• Builds are milestone-based: a deposit to begin, then payment per milestone on delivery of that milestone.
• Retainers are invoiced monthly in advance.
• Invoices are in USD for international clients and INR for domestic work, due within fourteen days. Work may pause on overdue invoices, and we will tell you before that happens rather than after.

Prices exclude taxes, duties or withholdings applicable in your jurisdiction, which are your responsibility.

5. What we need from you

• Timely answers to questions that block progress.
• Access to the systems, repositories and representative data the work requires.
• Authority to grant that access — you confirm you are entitled to share whatever you share with us.
• A named person who can make decisions and approve milestones.

Timelines assume this. Where they slip because access or decisions do not arrive, dates move accordingly, and we will flag it early.

6. Intellectual property

Your material stays yours: your code, data, content and systems remain your property throughout.

Work we produce transfers to you on full payment, including the commit history and accompanying documentation.

General building blocks — the generic utilities and patterns any engineer carries between engagements — remain ours to reuse. This never includes anything specific to your product, domain, data or business logic.

Open source components remain under their own licences, and we will tell you what has been introduced and under which licence.

7. Confidentiality

Anything non-public you share stays confidential, indefinitely, and is used only to do the work. Within the team, access is limited to the people working on your engagement. We will not name you as a client publicly without your written agreement — which is why this site carries no client logos. We are happy to sign your NDA, and everyone on the team is bound by the same confidentiality obligations.

8. What we do and do not warrant

We warrant that the work will be performed with the reasonable skill and care of senior engineers in this field, and that it will substantially match the agreed scope.

We do not warrant that software will be free of defects, that performance will improve by a specific percentage, or that any system will achieve a particular uptime. We do not offer a 24/7 on-call rotation or an uptime SLA as standard; any such commitment must be agreed separately and in writing.

9. Limitation of liability

Our total liability arising from an engagement is limited to the fees you paid for that engagement. We are not liable for indirect or consequential loss, lost profit, lost revenue, or loss of data. Nothing here limits liability that cannot lawfully be limited, including for fraud.

10. Ending an engagement

• Retainers: either side may end the arrangement with thirty days written notice.
• Builds: you may stop at any milestone boundary; you pay for work completed and delivered up to that point.
• Audits: once started, the fee is committed, as the time is reserved.

On termination we hand over completed work you have paid for, along with whatever documentation exists at that point.

11. Independent contractor

We work as an independent practice. Nothing in an engagement creates employment, partnership, agency, or joint venture between you and us or any member of the team, and MyDigiShell remains responsible for its own taxes, equipment and insurance.

12. Disputes and governing law

If something goes wrong, raise it with us directly first — most problems are a conversation, not a claim. Failing that, these terms are governed by the laws of India, and the courts there have jurisdiction, unless we have agreed otherwise in a signed agreement.

13. Changes

These terms may be revised; the effective date above tracks it. The version in force for your engagement is the one current when we agreed the work, not whatever is published later.

14. Contact

Questions about any of this go to mijanur@mydigishell.com.