Cookies, Terms & Conditions Consent Log

By Fernando Tellado

★ 5.0/5 (3 ratings)200+ active installationsVersion 2.1.0

Tamper-evident GDPR consent log: cookie banner decisions (Complianz, CookieYes, Moove), WooCommerce, CF7, WPForms, Gravity Forms, comments and login.

Description

WordPress stores consent as a yes. Nothing about when, from where, or which version of your terms was on screen. The day somebody disputes it, that yes is worth very little.

Cookies, Terms & Conditions Consent Log fills the gap on any acceptance checkbox of your site: WooCommerce checkout (classic and blocks), Contact Form 7, WPForms, Gravity Forms, Fluent Forms, comments, login and registration, or a stand-alone shortcode or block. It also records what each visitor chooses in the cookie banner you already run, Complianz, CookieYes and GDPR Cookie Compliance by Moove for now, without showing a banner of its own.

Every accepted consent writes a row to a dedicated indexed table with the timestamp, the IP, the user agent, the document version in force and the exact text shown, sealed with a SHA-256 hash so any later change is detectable. Exactly what Article 7.1 of the GDPR requires you to be able to demonstrate.

Filter, search, export to CSV, integrate with the native WordPress Privacy Tools and open a printable A4 certificate for any record, one click to save it as PDF.

Works with or without WooCommerce

The admin menu lives under Users → Consent log on every install, with or without WooCommerce. The WooCommerce-specific bits (checkout capture for both the classic and the block checkout, order metabox, “Consent” column on the orders list, optional consent line in the order emails) load only when WooCommerce is active; everything else (Records, Settings, CSV export, PDF certificate, Privacy Tools integration) works the same way on any WordPress site.

Sources of consent

  • Cookie banner decisions (auto when a supported banner is active): records what each visitor chooses in the cookie banner your site already runs, accept all, reject, pick categories or withdraw, in a table of its own. Complianz, CookieYes and GDPR Cookie Compliance by Moove are supported out of the box (CookieYes when it runs on its own, without its web app); any other banner can be covered with a snippet against the documented API. The plugin shows no banner and changes nothing in yours.
  • WooCommerce classic checkout (auto when WC is active): captures the native terms checkbox. Stored as terms_and_privacy.
  • WooCommerce block checkout (auto when WC is active): captures purchases made through the block checkout, which is what WooCommerce builds for new stores since version 8.3 and which the classic hooks never see. Stores the exact wording of the Terms and Conditions block. Recorded as terms_and_privacy when that block requires a checkbox, or as terms_notice when it only shows the informational paragraph WooCommerce ships by default, so acceptance by conduct is never logged as explicit consent. An opt-in toggle adds a required checkbox of the plugin’s own, validated server-side, for evidence that does not depend on browser-side validation. On by default.
  • Contact Form 7 (auto): detects [acceptance] fields automatically and the first email field of the form. Stored as cf7_form_{ID}, one type per form. No snippets required. On by default; turn off in Settings if it does not apply.
  • WPForms (auto): detects GDPR Agreement fields automatically and the first email field of the form. Stored as wpforms_form_{ID}, one type per form. Works with WPForms Lite and Pro. No snippets required. On by default; turn off in Settings if it does not apply.
  • Gravity Forms (auto): detects Consent fields automatically and the first email field of the form. Stored as gravityforms_form_{ID}, one type per form. No snippets required. On by default; turn off in Settings if it does not apply.
  • Fluent Forms (auto): detects GDPR Agreement and Terms & Conditions fields automatically and the first email field of the form. Stored as fluentforms_form_{ID}, one type per form. Works with Fluent Forms Lite and Pro. No snippets required. On by default; turn off in Settings if it does not apply.
  • WordPress comments (auto): logs the native wp-comment-cookies-consent checkbox (introduced in WP 4.9.6) when the visitor opts in. Stored as comment_consent. On by default; turn off in Settings if your site uses Disqus, Jetpack or another third-party comments system. Note that this native checkbox is a cookie preference, not consent to store the commenter’s data.
  • Privacy consent on comments and WooCommerce reviews (opt-in): adds a required privacy checkbox to the comment form, blocks the submission server-side if it is left unticked, and stores the acceptance as comment_privacy. This is the Article 7.1 consent to processing the name and email a commenter hands over, as opposed to the cookie preference above. WooCommerce product reviews share the comment form, so they are covered by the same option. Off by default.
  • Membership, course and custom sign-up forms (opt-in): captures accounts created outside the standard WordPress and WooCommerce forms, such as those from MemberPress, LearnDash, Ultimate Member or Paid Memberships Pro, and multisite sign-ups. Stored as user_register. Accounts created from the admin Users screen are never recorded. Off by default.
  • WordPress login and registration (auto): captures successful logins and registrations through wp-login.php when a consent checkbox is ticked on the form. Stored as wp_login and wp_register. Registration is on by default; login is off by default (a normal login form has no consent checkbox, so login only matters for re-consent flows). The “Remember me” checkbox is excluded by design (ePrivacy / cookie preference, not GDPR consent).
  • WooCommerce login and registration (auto when WC is active): same idea for the My Account page. Stored as wc_login and wc_register. Registration is on by default; login is off by default, like the WordPress rows above. An opt-in toggle can inject the consent checkbox into the WC register form, since WooCommerce does not ship one natively.
  • [tccl_consent_box] shortcode and Gutenberg block: drop a self-contained consent checkbox in any page, post or widget area as a stand-alone block. Submission posts to a REST endpoint and writes a record. Always available.

For anything else (Elementor Forms, Forminator, custom flows), call tccl_save_consent() from the appropriate hook.

Why a dedicated table

Storing thousands of consent records in wp_postmeta is wasteful and slow. The plugin uses its own indexed table and exposes a public function (tccl_save_consent) that you can call from anywhere to log additional consents in the same place.

Main features

  • Records timestamp UTC, IP, user agent, document version, source URL and full consent text per acceptance.
  • Custom database table with the right indexes (no wp_postmeta bloat).
  • Tamper-evident: each record is sealed with a SHA-256 hash. Any later change to the stored text is detected and reported as TAMPERED in the records list.
  • Sealed copies of your legal pages: every time your privacy policy, terms or refund page change, a copy of what they said is kept and sealed, and each record points to the copies in force when the consent was given.
  • Printable A4 certificate per record, with a built-in “Print / Save as PDF” button — the browser exports the certificate to PDF natively, no external library bundled.
  • Native Privacy Tools integration: Tools > Export Personal Data and Tools > Erase Personal Data both include consent records (erasure anonymises rather than deletes — the record itself is the lawful basis to keep it) and the cookie banner decisions of signed-in visitors (erasure deletes those, because the identifier is all that identifies them).
  • WooCommerce checkout texts are optional — leave them empty and the WooCommerce native text is shown to the customer and stored verbatim.
  • Automatic version bump when the text changes (suggests MAJOR.MINOR-YYYY-MM-DD).
  • Optional opt-out of IP and/or user agent tracking.
  • Configurable retention with a one-click anonymise button (records kept; PII scrubbed).
  • Configurable access by role: grant the consent log to extra roles (for example a DPO) from Settings → Access, without making them administrators.
  • One record per ticked box: a form with a required privacy checkbox and an optional marketing one produces two separate records, so the optional consent is evidenced on its own instead of being swallowed by the required one.
  • Per-form consent wording: the WordPress login, WordPress registration, WooCommerce login and WooCommerce registration forms can each store their own text, falling back to a site-wide default.
  • Live partial-match filters (email, order, date range, type, full-text search inside the accepted text) + filtered CSV export with UTF-8 BOM (opens cleanly in Excel).
  • (When WooCommerce is active) Order metabox with the consent summary, integrity badge and outdated-version indicator. “Consent” column on the orders list (legacy and HPOS) with a quick visual status. Optional consent line in the New order email (admin) and the order confirmation email (customer) — both off by default.
  • Optional delete_data_on_uninstall setting (off by default) — uninstalling does not destroy consent evidence unless you explicitly opt in.
  • HPOS (custom order tables) compatible.
  • Public tccl_save_consent() function to log consents from anywhere.

Translation ready

All strings use the terms-conditions-consent-log text domain. Translations are managed through translate.wordpress.org.

Support

Need private support or custom development?

Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need.

Need help or have suggestions?

Love the plugin? Please leave us a 5-star review and help spread the word!

About AyudaWP.com

We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

Installation

  1. Upload the plugin folder to /wp-content/plugins/terms-conditions-consent-log/ or install through Plugins > Add New.
  2. Activate the plugin.
  3. Open the plugin admin page: Users > Consent log.
  4. In the Settings tab, the integrations (WordPress comments, Contact Form 7, WPForms, Gravity Forms, Fluent Forms, WP/WooCommerce registration) are on by default to support GDPR Article 7.1 (proof of consent) — turn off any that do not apply to your site. Login capture is off by default and only needs turning on if your login form carries a consent checkbox (for example a re-consent prompt). The privacy checkbox for comments and reviews, and the capture of sign-ups from membership plugins, are also off by default: enable them if they apply to your site. You can also paste [tccl_consent_box] in any page or post.
  5. (Optional, WooCommerce only) Override the checkbox text or add a pre-checkout informational paragraph. Leave them empty to keep the WooCommerce native text.
  6. Every accepted consent from any of the enabled sources will be logged automatically from now on.

FAQ

Can I use the plugin without WooCommerce?

Yes. Activate it on any WordPress site and the Records, Settings, CSV export, PDF certificate and Privacy Tools integration all work the same way. The WooCommerce-specific bits (checkout capture, order metabox, order list column, order email line) only load when WooCommerce is active.

How do I keep a consent log for Complianz?

Nothing to set up. With Complianz active, the Cookies tab under Users > Consent log fills up on its own: one sealed row per decision, with the categories accepted, the version of the cookie policy on screen and the law that applied.

Check it in a private window: choose something in your banner and the row appears.

Complianz, CookieYes and Moove today, and other banners release by release. For any other, Settings > Cookie banner decisions has a custom source to switch on and feed from a snippet of your own.

How do I keep a consent log for CookieYes?

Nothing to set up while CookieYes runs on its own. With its banner on, the Cookies tab fills up with one sealed row per decision: the categories accepted, the law that applied and a sealed copy of the banner the visitor saw.

CookieYes keeps no version of its banner, so the plugin copies its texts, its buttons and its categories, and takes a new copy only when what the visitor reads changes.

Not recorded yet: CookieYes connected to its web app, where the banner comes from CookieYes’s servers, and its legacy version. Settings > Cookie banner connection says which case is yours.

How do I keep a consent log for GDPR Cookie Compliance (Moove)?

Nothing to set up. With Moove’s banner active, the Cookies tab fills up with one sealed row per decision: the categories accepted and a sealed copy of the banner the visitor saw.

Moove keeps no version of its banner, so the plugin copies its texts, its buttons and its categories, and takes a new copy only when what the visitor reads changes.

Each new copy also makes Moove ask every visitor again, so nobody keeps a consent given to a text that is gone. That includes a Moove update that changes the default texts your banner uses. Installing or updating this plugin asks nobody again. Purge your page cache after changing the banner. To turn it off: add_filter( 'tccl_moove_renew_consent', '__return_false' );

If you also run Moove’s Premium Consent Log, it keeps receiving every decision, and its own consent renewal takes precedence.

Does the plugin set a cookie?

One, tccl_cid, and only after a visitor decides something in your banner. Somebody who just reads your site is given nothing.

It holds a random identifier your server mints, scripts cannot read it, and it ties one visitor’s decisions together. Declare it as strictly necessary in your cookie policy.

How do I record a banner the plugin does not know yet?

Declare it with the tccl_cookie_sources filter, then send each decision from the browser:

add_filter( 'tccl_cookie_sources', function ( $sources ) {
    $sources['my_banner'] = array( 'label' => 'My banner', 'active' => true, 'version' => '3', 'law' => 'optin' );
    return $sources;
} );

window.tcclCookieConsent.record( 'my_banner', { action: 'accept_all', categories: [ 'functional' ], raw: {}, user_action: 'yes' } );

action is `accept_all`, `reject`, `custom` or `withdraw`; your server signs the version and the law. If your banner fires one event per category, use `queue( 'my_banner', fn )` and they collapse into one row. With no filter, tick "Let my own snippet record decisions" in Settings and use `custom`.

Nothing shows up in the Cookies tab. What now?

Look at Settings > Cookie banner connection: it says which banner is running, whether a decision has ever arrived and when the last one did. If it is running and nothing arrives, it has probably changed its script: say so in the support forum and it gets an updated adapter.

Do Export and Erase Personal Data cover cookie decisions?

The ones taken by someone signed in: those carry the user, so WordPress finds them from an email. Exporting returns them, erasing deletes them.

A decision taken without signing in has no email on it and cannot be found from one. Act on those by their identifier, in Users > Consent log > Cookies.

Erasing deletes instead of anonymising, like the retention period does: scrubbing the address would leave a row that still points at the same browser and proves nothing.

What does a cookie record prove, exactly?

That your site showed that version of that banner under that law, signed by your server, and that the row has not been touched since.

Not that a named person clicked: a browser reports the decision, as in every cookie consent log, paid ones included. It is why no row is written at all for a visitor who has decided nothing.

How do I capture consents from Contact Form 7?

Open Consent log > Settings > Integrations and tick “Log every CF7 form submission that ticks an [acceptance] field”. Then make sure your CF7 forms include an [acceptance] field, e.g.:

[acceptance privacy] I have read and agree to the privacy policy. [/acceptance]

The plugin uses the form ID as part of the consent_type (cf7_form_{ID}), so each form is filterable separately. The first email field of the form is used as the subject email. No snippets, no functions.php edits.

How do I capture consents from WPForms?

Open Consent log > Settings > Integrations and tick “Log every WPForms submission that ticks a GDPR Agreement field”. Then add a GDPR Agreement field to your form from the WPForms builder (Fancy Fields → GDPR Agreement) and edit its label to the exact wording you want recorded (e.g. “I have read and agree to the privacy policy.”).

The plugin uses the form ID as part of the consent_type (wpforms_form_{ID}), so each form is filterable separately. The first email field of the form is used as the subject email, and the GDPR Agreement field label is what gets stored as the accepted text. Works with WPForms Lite and Pro. No snippets, no functions.php edits.

How do I capture consents from Gravity Forms?

Open Consent log > Settings > Integrations and tick “Log every Gravity Forms submission that ticks a Consent field”. Then add a Consent field to your form from the Gravity Forms editor (Advanced Fields → Consent) and set its checkbox label to the exact wording you want recorded (e.g. “I have read and agree to the privacy policy.”).

The plugin uses the form ID as part of the consent_type (gravityforms_form_{ID}), so each form is filterable separately. The first email field of the form is used as the subject email, and the Consent field’s checkbox label is what gets stored as the accepted text. No snippets, no functions.php edits.

How do I capture consents from Fluent Forms?

Open Consent log > Settings > Integrations and tick “Log every Fluent Forms submission that ticks a GDPR Agreement or Terms & Conditions field”. Then add a GDPR Agreement or a Terms & Conditions field to your form from the Fluent Forms editor.

The plugin uses the form ID as part of the consent_type (fluentforms_form_{ID}), so each form is filterable separately. The first email field of the form is used as the subject email, and the field’s agreement text is what gets stored as the accepted text. Works with Fluent Forms Lite and Pro. No snippets, no functions.php edits.

One setting to check on the field itself: the Terms & Conditions field has a checkbox toggle, and it is what makes the field an act of consent. With it turned off, Fluent Forms shows your terms as plain text and renders no checkbox at all, so the visitor never accepts anything and there is nothing to record. Open the field in the Fluent Forms editor and make sure the checkbox is enabled.

I added a consent field but nothing is recorded. Why?

The most common reason is that the form has no email field. The consent log identifies the subject of every record by their email address, and the form integrations take it from the first email field of the form. Without one, an anonymous visitor cannot be identified and the submission is skipped on purpose, because a record that cannot be attributed to anybody is not evidence of anything.

If the person submitting the form is logged in, the plugin falls back to the email address on their WordPress profile, so forms behind a login (members areas, course enrolments) are recorded even with no email field on the form. For public forms, add an email field.

The other thing to check is that the consent field is really a consent field of the form builder, ticked by the visitor: an [acceptance] tag in Contact Form 7, a GDPR Agreement field in WPForms, a Consent field in Gravity Forms, or a GDPR Agreement or Terms & Conditions field in Fluent Forms. A plain checkbox or an HTML block with your terms in it is not detected.

How does the [tccl_consent_box] shortcode work?

It renders a self-contained consent checkbox + submit button, with optional email field for visitors who are not logged in. Submission posts to a REST endpoint that records the consent through tccl_save_consent(). Drop it in any page, post or widget area as a stand-alone block, e.g.:

[tccl_consent_box text="I have read and agree to the privacy policy." consent_type="newsletter_signup"]

The same functionality is also available as a Gutenberg block called “Consent box”.

Important: the shortcode renders its own <form> with a submit button, so it should NOT be nested inside another form builder’s form (Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Elementor Forms, etc.). If you embed it inside another form you will end up with two submit buttons and conflicting submit flows. For form builders, use the dedicated integration (Contact Form 7, WPForms, Gravity Forms and Fluent Forms are built in; for the rest, hook tccl_save_consent() from the relevant submission action — see the FAQ below).

Also: do NOT use this shortcode as a substitute for the cookie checkbox of a cookie/banner plugin (Complianz, CookieYes, Real Cookie Banner, etc.). The legal context is different — cookie banners cover ePrivacy/cookies, this consent log covers GDPR art. 7.1 specific consents to specific personal-data processing. Mixing them yields ambiguous evidence.

How are WordPress and WooCommerce login / registration consents logged?

When a login or registration form carries a ticked consent checkbox, the plugin writes a record: wp_login, wp_register, wc_login or wc_register. It listens to wp_login (wp-login.php and the WooCommerce My Account login), register_new_user and woocommerce_created_customer.

  • No checkbox, no record. A plain login or sign-up is never logged.
  • “Remember me” is never a consent. It is a cookie preference, not GDPR Article 7.1 consent, and is excluded by design.
  • How the checkbox is found. Any field whose name contains consent, gdpr, privacy, terms, acceptance, agreement, accept, rgpd, politica, privacidad or terminos. Other names go in Settings → Integrations → “Custom consent field names” (comma-separated, exact match).
  • WooCommerce has no checkbox of its own in its register form. Settings can add a required one, checked on the server, and the same for the WordPress form.
  • Every ticked box is its own record. The first keeps the plain type; each other one adds its field name, such as wp_register_newsletter_consent, so an optional marketing consent is evidenced on its own.
  • The stored text comes from Settings: “Consent text for login / registration”, HTML allowed. Paste the exact wording of the form. “Use a different wording per form” covers forms that say something else.
  • An account created at the WooCommerce checkout is not a registration record. The box ticked there is the order’s terms, already recorded as terms_and_privacy.
  • Social logins are not captured on their own: see the next question.

How do I record consent from social logins (Nextend Social Login and similar)?

Not on its own, and on purpose. A social login ends in an OAuth callback with no form and no ticked box, so a record there would describe something nobody saw the visitor do.

To record the acceptance your social login plugin already collected, enable “Also record sign-ups created by membership, course or custom registration forms” in Settings > Integrations and feed the detector with the tccl_consent_detection_payload filter:

add_filter( 'tccl_consent_detection_payload', function ( $payload, $context ) {
    if ( 'user_register' !== $context ) {
        return $payload; // Never touch the other flows.
    }
    // Read the acceptance wherever your social login plugin left it before
    // sending the visitor to the provider: a transient, a cookie, a session.
    if ( get_transient( 'my_social_consent' ) ) {
        $payload['privacy_consent'] = '1';
    }
    return $payload;
}, 10, 2 );
  • The key you add must look like a consent field (consent, privacy, terms, gdpr…) or be listed in “Custom consent field names”.
  • $payload must come back untouched for every other context, or it affects logins, comments and the rest of the request.
  • If your social login plugin has its own “after register” hook, you can call tccl_save_consent() from there instead, like the custom-form example further down.

Are WordPress comment opt-ins logged automatically?

Yes, by default. Only comments where the visitor ticks the native “Save my name, email, and website…” checkbox are recorded. You can opt out in Consent log > Settings > Integrations if your site uses Disqus, Jetpack Comments or any other third-party comments system where the native checkbox is not rendered.

Be aware of what that native checkbox actually is, though: it asks permission to leave a cookie so the browser remembers the commenter next time. That is an ePrivacy cookie preference, the same nature as the “Remember me” box on the login form, and it is not the GDPR Article 7.1 consent to processing the name and email the commenter is handing you. For that, use the separate option described in the next FAQ.

How do I record a real privacy consent on comments and product reviews?

Open Consent log > Settings > Integrations and tick “Add a required privacy checkbox to the comment form and record who accepts it”. From then on:

  • A privacy checkbox is rendered on the comment form, for both logged-out and logged-in visitors.
  • A comment submitted without ticking it is rejected on the server, not just in the browser, so it cannot be bypassed.
  • Each acceptance is stored as consent_type = comment_privacy, which keeps it clearly separate from the comment_consent cookie opt-in. Both can coexist on the same comment.
  • WooCommerce product reviews go through the very same comment form and hooks, so enabling the option covers them too. There is nothing extra to configure for a shop.

The wording lives in “Privacy text for comments” and accepts HTML, so you can link to your privacy policy. Whatever you write there is what gets stored with every record as the text the commenter agreed to. Leave the option off if you already run a privacy plugin that adds its own checkbox to the comment form, otherwise your visitors will see two.

My users register through MemberPress, LearnDash or another membership plugin. Are those sign-ups logged?

Only if you enable “Also record sign-ups created by membership, course or custom registration forms” in Consent log > Settings > Integrations.

The WordPress and WooCommerce options above hook the events those two fire on their own forms. A membership, LMS or custom registration plugin creates the account through the generic WordPress user-creation path instead, which those options never see. This setting adds a safety net over that generic path and stores the record as consent_type = user_register. It still requires a ticked consent checkbox in the submission, exactly like every other flow, and it never records an account you create yourself from Users > Add New, because no consent is given there.

It is off by default because most sites do not need it, and because the sign-up forms of those plugins vary enough that you will want to check the first record it produces before relying on it.

Does it work with the WooCommerce block checkout?

Yes, since 1.7.0. Both checkouts are supported, and the Settings screen tells you what your own checkout page will record.

There is one difference worth understanding, because it is a limitation of WooCommerce and not of this plugin. The checkbox in the native “Terms and Conditions” block is validated in the browser only: its value is never sent to the server, so no plugin can read it. What the plugin records depends on how that block is configured:

  • Block with “Require checkbox” enabled: recorded as terms_and_privacy, the same type the classic checkout uses. The order could not have been placed without ticking the box, so acceptance is certain, and the stored text is the exact wording of the block.
  • Block without a checkbox (the WooCommerce default): the block only shows an informational paragraph, so the shopper accepted by proceeding rather than by an affirmative act. That is contractually meaningful but it is not the explicit consent of Article 7.1, so it is recorded as terms_notice to keep the two apart in your evidence trail.
  • No Terms and Conditions block on the page: nothing is recorded for the purchase, because nothing was shown.

If you want evidence the server itself validated, turn on “Inject required checkbox” under Settings > Block checkout. It adds its own required checkbox through the official WooCommerce additional-checkout-fields API, so the value travels with the request, is validated server-side and is stored on the order. WooCommerce renders those labels as plain text, so that checkbox cannot contain links; keep the Terms and Conditions block on the page for the linked wording.

Why does my block checkout record “terms_notice” instead of “terms_and_privacy”?

Because your Terms and Conditions block has no checkbox, which is how WooCommerce ships it. The customer was shown a sentence saying that continuing implies acceptance, and never ticked anything.

The plugin could record that as ordinary consent, but it would be putting an affirmative act in your log that never happened, and a consent log that overstates its evidence is worse than one that does not.

This is not the plugin telling you your shop is non-compliant, and the distinction is not a warning. Processing an order rests on performing the contract (GDPR Article 6.1.b), not on consent, and accepting the terms of sale by placing the order is contractually meaningful in its own right. Whether you need an affirmative act on top of that depends on what you ask your customers to agree to, and that is your call, not the plugin’s. What the plugin does is refuse to file the two under the same name.

If you do want the explicit tick, enable “Require checkbox” on that block in the editor, or turn on the injected checkbox in Settings. Records already stored as terms_notice keep that type: they are the accurate account of what those customers actually saw.

My site is not in English. Will the record match what my customers read?

Only if you write your own wording into the Terms and Conditions block, which is what the Settings screen recommends when it detects this situation.

The reason is a limitation of where WooCommerce keeps that text. The default wording of the block is assembled in JavaScript and its translations live in WooCommerce’s script-translation files, which PHP cannot read, so no plugin can fetch the exact sentence your visitor was shown. This plugin therefore reproduces the same sentence under its own text domain. In English both are the same string. In any other language the stored text is this plugin’s translation of that sentence, which may differ word for word from WooCommerce’s.

Anything you type into the block is stored verbatim, in any language, with no translation involved. For a consent log that is the difference between a transcription and a reconstruction, so it is worth the two minutes in the editor. The same applies to the injected checkbox: its text comes from your own setting.

The “Terms checkbox text” setting does nothing on my checkout. Why?

That setting, and the pre-checkout informational text next to it, only apply to the classic checkout. In the block checkout the wording lives in the Terms and Conditions block, which you edit on the checkout page itself.

This is deliberate. Those records store what the block shows, not what you type in Settings, because the point of the log is to prove what the customer read.

Does a record prove what my terms said that day?

Yes, for records taken from now on. The plugin keeps a sealed copy of your legal pages every time they change, and each record points to the copies in force when the consent was given.

  • Copied without any setup: the privacy policy page of the site, and the WooCommerce terms and refund pages.
  • Anything else, such as a cookie policy or a legal notice: add it in Settings > Documents in force.
  • Each copy holds the text as it is read, so pages built with a shortcode or a block are covered.
  • The certificate of a record lists its documents and says whether they have changed since.
  • Private pages and pages behind a password are not copied.

Older records have no copies. WordPress revisions are not a substitute: they can be limited or switched off.

The consent box says the form is out of date. Why?

The page was rendered before the plugin was updated and is being served from a page cache. Purge the cache and it will work again.

The form carries a payload signed by the server with the exact text it shows, and the plugin only records what that payload says. A form with no payload, or with one that has been altered, is rejected.

The consent box says it cannot record a consent here. Why?

You are looking at it in a preview, a draft or the editor, and you cannot publish posts.

  • Whoever edits a draft decides its wording, so the form there is not signed and its button is disabled.
  • It works on the published page.
  • Users who can publish see it working in previews too.

The consent box fails for visitors who are not logged in. Why?

Something is closing the WordPress REST API to anonymous visitors, usually a security plugin set to allow it only for logged-in users. The consent box sends its form to /wp-json/tccl/v1/consent, so that route has to stay public. Allow the tccl/v1 namespace in that plugin, or switch it to a mode that only blocks the routes you choose.

Where is the data stored?

In a custom indexed table called wp_tccl_consents (with your site prefix). The sealed copies of your legal pages live in a second table, wp_tccl_snapshots. When WooCommerce is active, each order also gets three meta entries (_tccl_terms_accepted, _tccl_terms_version, _tccl_recorded_at) so the order edit screen can show the summary without querying the table.

How do I bump the document version when I change my terms?

Edit the version field in Consent log > Settings, or simply check “Bump version on save”. The plugin can also bump it automatically if it detects the checkbox text has changed but the version field has not.

Three things to keep in mind:

  1. The version string in Settings must match the version label of your terms document character by character (e.g. 1.1-2026-05-17). It is a free-text identifier and the plugin just compares strings, so a trailing space or a different separator will be treated as a different version.
  2. Once you bump the version, every record stored under the previous version is automatically flagged as “Outdated” in the records list. This is on purpose — it is the GDPR audit trail showing which exact wording each subject accepted at that moment. “Outdated” is a feature, not a bug.
  3. Do NOT delete or “clean up” Outdated records. They are the legal proof of consent for the version that was in force when the subject accepted it. If the user retires the terms and a regulator later asks for evidence, those rows are what you show them.

How do I delete or anonymise data for a specific customer?

Use the WordPress native Tools > Erase Personal Data screen. The plugin registers an eraser that anonymises records linked to the requested email (it does not delete them, since the record itself is the lawful basis to keep the proof of consent). You can also anonymise filtered records from the Records tab.

How do I export a customer’s consent history?

Use Tools > Export Personal Data. The plugin registers an exporter that returns every consent record linked to the requested email, and the documents in force when each one was given, with their text.

Will an uninstall destroy my data?

Only if you explicitly opt in. The setting “Delete all data on uninstall” is off by default. Even if you uninstall accidentally, your consent evidence will survive.

If you need to clean up a handful of test rows you generated while configuring the plugin (and you do not yet have the upcoming bulk-delete UI), you can remove them with a direct SQL statement against the consent table, e.g.:

DELETE FROM wp_tccl_consents WHERE id IN (1, 2, 3);

Replace wp_ with your site’s actual table prefix. This is an escape hatch for legitimate clean-up after a misconfigured form; it is not a recommended day-to-day flow — to handle real subject requests, use Tools > Erase Personal Data (anonymises) instead.

How do I capture consents from Elementor Forms, Forminator or any other source?

Contact Form 7, WPForms, Gravity Forms and Fluent Forms are captured automatically once you enable their toggle in Settings > Integrations; no code is needed for those four. For any other source, call the public tccl_save_consent() function from that plugin’s submission hook. Always read the document version from the plugin setting (tccl_get_setting( 'consent_version', '1.0' )) so all records line up with the current version in Settings — if you hardcode a date that differs from the one in Settings, every record will be flagged as “Outdated” forever.

add_action( 'the_submission_hook_of_your_form_plugin', function ( $submission ) {
    tccl_save_consent( array(
        'email'           => sanitize_email( $submission['email'] ), // however your plugin exposes the email
        'consent_type'    => 'my_custom_form',
        'consent_version' => tccl_get_setting( 'consent_version', '1.0' ),
        'consent_text'    => 'I have read and agree to the privacy policy.',
        'consent_value'   => 1,
    ) );
} );

Common hooks to adapt this to: elementor_pro/forms/new_record, forminator_custom_form_after_submission, user_register. Adjust the callback signature and how you read the email and the acceptance to each plugin’s documented arguments.

Does the IP detection work behind Cloudflare or other reverse proxies?

The plugin reads REMOTE_ADDR only and does not trust forwarded headers, which can be spoofed without a verified proxy. If your hosting puts the proxy IP in REMOTE_ADDR instead of the real client IP, all entries will record the proxy IP. Most WordPress-friendly hostings pass the real IP correctly.

What does “Tamper-evident” mean here?

When a consent is written, the plugin computes a SHA-256 hash of the exact accepted text and stores it alongside the record. On every read, the stored hash is compared against a freshly computed one — any difference is reported as TAMPERED in the records list, the order metabox and the certificate view. This is a cryptographic integrity check, not an electronic signature.

Is the certificate a real PDF?

The plugin renders a one-page A4 view with print-optimised CSS and a “Print / Save as PDF” button. Modern browsers (Chrome, Safari, Firefox, Edge) export that view to a real PDF natively — same fidelity as a server-side library would produce, with the added benefit that it respects your site’s language and fonts. No external library bundled, so the plugin stays small.

To be clear: the plugin does NOT store any PDFs on disk and does NOT create an uploads folder of its own. The certificate is generated on demand as HTML each time you open it, and only becomes a PDF if you (or the customer) clicks “Print / Save as PDF” in the browser. There is nothing to clean up on the server. If the site has a Site Icon defined in Settings > General (the same option block themes and classic themes share), it is shown in the certificate header next to the site name — including on certificates of consents recorded before this version, since the icon is added at render time, not at storage time.

Screenshots

Changelog

2.1.0

Records what your visitors choose in GDPR Cookie Compliance by Moove, with a sealed copy of the banner they saw, and has Moove ask again when what that banner says changes.

  • New: GDPR Cookie Compliance by Moove is recorded out of the box. Accept all, reject, choose categories or withdraw, from the notice, the settings panel or a link that opens it: each decision becomes one sealed row in the Cookies tab, with its categories in the same names as every other banner and the consent type Moove applies. Moove’s Accept also says yes to the Premium categories a site without Premium does not show; those stay in the banner’s own state and are not counted as accepted. A rejection is recorded as well on a site that tells Moove not to keep a cookie for it. If the page loses the list of categories the banner offers, for example to a script optimiser, nothing is recorded rather than a wrong decision.
  • New: a sealed copy of the Moove banner stands for the version of what was shown. Moove keeps no version of its own, so the plugin copies the notice, the buttons switched on, what the close button does when it decides something, and each category with whether it is on before anybody consents, and takes a new copy only when what the visitor reads changes. Only the settings that make up that text go into the copy: never the scripts a site pastes into each Moove category.
  • New: when what the Moove banner says changes, Moove asks every visitor again. Each new copy hands Moove a higher consent version, and Moove drops the decisions taken on an older one and shows the banner. A Moove update that changes the default texts the banner uses counts as a change too. The first copy of each language is version 1, which is how Moove reads the decisions it already had, so installing or updating the plugin asks nobody again. A cached page keeps the previous version until the cache is purged. A version set by Moove’s Premium is left alone, and the tccl_moove_renew_consent filter switches it off.
  • Improved: Moove’s Premium Consent Log keeps working next to this plugin. Whether it loads before or after, it keeps receiving every decision.
  • Fix: the CookieYes banner preview opened with an encoded address, such as ?cky_preview=%74rue, could be recorded as a decision. It is now read the way CookieYes reads it.
  • Fix: two calls into CookieYes that were not guarded could stop every page with a fatal error if a later CookieYes changed them. CookieYes now stops being recorded instead, and Settings says so.

For older changelog entries, please check the changelog.txt file.