Terms & Conditions Consent Log

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.

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.

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.

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.

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.

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.

The plugin hooks into the standard wp_login event (which covers both wp-login.php and the WooCommerce My Account login) and into the public registration events (register_new_user for the WP form and woocommerce_created_customer for the WC form). For each event, it inspects the submission $_POST for a ticked consent checkbox and, if one is present, writes a record with consent_type set to wp_login, wp_register, wc_login or wc_register accordingly.

A few specifics worth knowing:

• “Remember me” is excluded by design. It is an ePrivacy preference about extending the session cookie, not a GDPR Article 7.1 consent. Logging it would contaminate the audit trail with non-consent events. The exclusion is hard-coded.
• No checkbox in the form, no record. The plugin does not log “raw logins” — it only writes a row when there is something resembling an explicit consent checkbox to record. A login or registration without a consent field never produces a record.
• The detector is heuristic. Field names containing consent, gdpr, privacy, terms, acceptance, agreement, accept, rgpd, politica, privacidad or terminos (case-insensitive) are treated as the consent checkbox. If your GDPR / privacy plugin uses a different name, list it in Settings → Integrations → “Custom consent field names” (comma-separated, exact match).
• The injected checkbox option fills the WooCommerce gap. WooCommerce does not include a consent checkbox in its register form out of the box — only a privacy-policy paragraph. If your site does not run a separate GDPR plugin, enable “Add a required consent checkbox to the WooCommerce registration form” in Settings; the plugin will render the checkbox above the submit button and reject the registration if it is left unticked. The same option exists for the WP register form.
• Social logins are not captured on their own. Plugins like Nextend Social Login bypass the WP login form entirely (OAuth callback), so there is no submission $_POST for the detector to inspect. See the dedicated FAQ below for the two ways to cover them.
• Every ticked box is recorded, not just the first one. Registration forms often carry a required privacy checkbox plus an optional marketing or newsletter one. Both are written as separate records. The first one detected keeps the plain flow type (wp_register, wc_register…) so your existing records and saved filters stay comparable, and each additional one appends its field name, for example wp_register_newsletter_consent. That way an optional marketing consent, which is exactly the kind a regulator asks you to evidence separately, never gets swallowed by the required one.
• The stored consent_text comes from Settings. Paste in “Consent text for login / registration” the exact wording that the visitor sees on the form (whether it comes from your GDPR plugin or from the injected checkbox), so the record reflects what was actually shown. HTML is allowed in that field, so you can include a link to your privacy policy. If your forms do not all say the same thing, open “Use a different wording per form” underneath and fill in only the ones that differ; anything left empty falls back to the site-wide text.
• Creating an account at the WooCommerce checkout does not produce a registration record. The box ticked there is the order’s terms checkbox, which is already recorded as terms_and_privacy for the order itself, so counting it again as a registration consent would put something in your log the shopper never agreed to. If your checkout carries a separate consent checkbox of its own, that one is still recorded normally.

Not automatically, and that is on purpose. A social login ends in an OAuth callback coming back from Google, Facebook or Apple: there is no form submission, so there is no ticked checkbox anywhere in the request. A record written there would be a record of something nobody saw the visitor do, which is the opposite of what a consent log is for.

What you can do is hand the plugin the acceptance your social login plugin already collected. Enable “Also record sign-ups created by membership, course or custom registration forms” in Settings > Integrations (that is the option covering account creation outside the WP and WooCommerce forms) and use the tccl_consent_detection_payload filter, which lets you feed the detector a payload of your own for one specific flow:

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 );

Two things to respect. The key you add has to look like a consent field to the detector (any name containing consent, privacy, terms, gdpr…) or be listed in “Custom consent field names”. And $payload must come back untouched for every other context, or you will contaminate the detection of logins, comments and everything else running in the same request.

If your social login plugin fires its own “after register” hook and you would rather write the record yourself, call tccl_save_consent() from there instead, exactly like the custom-form example further down.

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.

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.

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.

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.

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.

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.

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.

In a custom indexed table called wp_tccl_consents (with your site prefix). 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.

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.

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.

Use Tools > Export Personal Data. The plugin registers an exporter that returns every consent record linked to the requested email.

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.

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.

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.

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.

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.