How do I write terms and conditions for my website or business?
Write terms that say who may use the service and how, what you charge and refund, who owns the content and code, what you are not liable for, how either side can end it, and which Indian law and courts settle a dispute; a free generator gives you the first draft. If you sell to consumers online, the Consumer Protection (E-Commerce) Rules 2020 add specifics: show your return, refund, exchange, warranty, delivery and payment terms and a grievance mechanism before purchase, acknowledge a complaint within 48 hours and resolve it within one month. Have users accept the terms with a clear click or checkbox, and keep the privacy policy as its own document. Termly's terms generator gives one policy free, and Shopify's free generator writes terms, refund and privacy policies for a store. A B2B SaaS deal needs a signed master services agreement with service levels and a data processing agreement, not website terms.
The Ministry of Consumer Affairs' release on the e-commerce rules: what every e-commerce entity must show before purchase and how fast it must handle complaints.
This is the exact question, answered in Indian law. It draws the line most founders get wrong: a Privacy Policy is mandatory the moment you collect any personal data (name, email, phone, location) under the DPDP Rules 2025, while a Terms of Service is strongly recommended but not strictly mandated. It gives a per-surface decision tree (mobile app: both mandatory before launch; website with a contact form: policy mandatory now) plus the DPDP timeline to May 2027 and the up-to Rs 250 crore penalty, so you know what to do this week versus later.
From
Growth Gurukulby Growth Gurukul editorial12 min read
Privacy Policy is legally mandatory if you collect any personal data; Terms of Service is strongly recommended, so ship both before an app-store launch.
DPDP Rules 2025 (effective November 2025) drive the requirement, with a phased runway to May 2027 and penalties up to Rs 250 crore per breach.
Use the decision tree by surface (app vs website vs contact form) to decide what is required at launch versus what can wait for legal review.
Once onboarding clears, the enterprise legal team hands you a contract, and a solo founder who negotiates blind gets buried in unlimited liability and a payment term that starves cashflow. This is a working lawyer's breakdown of the five documents that make up an Indian enterprise deal (MSA, Order Form, DPA under the DPDP Act 2023, SLA, security terms) and the exact clauses to hold your line on. Its most useful move: cap your liability at fees paid over a reasonable period instead of accepting open-ended exposure, and keep IP clean with platform-yours, data-theirs, framed under the Indian Contract Act and IT Act so it reads as an equal, not a scared vendor.
An Indian enterprise deal is five documents, not one: MSA, Order Form, DPA (DPDP Act 2023), SLA, and security terms, know which one carries which risk
Cap liability at fees paid over a defined period, unlimited liability is the clause that quietly ends solo founders, and it is negotiable
Keep IP explicit (you own the platform, they own their data) and make payment terms and GST/TDS treatment transparent so procurement has no reason to stall