Confidr

Confidr helps a WooCommerce store meet the Digital Personal Data Protection Act, 2023 (DPDPA) — India’s data protection law. It is built specifically for this Act, not adapted from a GDPR plugin, which matters: several GDPR-standard patterns (a “legitimate interest” balancing test, a sensitive-data tier, a data portability right, generic 30-day deadlines) simply don’t exist under DPDPA, and a plugin that assumes they do will mislead you.

Everything lives inside your own WordPress/MySQL install. No external service holds your customer data, your consent records, or your audit trail. The only outbound request this plugin ever makes is a narrow, disclosed, opt-in exception: an AI-assisted notice/policy drafting feature (off by default, uses your own API key).

Every feature in this plugin is free — there is no paid tier.

What it does

• Cache-safe consent banner — client-side decision logic, safe behind any full-page cache, with a language switcher (English + Hindi shipped).

• Client-side + server-side script blocking — a maintained tracker signature library plus a wrapper snippet for anything it can’t reach, with honest UI about the limits of automatic blocking.

• First-party checkout & registration consent — classic and block checkout, unticked by default.

• Staff-entered consent for phone/WhatsApp orders taken directly in wp-admin (S3(a)(ii)).

• Rights Centre — access, correct, complete, update, erase, withdraw, nominate, and an elevated grievance path that’s the statutory pre-Board shield (S13(3)).

• Native WordPress privacy tools integration — plugs into Tools → Export/Erase Personal Data rather than reinventing it.

• Retention engine implementing the real S8(8)/S8(11) dual test, correctly scoped to Third Schedule-class fiduciaries — never a fabricated timer for everyone else.

• Withdrawal propagation to your registered processors, correctly scoped so it never touches fulfilment of orders already placed and paid for (S6(5)).

• Breach Console — record, scope, notify principals and prepare the Board report, plus a penalty-mitigation export (S32/S33(2)).

• Command Center — searchable customer consent state, force-block, off-platform opt-out recording.

• Re-consent Campaign for customers who pre-date this plugin (S5(2)) — a notice duty, never a forced fresh opt-in.

• Processor Register with the S8(3) proactive data-quality duty surfaced for fiduciary-role and decision-affecting entries.

• Notice & privacy policy generator — static templates by default, optional AI-assisted drafting, always an editable draft.

• Audit trail for every sensitive action, with a 12-month retention floor that survives customer erasure as a non-identifiable stub.

• Setup wizard that ends with a real, unauthenticated check that your banner is actually live — not just configured.

What this plugin does not do

Being honest about scope is part of the product. Confidr deliberately does not:

• Adjudicate whether an incident is a notifiable breach, or transmit anything to the Data Protection Board on your behalf.

• Claim to block every tracking script automatically — a hand-pasted script needs the wrapper snippet.

• Implement GDPR concepts that don’t exist under DPDPA (data portability, a sensitive-data tier, “legitimate interest”).

• Apply a Significant Data Fiduciary duty, an exemption, or a Third Schedule threshold automatically — these depend on notifications only you (with counsel) can confirm apply to you.

• Operate as a Consent Manager, or hold your customer data anywhere but your own database.

Not legal advice

Nothing in this plugin, its generated content, or its documentation constitutes legal advice. Have India-based DPDPA counsel review your actual notice, policy, and processes before you rely on them.

External services

This plugin does not send customer data, consent records, or audit logs to any third party. All of that stays in your WordPress database.

Optional AI notice drafting (off by default)

com/v1/chat/completions ). That prompt contains only the business details you typed into Confidr (store name, contact, declared purposes, processor register summaries). It never includes customer emails, order data, or consent log rows.

The call happens only when you click generate on the Notice & Policy Generator screen. It does not run on page views.

This is provided by OpenAI. com/policies/how-your-data-is-used-to-improve-model-performance/

0 includes a core AI Client. 2, so the optional drafter uses your own OpenAI key until the minimum WordPress version can be raised.

Tracker signature list (no outbound call)

net) so it can block those scripts on your storefront until consent is given. Matching happens in your WordPress install. The plugin does not contact Google, Meta, or those CDNs for this purpose.

Banner live-check

During setup, the wizard fetches your own site’s front page ( home_url ) to confirm the banner HTML is present. That request stays on your server.