Ayuda WordPress

Fernando Tellado

<p>Article 7.1 of the GDPR demands more than a boolean: the defensible consent record needs the timestamp, the IP, the user agent, the document version in force at that moment and the exact text the user was shown.</p>
<p>Terms & Conditions Consent Log fills that gap for any acceptance checkbox on your site, with or without WooCommerce. Every accepted consent — at the WooCommerce checkout, in a Contact Form 7 form, in a WPForms form, in the WordPress comments form, on the WordPress / WooCommerce login or registration form, or in a stand-alone shortcode/block — writes a row to a dedicated indexed table, sealed with a SHA-256 hash of the accepted text so any later change is detectable. From a clean admin screen you can filter, search, export to CSV, integrate with the native WordPress Privacy Tools, and open a one-page printable A4 certificate per record (your browser saves it as PDF in one click).</p>
<h4>Works with or without WooCommerce</h4>
<p>The admin menu lives under Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> Consent log on every install, with or without WooCommerce. The WooCommerce-specific bits (checkout capture, 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.</p>
<h4>Sources of consent</h4>
<ul>
<li><strong>WooCommerce checkout</strong> (auto when WC is active): captures the native terms checkbox.</li>
<li><strong>Contact Form 7</strong> (auto): detects [acceptance] fields automatically and the first email field of the form. Stored as <code>cf7_form_{ID}</code>, one type per form. No snippets required. On by default; turn off in Settings if it does not apply.</li>
<li><strong>WPForms</strong> (auto): detects GDPR Agreement fields automatically and the first email field of the form. Stored as <code>wpforms_form_{ID}</code>, 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.</li>
<li><strong>WordPress comments</strong> (auto): logs the native <code>wp-comment-cookies-consent</code> checkbox (introduced in WP 4.9.6) when the visitor opts in. Stored as <code>comment_consent</code>. On by default; turn off in Settings if your site uses Disqus, Jetpack or another third-party comments system.</li>
<li><strong>WordPress login and registration</strong> (auto): captures successful logins and registrations through wp-login.php when a consent checkbox is ticked on the form. Stored as <code>wp_login</code> and <code>wp_register</code>. 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).</li>
<li><strong>WooCommerce login and registration</strong> (auto when WC is active): same idea for the My Account page. Stored as <code>wc_login</code> and <code>wc_register</code>. 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.</li>
<li><strong><code>[tccl_consent_box]</code> shortcode and Gutenberg block</strong>: 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.</li>
</ul>
<p>For anything else (Gravity Forms, Fluent Forms, Elementor Forms, Forminator, custom flows), call <code>tccl_save_consent()</code> from the appropriate hook.</p>
<h4>Why a dedicated table</h4>
<p>Storing thousands of consent records in <code>wp_postmeta</code> is wasteful and slow. The plugin uses its own indexed table and exposes a public function (<code>tccl_save_consent</code>) that you can call from anywhere to log additional consents in the same place.</p>
<h4>Main features</h4>
<ul>
<li>Records timestamp UTC, IP, user agent, document version, source URL and full consent text per acceptance.</li>
<li>Custom database table with the right indexes (no <code>wp_postmeta</code> bloat).</li>
<li><strong>Tamper-evident</strong>: 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.</li>
<li><strong>Printable A4 certificate</strong> per record, with a built-in “Print / Save as PDF” button — the browser exports the certificate to PDF natively, no external library bundled.</li>
<li><strong>Native Privacy Tools integration</strong>: <code>Tools > Export Personal Data</code> and <code>Tools > Erase Personal Data</code> both include consent records (erasure anonymises rather than deletes — the record itself is the lawful basis to keep it).</li>
<li>WooCommerce checkout texts are <strong>optional</strong> — leave them empty and the WooCommerce native text is shown to the customer and stored verbatim.</li>
<li>Automatic version bump when the text changes (suggests <code>MAJOR.MINOR-YYYY-MM-DD</code>).</li>
<li>Optional opt-out of IP and/or user agent tracking.</li>
<li>Configurable retention with a one-click anonymise button (records kept; PII scrubbed).</li>
<li>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).</li>
<li>(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.</li>
<li>Optional <code>delete_data_on_uninstall</code> setting (off by default) — uninstalling does not destroy consent evidence unless you explicitly opt in.</li>
<li>HPOS (custom order tables) compatible.</li>
<li>Public <code>tccl_save_consent()</code> function to log consents from anywhere.</li>
</ul>
<h4>Translation ready</h4>
<p>All strings use the <code>terms-conditions-consent-log</code> text domain. Translations are managed through translate.wordpress.org.</p>
<h3>Support</h3>
<p>Need private support or custom development?</p>
<p>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 <a href="mailto:terms-conditions-consent-log@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.</p>
<p>Need help or have suggestions?</p>
<ul>
<li><a href="https://servicios.ayudawp.com" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/terms-conditions-consent-log/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
<p>Love the plugin? Please leave us a 5-star review and help spread the word!</p>
<h3>About AyudaWP.com</h3>
<p>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.</p>


Terms & Conditions Consent Log


Errata: había puesto la reseña para otro plugin en el lugar equivocado y no sé como borrarla 😅


El plugin que permite cumplir al 100%

Tamper-evident GDPR consent log: WooCommerce, CF7, WPForms, WP comments, WP/WC login & registration, and a [tccl_consent_box] shortcode.

Terms & Conditions Consent Log vs Complianz – GDPR/CCPA Cookie Consent