getterms

<p>The GetTerms plugin helps you implement cookie consent management and embed legal policies directly into your WordPress site. It connects with your GetTerms account to provide compliant, auto-updating documents and a fully configurable cookie consent banner.</p>
<h3>Features</h3>
<ul>
<li>Connect to your GetTerms Compliance Pack using a unique token.</li>
<li>Embed the Cookie Consent Widget site-wide or via manual integration.</li>
<li>Shortcodes to display live-updated legal documents (Privacy Policy, Terms, AUP, etc.).</li>
<li>Support for multiple languages for both widget and policies.</li>
</ul>
<h3>Usage</h3>
<h3>Setting Up</h3>
<ol>
<li>Navigate to <code>GetTerms</code> in the WordPress admin menu.</li>
<li>Enter your GetTerms token and save your settings.</li>
</ol>
<h3>Embedding the Cookie Consent Widget</h3>
<ul>
<li>Enable the auto-embed option in plugin settings to insert the consent widget in the <code>&lt;head&gt;</code> tag.</li>
<li>You can also embed manually with the provided script tag for advanced use cases or multilingual configurations.</li>
<li>To ensure proper consent enforcement, embed the script as early as possible in the head section.</li>
<li>If you have manually included other scripts in your <code>&lt;head&gt;</code> the recommendation is to manually embed the GetTerms script above all other scripts, and not use auto-embed</li>
</ul>
<h3>Using Shortcodes</h3>
<p>Use the following shortcodes to display your policy documents:</p>
<ul>
<li><code>[getterms_privacy_en]</code>, <code>[getterms_terms_en]</code>, <code>[getterms_aup_en]</code></li>
<li><code>[getterms_privacy_fr]</code>, <code>[getterms_terms_fr]</code>, <code>[getterms_aup_fr]</code></li>
<li>Additional languages and policies are listed in the plugin settings.</li>
</ul>
<h3>How wp_head and wp_enqueue_script work</h3>
<p>WordPress loads styles and scripts in two steps:</p>
<p>1) Registration + enqueue (what you do in PHP)<br />
– You register a script/style and enqueue it using WordPress functions.<br />
– Common hooks:<br />
  – <code>wp_enqueue_scripts</code> (front end): enqueue scripts/styles for the theme and plugins.<br />
  – <code>admin_enqueue_scripts</code> (wp-admin): enqueue for specific admin screens.<br />
  – <code>login_enqueue_scripts</code> (login screen): enqueue for wp-login.php.</p>
<p>2) Output (what WordPress prints into the page)<br />
– WordPress prints the enqueued styles and scripts into the HTML at the proper places, using theme hooks:<br />
  – <code>wp_head</code>: prints styles and any head scripts (e.g., those with <code>$in_footer = false</code>).<br />
  – <code>wp_footer</code>: prints scripts that were enqueued for the footer (those with <code>$in_footer = true</code>).</p>
<p>In practice, you should enqueue on the correct action, and let WordPress output them on <code>wp_head</code>/<code>wp_footer</code>. Example:</p>
<ul>
<li>
<p>Register and enqueue a script</p>
<p>function myplugin_enqueue_assets() {<br />
  wp_register_script(<br />
      ‘myplugin-frontend’,<br />
      plugins_url(‘dist/myplugin.js’, <strong>FILE</strong>),<br />
      array(‘jquery’),<br />
      ‘1.0.0’,<br />
      true // load in footer<br />
  );<br />
  wp_enqueue_script(‘myplugin-frontend’);<br />
}<br />
add_action(‘wp_enqueue_scripts’, ‘myplugin_enqueue_assets’);</p>
</li>
<li>
<p>What gets printed where</p>
<ul>
<li>Because <code>$in_footer = true</code>, the script tag is printed near the end of the page when the theme calls <code>wp_footer()</code>.</li>
<li>If <code>$in_footer = false</code> (default), it will be printed in the <code><head></code> when the theme calls <code>wp_head()</code>.</li>
</ul>
</li>
</ul>
<p>How this plugin uses these hooks<br />
– For the Cookie Consent Widget, you can choose between:<br />
  – Auto-embed: The plugin hooks into <code>wp_head</code> very early to print the consent script as high as possible in the <code><head></code> for best consent enforcement. This is intentional because consent tools must run before other scripts.<br />
  – Manual embed: You paste the provided <code><script></code> tag directly into your theme (ideally above other scripts in the head) if you need strict ordering or have custom setups.<br />
– For admin pages and settings, the plugin uses <code>admin_enqueue_scripts</code> to load its admin bundle only on our settings page to keep the rest of wp-admin lightweight.</p>
<p>Troubleshooting and best practices<br />
– Always load third-party tracking scripts after consent scripts have run. If you must hard-code tags, put the GetTerms script above them in the head.<br />
– Never echo <code><script></code> tags directly in templates unless you must. Prefer <code>wp_enqueue_script</code> to let WP handle dependencies, versions, and placement.<br />
– Make sure your theme calls <code>wp_head()</code> before <code></head></code> and <code>wp_footer()</code> before <code></body></code>. Most themes already do; if not, scripts will not appear.</p>
<h3>Data Collection and Privacy</h3>
<p>The plugin communicates with the GetTerms content network (<code>https://app.getterms.io</code>, <code>https://gettermscmp.com</code>, <code>https://gettermscdn.com</code>) to deliver policy content and manage cookie consent. The following data is transmitted:</p>
<ul>
<li><strong>Authentication Token</strong>: Used to authenticate and fetch Compliance Pack data.</li>
<li><strong>Domain Name</strong>: Validates the plugin’s authorization and retrieves domain-specific settings.</li>
<li><strong>User Consent Logs</strong>: Records of accepted/rejected cookie categories (anonymized).</li>
<li><strong>Policy Requests</strong>: Dynamic retrieval of policy content for embedding.</li>
<li><strong>Error Logs</strong>: Technical error messages (non-personal) may be sent to assist with debugging.</li>
</ul>
<p>All data is anonymized where applicable and stored in compliance with GDPR data sovereignty standards.</p>
<p>For more information, refer to our:<br />
– <a href="https://getterms.io/our-privacy-policy" rel="nofollow ugc">Privacy Policy</a><br />
– <a href="https://getterms.io/our-terms-of-service" rel="nofollow ugc">Terms of Service</a></p>
<h3>External Services</h3>
<p>This plugin relies on external services operated by GetTerms to function. It reaches out to these services to display the Cookie Consent Widget, record consent choices, and embed automatically updating legal documents. Below we explain what each service is used for, what data is sent, and when.</p>
<p>Services used (all operated by GetTerms Pty Ltd):<br />
– https://app.getterms.io — Application/API used for account authentication, compliance pack configuration, and policy retrieval.<br />
– https://gettermscmp.com — Cookie Consent Widget service that renders the banner and manages user consent interactions.<br />
– https://gettermscdn.com — Content Delivery Network for static assets and the document/embed runtime used to display policies.</p>
<p>What data is sent and when<br />
– When you save settings in the WordPress admin (Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> GetTerms):<br />
  – Authentication token (provided by you) is sent to app.getterms.io to verify your account and fetch your Compliance Pack configuration.<br />
  – Your site’s domain is sent to app.getterms.io to validate authorization and deliver domain‑specific settings.<br />
– When a page loads with the Cookie Consent Widget enabled (auto‑embed or manual embed):<br />
  – The page will request widget resources from gettermscmp.com and gettermscdn.com.<br />
  – Anonymous consent state and user choices (e.g., accepted/rejected categories) are transmitted to gettermscmp.com when visitors interact with the banner, for the purpose of storing and enforcing consent. No personally identifiable information is required for this.<br />
– When a page renders a policy via a shortcode (e.g., Privacy Policy, Terms):<br />
  – The embed runtime from gettermscdn.com requests the latest policy content from app.getterms.io and/or the CDN, along with the configured language.<br />
– When technical errors occur:<br />
  – Non‑personal error details may be sent to the above services to help diagnose and resolve issues.</p>
<p>Terms of Service and Privacy Policy<br />
– All of the above domains are operated by GetTerms and governed by the same legal documents:<br />
  – Terms of Service: https://getterms.io/our-terms-of-service<br />
  – Privacy Policy: https://getterms.io/our-privacy-policy</p>
<p>We disclose these external connections for transparency and to help you assess compliance obligations for your site.</p>
<h3>Development</h3>
<h3>Source for Compiled Assets (Required by WordPress.org)</h3>
<p>The full human‑readable, non‑minified source code for the compiled JavaScript/CSS is publicly available in our GitHub repository. This satisfies the WordPress.org guideline requiring publicly accessible sources for generated assets.</p>
<ul>
<li>
<p>Public source repository (first‑party):</p>
<ul>
<li>https://github.com/GetTerms/getterms-cookie-consent-and-policies</li>
<li>Key sources: <code>src/getterms.js</code>, <code>vite.config.mjs</code>, <code>package.json</code></li>
</ul>
</li>
<li>
<p>Compiled files shipped with the plugin (in this ZIP):</p>
<ul>
<li>JavaScript bundle: <code>dist/getterms.bundle.js</code></li>
</ul>
</li>
<li>
<p>Third‑party libraries used in the bundle (public sources):</p>
<ul>
<li>Tippy.js (tooltip library): https://github.com/atomiks/tippyjs</li>
<li>Popper Core (positioning engine): https://github.com/popperjs/popper-core</li>
</ul>
</li>
</ul>
<p>Note: The distributed plugin package does not include the <code>src/</code> directory. For review or contributions, please use the public repository linked above.</p>
<h3>Build Tools</h3>
<p>This plugin uses modern build tooling for asset management:</p>
<ul>
<li><strong>Vite</strong> compiles source JavaScript files from <code>src/</code> to <code>dist/</code>.</li>
<li><strong>NPM</strong> manages dependencies and scripts.</li>
<li>Output is compiled as an IIFE for safe WordPress execution.</li>
</ul>
<p>Build config: <code>vite.config.mjs</code></p>
<p>Build steps to reproduce the distributed assets:</p>
<ol>
<li>Install Node.js (use <code>.nvmrc</code> for the recommended version).</li>
<li>Clone the public repository and from the plugin root directory, run:
<ul>
<li><code>npm install</code></li>
<li><code>npm run build</code></li>
</ul>
</li>
<li>The compiled output will be written to <code>dist/</code>.</li>
</ol>
<p>No private repositories are required to build; all source files needed are available in the public repository.</p>
<h3>Support</h3>
<p>For help, email <a href="mailto:support@getterms.io" rel="nofollow ugc">support@getterms.io</a></p>
<h3>License</h3>
<p>This plugin is licensed under the <a href="https://www.gnu.org/licenses/gpl-2.0.html" rel="nofollow ugc">GPLv2 or later</a>.</p>


GetTerms Cookie Consent & Policies

The GetTerms plugin allows users to manage their GetTerms compliance packs, embed auto-updating policies, and display their Cookie Consent Widget.

Saji

Mahdi Yazdani

MyPreview

<p>Additional Terms for WooCommerce helps store owners add an extra agreement checkbox to the WooCommerce checkout page. Use it for return policies, refund conditions, cancellation terms, privacy notices, age confirmations, delivery notices, warranty acknowledgements, payment method notices, or any other policy that customers should review before purchase.</p>
<p>The plugin is designed to be simple to configure while still giving store owners control over how the terms appear during checkout.</p>
<h4>What you can do with the free version</h4>
<ul>
<li>Add an additional terms and conditions checkbox to WooCommerce checkout.</li>
<li>Make the checkbox required or optional.</li>
<li>Show a custom validation message when required terms are not accepted.</li>
<li>Link the checkbox label to a selected terms page using the <code>{{additional-terms}}</code> smart tag.</li>
<li>Display linked terms content in a modal, in a new tab, or directly above the checkbox.</li>
<li>Enable or disable the checkbox without deleting the saved settings.</li>
<li>Display the checkbox on the classic WooCommerce checkout shortcode.</li>
<li>Add the dedicated Additional Terms block inside the WooCommerce Checkout Block.</li>
<li>Save customer acceptance details in WooCommerce order notes.</li>
<li>Use the plugin on multilingual stores with translation-ready strings and support for WPML and Polylang workflows.</li>
</ul>
<h4>Common use cases</h4>
<p>Additional Terms for WooCommerce can be useful when your store needs customers to acknowledge specific policies before checkout, including:</p>
<ul>
<li>Refund and cancellation policies.</li>
<li>Subscription terms.</li>
<li>Product warranties.</li>
<li>Age-restricted product notices.</li>
<li>Shipping delays or delivery conditions.</li>
<li>Digital download terms.</li>
<li>Liability waivers.</li>
<li>Privacy and GDPR-related notices.</li>
<li>Return policy exceptions.</li>
<li>Special product or service conditions.</li>
<li>Payment-method-specific terms, such as bank transfer instructions, cash on delivery notices, manual payment disclaimers, financing terms, or payment gateway requirements.</li>
</ul>
<h4>Built for classic and block-based checkout</h4>
<p>The plugin works with both WooCommerce checkout approaches. On stores using the classic <code>[woocommerce_checkout]</code> shortcode, the checkbox can appear automatically near the WooCommerce terms and conditions area. On stores using the WooCommerce Checkout Block, you can place the Additional Terms block inside the checkout layout and move it to the preferred position.</p>
<h4>Keep a record of accepted terms</h4>
<p>When customers place an order, their additional terms acceptance is saved with the WooCommerce order. This gives store owners a clearer record of which checkout agreement was accepted during purchase and can help with internal review, customer support, and dispute prevention.</p>
<h4>Upgrade to Additional Terms Pro</h4>
<p>Need more advanced checkout agreements? Additional Terms Pro gives WooCommerce stores more flexibility, more control, and better record keeping for complex checkout policies.</p>
<p>With Additional Terms Pro, you can:</p>
<ul>
<li>Create unlimited additional terms checkboxes for different policies, notices, waivers, and acknowledgements.</li>
<li>Set default checkbox states for optional agreements.</li>
<li>Display accepted additional terms directly inside WooCommerce order emails.</li>
<li>Attach a PDF receipt of accepted terms to WooCommerce order emails.</li>
<li>Show an acceptance summary on the WooCommerce order details screen.</li>
<li>Use advanced conditional logic to show terms only when they are relevant.</li>
<li>Display terms based on products, categories, tags, shipping locations, user roles, shipping classes, product types, payment gateways, weekdays, and WooCommerce Brands.</li>
<li>Add payment-method-specific agreements for options such as bank transfer, cash on delivery, manual payment methods, financing, or custom gateways.</li>
<li>Link checkboxes to content from a selected post type, not only standard WordPress pages.</li>
<li>Use Hidden Cart Matching for custom checkout layouts where products may be hidden or modified by the theme or checkout builder.</li>
<li>Export and import plugin settings when moving terms configuration between stores.</li>
<li>Generate structured Terms and Conditions content using the guided Terms Generator.</li>
<li>Receive premium updates and priority support through WooCommerce.com.</li>
</ul>
<p>Additional Terms Pro is a strong fit for stores that need product-specific policies, payment gateway notices, subscription terms, regional notices, warranty acknowledgements, age confirmations, custom checkout agreements, or clearer documentation of what customers accepted during checkout.</p>
<p><a href="https://woocommerce.com/products/additional-terms-pro/" rel="nofollow ugc">Upgrade to Additional Terms Pro</a></p>
<h4>Important note</h4>
<p>This plugin helps you present and record checkout agreements, but it does not provide legal advice. Always review your terms and policies carefully, and consult a qualified legal professional when needed.</p>


Additional Terms for WooCommerce

Improve your WooCommerce checkout process with an additional terms and conditions checkbox. Ask customers to review and accept important store policie …

GetTerms Cookie Consent & Policies vs Additional Terms for WooCommerce