Cookies, Terms & Conditions Consent Log
Tamper-evident GDPR consent log: cookie banner decisions (Complianz, CookieYes, Moove), WooCommerce, CF7, WPForms, Gravity Forms, comments and login.
Safe pick
Yes — Cookies, Terms & Conditions Con… is a safe, well-maintained plugin to use in 2026. It runs on 200+ sites, is rated 5/5 and was last updated 5 days ago, and scores 80/100 on our health check.
- Actively developed — last update 5 days ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 235.1% vs the previous 30 days
- Small user base (200+ active installs)
- Very few reviews so far
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Cookies, Terms & Conditions… stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| consent-log | #6 |
| cookie consent | #56 |
| GDPR | >100 |
| terms and conditions | #7 |
| woocommerce | >100 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 3 reviews
About Cookies, Terms & Conditions Consent Log
From the official readme · v2.1.0Description
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_privacywhen that block requires a checkbox, or asterms_noticewhen 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-consentcheckbox (introduced in WP 4.9.6) when the visitor opts in. Stored ascomment_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_loginandwp_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_loginandwc_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_postmetabloat). - 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 DataandTools > Erase Personal Databoth 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_uninstallsetting (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
- Upload the plugin folder to
/wp-content/plugins/terms-conditions-consent-log/or install through Plugins > Add New. - Activate the plugin.
- Open the plugin admin page: Users > Consent log.
- 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. - (Optional, WooCommerce only) Override the checkbox text or add a pre-checkout informational paragraph. Leave them empty to keep the WooCommerce native text.
- Every accepted consent from any of the enabled sources will be logged automatically from now on.
Changelog
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.
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_consentfilter 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.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
FAQ
Cookies, Terms & Conditions Consent…: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Nov 17, 2026
Is Cookies, Terms & Conditions Con… free?
Yes. Cookies, Terms & Conditions Con… is free to download and use from the official WordPress.org plugin directory.
Is Cookies, Terms & Conditions Con… safe to use in 2026?
Yes — Cookies, Terms & Conditions Con… is a safe, well-maintained plugin to use in 2026. It runs on 200+ sites, is rated 5/5 and was last updated 5 days ago, and scores 80/100 on our health check.
How many websites use Cookies, Terms & Conditions Con…?
Cookies, Terms & Conditions Con… is active on 200+ WordPress websites and has been downloaded 3,937 times since it launched in May 2026. It was downloaded 1,612 times in the last 30 days.
Does Cookies, Terms & Conditions Con… work with WordPress 7.1?
Yes. The developer has tested Cookies, Terms & Conditions Con… up to WordPress 7.1.4, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Cookies, Terms & Conditions Con… need?
Cookies, Terms & Conditions Con… requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Cookies, Terms & Conditions Con… last updated?
The latest version, 2.1.0, was released on November 12, 2026 (5 days ago).
Who makes Cookies, Terms & Conditions Con…?
Cookies, Terms & Conditions Con… is developed and maintained by Fernando Tellado.
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card