GDPR-Extensions.com

<p>The <strong>Google Reviews List LocalLoad Solution</strong> by GDPR-Extensions.com is a plugin designed to help website owners display authentic Google reviews on their WordPress sites without compromising data privacy. Key features include:<br />
1. Seamless Integration: Sync reviews directly from Google accounts.<br />
2. Local Data Storage: Ensures compliance with GDPR regulations.<br />
3. Customizable Display Options: Adjust styles to match your website.<br />
4. Fast Load Times: Optimized for performance.</p>
<h3>Features and Customization</h3>
<h3>Dashboard Features (GDPR-Extensions.com)</h3>
<h4>Reviews Hub:</h4>
<ul>
<li>Centralized hub to organize and manage your Google reviews.</li>
<li>Connect Google accounts securely using OAuth 2.0.</li>
<li>Filter and select reviews for specific websites.</li>
</ul>
<h4>API Key Management:</h4>
<ul>
<li>Generate unique API keys for each Reviews Hub for seamless plugin integration.</li>
</ul>
<h3>Plugin Features (WordPress)</h3>
<ol>
<li><strong>API Key Integration</strong>: Connect your WordPress site to your configured Reviews Hub.</li>
<li><strong>Fetch Reviews</strong>: Automatically retrieve and sync reviews into your WordPress project for display.</li>
<li><strong>Customizable Review Display</strong>:
<ul>
<li>Add the Google Reviews List block to any post or page.</li>
<li>Customize elements such as text color, background color, and layout options directly within the WordPress editor.</li>
</ul>
</li>
<li><strong>Display Management</strong>:
<ul>
<li>Reviews are stored locally for fast access.</li>
<li>Users can update or remove displayed reviews anytime by re-syncing through the plugin.</li>
</ul>
</li>
</ol>
<h3>How It Works</h3>
<ol>
<li><strong>API Communication:</strong> The plugin connects to the <strong>GDPR-Extensions.com</strong> API to fetch and authenticate reviews securely.</li>
<li><strong>Authentication & Security:</strong>
<ul>
<li>The API key is required for authentication and is stored locally on the user’s WordPress site.</li>
<li>Secure <strong>OAuth 2.0</strong> authentication ensures user data protection.</li>
</ul>
</li>
<li><strong>Data Handling:</strong>
<ul>
<li>User reviews are stored locally on the WordPress site after fetching them from <strong>GDPR-Extensions.com</strong>.</li>
<li>No sensitive user credentials are stored in the plugin.</li>
</ul>
</li>
<li><strong>Consent Management:</strong>
<ul>
<li>The plugin does not track users or collect unnecessary data.</li>
<li>The API only processes the reviews selected by the user.</li>
</ul>
</li>
</ol>
<h3>External Services</h3>
<p>This plugin integrates with <strong>GDPR-Extensions.com</strong> to securely fetch and manage Google reviews while ensuring <strong>GDPR compliance</strong>. The integration enables website owners to display Google reviews locally while maintaining privacy and control over their data.</p>
<h3>API Endpoints Used by the Plugin</h3>
<p>The plugin makes API requests to the following URLs:</p>
<ul>
<li><strong>Authenticate API Key:</strong><br />
  https://dashboard.gdpr-extensions.com/review/api/{reviews_api_key}/authenticate-key.json<br />
This endpoint verifies the API key of your site through our dashboard at gdpr-extensions.com.</li>
<li><strong>Fetch Reviews:</strong><br />
  https://dashboard.gdpr-extensions.com/review/api/{reviews_api_key}/reviews-list.json<br />
Once the API key is authenticated, this endpoint retrieves reviews associated with it.</li>
</ul>
<h3>Data Handling Policy</h3>
<h4>Objective:</h4>
<p>This plugin complies with GDPR regulations by ensuring secure, transparent, and minimal data handling. Below are the details:</p>
<ol>
<li><strong>Google Reviews Integration</strong>
<ul>
<li><strong>Purpose:</strong> Fetch and sync Google reviews for local display.</li>
<li><strong>Data Sent:</strong> Upon user authentication via OAuth 2.0, the plugin fetches reviews data (e.g., content, ratings, timestamps). No sensitive credentials are stored.</li>
<li><strong>Data Storage:</strong> Reviews are stored locally for fast access and offline reliability.</li>
</ul>
</li>
<li><strong>gdpr-extensions.com Service</strong>
<ul>
<li><strong>Purpose:</strong> Manage reviews via the Reviews Hub.</li>
<li><strong>Data Sent:</strong> Users manually copy an API key from the GDPR-Extensions.com dashboard. Data syncing only occurs upon user action.</li>
<li><strong>Data Storage:</strong> Data remains accessible locally on the WordPress site. No unnecessary data is transferred.</li>
</ul>
</li>
<li><strong>Security and User Control</strong>
<ul>
<li>All data handling complies with GDPR.</li>
<li>Secure encryption is applied to data transfer and storage.</li>
<li>Users can manage, update, or delete reviews via the plugin interface.</li>
<li>Data is never shared with unauthorized third parties.</li>
</ul>
</li>
</ol>
<p>For more details, review our privacy policies:<br />
-[Google Privacy Policy] (https://policies.google.com/privacy)<br />
–<a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a><br />
–<a href="https://www.gdpr-extensions.com/gdpr-solutions/our-local-load-solutions/google-reviews-list/terms-of-use" rel="nofollow ugc">GDPR-Extensions.com Terms</a><br />
–<a href="https://www.gdpr-extensions.com/gdpr-solutions/our-local-load-solutions/google-reviews-list/privacy-policy" rel="nofollow ugc">GDPR-Extensions.com Privacy Policy</a></p>
<p>This ensures full transparency in data usage, aligning with <strong>GDPR compliance</strong> for privacy and security.</p>
<h3>Frequently Asked Questions (FAQ)</h3>
<h4>What is the LocalLoad Solution?</h4>
<p>The LocalLoad Solution ensures that your Google reviews are stored securely on the GDPR-Extensions.com dashboard and fetched to your WordPress project via an API key. This minimizes data exposure and ensures compliance with GDPR regulations.</p>
<h4>How does the plugin store and fetch reviews?</h4>
<ol>
<li>Reviews are first stored securely on the GDPR-Extensions.com dashboard.</li>
<li>After creating a Reviews Hub, users copy the unique API key generated for their hub.</li>
<li>The API key is entered into the plugin’s customization page in WordPress.</li>
<li>The plugin fetches the reviews to be displayed locally on the WordPress site.</li>
</ol>
<h4>Do I need an account on GDPR-Extensions.com to use this plugin?</h4>
<p>Yes, an account is required. You will use the dashboard to connect your Google account, manage reviews, and generate the API key needed for the plugin to function.</p>
<h4>Is my data secure?</h4>
<p>Absolutely. All data transfers use secure encryption, and reviews are stored locally on your WordPress project. No data is shared with unauthorized third parties.</p>
<h3>Contact</h3>
<p>For questions or support, reach out to us at support@gdpr-extensions.com.</p>


GDPR-Extensions-com – Google Reviews List Localload Solution

Short Description: Showcase Google Reviews on WordPress with GDPR compliance and secure local data storage using the LocalLoad Solution plugin.

WordPress.org

Viktor Szépe

Rogier Lankhorst

Aert

Mark

Mathieu Paapst

pepe

Konstantinos Xenos

Aurooba Ahmed

Johan Holst Nielsen

mujuonly

<p>WP Consent API is a plugin that standardizes the communication of accepted consent categories between plugins. It requires a cookie banner plugin and, at least, one other plugin that supports the WP Consent API.</p>
<p>With this plugin, all supporting plugins can use the same set of methods to read and register the current consent category, allowing consent management plugins and other plugins to work together, improving compliance with privacy laws.</p>
<p>WARNING: the plugin itself will not handle consent. It will show you how many plugins you have without Consent API support and will improve compliance on your site by ensuring smooth communication between cookie banner plugins and plugins that set cookies or track user data.</p>
<h4>What problem does this plugin solve?</h4>
<p>Currently, it is possible for a consent management plugin to block third-party services like Facebook, Google Maps, Twitter, etc. But if a WordPress plugin places a PHP cookie, a consent management plugin cannot prevent this.</p>
<p>Secondly, some plugins integrate the tracking code on the clientside in javascript files that, when blocked, break the site.</p>
<p>Or, if such a plugin’s javascript is minified, causing the URL to be unrecognizable and won’t get detected by an automatic blocking script.</p>
<p>Lastly, the blocking approach requires a list of all types of URL’s that tracks data. A generic API where plugins adhere to can greatly<br />
facilitate a webmaster in getting a site compliant.</p>
<h4>Does usage of this API prevent third-party services from tracking user data?</h4>
<p>Primary this API is aimed at compliant first-party cookies or tracking by WordPress plugins. If such a plugin triggers, for example, Facebook,<br />
usage of this API will be of help. If a user embeds a Facebook iframe, a blocking tool is needed that initially disables the iframe and or scripts.</p>
<p>Third-party scripts have to blocked by blocking functionality in a consent management plugin. To do this in core would be to intrusive, and is also not applicable to all users: only users with visitors from opt-in regions such as the European Union require such a feature. Such a feature also has a risk of breaking things. Additionally, blocking these and showing a nice placeholder requires even more sophisticated code, all of which should in my opinion not be part of WordPress core, for the same reasons.</p>
<h4>How does it work?</h4>
<p>There are two indicators that together tell if consent is given for a specific consent category, e.g., “marketing”:<br />
1) the region based consent_type, which<br />
can be opt-in, opt-out, or other possible consent_types;<br />
2) and the visitor’s choice: not set, allow, or deny.</p>
<p>The consent_type is a function that wraps a filter, “wp_get_consent_type”. If there’s no consent management plugin to set it, it will return false. This will cause all consent categories to return true, allowing cookies to be set on all categories.</p>
<p>If opt-in is set using this filter, a category will only return true if the value of the visitor’s choice is “allow”.</p>
<p>If the region based consent_type is opt-out, it will return true if the visitor’s choice is not set or is “allow”.</p>
<p>Clientside, a consent management plugin can dynamically manipulate the consent type and set several cookie categories.</p>
<p>A plugin can use a hook to listen for changes or check the value of a given category.</p>
<p>Categories and most other stuff can be extended with a filter.</p>
<h3>Existing integrations</h3>
<p>Categorized, and sorted alphabetically</p>
<h4>Example plugin</h4>
<ul>
<li><a href="https://github.com/rlankhorst/consent-api-example-plugin" rel="nofollow ugc">Example plugin</a>. The plugin basically consists of a shortcode, with a div that shows a tracking or not tracking message. No actual tracking is done 🙂</li>
</ul>
<h4>Consent Management Providers</h4>
<ul>
<li><a href="https://wordpress.org/plugins/sirdata-cmp/" rel="ugc">Abconsent Sirdata CMP</a>.</li>
<li><a href="https://wordpress.org/plugins/beautiful-and-responsive-cookie-consent/" rel="ugc">Beautiful Cookie Consent Banner</a>.</li>
<li><a href="https://wordpress.org/plugins/clickio-consent/" rel="ugc">Clickio Consent</a></li>
<li><a href="https://wordpress.org/plugins/complianz-gdpr/" rel="ugc">Complianz GDPR/CCPA</a>.</li>
<li><a href="https://consent.studio/" rel="nofollow ugc">Consent Studio</a>.</li>
<li><a href="https://wordpress.org/plugins/consent-manager/" rel="ugc">consentmanager</a>.</li>
<li><a href="https://conzent.net/" rel="nofollow ugc">Conzent</a>.</li>
<li><a href="https://wordpress.org/plugins/cookiebot/" rel="ugc">Cookiebot</a>.</li>
<li><a href="https://wordpress.org/plugins/cookiefirst-gdpr-cookie-consent-banner/" rel="ugc">CookieFirst</a>.</li>
<li><a href="https://wordpress.org/plugins/cookiehub/" rel="ugc">CookieHub</a>.</li>
<li><a href="https://wordpress.org/plugins/cookietractor/" rel="ugc">CookieTractor</a>.</li>
<li><a href="https://wordpress.org/plugins/cookie-law-info/" rel="ugc">CookieYes – Cookie Banner for Cookie Consent</a>.</li>
<li><a href="https://wordpress.org/plugins/gdpr-cookie-compliance/" rel="ugc">GDPR Cookie Compliance</a>.</li>
<li><a href="https://www.webtoffee.com/product/gdpr-cookie-consent/" rel="nofollow ugc">GDPR Cookie Consent Plugin – CCPA Ready</a>.</li>
<li><a href="https://getterms.io/consent-manager/" rel="nofollow ugc">GetTerms</a>.</li>
<li><a href="https://wordpress.org/plugins/iubenda-cookie-law-solution/" rel="ugc">iubenda | All-in-one Compliance</a>.</li>
<li><a href="https://wordpress.org/plugins/ibamu/" rel="ugc">Lawwwing</a>.</li>
<li><a href="https://wordpress.org/plugins/pressidium-cookie-consent/" rel="ugc">Pressidium Cookie Consent</a>.</li>
<li><a href="https://wordpress.org/plugins/trustarc-cookie-consent-manager/" rel="ugc">TrustArc Cookie Consent Manager</a></li>
</ul>
<h4>Consent Requiring Plugins</h4>
<ul>
<li><a href="https://wordpress.org/plugins/add-to-any/" rel="ugc">AddToAny</a>.</li>
<li><a href="https://www.appfromlab.com/product/woocommerce-utm-tracker-plugin/" rel="nofollow ugc">AFL UTM Tracker Plugin</a>.</li>
<li><a href="https://wordpress.org/plugins/burst-statistics/" rel="ugc">Burst Statistics</a>.</li>
<li><a href="https://wordpress.org/plugins/google-site-kit/" rel="ugc">Google Site Kit</a>.</li>
<li><a href="https://wordpress.org/plugins/woocommerce-google-adwords-conversion-tracking-tag/" rel="ugc">Pixel Manager for WooCommerce</a>.</li>
<li><a href="https://wordpress.org/plugins/woocommerce/" rel="ugc">Woo</a>.</li>
<li><a href="https://wordpress.org/plugins/wp-statistics/" rel="ugc">WP Statistics</a>.</li>
</ul>
<h3>Demo site</h3>
<p><a href="https://wpconsentapi.org/" rel="nofollow ugc">wpconsentapi.org</a><br />
Below are the plugins used to set up the demo site:</p>
<ul>
<li>Complianz</li>
<li><a href="https://github.com/rlankhorst/consent-api-example-plugin" rel="nofollow ugc">The example plugin</a></li>
</ul>
<h4>javascript, consent management plugin</h4>
<pre><code>//set consent type
window.wp_consent_type = 'optin'

//dispatch event when consent type is defined. This is useful if the region is detected server side, so the consent type is defined later during the pageload
let event = new CustomEvent('wp_consent_type_defined');
document.dispatchEvent( event );


//consent management plugin sets cookie when consent category value changes
wp_set_consent('marketing', 'allow');
</code></pre>
<h4>javascript, tracking plugin</h4>
<pre><code>//listen to consent change event
document.addEventListener("wp_listen_for_consent_change", function (e) {
  var changedConsentCategory = e.detail;
  for (var key in changedConsentCategory) {
    if (changedConsentCategory.hasOwnProperty(key)) {
      if (key === 'marketing' && changedConsentCategory[key] === 'allow') {
        console.log("just given consent, track user")
      }
    }
  }
});

//basic implementation of consent check:
if (wp_has_consent('marketing')){
  activateMarketing();
  console.log("set marketing stuff now!");
} else {
  console.log("No marketing stuff please!");
}
</code></pre>
<h4>PHP</h4>
<pre><code>//declare compliance with consent level API
$plugin = plugin_basename( __FILE__ );
add_filter( "wp_consent_api_registered_{$plugin}", '__return_true' );

/**
* Example how a plugin can register cookies with the consent API
 * These cookies can then be shown on the front-end, to the user, with wp_get_cookie_info()
 */

function my_wordpress_register_cookies(){
    if ( function_exists( 'wp_add_cookie_info' ) ) {
        wp_add_cookie_info( 'AMP_token', 'AMP', 'marketing', __( 'Session' ), __( 'Store a unique User ID.' ) );
    }
}
add_action('plugins_loaded', 'my_wordpress_register_cookies');


if (wp_has_consent('marketing')){
//do marketing stuff
}
</code></pre>
<h4>Service-level consent</h4>
<p>In addition to category-based consent, the API supports service-level consent control. This allows consent management plugins to grant or deny consent for specific services (like ‘google-analytics’ or ‘facebook-pixel’) independently from their category. When checking service consent with wp_has_service_consent(), the API first checks if explicit consent exists for that service. If no explicit consent is set, it falls back to the consent status of the service’s category. This enables fine-grained control: a user might accept statistics cookies in general, but explicitly deny a specific analytics service.</p>
<p>Service consent can be checked and set both server-side (PHP) and client-side (JavaScript):</p>
<p>PHP:</p>
<pre><code>//check if a specific service has consent
if ( wp_has_service_consent( 'google-analytics' ) ) {
    //activate google analytics
}

//check if a service is explicitly denied
if ( wp_is_service_denied( 'facebook-pixel' ) ) {
    //service was explicitly denied by user
}

//set service consent
wp_set_service_consent( 'google-analytics', true ); //grant consent
wp_set_service_consent( 'facebook-pixel', false ); //deny consent

//listen for service consent changes
add_action( 'wp_consent_service_changed', function( $service, $consented ) {
    error_log( "Service {$service} consent changed to: " . ( $consented ? 'granted' : 'denied' ) );
}, 10, 2 );
</code></pre>
<p>JavaScript:</p>
<pre><code>//check service consent
if ( wp_has_service_consent( 'youtube' ) ) {
    //activate tracking
}

//check if explicitly denied
if ( wp_is_service_denied( 'facebook-pixel' ) ) {
    //service denied
}

//set service consent
wp_set_service_consent( 'youtube', true );

//listen for service consent changes
document.addEventListener( 'wp_consent_api_status_change_service', function( e ) {
    console.log( 'Service: ' + e.detail.service + ', consented: ' + e.detail.value );
});
</code></pre>
<p>Any code suggestions? We’re on <a href="https://github.com/WordPress/wp-consent-level-api" rel="nofollow ugc">GitHub</a> as well!</p>


WP Consent API


Louis was great helping me with an issue. Plugin works great and highly recommend!


Great Support Team


The wp‑consent‑api plugin provides a clean, standardized way to manage user consent across plugins and themes. It solves a core problem with a lightweight API. This is definitely a feature that should be integrated into WordPress core to ensure consistent and compliant consent handling by default.


Future of WP Consent Management

Simple Consent API to read and register the current consent category.

GDPR-Extensions-com – Google Reviews List Localload Solution vs WP Consent API