A US client sends you a master services agreement before the first statement of work, and clause 14 says you must carry professional indemnity insurance. You have never bought a policy, so you either search for a quote and accept whatever the first page says, or you tell the client you will sort it out later. Both are guesses. This post explains professional indemnity insurance for developers and IT consultants in India: how these policies are typically built, what to read in the wording, and what to ask before you sign.
Wordings differ by insurer, so your own policy document decides. If you want the basic case for why a freelancer is personally liable, the earlier guide to professional indemnity insurance for freelancers covers it. This one covers the mechanics a developer should check.
A tech PI policy typically pays for financial loss caused by your error
Professional indemnity (PI) for technology work pays when a client claims financial loss caused by an error, an omission or negligent advice in your work. Typical examples are faulty software, integration or deployment mistakes, and missed deadlines that trace back to negligence. It also usually covers the legal defence costs of answering such a claim, subject to the limit. It is not a guarantee that any claim gets paid, because the wording, the exclusions and the insurer's assessment decide that.
The word to notice is negligence. A client who is unhappy with a design choice has a dispute. A client who lost money because your deployment script wiped their production data has a possible claim, and that second kind is what the policy is built around.
Claims-made cover depends on two dates, not one
PI in India is typically written on a claims-made basis. The claim must first be made against you in writing during the policy period, and the work behind it must have been done on or after the policy's retroactive date. If either date misses, the policy usually does not respond, even if the mistake was real and the client's loss was genuine.
Here is an illustration. Say your policy has a retroactive date of 1 January 2020. A bug you shipped in December 2019 is not covered, because the work is older than the retroactive date. A bug shipped in March 2024 is covered only if the client's written claim reaches you while a policy is in force. If you let the policy lapse in 2025 and the claim arrives in 2026, you have the work inside the retroactive window and no live policy to claim against.
Keep the same retroactive date when you renew or switch
When you renew or move to a new insurer, ask for the original retroactive date to carry over. If the new policy starts a fresh date, every project you delivered before it falls outside cover, and your older clients can still make claims. A lapse in cover can have the same effect, because it can remove cover for earlier projects. Check the wording for an extended reporting period or run-off cover, which some policies offer so that claims can still be notified after the policy ends.
Notification matters too. Late notification is a common reason for a denied claim, according to brokers. If a client emails that a release broke their checkout and they may hold you responsible, that email is the kind of circumstance most wordings ask you to report promptly. Read the notification clause and note the exact window.
Defence costs usually come out of the same limit
Under many PI wordings, compensation, the claimant's costs and your defence costs together cannot exceed the limit of indemnity. The insurer also usually needs to approve defence costs before you incur them. So a policy with a headline limit does not mean that full amount is available as compensation.
An illustration with round numbers, not a suggested limit: if your limit is ₹10,00,000 and defending the claim uses ₹3,00,000 in legal fees, only ₹7,00,000 remains for any compensation. If a lawyer you hired yourself sends a large bill before the insurer agreed to it, that bill may not be covered at all. Ask how defence costs are treated and whether you can choose your own lawyer.
Common exclusions are where claims fail
Read the exclusions before the benefits. Wordings commonly exclude fraud and deliberate acts, contractual penalties and liquidated damages, contractual liability beyond what the law would impose anyway, bodily injury and property damage, hardware failure, war, and claims or circumstances you already knew about when you bought the policy. Fines and regulatory penalties are also commonly excluded, including those under data protection and IT laws, though some policies offer a regulatory defence extension.
Two of these catch developers out. A client contract that promises a penalty of ₹10,000 per day of delay creates a liability the policy may not touch, because it comes from the contract rather than from your negligence. And a performance guarantee, such as promising 99.9 percent uptime, is often excluded as a contractual promise. The guide to the limitation of liability and indemnity clause explains how to keep those promises out of the contract in the first place.
Data breach and client IP vary by policy, so read the wording
Cover for data breach and for intellectual property claims differs from one insurer to the next, and you should not assume either is included. Some brokers describe PI that responds to loss of client data or breach of client information, while others say PI does not cover cyber attacks and that a separate cyber policy is needed. A cyber policy is a different product from PI.
On intellectual property, some wordings may cover unintentional copyright or trademark infringement, while patent claims are commonly excluded. If you copy a licensed component into a client build and the licence owner objects, check whether that falls under your wording at all. For who owns the code you write, see the guide to IP ownership for freelancers.
When a client contract asks for proof of cover
PI is not legally required for IT freelancers in India. But enterprise clients, especially in the US and Europe, often ask for it in the master agreement or before the first statement of work. There is no authoritative minimum limit, so the figure in a client clause is their negotiating position, not a legal standard.
Read the insurance clause before you sign. Check the limit they name, whether they want to be listed on your policy, whether they ask for a certificate, and how long cover must continue after the project ends. If the clause asks for more than your budget allows, raise it in negotiation rather than signing and hoping. The contract guide for developers shows where this sits among the other clauses, and the freelance contract guide covers the full structure.
How to buy: what the proposal asks and what to ask a broker
You buy PI through an insurer or a broker, and you will fill in a proposal form. The usual documents are the proposal form, PAN or KYC, revenue and billing details, the services you offer and your claims history. You must disclose claims and circumstances you know about, and a missed disclosure can undermine a later claim.
Premium depends on your revenue, the mix of services, where your clients are, headcount, claims history, the limit you choose, the deductible and whether you use subcontractors. A higher deductible generally lowers the premium. Quotes vary too widely for one figure to help. Get written quotes for the same limit and deductible so you can compare them directly.
Ask early whether the insurer or broker quotes for sole proprietors, because some tech PI products are written for companies only. Also ask about the retroactive date, defence costs, data breach, IP, subcontractors and the notification window. If you hire help, the guide to hiring a subcontractor covers the contract side.
Keep the signed contract and the policy together
When a claim lands, you will need the signed contract, the scope, the change history and the policy. Rinto lets you send contracts for e-signature (a Pro feature), where the client signs in the browser, and you can link the contract to the project it kicks off. Rinto does not sell or advise on insurance, so use an insurer or broker for the policy itself. This post is general information, not financial, insurance or tax advice.
Frequently Asked Questions
Is professional indemnity insurance mandatory for freelance developers in India?
No law requires an IT freelancer in India to carry professional indemnity insurance. The pressure comes from clients instead. Brokers report that enterprise buyers, particularly in the US and Europe, often write an insurance requirement into the master services agreement or ask for proof before the first statement of work. There is no authoritative minimum limit, so the amount in a client's clause is a commercial demand that you can negotiate. Read that clause before signing and compare it with what you can afford to buy. If the client needs it, ask whether they will accept a lower limit or a later start date for cover.
What is a retroactive date in professional indemnity insurance?
The retroactive date is the earliest date from which your work is covered. In a claims-made policy, a claim is covered only if the work was done on or after that date and the claim is made in writing during the policy period. As an illustration, with a retroactive date of 1 January 2020, an error from December 2019 is not covered. When you renew or switch insurers, ask to keep the same retroactive date. A fresh date can leave earlier projects uncovered, and a lapse in cover can have a similar effect. Your policy schedule shows the date.
Does professional indemnity cover data breach for IT consultants?
It varies by policy. Some brokers describe PI that responds to breach of client information or loss of client data, and some policies add breach-response costs by extension. Other brokers say PI does not cover cyber attacks and that you may need a separate cyber policy, which is a different product. Fines and penalties under data protection and IT laws are commonly excluded, though a regulatory defence extension may exist. Do not assume cover. Ask the insurer or broker in writing whether your wording includes data breach, what the sub-limit is and what it excludes, and compare it with a cyber policy quote.
What is not covered under professional indemnity insurance?
Common exclusions include fraud and deliberate acts, contractual penalties and liquidated damages, contractual liability beyond what the law would impose anyway, bodily injury and property damage, hardware failure, war, and claims or circumstances known before you bought the policy. Fines and regulatory penalties are also commonly excluded, and patent claims are often excluded as well. The exact list differs by insurer, so read the full exclusions section of your wording rather than the brochure. A promise in a client contract, such as a delay penalty or an uptime guarantee, is a typical place where cover may not respond.
Can a freelancer buy professional indemnity insurance in India?
Retail pages for professional indemnity exist, but eligibility for an individual sole proprietor is not always spelled out, and some tech PI products are written for companies or organisations. Ask a broker or insurer directly whether they quote for sole proprietors before you spend time on a proposal. You buy through an insurer or a broker, fill in a proposal form and disclose your claims history and any known circumstances. Expect to give PAN or KYC details, revenue and billing figures and the services you offer. Get written quotes for the same limit and deductible so you can compare them.