FAQ and troubleshooting

General

Is there a Pro version?

Yes. Kavin DPDP Cookie Consent Pro is a separate, paid plugin that adds 22 banner languages, a privacy notice page, a privacy request form and re-notice emails. The free plugin does not connect to any Pro service and works fully without it. See Getting started.

Does the banner work with page caching?

Yes. The page is always sent with tags held back, and the choice is read in the visitor's browser, so a cached page never has tracking switched on.

Which Google Consent Mode is used?

Basic mode. Google tags are not loaded at all until the visitor allows them, so nothing reaches Google before consent. See Tracking tools.

My site has no analytics or ads. Will a banner appear?

No. With no tracking tools configured or found, no banner is shown. The form notice shortcode still works.

Where is the consent record kept?

In a table in your WordPress database. The IP address is stored only as a one-way hash. See Consent records.

Is anything sent to Kavin Studios?

No. Tracking tools load only when you enter their ID (or Site Kit already holds it), and only after the visitor allows that tool's category. Nothing is sent to Kavin Studios at any time.

Is this legal advice?

No. The plugin helps you meet the DPDP Act's consent requirements. Your privacy notice must still describe what your site actually does.

The banner does not show

Check these in order:

1. You already made a choice. The banner does not show again once you have chosen. Open your site in a private window, or use preview the banner on the Banner and notice tab.
2. No tracking tools are set up or found. Enter an ID on the Tracking tools tab, or click Scan my site now. With nothing to ask about, there is no banner.
3. A category is missing. A category with no tools on your site is left out of the banner. Add or scan for a tool in that category.

A tag still runs, or runs twice

• Hold back known tracking tags until the visitor agrees must be on for tags added by your theme or other plugins. Tags the plugin does not recognise are not held back.
• Google AdSense is never held back. It runs in limited-ads mode until the visitor allows Advertising.
• If you enter an ID on the Tracking tools tab and the same tag is also added by your theme or another plugin, visits are counted twice. The field shows a warning. Remove one of them.

The site scan says it could not open my pages

Your host may block the site from loading its own pages. Visit your home page, a product page and the checkout in a private window instead. Tags found there appear under Found on your site. Pages are also checked as visitors browse.

My ID was not saved

The message "Not saved, because the format looks wrong" means the ID does not match its tool's format. Check the example under each box. For example, a Google Analytics ID starts with G-, a Google Ads ID starts with AW-, and a Meta Pixel ID is numbers only.

The page reloads when a visitor withdraws

This is expected. Scripts that already ran cannot be unloaded, so the page reloads with only what is still allowed. The withdrawn category's cookies are deleted.

I changed my notice. How do I ask everyone again?

On the Banner and notice tab, click Raise version and ask again. Earlier choices no longer count, and every visitor sees the banner again.

What happens to my data if I delete the plugin?

Deleting Kavin DPDP Cookie Consent from the Plugins screen removes its settings, the list of found tags and the consent records table. Download your records as CSV first. Deleting Pro removes Pro's settings and the re-notice list.

Pro

Pro says it is not licensed

Pro's features stay off until a licence is active. Activate your licence under Kavin Studios → Account. Updates then arrive in the Plugins screen.

Pro says it needs the free plugin

Pro is an add-on. Install and activate Kavin DPDP Cookie Consent, and Pro starts working.

Re-notice emails or request replies are not sent

Both go through your site's normal email sending. Check that your site can send email, for example with Kavin SMTP. A failed request reply is noted in the request's history.

A reply to a request was not sent

A reply that is empty, or still has a "[Fill in: ...]" gap, is not sent. Write that part, then send again. See Privacy requests.

Are the translations ready to use?

The 21 translations beyond English and Hindi ship as drafts. Have a native speaker check each one before relying on it. You can correct any line. See Languages.