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.