Skip to content
Kaagazo.
FreeLEGAL DRAFT

Privacy Policy Generator

Generate baseline website privacy terms compliant with general data rules and India's DPDP Act.

100% client-side. Nothing you type is uploaded or stored on a server.

Every website, app and WhatsApp business that collects a name, a phone number or an order address now has a legal duty to say what it does with them. The Digital Personal Data Protection Act, 2023 and the DPDP Rules notified in 2025 require a clear notice, a stated purpose, a way to withdraw consent and a grievance contact — and Google, Meta and payment gateways will not approve accounts without a privacy policy URL. This generator drafts a plain-language privacy policy tailored to what your business actually collects, aligned to the DPDP framework, with the standard sections international services expect, exported as HTML or text for your site.

What the DPDP Act expects from a small business

RequirementWhat your policy must do
NoticeTell people what personal data you collect and for what purpose, in clear language (and in the languages of the Eighth Schedule if you serve those users)
ConsentExplain how consent is given and withdrawn — cookie banner, form checkbox, WhatsApp opt-in
Purpose limitationUse data only for the stated purpose; delete it when the purpose ends
RightsAccess, correction, erasure and grievance redressal; nomination
Grievance officerA contact (name/role and email) and response timeline
SecurityA statement of reasonable safeguards
ChildrenVerifiable parental consent for under-18s; no tracking or targeted ads to children
Breach notificationTell affected users and the Data Protection Board

The Rules are being implemented in phases; the practical checklist for small websites, apps and WhatsApp businesses is in DPDP Rules 2025: the compliance checklist.

How to use the generator

  1. Enter your business name, website/app, contact email and the grievance officer.
  2. Tick what you collect: contact details, order and delivery data, payment (via a gateway), account logins, location, device/analytics, cookies, marketing preferences, employee/applicant data.
  3. Tick what you use: analytics (Google Analytics, Meta Pixel), payment gateways, courier partners, email/SMS/WhatsApp providers, cloud hosting; the policy names each category of "data processor".
  4. Set retention periods (order data for tax records: 8 years; marketing consent until withdrawn) and whether you serve children.
  5. Generate, read it once, edit the parts that are specific to you, and publish at /privacy-policy. Link it from the footer, forms, the cookie banner and your app-store listing.

Sections the generated policy contains

Who we are · What we collect and why · Legal basis (consent / legitimate uses) · Cookies and analytics · Sharing with processors · Retention · Security · Your rights and how to exercise them · Children · Cross-border transfers · Grievance officer and Data Protection Board · Changes to this policy.

Companion documents

A privacy policy sits with Terms & Conditions (the contract) and, for sellers, a Refund/Return Policy (mandatory under the Consumer Protection E-Commerce Rules). Marketing consent should also match what you say in messages — see TRAI's new anti-spam rules. If your site runs on WordPress, harden it as well: WordPress security checklist.

Frequently asked questions

Is a privacy policy mandatory in India?

Yes for anyone processing digital personal data under the DPDP Act, and it was already required under the IT (Reasonable Security Practices) Rules 2011. Payment gateways, app stores and ad platforms also require one.

Is the generated policy legally sufficient?

It covers the DPDP requirements and standard international sections for a typical small business. Businesses handling sensitive data at scale, health data, or children's data should have a lawyer review it.

Do I need a grievance officer?

Yes — the DPDP Act requires a contact for grievances and the IT Rules require a grievance officer for intermediaries. For a small business this can be the owner.

What about cookies?

State what cookies you use (essential, analytics, marketing) and how users can decline. Analytics and marketing cookies should load only after consent.

How often should I update it?

Whenever you add a new data use, tool or processor, and at least annually. Keep a "last updated" date at the top.