GetTerms Cookie Consent & Policies

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.

Features

• Connect to your GetTerms Compliance Pack using a unique token.

• Embed the Cookie Consent Widget site-wide or via manual integration.

• Shortcodes to display live-updated legal documents (Privacy Policy, Terms, AUP, etc.).

• Support for multiple languages for both widget and policies.

Usage

Setting Up

• Navigate to GetTerms in the WordPress admin menu.

• Enter your GetTerms token and save your settings.

Embedding the Cookie Consent Widget

• Enable the auto-embed option in plugin settings to insert the consent widget in the <head> tag.

• You can also embed manually with the provided script tag for advanced use cases or multilingual configurations.

• To ensure proper consent enforcement, embed the script as early as possible in the head section.

• If you have manually included other scripts in your <head> the recommendation is to manually embed the GetTerms script above all other scripts, and not use auto-embed

Using Shortcodes

Use the following shortcodes to display your policy documents:

• [getterms_privacy_en], [getterms_terms_en], [getterms_aup_en]

• [getterms_privacy_fr], [getterms_terms_fr], [getterms_aup_fr]

• Additional languages and policies are listed in the plugin settings.

How wp_head and wp_enqueue_script work

WordPress loads styles and scripts in two steps:

1) Registration + enqueue (what you do in PHP)

– You register a script/style and enqueue it using WordPress functions.

– Common hooks:

– wp_enqueue_scripts (front end): enqueue scripts/styles for the theme and plugins.

– admin_enqueue_scripts (wp-admin): enqueue for specific admin screens.

php.

2) Output (what WordPress prints into the page)

– WordPress prints the enqueued styles and scripts into the HTML at the proper places, using theme hooks:

, those with $in_footer = false ).

– wp_footer: prints scripts that were enqueued for the footer (those with $in_footer = true ).

In practice, you should enqueue on the correct action, and let WordPress output them on wp_head / wp_footer. Example:

-

Register and enqueue a script

function myplugin_enqueue_assets() {

wp_register_script(

‘myplugin-frontend’,

js’, FILE ),

array(‘jquery’),

0’,

true // load in footer

);

wp_enqueue_script(‘myplugin-frontend’);

}

add_action(‘wp_enqueue_scripts’, ‘myplugin_enqueue_assets’);

-

What gets printed where

• Because $in_footer = true, the script tag is printed near the end of the page when the theme calls wp_footer().

• If $in_footer = false (default), it will be printed in the <head> when the theme calls wp_head().

How this plugin uses these hooks

– For the Cookie Consent Widget, you can choose between:

– Auto-embed: The plugin hooks into wp_head very early to print the consent script as high as possible in the <head> for best consent enforcement. This is intentional because consent tools must run before other scripts.

– Manual embed: You paste the provided <script> tag directly into your theme (ideally above other scripts in the head) if you need strict ordering or have custom setups.

– For admin pages and settings, the plugin uses admin_enqueue_scripts to load its admin bundle only on our settings page to keep the rest of wp-admin lightweight.

Troubleshooting and best practices

– 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.

– Never echo <script> tags directly in templates unless you must. Prefer wp_enqueue_script to let WP handle dependencies, versions, and placement.

– Make sure your theme calls wp_head() before </head> and wp_footer() before </body>. Most themes already do; if not, scripts will not appear.

Data Collection and Privacy

com ) to deliver policy content and manage cookie consent. The following data is transmitted:

• Authentication Token: Used to authenticate and fetch Compliance Pack data.

• Domain Name: Validates the plugin’s authorization and retrieves domain-specific settings.

• User Consent Logs: Records of accepted/rejected cookie categories (anonymized).

• Policy Requests: Dynamic retrieval of policy content for embedding.

• Error Logs: Technical error messages (non-personal) may be sent to assist with debugging.

All data is anonymized where applicable and stored in compliance with GDPR data sovereignty standards.

For more information, refer to our:

– Privacy Policy

– Terms of Service

External Services

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.

Services used (all operated by GetTerms Pty Ltd):

io — Application/API used for account authentication, compliance pack configuration, and policy retrieval.

com — Cookie Consent Widget service that renders the banner and manages user consent interactions.

com — Content Delivery Network for static assets and the document/embed runtime used to display policies.

What data is sent and when

– When you save settings in the WordPress admin (Settings → GetTerms):

io to verify your account and fetch your Compliance Pack configuration.

io to validate authorization and deliver domain‑specific settings.

– When a page loads with the Cookie Consent Widget enabled (auto‑embed or manual embed):

com.

com when visitors interact with the banner, for the purpose of storing and enforcing consent. No personally identifiable information is required for this.

, Privacy Policy, Terms):

io and/or the CDN, along with the configured language.

– When technical errors occur:

– Non‑personal error details may be sent to the above services to help diagnose and resolve issues.

Terms of Service and Privacy Policy

– All of the above domains are operated by GetTerms and governed by the same legal documents:

io/our-terms-of-service

io/our-privacy-policy

We disclose these external connections for transparency and to help you assess compliance obligations for your site.

Development

Source for Compiled Assets (Required by WordPress.org)

The full human‑readable, non‑minified source code for the compiled JavaScript/CSS is publicly available in our GitHub repository. org guideline requiring publicly accessible sources for generated assets.

-

Public source repository (first‑party):

• https://github.com/GetTerms/getterms-cookie-consent-and-policies

• Key sources: src/getterms.js, vite.config.mjs, package.json

-

Compiled files shipped with the plugin (in this ZIP):

• JavaScript bundle: dist/getterms.bundle.js

-

Third‑party libraries used in the bundle (public sources):

• Tippy.js (tooltip library): https://github.com/atomiks/tippyjs

• Popper Core (positioning engine): https://github.com/popperjs/popper-core

Note: The distributed plugin package does not include the src/ directory. For review or contributions, please use the public repository linked above.

Build Tools

This plugin uses modern build tooling for asset management:

• Vite compiles source JavaScript files from src/ to dist/.

• NPM manages dependencies and scripts.

• Output is compiled as an IIFE for safe WordPress execution.

mjs

Build steps to reproduce the distributed assets:

• Install Node.js (use.nvmrc for the recommended version).

• Clone the public repository and from the plugin root directory, run:

• npm install

• npm run build

• The compiled output will be written to dist/.

No private repositories are required to build; all source files needed are available in the public repository.

Support

io

License

This plugin is licensed under the GPLv2 or later.