Adds links from the settings screen into your AI Privacy Center account. No behavior change and no new network requests.<\/p>","1.6.6":"
Documentation only \u2014 no code change.<\/p>","1.6.5":"
The settings page now appears under Settings as "AI Privacy Center" rather than "Consent Connector". Same page, easier to find.<\/p>","1.6.4":"
Setup guidance only: a Settings link on the Plugins screen, a getting-started panel, and direct links to where your Widget Key lives. No behavior change.<\/p>","1.6.3":"
Fixes double consent banners on sites that still have the older "AI Privacy Center" plugin active. If you see the new notice telling you to delete that plugin, do -- your settings have already been copied across.<\/p>","1.6.2":"
Housekeeping only \u2014 no code change.<\/p>","1.6.1":"
Documentation only \u2014 no code change.<\/p>","1.6.0":"
Plugin renamed and internally re-prefixed. Your existing settings are migrated automatically \u2014 check Settings \u2192 Consent Connector after upgrading to confirm your Widget Key is still shown.<\/p>","1.5.2":"
Plugin-header metadata only \u2014 no behavior change. Safe to upgrade any time.<\/p>","1.5.1":"
Internal code-quality fixes only (directory-guideline compliance) \u2014 no behavior change. Safe to upgrade any time.<\/p>","1.5.0":"
Adds server-side tracker blocking and cache-aware safeguards. After upgrading, purge your cache and verify the banner and blocking while logged out.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3697757,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3697757,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3697757,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3697757,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.6.2","1.6.3","1.6.4","1.6.5","1.6.6","1.7.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3697757,"resolution":"1","location":"assets","locale":"","width":1533,"height":784},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3697757,"resolution":"2","location":"assets","locale":"","width":1300,"height":723},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3697757,"resolution":"3","location":"assets","locale":"","width":1300,"height":723},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3697757,"resolution":"4","location":"assets","locale":"","width":1568,"height":766}},"screenshots":{"1":"The consent banner on a live site (deny-by-default, WCAG 2.2 AA).","2":"The plugin settings screen \u2014 paste your widget key.","3":"The \"Verify configuration\" check reporting the plugin's current blocking state.","4":"The AI Privacy Center dashboard - plan, connected sites, open privacy requests and setup status."}},"plugin_section":[],"plugin_tags":[166295,20272,16626,131785,4306],"plugin_category":[],"plugin_contributors":[267959,280961],"plugin_business_model":[],"class_list":["post-347300","plugin","type-plugin","status-publish","hentry","plugin_tags-ccpa","plugin_tags-cookie-banner","plugin_tags-cookie-consent","plugin_tags-gdpr","plugin_tags-privacy-policy","plugin_contributors-kevin10676","plugin_contributors-puregraceai","plugin_committers-puregraceai"],"banners":{"banner":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/banner-772x250.png?rev=3697757","banner_2x":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/banner-1544x500.png?rev=3697757","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/icon-128x128.png?rev=3697757","icon_2x":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/icon-256x256.png?rev=3697757","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/screenshot-1.png?rev=3697757","caption":"The consent banner on a live site (deny-by-default, WCAG 2.2 AA)."},{"src":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/screenshot-2.png?rev=3697757","caption":"The plugin settings screen \u2014 paste your widget key."},{"src":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/screenshot-3.png?rev=3697757","caption":"The \"Verify configuration\" check reporting the plugin's current blocking state."},{"src":"https:\/\/ps.w.org\/puregrace-consent-connector\/assets\/screenshot-4.png?rev=3697757","caption":"The AI Privacy Center dashboard - plan, connected sites, open privacy requests and setup status."}],"raw_content":"\n
PureGrace Consent Connector links your WordPress site to AI Privacy Center, a consent-management service operated by Pure Grace AI, LLC, so your consent banner and your tracker blocking are configured in one place instead of pasted into your theme.<\/p>\n\n
Most cookie-consent plugins stop at the popup. This one also does the part a banner cannot: it neutralizes hard-coded tracker scripts on the server, before the browser parses them<\/strong>, so a tracker physically cannot fire before a visitor consents.<\/p>\n\n How this differs from the cookie-banner plugins already in the directory<\/strong><\/p>\n\n The directory has many consent-banner plugins, so it is fair to ask what this one adds. Two things, and both are structural rather than cosmetic.<\/p>\n\n It enforces consent on the server, not in the browser.<\/em> A banner plugin gates trackers with JavaScript after the page has loaded. This plugin rewrites hard-coded tracker tags into inert markup during page generation, before the HTML leaves your server<\/strong> \u2014 across four tag types: external It is a connector, not a standalone banner.<\/em> The banner, the consent records and the tracker classification live in AI Privacy Center, an external service. This plugin's job is to bind a WordPress site to that service and to do the server-side enforcement WordPress is uniquely placed to do. It is not a general-purpose cookie banner and is not useful without the service, in the same way an analytics connector is not useful without the analytics account.<\/p>\n\n If you want a self-contained cookie banner with no external account, one of the existing directory plugins will serve you better. This one exists for sites whose consent state is managed centrally across more than one property.<\/p>\n\n What the plugin does<\/strong><\/p>\n\n What it does not do<\/strong><\/p>\n\n Honest note on compliance.<\/strong> AI Privacy Center gives you tools and records to help you meet your privacy obligations. It is not a law firm and does not guarantee compliance with any law \u2014 compliance is an outcome of your own process, not a product setting.<\/p>\n\n An account is required.<\/strong> This plugin is the WordPress connector for the AI Privacy Center service. You need an account and a widget key to use it, in the same way an analytics plugin needs a property ID. A free plan is available.<\/p>\n\n No functionality in this plugin is gated behind a paid plan.<\/strong> Everything the plugin's own code does \u2014 the consent banner, and all four kinds of server-side tracker neutralization \u2014 runs on a free account as soon as a widget key is saved. There is no licence check, no tier check, no usage cap and no trial timer anywhere in the plugin. The only condition on tracker blocking is a saved widget key, because the plugin has to know which site's consent state it is enforcing. Paid plans buy additional capability in the hosted service<\/em> \u2014 such as AI-generated policy updates and longer record retention \u2014 none of which is implemented in, or withheld by, this plugin.<\/p>\n\n This plugin relies on one external service: AI Privacy Center<\/strong>, a consent-management platform operated by the plugin author, Pure Grace AI, LLC, at Nothing is sent until you save a widget key.<\/strong> With the key field empty the plugin makes no outbound request of any kind, from the browser or from your server.<\/p>\n\n Once a key is saved, these requests happen:<\/p>\n\n Terms and privacy<\/strong><\/p>\n\n A note on the tracker host names inside this plugin.<\/strong> Yes. The plugin is the WordPress connector for the service, and it needs a widget key to know which site's consent state it is enforcing. A free plan is available, and every feature implemented in this plugin \u2014 banner and all server-side tracker blocking \u2014 works on it. Paid plans add capability in the hosted service (for example AI-generated policy updates); nothing in the plugin's own code is switched off by plan.<\/p><\/dd>\n<script src><\/code>, inline <script><\/code> snippets, <img><\/code> tracking pixels and <iframe><\/code> embeds. A tracker that is never delivered as an executable tag cannot fire in the gap between page load and banner render, which is the gap browser-only gating cannot close. The transform is idempotent and fails safe: unquoted or unrecognized markup is left untouched rather than mangled.<\/p>\n\n\n
<script src><\/code> tags, inline (no-src) <script><\/code> snippets, tracking <img><\/code> pixels, and <iframe><\/code> embeds (YouTube, Vimeo, Maps, social widgets, and similar). This catches server-rendered trackers that browser-only banners miss.<\/li>\n\n
External services<\/h3>\n\n
https:\/\/app.aiprivacycenter.com<\/code>. The plugin cannot function without it, because the consent banner and the consent records it produces are the service.<\/p>\n\n\n
https:\/\/app.aiprivacycenter.com\/api\/v1\/widget\/apc-stub.min.js<\/code>. Loading it sends what any browser request for a script sends: the visitor's IP address, user agent and referring page.<\/li>\nhttps:\/\/app.aiprivacycenter.com\/api\/v1\/widget\/{your-widget-key}\/config<\/code> to learn how your banner is configured. It sends your site's widget key.<\/li>\nhttps:\/\/app.aiprivacycenter.com\/api\/v1\/widget\/health-beacon<\/code> containing only your widget key, so the platform can show you whether the banner is actually running.<\/li>\nhttps:\/\/app.aiprivacycenter.com\/api\/v1\/widget\/consent<\/code> containing your widget key, the consent choices made, how they were made (a banner interaction or a Global Privacy Control signal), and a randomly generated visitor identifier stored in a strictly necessary first-party cookie. That record is what proves consent was given. No name, email address, form content or page content is sent.<\/li>\nhttps:\/\/app.aiprivacycenter.com\/api\/v1\/widget\/unknown-scripts<\/code> with your widget key, so the unknown tracker can be classified rather than silently ignored. Host names only \u2014 no visitor data and no page content.<\/li>\nhttps:\/\/app.aiprivacycenter.com\/api\/v1\/widget\/{your-widget-key}\/config<\/code> to confirm the key is recognized.<\/li>\n<\/ul>\n\n\n
includes\/class-pgcc-neutralizer.php<\/code> contains a table of third-party host names \u2014 googletagmanager.com<\/code>, connect.facebook.net<\/code>, maps.googleapis.com<\/code>, widget.intercom.io<\/code> and others. That table is a local pattern list used to recognize and block<\/strong> those trackers in your page's HTML. The plugin never contacts those hosts and sends them no data; matching a host name in that table is what stops it from loading.<\/p>\n\n\n\n
\/wp-content\/plugins\/puregrace-consent-connector<\/code>, but installing from the directory means updates arrive automatically.<\/li>\n\n
Do I need an AI Privacy Center account?<\/h3><\/dt>\n