Plugin for Grav CMS - It allows to show up customisable privacy consents for visitors (as one of techniques for comply with GDPR), and manage content security policy (not only) meta tag based on visitor settings.

Plugin doesn`t require jQuery. Plugin uses and includes following scripts:
tingle.js - MIT https://github.com/robinparisi/tingle
js-cookie - MIT https://github.com/js-cookie/js-cookie

Plugin shows up Modal for site visitor.

Intention of this plugin is to show popup to visitor with short straightfoward information about site policy and give ability for user to setup his privacy settings. This information should have link to page containing full version of site policy.

• Custom content and inputs (checkboxes),
• modal content is loaded by ajax,
• accept and deny buttons can be customised with content and button classes,
• modal can show up immediately on page load, or can be deferred by given time after user scroll page, so visitor have time to know some content of page, before asking for privacy consents,
• after changing privacy information content, modal will show up for all visitors, even when they accepted previous version,
• You can add button on any page to show up modal for user which want to change privacy consents,
• You can add whitelisted pages, where popup won`t be shown (eg. page with site policy).

First: On plugin configuration, You can define consent names like analytics, affiliation, ads etc... and urls or valid Content Security Policy expression, and choose if some of them should be enabled by default (before user give any consents).

Second: By javascript callbacks, you can run callback after visitor accept some consent:

gdprPrivacySetupPlugin.onAllowed('webfonts', function () {
    WebFont.load({
        google: {
            families: [
                // fonts
            ]
        }
    });
});

Consent (webfonts) must be defined in plugin configuration (CSP tab). You can add many callbacks for single consent.

After defining consents in CSP tab, You have to add related inputs to privacy information content.
Eg. if You have consent name webfonts, in privacy information add:

<input type="checkbox" name="gdpr_webfonts" id="gdpr_webfonts">
<label for="gdpr_webfonts">Some Web Stored Fonts</label>

Important part is id="gdpr_webfonts", gdpr_ is prefix which can be defined in plugin settings and webfonts is consent name related to name defined in plugin settings.

You should also add checked and disabled attributes for checkboxes that should be enabled by default or visitor shouldn`t be able to reject some consent (see site consent on default configuration).

P.S. Sorry for my english :)