The WordPress Consent Solution Plugin is a powerful tool that empowers website owners to easily configure a Consent Management Platform (CMP) and preemptively block all trackers on their website. This plugin ensures compliance with privacy regulations by providing users with the ability to manage their consent preferences for tracking technologies.<\/p>\n
src<\/code> attribute or in the inner HTML that matches the strings you can configure on Avacy<\/a> for each vendor.<\/li>\n<\/ol>\nAvacy is a SaaS-based CMP that helps websites manage user consents efficiently and in compliance with data protection regulations. The platform offers customizable consent forms and integrates seamlessly with various web properties.<\/p>\n
Usage<\/h3>\nCookie Banners:<\/h3>\n
Cookie banners will automatically appear on your site once configured.
\nUsers can manage their consent preferences through these banners.<\/p>\n
Tracker Control:<\/h3>\n
Trackers are preemptively blocked based on a blacklist JSON file hosted on an AWS content delivery network.
\nEvery time a page in the website is loaded, Avacy checks if scripts injected in the current page have src<\/code> attribute or the innerHTML<\/code> property containing a string matching the patterns in the blacklist and, if so, overrides some attributes and blocks the script.
\nEvery script blocked this way will be launched only if user grants consent to the corresponding vendor and purposes by opting-in from the first layer or by selecting the vendor and its purposes from the second layer (the preference center).<\/p>\nCDN Information<\/h4>\n
The CDN used by Avacy is CloudFront, pointing to the following S3 bucket:<\/p>\n
https:\/\/avacy-cdn.s3.eu-central-1.amazonaws.com\/\n\nhttps:\/\/assets.avacy-cdn.com\/\n<\/code><\/pre>\nIntegration Example<\/strong>
\nEach custom vendor list can be reached using the following format:<\/p>\nhttps:\/\/assets.avacy-cdn.com\/config\/{avacy_team_name}\/{avacy_webspace_key}\/custom-vendor-list.json;\n<\/code><\/pre>\nExplanation<\/strong><\/p>\nBase Url<\/strong>: The base URL for the configuration file is https:\/\/assets.avacy-cdn.com\/config\/.
\navacy_team_name<\/code><\/strong>: This option should be replaced with your specific tenant identifier. This is a unique identifier for your organization within Avacy.
\navacy_webspace_key<\/code><\/strong>: This option should be replaced with your specific webspace key. This is a unique identifier for your specific webspace within your tenant\u2019s account.<\/p>\nExample URL<\/strong>
\nAssuming the following:<\/p>\nTenant ID: tenant123<\/em>
\nWebspace Key: webspace456<\/em>
\nThe URL to access the custom vendor list would be:<\/p>\nhttps:\/\/assets.avacy-cdn.com\/config\/tenant123\/webspace456\/custom-vendor-list.json\n<\/code><\/pre>\nAccount Requirements<\/strong>
\nTo connect to and utilize Avacy\u2019s services, you need an active Avacy account with valid credentials, which include:<\/p>\nTenant ID<\/strong>: Provided upon registration with Avacy.
\nWebspace Key<\/strong>: Generated after creating a new web space on Avacy.
\nEnsure you have these credentials available to correctly generate the URLs needed for integration.<\/p>\nAvacy Consent Solution API<\/h3>\n
The plugin provides an interface that allows connecting to your consent archive on Avacy. To do this, it\u2019s necessary to generate a token from the Avacy platform and insert it into the Token field in the API token tab. This way, all the forms present on the page will be visible, and it will be possible to select various options, including:<\/p>\n
\n- the ability to store consents given for that specific form in the consent archive;<\/li>\n
- the fields to store for that form;<\/li>\n
- a field to identify the user who has given the consent to be stored in the archive.<\/li>\n<\/ul>\n
Everytime a user submits his data from a contact form, Avacy will perform a POST request towards Avacy Consent API, using the previously generated token as authenticator.<\/p>\n
Under What Circumstances is Avacy Used?<\/h4>\n
Avacy is utilized whenever users provide consent through forms or interactions on your WordPress site. The plugin sends this consent data to Avacy\u2019s servers for storage and processing.<\/p>\n
Avacy Service Link<\/h4>\n
For more information about Avacy and its features, visit Avacy\u2019s website<\/a>.<\/p>\nAvacy Terms of Use and Privacy Policies<\/h4>\n
Avacy uses 3rd party services as the Avacy REST API and AWS distributions to provide assets as the blacklist JSON file.
\nBefore integrating Avacy with this plugin, please review the Avacy Terms of use<\/a> and Privacy Policy<\/a> to understand how your data is handled and what responsibilities you have as a user of their service.<\/p>\nWe welcome your feedback and suggestions to improve the functionality of the plugin.<\/p>\n
Disclosure of Third-Party Service Usage<\/h3>\n
Our plugin utilizes third-party services to enhance its functionality. Below, we detail the specific circumstances under which these services are used, along with links to the respective service providers, their terms of use, and privacy policies.<\/p>\n
Services Utilized<\/h3>\n
Amazon Web Services (AWS)<\/strong> is a leading cloud platform offering a wide range of services, including computing power, storage, and networking, as well as advanced technologies like machine learning and IoT. AWS is designed for flexibility, scalability, and service reliability.<\/p>\nAWS CloudFront<\/strong> is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to users globally with low latency and high transfer speeds.<\/p>\n\nThe URLs https:\/\/jumpgroup.avacy-cdn.com<\/em> and https:\/\/assets.avacy-cdn.com<\/em> are custom domains provided to access the AWS CloudFront service. Each asset is fetched from these URLs.<\/p>\n<\/blockquote>\nScript Enqueuing<\/strong>
\nScript enqueuing involves dynamically adding the main JavaScript core in order to display the cookie banner on your page. This method ensures that scripts are loaded only when needed, reducing page load times and improving performance.<\/p>\nConfiguration Fetching<\/strong>
\nCMP configuration fetching is used to dynamically load the latest CMP configuration settings and vendor lists from a remote server. This process ensures that the plugin operates with the most current data, improving security, compatibility, and functionality.<\/p>\nService Provider Information<\/h4>\n
Service URL<\/strong>: Amazon Web Services<\/a>
\nPrivacy Policy<\/strong>: AWS Privacy Policy<\/a>
\nTerms of Use<\/strong>: AWS Terms of Use<\/a><\/p>\nLegal Protection<\/strong>
\nFor your protection and to ensure transparency, we disclose the reliance on third-party services within our plugin. The URLs above provide detailed information on the terms of use and privacy policies of AWS. Users are encouraged to review these documents to understand the terms and conditions under which these third-party services operate.<\/p>\nBy using our plugin, you acknowledge and agree to these terms and conditions. If you have any questions or concerns, please refer to the provided links or contact us directly for more information.<\/p>\n
License<\/h3>\n