Small business IT

EpiFive Website Privacy Kit: Open-Source DPDP Consent Banner and Privacy Toolkit

Set up a DPDP privacy notice in English and Hindi, a purpose-wise consent banner, consent records and a rights-request inbox for an Indian website with the free, self-hosted EpiFive Website Privacy Kit.

By EpiFive Editorial TeamReviewed/updated 12 min readHow we check our guides
On this page

EpiFive Website Privacy Kit is a free, open-source (MIT) web app that gives an Indian small business website the pieces the DPDP Rules ask for: an itemized privacy notice in English and Hindi, a consent banner with Accept, Reject and Choose of equal weight, consent records you can verify, a privacy page with a rights-request form, and a breach register with timers. You host it yourself, install it in about ten minutes plus a first build, and add the banner to your site with one script tag. It helps you meet DPDP requirements; it is not legal advice, and every legal text it produces is a draft pending lawyer review.

Who this guide is for

This guide is for owners and web developers of small Indian websites: clinics, coaching centers, online stores, agents and CA firms that collect names, phone numbers or emails through forms, WhatsApp opt-ins or analytics tags. By the end you will have the Free edition running, a published notice, the banner on your website with analytics held back until a visitor agrees, and a rights inbox that tracks due dates.

You need a server or computer with Node.js 24.7 or newer and about 2 GB of free memory for the first build, a domain with HTTPS for production, and an SMTP account for email. The source is at github.com/epifive/website-privacy-kit.

What the DPDP Rules ask of a small website from 13 May 2027

The Digital Personal Data Protection Rules, 2025 were published in the Gazette on 13 November 2025. Rule 1(4) brings Rules 3, 5 to 16, 22 and 23 into force eighteen months after publication, which is 13 May 2027. Rule 4, the registration of Consent Managers, started a year after publication. The points below are the ones a small website meets every day.

Notice before collection, itemized, in English or an Eighth Schedule language (s.5, Rule 3)

Section 5 of the Act requires a notice with every request for consent, and Section 5(3) says the Data Principal must have the option to read it in English or any language in the Eighth Schedule to the Constitution, which includes Hindi. Rule 3 adds that the notice must stand on its own, use clear and plain language, give "an itemised description of such personal data" and the specified purpose for each, and explain how to withdraw consent, use your rights and complain to the Board.

Section 6(4) gives the Data Principal the right to withdraw consent at any time, "with the ease of doing so being comparable to the ease with which such consent was given." For a website that means the same banner that took one click to accept needs a one-click way back, not an email to a support address.

Requests answered within your published period, never above 90 days (Rule 14)

Rule 14(3) asks every Data Fiduciary to prominently publish the period within which it responds to grievances, "a reasonable period not exceeding ninety days," and to put measures in place to keep to it. Rule 9 asks you to publish the business contact of a person who can answer questions about your processing, and to mention that contact in every response to a rights request.

Breaches: CERT-In 6 hours, the Board within 72 hours (Rule 7)

Rule 7 asks you to tell each affected person without delay, to tell the Data Protection Board without delay, and to send the Board a detailed report within seventy-two hours of becoming aware of the breach. Separately, the CERT-In Directions of 28 April 2022 require reporting the cyber incidents listed in their Annexure I to CERT-In within 6 hours of noticing them. The two clocks run in parallel, and not every breach is a reportable cyber incident.

Install the Free edition in 10 minutes

npm install, npm run setup, npm start

git clone https://github.com/epifive/website-privacy-kit.git
cd website-privacy-kit
npm install
npm run setup     # writes .env.local with a new master key and job secrets
npm start         # builds once (a few minutes), then serves http://localhost:3000

npm start runs a one-time production build if none exists yet. After a later git pull, run npm run build yourself before starting again. Copy WPK_MASTER_KEY from .env.local into your password manager straight away: it unlocks the encrypted contact details and attachments, and it must never be stored with your database backups.

The web installer: SQLite or MySQL, administrator, two-step verification

Open http://localhost:3000. The installer asks for the database: SQLite needs nothing set up, MySQL 8 needs a host, database, user and password. It then creates the administrator account. Administrators must use two-step verification, so scan the QR code with an authenticator app and save the recovery codes, which are shown only once.

For production, run the app under systemd or PM2 behind Caddy or Nginx with HTTPS and set SITE_URL=https://privacy.contoso.com. A Docker Compose file for SQLite and an override for MySQL are included. The reminders, breach timers and erasure tasks run when a cron job calls /api/v1/cron/run every 15 minutes, as described in scripts/cron.md in the repository.

To look around before entering real data, set DEMO_SEED=true in .env.local before running the installer with SQLite. An empty database then gets a sample clinic with a published notice, four rights requests, a breach and 45 days of consent records, all with fake names.

Set up your notice with the wizard

Sector preset, data items per purpose, contacts, response period

The dashboard's Notice wizard has four steps: Business (who you are and what you offer), Contact (who people can write to with questions and grievances, the Rule 9 contact), Purposes and Rights. Pick a sector preset (clinic, coaching center, online store, agent or CA firm) and the Purposes step suggests purposes such as booking appointments or sending offers on WhatsApp. Tick the ones that apply and list every data item you collect for each, because Rule 3 asks for an itemized description per purpose.

In the Rights step, Days to respond to requests defaults to 30 and the field does not accept more than 90. That number appears on your privacy page and drives the due dates in the inbox.

Publish: versions and SHA-256 fingerprints in English and Hindi

Review the English and Hindi drafts, then publish. Each publish creates an immutable notice version with a SHA-256 fingerprint per language, so you can later show exactly which text a visitor saw. The generated text is marked as a draft pending lawyer review; have a lawyer read it before you rely on it.

Add the banner to your website

One script tag (or the WordPress plugin)

Dashboard, then Websites, shows a one-line snippet for your site: a script tag that loads w.js from your own kit server with three attributes, which you paste into every page:

src        https://privacy.contoso.com/w.js
data-site  pk_live_...   (your site key)
async

The banner script is about 7 KB gzipped and shows Accept all, Reject all and Let me choose with equal weight, nothing pre-ticked, a preference center and an English/Hindi switch. Any element with data-wpk-open reopens the choices, which gives visitors the easy withdrawal Section 6(4) asks for.

On WordPress, use the free plugin from github.com/epifive/website-privacy-kit-wp (GPL-2.0-or-later). Under Settings, then Website Privacy Kit, paste your server address and the site key that starts with pk_, press Test connection, and list script handles to gate, for example google-analytics=analytics. The [wpk_privacy_link] and [wpk_privacy_choices] shortcodes add footer links to the privacy page and the choices.

Gate analytics and ad scripts with type="text/plain" data-wpk-purpose

A script with type="text/plain" is not run by the browser. The banner replaces it with a normal script only after the visitor grants every purpose listed in data-wpk-purpose. For the Google tag, keep its src and add two attributes to the same script tag:

type              text/plain
data-wpk-purpose  analytics
src               https://www.googletagmanager.com/gtag/js?id=G-XXXX   (unchanged)

Iframes work the same way with data-wpk-src instead of src. For Google tags, the banner also pushes a Google Consent Mode v2 default before anything else: ad_storage, ad_user_data, ad_personalization, analytics_storage and personalization_storage start as denied with wait_for_update set to 500 ms, and are updated from the visitor's choice. Google's documentation asks for exactly this order: the default command before any tag that sends measurement data.

To verify, open your site in a private window, open the browser's developer tools on the Network tab, and reload. Before you choose anything, no request should go to googletagmanager.com. Click Reject all and reload: still none. Click Accept all: the tag loads.

For forms that collect an email or phone number for marketing, call wpk.form(formEl, { purposes: ["marketing_email"], subject: "email" }). It adds unticked consent checkboxes for those purposes and records the choice with the email address when the form is sent. The WordPress plugin does the same for Contact Form 7 and WPForms.

Append-only log and hash chain, Verify chain, retention purge with checkpoints

Every grant, refusal and withdrawal is stored with the notice version, language, channel and page, under a pseudonymous visitor id. Records are append-only: database triggers refuse edits, and each site's records form a SHA-256 hash chain. Verify hash chain on the Consent log page recomputes the chain and reports a break if any record was changed or removed. When old records reach the end of their retention period, the purge deletes them and leaves an insert-only checkpoint, so the chain still verifies afterwards. Export CSV gives the log as a file.

The privacy hub and the rights inbox

Email-code verification, due dates, reply templates with your Rule 9 contact

Each organization gets a public privacy hub at /p/<your-org> with the current notice in English and Hindi, your rights, the withdraw page and a request form for access, correction, erasure, nomination and grievances. A request counts only after the person confirms a code sent to their email, which is why SMTP must be set up; Cloudflare Turnstile can be switched on against spam.

In Requests, every request shows its due date from your response period, with an on-track, due-soon or overdue badge, an assignee and notes. Reply templates in English and Hindi insert your Rule 9 contact, so every response carries it. Attachments are encrypted at rest.

Breaches and retention

The breach register starts clocks the moment you log an incident: the CERT-In 6-hour report (which you can mark not applicable when the incident is not an Annexure I cyber incident), the Board intimation without delay, the 72-hour detailed report and the notice to affected people. Each step has the Rule 7 text in English and Hindi and a Mark as sent button, and the incident prints as a Board report.

The retention schedule lists each data category with its period and legal reference, creates erasure tasks with sign-off, and keeps a one-year floor for logs. Rule 8(3) asks you to keep personal data, traffic data and logs of processing for at least one year from the processing. A vendor register records your processors and whether each has a contract. Children mode adds an age gate: an under-18 visitor's choices are not recorded and tracking stays off.

Exports: CSV registers and the JSON proof file

The Exports page downloads every register as CSV (consent log per site, rights requests, breaches, vendors, purposes, retention schedule, erasure tasks) and Download proof.json: every published notice version with its SHA-256 and the hash-chain check of each website's consent log in one file. Every export is written to the audit log. A paid Pro edition, described on the EpiFive Website Privacy Kit Pro page, adds multiple organizations, team roles, the parental-consent flow, an evidence pack and an API; this guide covers the free MIT edition only.

Section 2(g) of the Act defines a Consent Manager as "a person registered with the Board" that acts as a single point of contact for a Data Principal to give, manage, review and withdraw consent through an interoperable platform. The kit is none of that: it is a banner, consent records and an inbox that one business runs for its own websites, so that business stays the Data Fiduciary and stays responsible under Section 8. The software helps you meet DPDP requirements, but no tool can do that for you on its own, and the notices, banner wording and reply templates it generates are drafts pending lawyer review.

Before you go live, check this list:

  • Notice published in English and Hindi, read by a lawyer, linked from your footer.
  • Banner on every page, with analytics and ad tags gated and verified in the Network tab.
  • Privacy hub linked, SMTP working, a test request confirmed by email code.
  • Response period published, Rule 9 contact filled in.
  • Cron job running, master key stored away from backups, nightly encrypted backup set up.

See also

What we checked

  • Read Rules 1, 3, 7, 8, 9 and 14 in the DPDP Rules, 2025 PDF published by MeitY (Gazette G.S.R. 846(E), dated 13 November 2025) on 2026-11-20; Rule 1(4) gives eighteen months for Rules 3, 5 to 16, 22 and 23, which we counted to 13 May 2027.
  • Read Sections 2(g), 5(3) and 6(4) in the DPDP Act, 2023 PDF on meity.gov.in and quoted the withdrawal and Consent Manager wording from it.
  • Checked the 6-hour reporting rule and the Annexure I wording in the CERT-In Directions of 28 April 2022 on cert-in.org.in.
  • Compared the Consent Mode defaults in the banner source (src/widget/runtime/index.ts) with Google's consent mode guide: the five types start as denied with wait_for_update: 500 before any tag.
  • Checked the interface labels quoted here (Notice wizard steps, Days to respond to requests with its default of 30 and maximum of 90, Verify hash chain, Download proof.json) against the app's English message file and the dashboard screenshots in the repository.
  • Checked the WordPress steps and shortcodes against the plugin's readme.txt (version 1.0.0, tested up to WordPress 7.1).
  • Not checked: we did not run a fresh install for this article or confirm a live Google tag in a browser; the install steps follow the repository README as of today.

Last tested: 2026-11-20.

References

Questions people ask

When do the DPDP Rules apply to a small business website?

The DPDP Rules, 2025 were published in the Gazette on 13 November 2025. Rules 3 and 5 to 16, which cover notices, security safeguards, breach intimation, retention, contact details, children's data and Data Principal rights, come into force eighteen months later, which is 13 May 2027. Check the MeitY notification for the date that applies to you.

Is the EpiFive Website Privacy Kit a Consent Manager?

No. Under Section 2(g) of the DPDP Act a Consent Manager is a person registered with the Data Protection Board. The kit is a consent banner, consent records and a rights inbox that a business runs for its own websites, so the business remains the Data Fiduciary.

Does the kit work with WordPress?

Yes. The free EpiFive Website Privacy Kit plugin for WordPress (GPL-2.0-or-later) connects a WordPress site to your own kit server. It loads the banner, gates scripts by their handle, prints Google Consent Mode defaults and adds consent checkboxes to Contact Form 7 and WPForms forms.

Will the kit alone meet every DPDP requirement?

No. It helps you meet DPDP requirements by organizing notices, consent records, requests, breaches and retention, but its legal texts are drafts pending lawyer review and not legal advice. Have a lawyer check your notice and your processes.

EpiFive Website Privacy KitDPDP ActConsent bannerPrivacy noticeOpen sourceWordPress