What is Google Additional Consent?

Google Additional Consent (AC) is a specification that lets cookie banners signal consent to Google Ad Tech Providers (ATPs): advertising technology companies that work with Google but aren’t registered on the IAB Global Vendor List (GVL).

The IAB Transparency and Consent Framework (TCF) is the industry standard for consent signaling in digital advertising. It maintains the GVL, a list of registered ad tech vendors. When your cookie banner collects consent, it communicates those choices to vendors on that list. Google Additional Consent extends that signaling to cover Google’s ATPs, which operate outside the GVL.

Without Google Additional Consent, consent signals wouldn’t reach those providers at all.

Google Additional Consent v1 and v2: what’s the difference?

Google Additional Consent has two versions: v1 and v2. Both signal consent to Google ATPs, but they differ in format and capabilities.

ACv2 updates the format used to signal consent and adds the ability to declare disclosed vendors. It aligns with more recent TCF implementations and Google’s current requirements.

Which version of Google Additional Consent should I use?

Use v2. It’s the current standard and keeps your setup compatible with Google’s advertising ecosystem going forward.

iubenda sets gacVersion to 2 by default. If you haven’t explicitly set a version in your configuration, your setup already uses v2. If you have gacVersion: 1 in your configuration, we recommend switching to 2.

When should I stay on Google Additional Consent v1?

In most cases you won’t need to. But if your setup includes a legacy integration built around the v1 AC string, internal scripts that expect the v1 format, or a complex ad stack where changes need careful testing, you may want to stay on v1 temporarily while you prepare for the switch.

How to configure Google Additional Consent

Using the Privacy Controls and Cookie Solution Configurator

Enable Google Additional Consent from the Privacy Controls and Cookie Solution Configurator, under the IAB TCF settings. To configure the version (v1 or v2), use the configuration script below.

Using the configuration script

To configure Google Additional Consent manually, add both googleAdditionalConsentMode and gacVersion to your _iub.csConfiguration object, before the iubenda Privacy Controls and Cookie Solution script.

googleAdditionalConsentMode: true enables Google Additional Consent. gacVersion sets the version (1 or 2).

To enable Google Additional Consent with v2 (recommended):

<script>
window._iub = window._iub || {};
_iub.csConfiguration = {
googleAdditionalConsentMode: true,
gacVersion: 2
};
</script>

To enable Google Additional Consent and keep v1:

<script>
window._iub = window._iub || {};
_iub.csConfiguration = {
googleAdditionalConsentMode: true,
gacVersion: 1
};
</script>

If you’re using the unified embed code, add this block immediately before the main iubenda script tag.

Need help?

Reach out to us via support if you need any further assistance.

The post Google Additional Consent: what it is and how to configure it appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

The new iubenda’s Accessibility Widget uses AI-powered adjustments to automatically make your website more accessible for users with various disabilities. The solution supports a range of accessibility features, making it easier for users to navigate and interact with your site.

What is iubenda’s Accessibility Widget?

iubenda’s Accessibility Widget is a fully automated widget designed to enhance your website’s accessibility. It adjusts your website in real-time to accommodate the needs of users with disabilities, including options like text resizing, high-contrast modes, screen reader compatibility, and more. Key features include:

• Screen Reader Compatibility: Helps make your website readable by screen readers for visually impaired users.
• Contrast and Text Resizing: Allows users to adjust the contrast and font size to suit their needs.
• Keyboard Navigation: Improves keyboard navigation for users with motor impairments.
• Control Over Dynamic Content: Lets users with epilepsy or other conditions stop animations or dynamic content that might be harmful.

With a simple installation process, you can get started right away without having to overhaul your website’s code.

Step 1: Activating the Accessibility Widget

1. Go to the iubenda Dashboard: From your iubenda Dashboard, find the Accessibility Widget tile under your available products.
2. Activate the Widget: Click the Activate button to start using the Accessibility Widget.

Step 2: Customizing the Accessibility Widget

Once you’ve activated the Accessibility Widget, you can make it match your website’s look and feel by using the Accessibility Widget Configurator. This tool is available for both new pricing plans and legacy plans.

1. Go to your iubenda Dashboard.
2. Find the Accessibility Widget tile.
3. Click on the Settings button to open the configurator.

The configurator will look like this:

Inside the configurator, you’ll find several options to make the widget your own:

• Trigger Button Position: Choose where the widget’s button appears on the screen: Top-left, Bottom-left, Bottom-right, Top-right

The main widget panel will always open from the bottom of the screen.

• Widget Background Color: Change the background color to better fit your site’s design. (Text customization is not available yet.)
• Trigger Button Appearance: Adjust both the icon color and the background color of the trigger button.
• Default language: Set the default language for the widget’s interface, making it more accessible for your audience.
• Accessibility Statement URL: Add a custom link to your site’s accessibility statement, so users can easily find it.

Any changes you make in the configurator will be applied automatically to your Accessibility Widget, even if it’s already embedded on your website.

Step 3: Installing the Accessibility Widget on Your Website

Once you’ve activated and configured the widget, you can embed it on your site.

1. Embed the Widget: Copy the provided snippet of code for the Accessibility Widget and paste it at the very beginning of the head section of your website (right after the <head> tag) to install the widget.



2. Verify the Widget’s Functionality: After embedding, refresh your website to ensure the widget is visible and functional. You should now see a small accessibility icon:

How it Works for End Users

Once the Accessibility Widget is embedded and active on your website, end users will be able to interact with it to customize their browsing experience. As users change their settings through the widget, real-time adjustments are made to the website’s layout, ensuring that the content is instantly optimized based on the selected preferences. Here’s how the widget behaves and the features it provides:

1. Widget Appearance: The Accessibility Widget appears as a small icon, when users click on the icon, it opens a menu of accessibility options, providing a seamless way to adjust the website’s layout.



2. User Preferences: The widget lets users select their accessibility preferences, such as:
• Text size: Users can adjust the size of the text for better readability.
• Contrast settings: Adjust the contrast to make content stand out more clearly, especially for those with visual impairments.
• Other display options: The widget also offers a range of display settings to cater to different needs, making it easier for users to navigate the site in a way that suits them best.
• Text size and style: Enlarges or adjusts text in a way that makes it more readable without requiring a page reload.
• Contrast: Applies changes to background and text colors to enhance visibility for users with color blindness or low vision.
3. Dynamic Content Control: For users who may be sensitive to animations or flashing content, the widget gives them the option to turn off animations or modify the behavior of dynamic content. This is particularly beneficial for individuals with conditions like epilepsy.
4. Enhanced Navigation: In addition to visual changes, the widget improves keyboard navigation by optimizing focus order, making it easier for users with motor impairments to navigate and interact with the page efficiently.
5. Screen Reader Compatibility: The widget ensures that all elements are compatible with screen readers, ensuring that visually impaired users can easily understand and interact with all the content on your site.
6. Convenient and Accessible: The accessibility settings remain easily accessible at any time, with the widget floating in a fixed position on the site, allowing users to make changes whenever they need to.

With iubenda’s Accessibility Widget, you can improve your website accessibility and provide a better, more inclusive experience for all users.

The post Getting Started with iubenda’s Accessibility Widget: A Step-by-Step Guide appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Powerful Solutions for Digital Accessibility

iubenda offers accessibility solutions developed in collaboration with AccessiWay, designed to support businesses of all sizes in starting their journey toward greater accessibility.

All prices above are intended VAT included.

*Alt text is automatically added to your first 20 images for enhanced accessibility.

**Accessibility profiles combine related settings designed to help users with specific disabilities. Visitors can select the profile that works best for them. Profiles available: Seizure Safe Profile, Vision Impaired Profile, ADHD-Friendly Profile, Cognitive Disability Profile, Keyboard Navigation Profile (Motor), and Blind Users Profile (Screen-readers).

***Sites that exceed this limit will be required to upgrade to the Accessibility Widget Standard tier to maintain accessibility coverage.

Why iubenda’s Accessibility Widget Makes Sense for Your Business

1. Budget-Friendly Options

We offer two tiers of accessibility solutions with transparent pricing to provide essential features at price points that make sense for businesses of all sizes.

2. Simple Implementation

No complex integration or technical expertise required. Both solutions install quickly and start working immediately, with minimal configuration needed.

3. Tailored Feature Sets

Our tiered approach ensures you get exactly what you need—essential features for smaller sites or comprehensive capabilities for larger ones—without paying for unnecessary functionality.

4. Scalable Solutions

As your business grows, you can easily upgrade from Accessibility Widget Lite to Accessibility Widget Standard to accommodate increased traffic and more advanced needs. Your accessibility solution grows with your website.

Need Enterprise-Level or Custom Accessibility Services?

For large enterprises with advanced accessibility requirements, AccessiWay offers specialized consulting services to complement our accessibility solutions:

• Detailed accessibility auditing and compliance evaluation
• Expert consulting and tailored accessibility strategy
• Custom implementation support
• Custom accessibility statement
• Ongoing compliance management
• Advanced technical capabilities for complex websites

Their enterprise services include:

Litigation Support Package – Proactive legal protection

Service Level Agreement (SLA) – Guaranteed performance

Dedicated Account Manager – Expert guidance on compliance

Specialized Consultancy Services – Tailored accessibility strategy

Through our partnership with AccessiWay, we can connect you with these enterprise-level services to complement your iubenda accessibility solution.

The post iubenda’s Accessibility Widget: Which Version Is Right for Your Business? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In the context of UET Consent Mode, first-party cookies are generated by your website’s domain (the advertiser), while third-party cookies are created by Microsoft Advertising (e.g., Bing.com).

How It Works

Consent mode is set via a property in UET called ad_storage. The possible values for ad_storage are:

Set Up Microsoft Consent Mode with iubenda Privacy Controls and Cookie Solution

iubenda Privacy Controls and Cookie solution provide built-in out-of-the-box support for UET consent mode, both using Autoblocking or having the iubenda.com/sync snippet in your configuration available in all the recent integration codes.

If your code is provided with one of the two snippets, you don’t have to do any additional steps: Autoblocking or sync snippet will take care of setting automatically the default state (ad_storage to denied) and send the update signal as soon as the user updates their preferences via the existing global window.uetq property.

And you’re done!

Validating Consent Mode Implementation with UET Tag Helper Browser Plugin

To verify the implementation of Consent Mode within UET you can:

• Check in the browser console the value of window.uetq before and after the consent is granted or denied by the user.
• Use the UET Tag Helper available for Edge and Chrome.

The post Microsoft Universal Event Tracking (UET) Consent Mode appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Features

This all-in-one solution lets you integrate all iubenda compliance solutions with a single installation, and basic setup is completely free.

The app scans your site and auto-configures everything based on your site’s specific needs.

All our solutions are fully responsive (perfect for all screen sizes) and WCAG Level AAA Compliant.

Our solutions are automatically updated when laws change, so they are always up-to-date. The built-in site scanner runs periodic scans on your site and alerts you if it detects anything that should be added to your compliance documents.

How to start

As a Duda user, you can easily install and configure the app to make your website compliant with iubenda. Follow these steps to get started:

Firstly, you need to add the app. Start by choosing your site. From the Site List page in your Duda dashboard, select the site where you want to install the app.

Go to the Duda Site Editor page for your chosen site. Click on “App Store” from the Sidebar menu. Search for “iubenda” and click “+Install“

• Note: If you have already added the app, click “Open” instead.

After clicking “+ Install” a pop-up window will appear. Choose your preferred iubenda plan and click “Choose“

Note: For a simplified cookie banner/consent banner, and privacy policy setup, you can choose the FREE plan to get started.

Once you select a plan, the installation process will start automatically. Wait until it is completed.

After installation, you’ll see a loading page. Our app will automatically scan your site and provide a rating based to your site’s specific needs.

Once website scanning is completed, a percentage rating appears on the Welcome to iubenda! page, here you can find your site’s compliance elements summarized including the iubenda products to be configured or activated.

After installing the app, you can click on “Setup” to proceed to the product configurator, or simply click “Dashboard” at any time to setup and configure services as needed. If your current plan does not include any of the products or features you wish to activate, click “Upgrade”.

You can also click on “Make My Website Compliant!” to proceed with plan configuration.

Finally, once you have activated and provisioned your iubenda products, you can directly access the configuration tiles from the Site Editor to start making your site compliant in minutes.

Now You Are Ready to Set Up and Configure Services According to Your Needs

To make your website compliant, you can start by activating and using the iubenda solutions. Let’s briefly explore what you can achieve with them:

Privacy Controls and Cookie Solution

Includes cookie banner/CCPA notice, and cookie consent management (blocking scripts until consent is collected as legally required). Free basic setup and full CCPA support.

• Easy and guided set-up: Analyzes your site and auto-configures everything to make set-up as easy as possible.
• Fully customizable cookie banner – change functionality, design, location, colors, add your logo and more.
• Asynchronously re-activates cookie scripts once consent is collected (no page reload needed).
• Lightning-fast: won’t affect page performance.
• Auto-detects and blocks a wide range of 3rd party scripts like Google Analytics, Google Maps, Facebook and Instagram widgets, Youtube, Twitter, PayPal, Disqus, Outbrain, AdRoll, Kissmetrics, Freshchat and more.
• Allows you to provide your users with granular, per-category preference control (e.g. basic functionalities, experience enhancement, targeting & advertising)
• Google Consent Mode (both Basic and Advanced implementations; no extra setup required): Enables efficient conversion tracking even without user consent for cookies and tracking technologies, enhancing Google Analytics and Ads performance.
• Integrates with IAB’s Transparency and Consent Framework (TCF) to maximize ad revenue (needed if your site uses ad networks like Google ads and more)
• Compatible with Google’s Accelerated Mobile Pages (AMP)
• Allows you to auto-detect and limit prior-blocking and cookie consent requests only to users from the EU – where this is a legal requirement for GDPR compliance – while running cookies scripts normally in regions where you are still legally allowed to do so.
• Features an easy-to-use interface for entering custom scripts and iframes
• Cookie database feature allows you to auto-set cookie lifetime information.
• Display CCPA / CPRA notice and opt-out link as required by the California Consumer Privacy Act
• Provides cookie consent analytics for high-traffic sites.
• Detects bots/spiders and serves them a clean page so that your SEO efforts are never compromised

For more customization options, go to your Dashboard and click “Manual.” Next, select “Configure cookie banner by clicking here” to set up your cookie banner on our website. Once you’re finished, paste the embed code and click “Save snippets”, to complete the integration.

Need more help? Check out our full guide on the Privacy Controls and Cookie Solution for step-by-step instructions on configuring your cookie banner.

Privacy and Cookie Policy Generator

This solution lets you generate professional privacy and cookie policies in minutes.

• Super easy interface, guided process, fully customizable
• All legal text written by actual legal professionals
• Quick select from over 1900 clauses or create custom clauses
• Activate cookie policy in a single click
• Site Scanner to quickly detect which services/ clauses you need to add to your policies.
• One-click translation. 15 languages supported: Czech, Danish, Dutch, US English, UK English, French, German, Greek, Italian, Polish, Portuguese, Brazilian Portuguese, Russian, Spanish, Swedish
• One-click activation for country/ region-specific text.
• Compatible with Google’s Accelerated Mobile Pages (AMP)
• Documents are remotely updated when legal requirements change
• Manage documents for multiple sites from a single dashboard
• White label option allows you to seamlessly integrate your privacy policy text into the body of your webpage

To start configuring, click the Configure button under Privacy and Cookie Policy. Then, select “Setup your privacy and cookie policy on iubenda.com.” This will open the Privacy and Cookie Policy Generator on iubenda.com, where you can easily set up and edit your policy.

Need help setting up your privacy policy? Check out this guide for step-by-step instructions on using your iubenda dashboard.

Consent Database

Collect consent, document opt-ins and opt-outs via your web forms. This solution smoothly integrates with your consent collection forms to auto-create legally required GDPR and LGPD consent records.

About Legal requirements and Consent Records

These records should include a userid, timestamp, consent proof, record of the consenting action, and the legal documents available to the user at the time of consent, among other things.

This app is THE most complete solution for recording, sorting and maintaining GDPR & LGPD records of consent for optimal privacy compliance.

The app also boasts built-in compatibility with WordPress comment form, Contact Form 7, Elementor forms and WP Forms plugins for your convenience, but can be manually integrated with any type of web-form and can even store consent proofs for consents collected offline (e.g in-store sign-ups) via WP media upload.

• It’s auto-compatible with and allows super easy mapping of Contact Form 7, WP Forms, WordPress comment, Mailchimp for WordPress, Germanized for WooCommerce, Elementor forms and WooCommerce checkout forms
• Also allows manual integration with any type of web-form
• For each consent, track the form/wording the user was prompted with at the time of the consent collection
• Accurate timestamping and recording of consenting action
• Flexibly upload any form of proof of consent or legal notice, including a PDF if consent was collected offline
• It provides a high granularity: map individual form fields, exclude fields (like password inputs), add legal notices available at the time of consent collection, indicate double opt-in, set preferences and more
• REST HTTP API and JS SDK, to give you total control and how and when consent is stored
• Store multiple preferences for each user (e.g. if you have multiple newsletters or opt-ins)
• Features an easy-to-use interface for entering custom scripts and iframes
• It provides API input field for quick and easy activation

To get started, activate the Consent Database in your iubenda dashboard on iubenda.com and paste the API key when prompted.

After that, remember to click on Save settings at the bottom right of the page.

Once saved, you can configure your Consent Database by following this detailed guide.

Terms and Conditions

Create your terms and conditions in minutes.

Customizable from hundreds of combinations, available in 15 languages, powerful and precise — our solution is capable of handling even the most complex, individual scenarios. Optimized for e-commerce, marketplace, SaaS, apps and more.

• Easy, guided set-up
• Expertly crafted at the hands of our international legal team
• Pre-defined scenarios modules for everything from basic disclaimers to copyright licenses, account terminations rules, product-comparison, age-related disclaimers, virtual currency, and more.
• Plug-and-go integrations for popular eCommerce solutions like Shopify, Wix, Squarespace, Weebly, WooCommerce, PrestaShop and more
• One-click translation (15 languages supported Czech, Danish, Dutch, US English, UK English, French, German, Greek, Italian, Polish, Portuguese, Brazilian Portuguese, Russian, Spanish, Swedish)
• Compatible with Google’s Accelerated Mobile Pages (AMP)
• Manage documents for multiple sites from a single dashboard
• White label option allows you to seamlessly integrate your privacy policy text into the body of your webpage

To start, activate and configure your Terms and Conditions on the iubenda website. You can follow our step-by-step guide to the generation here.

Then, paste the embedding code and choose from the integration preferences provided.

Once you’re done, remember to click on Save settings at the bottom right of the page.

Pricing

About iubenda

We help companies all over the world to keep their websites and apps compliant with international privacy laws for optimal peace of mind. More here.

Languages

Our services are currently available in the following languages:

• English US and UK
• Italian
• French
• Spanish
• Portuguese
• Brazilian Portuguese
• German
• Dutch
• Russian
• Czech
• Swedish
• Danish
• Greek
• Polish

Support & Updates

All our solutions and plugins are regularly updated and well maintained to ensure that you’re always protected.

You can access our friendly support in multiple languages (currently EN, IT, DE, FR, PT, PT-BR) via info@iubenda.com, our onsite chat (just click the green Help button on the right side of the page).

Other links:

• Documentation
• Feedback & Support forum

FAQ

The post iubenda app for Duda | All-in-one Compliance for GDPR / CCPA Cookie Consent, and more appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Understanding the Issue

Ad-blockers can prevent cookie banners or privacy notices from appearing on your website. This might seem problematic because it could appear that you’re not informing visitors about cookie usage or collecting their consent. However, compliance can still be achieved by understanding a few things, let’s see!

GDPR Compliance and Accountability

Under the GDPR, website owners (Data Controllers) must follow the accountability principle. This means they need to show they have procedures in place that allow users (Data Subjects) to exercise their privacy rights.

Key Points:

1. Accountability Principle: Website owners must prove they have implemented processes to protect user privacy.
2. User Consent: If users willingly use ad blockers, they effectively waive certain privacy rights, as stated in the tool’s terms and conditions.
3. No Liability: Data Controllers can avoid liability if they show they comply with GDPR and have no control over users’ use of ad blockers. This is supported by Article 82(3) of the GDPR.

US Perspective on Privacy Compliance

Similar principles apply in the US. Website owners (Controllers) must demonstrate accountability and show they have enabled individuals to exercise their privacy rights. If individuals willingly use tools that block privacy features, they waive some of their rights.

Key Points:

1. Accountability: Controllers must show they have implemented privacy procedures.
2. User Consent: Conscious use of ad blockers means users waive certain privacy rights.
3. No Liability: Controllers are not liable if they comply with legal requirements and cannot control the use of ad blockers.

Best Practices for Website Owners

1. Implement Privacy and Cookie Policies: Ensure you have all necessary GDPR measures in place, including a comprehensive Privacy Policy and Cookie Policy. Clearly outline how your site handles data and cookies.
2. Detecting Ad-Blockers: According to the European Commission, you can detect if a user is using an ad-blocker without needing their prior consent. This detection should be included in your Privacy Policy, explaining that it’s necessary to ensure proper consent management. You can easily integrate this detection via a custom clause using iubenda’s generator as detailed here.
3. Inform Users: If an ad-blocker is detected, inform users that their use of such tools may prevent them from seeing important privacy notices and cookie consent banners. Encourage them to disable the ad-blocker for full functionality.

How You Can Integrate Ad-Blocker Detection into Your Privacy Policy with iubenda

To add a custom service for ad-blocker detection to your iubenda privacy policy, you can follow these detailed steps:

1. Log in to your iubenda account and go to the Dashboard.
2. Once in the Privacy and Cookie Policy generator, choose the "Add service" option.
3. Click on "Create custom service." This will lead you to the input prompts for creating a custom clause.
4. Fill Out Mandatory Fields
   • Service Name: Enter a clear and concise title, such as "Ad-Blocker Detection"
   • Privacy Policy Description: Detail the types of data collected by the ad-blocker detection service, how this data is used, and if shared with any third parties. Include information about the third party, if applicable, such as their headquarters location and a link to their privacy policy.
5. Optional Fields:
   • Purpose: Assign a purpose from the provided drop-down list to categorize the data collection activities. For example, you might select "Handling activities related to compliance"
   • Show this service on: Specify where this service will appear—either in the privacy policy, the cookie policy, or both.
6. By checking the "Specify service translations" box, you can provide translations for different languages, ensuring your policy is accessible and clear to all users.
7. Once all fields are completed, save the custom service. It will automatically integrate into your privacy policy text, ensuring that it appears seamlessly alongside other pre-made clauses.

By following these steps, you ensure that the ad-blocker detection feature is transparently disclosed in your privacy policy, helping to maintain compliance with GDPR and providing users with clear information about data collection practices.

While ad blockers and certain browsers can pose challenges, demonstrating that your site has the necessary privacy tools installed will keep you compliant with GDPR and other privacy and cookie laws. This proactive approach helps protect your business and ensures that you are fulfilling your legal obligations.

Legal Framework and Liability

Perimeter of Liability of the Controller: The concept of “strict” liability in GDPR means that a controller may be held liable even in the absence of personal fault. This applies particularly to (1) obligations that impose a result-based requirement on the controller and (2) liability for actions taken by processors under the controller’s authority.

• Recital 74; Article 24: The controller is responsible for implementing appropriate technical and organizational measures to ensure and demonstrate that its processing activities are compliant with GDPR requirements. These measures may include adopting a suitable privacy policy.
• Article 82(3): A controller or processor is exempt from liability if they can prove that they are not responsible for the event causing the damage.
• Recital 55 of Directive 95/46: Provides examples of how a controller might demonstrate that they are “not responsible for the event giving rise to the damage.”

The post How Ad-Blockers Affect iubenda’s Privacy Controls and Cookie Solution or Cookie Banner: What You Should Know appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Step 1: Ensure the iubenda Privacy Controls and Cookie Solution Script is Embedded

First, make sure that the iubenda Privacy Controls and Cookie Solution script is already embedded on your site.

Once the script is in place, you can customize it to prevent the banner from displaying on specific pages.

Step 2: Hide the Banner on a Specific Page

To hide the cookie banner on a particular page, you can implement a quick adjustment, by adding a custom script after the iubenda Privacy Controls and Cookie Solution script. For example, if you want to hide the banner on your cookie policy page, follow these steps:

1. Identify the page where you want to exclude the banner. In this example, let’s say the URL is http://provawordpress.local/cookie-policy/.
2. You can add a simple rule that ensures the banner won’t appear on that specific page.

Here’s an example of how you can achieve this:

<script>
if(window.location.pathname === "/cookie-policy/") { 
    
     document.head.innerHTML = document.head.innerHTML + '<style>div#iubenda-cs-banner { display: none !important; } </style>';

}
</script>

In this case, the banner will be hidden when someone visits the cookie-policy page.

Here’s an example of how this script might look:

<script type="text/javascript">
var _iub = _iub || [];
_iub.csConfiguration = {"cookiePolicyUrl":"http://provawordpress.local/cookie-policy/","consentOnContinuedBrowsing":false,"enableTcf":false,"whitelabel":false,"lang":"en-GB","siteId":1129739,"floatingPreferencesButtonDisplay":"bottom-right","perPurposeConsent":true,"cookiePolicyId":33731144, "banner":{ "closeButtonRejects":true,"acceptButtonDisplay":true,"customizeButtonDisplay":true,"explicitWithdrawal":true,"position":"float-top-center","closeButtonCaption":"<button type=\"button\" class=\"iubenda-cs-close-btn\" tabindex=\"0\" role=\"button\" aria-pressed=\"false\" style=\"background-color: rgb(239, 239, 239) !important; border-radius: 55px !important; border: 1px solid rgb(119, 119, 119) !important; font-size: 16px !important; font-weight: bold !important; padding: 10px 20px !important; height: 34px !important; color: rgb(102, 102, 102) !important; visibility: visible;\">Continue without accepting</button>" }, "footer":{"btnCaption":"Custom Test Here"}};

</script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/tcf/stub-v2.js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

<script>

//custom script to add

if(window.location.pathname === "/cookie-policy/") { 
    
     document.head.innerHTML = document.head.innerHTML + '<style>div#iubenda-cs-banner { display: none !important; } </style>';

}
</script>

Step 3: Customize for Any Page on Your Website

You can easily apply this same logic for any other page on your website. Let’s say you want to hide the banner on a different page, like www.test.com/about-us. In that case, simply update the script to match the URL of the page where you want the banner hidden.

For example:

<script>
if(window.location.pathname === "/about-us/") { 
    
     document.head.innerHTML = document.head.innerHTML + '<style>div#iubenda-cs-banner { display: none !important; } </style>';

}
</script>

This script will hide the banner whenever a user visits the /about-us/ page.

This small adjustment allows you to decide where the iubenda cookie banner displays on your website. Whether you want to hide the banner on a specific policy page or any other section of your site, you can easily customize the banner’s visibility according to your needs.

The post How to Hide the iubenda Banner on Specific Pages appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In this guide, we’ll walk you through how to easily set up and manage webhooks for 2-Way Sync, ensuring your consent data is always up-to-date across all your platforms.

1. Accessing the Webhooks Section in iubenda

1. Go to Settings: From the iubenda Dashboard, select the project and click the settings icon.
2. Open Consent Database Webhooks: In the side menu, click on “Consent database webhooks“. This section is your starting point for setting up the synchronization between the Consent Database and your connected platforms.



3. Activate the Consent Database (If required): If the Consent Database is not yet active, you’ll see a message: “To start setting up webhooks, you first need to activate the Consent Database.” Click Activate Consent Database and follow the prompts.



4. If your Consent Database is already active, proceed to create a new webhook. You’ll see a description of how webhooks work, with a “+ Create a new webhook” button available to get started.

2. Creating a New Webhook

Setting up a webhook lets you automatically synchronize and notify connected platforms about consent status changes. Here’s how to set one up:

1. Click “+ Create a new webhook”, this will open the webhook creation modal.
2. Select the Webhook Type: You’ll see two options at the top:

• Inbound: Use this to automatically update your Consent Database when a specific event, like a user consent change, is triggered on an external platform. It reacts to updates made outside the Consent Database (e.g., a user updating their preferences in your CRM or email tool), ensuring those updates are promptly reflected within your database.
• Outbound: Use this to notify external systems whenever an event, such as a consent status change, is registered in your Consent Database.

In some cases, the Consent Database can serve as a bridge between two platforms. For example, an inbound webhook can capture consent changes from a platform like Mailchimp, and an outbound webhook can send those updates to another platform, like HubSpot. This allows you to keep all systems in sync through iubenda, without manual intervention.

Let’s go through how to set up each type.

3. How to Set Up an Inbound Webhook

An inbound webhook is used to automatically update the Consent Database when user actions, like consent changes, occur on an external platform. For example, if a user opts in to your newsletter via a form on your website, this change will automatically sync with your Consent Database.

Step-by-Step Instructions

1. Choose the “Inbound” Tab.

2. Specify the Preference to Be Updated:

• Newsletter (These details are based on the Newsletter Opt-in Booster naming):
  • Use the dropdown to select the preference value (e.g., True for Subscribed, False for Unsuscribed). This refers to the actual value associated with the user’s consent preference in your Consent Database.

  

• If you wish to use different names and values, choose the ‘Custom’ option below. (This option is needed if you’ve set up custom preferences or values that are specific to what you’re saving in the Consent Database.)
  • Enter your custom preference name (e.g., tosAccepted).
  • Enter the value (e.g., true). Remember, both fields must be filled.

  

3. Click “Save” to complete the setup and save the webhook.

Your Consent Database will now automatically receive updates whenever the specified event occurs, matching the subject’s email and updating the corresponding consent status.

4. How to Set Up an Outbound Webhook

An outbound webhook sends notifications to external systems (like Mailchimp or your CRM) whenever there’s a change in the Consent Database. This is useful for keeping your platforms updated with the latest consent preferences.

Step-by-Step Instructions

1. Select the “Outbound” Tab.

2. Specify the Endpoint URL: Enter the URL where updates should be sent. (Note: This is a required field.)
3. Choose the Preference to Track:

• Newsletter (These details are based on the Newsletter Opt-in Booster naming):
• Optionally, select “Set for specific preference value only” to track changes for a specific value and use the dropdown to select the preference value (e.g., True for Subscribed, False for Unsubscribed).

• If you wish to use different names and values, select the ‘Custom’ option below.”
  • Enter a custom preference name (e.g., tosAccepted).
  • If you only want to send notifications for specific values, check “Set for specific preference value only” and enter the value (e.g., true).

  

3. Click “Save” to create the outbound webhook.

It will now notify the specified platform whenever the chosen consent changes occur in the Consent Database.

5. Managing Webhooks in the Consent Database Dashboard

Activating or Pausing Webhooks

Each webhook (inbound or outbound) has a toggle switch that allows you to enable or pause updates. This control is helpful when you need to temporarily stop syncing data.

Editing a Webhook

Find the webhook you want to modify and click the “Edit” button. This opens the webhook setup interface, where you can change the endpoint URL, tracked preferences, or any other settings. Click Save to apply the updates.

Deleting a Webhook

To delete a webhook, click the trash icon next to it. A confirmation prompt will appear to ensure you want to proceed. Click “Confirm” to permanently remove the webhook.

Webhooks in iubenda’s Consent Database are a powerful way to keep your marketing tools, CRMs, and other platforms updated with the latest consent preferences. With just a few clicks, you can ensure that user preferences are always in sync across your platforms, helping you maintain compliance and streamline your processes.

The post How to Keep Your Consent Data in Sync Across Different Platforms with iubenda’s 2-Way Sync appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

If you see your analytics numbers dropping, you’re not alone. Many website owners observe a decrease in analytics figures after implementation, which can be quite concerning. However, this is a normal effect of how Google Consent Mode works. Let’s dive deeper to understand why this occurs.

Google Consent Mode v2 and its advanced features, along with Google Analytics 4’s (GA4) behavioral modeling, play a significant role in understanding this data loss. When you first switch to Consent Mode v2, especially without using its previous version, you might see a significant drop in your reported data. This reduction might alarm you, but the duration of this data loss depends on specific aspects of GA4’s behavioral modeling.

Here’s what needs to happen for behavioral modeling, which helps compensate for lost data when users do not consent to analytics, to start working:

1. Advanced Consent Mode Usage: Your site should use not only the basic features of Consent Mode but also its advanced functionalities.
2. Required Data Volume: Your site needs to collect at least 1,000 events per day where analytics storage is denied (analytics_storage=’denied’) for at least seven consecutive days.
3. Minimum User Engagement: You need at least 1,000 daily users sending events with analytics storage granted (analytics_storage=’granted’) for at least seven of the past 28 days.

After your site meets these conditions, it qualifies for behavioral modeling. Initially, you may see a steep decline in your data, but as the site complies with the behavioral modeling criteria, you will observe a recovery in data collection, though there may still be a gap from when the conditions were unmet.

What Can You Do?

If you’re facing these challenges, here are a few strategies you could try:

• Drive More Traffic: Boosting your site’s traffic can help meet the thresholds needed for behavioral modeling.
• Estimate Manually: If some of your visitors consent to tracking, manually estimate your overall traffic based on this data.
• Explore Other Analytics Tools: Use tools like Google Search Console for verification, or switch to privacy-focused analytics platforms like Piwik Pro or Microsoft Clarity, which offer privacy considerations similar to those of Universal Analytics.

The post Why Is Data Decreasing After Installing Google Consent Mode v2? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Adding a HubSpot cookie banner to your website is easy with iubenda’s Privacy Controls and Cookie Solution. Just follow these steps, and you’ll have it up and running in no time!

How do I add a cookie banner in HubSpot?

To add a cookie banner in HubSpot, you simply create a JavaScript file with the iubenda code, attach it to your site’s template, and include it on all relevant pages.

Here’s the step-by-step process

Step 1: Create a New JavaScript File for the iubenda Privacy Controls and Cookie Solution

1. Go to Your HubSpot Account:

• Click on Marketing then Design Tools.

2. Create a New File:

• In the sidebar, click File > New file. (You might need to click the folder icon first.)
• Choose JavaScript from the “What would you like to build today?” dropdown.
• Click Next.

3. Name Your File:

• Type in a name for your script in the File name field.

4. Select File Location:

• Click Change in the File location section and pick a folder.
• Click Create.

5. Enter the iubenda Code:

• Paste the iubenda Privacy Controls and Cookie Solution code into the editor.
• If ESLint shows warnings or errors, use the Show output switch to see them.
• Click Publish changes when you’re done.

Still Without a Cookie Banner?

---

Easily generate a compliant cookie consent banner for free with our user-friendly generator.

Generate your Free Cookie Banner for HubSpot Now!

Step 2: Attach the iubenda Privacy Controls and Cookie Solution to a Template

1. Find Your Template:

• Use the finder on the left to pick the template you want to update.

2. Edit Template:

• In the inspector on the right, click the Edit tab.
• Under Linked JavaScript files, click Add and select your iubenda script.
• Click Publish changes to finish.

Step 3: Include the iubenda Privacy Controls and Cookie Solution on HubSpot Pages

1. Accessing the File’s Public URL:

• Find your script in the sidebar and click Actions > Copy public URL.

2. Add Script to All Pages on a Domain:

• Go to Settings: Click the settings icon in the main navigation bar.
• Navigate to Your Site’s Pages: Choose Website > Pages in the sidebar.
• Select Your Domain: Use the dropdown to pick a domain or set it for all domains.
• Add Your Script: In Site footer HTML, paste the script tag with your public URL.



Example:

<!-- start iubendaCookieSolution.js Do Not Remove -->
<script src='insert your file's public URL here'></script>
<!---End iubendaCookieSolution.js-->

• Click Save.

3. Add Script to an Individual Page:

• Edit Your Page: Go to Marketing > Website > Website Pages or Landing Pages. Hover over a page and click Edit.
• Page Settings: Click the Settings tab, then Advanced options.
• Insert Your Script: In Footer HTML, paste the script tag with your public URL.



Example:

<!-- start iubendaCookieSolution.js Do Not Remove -->
<script src='insert your file's public URL here'></script>
<!---End iubendaCookieSolution.js-->

• Click Update in the upper right to apply your changes.

That’s it! You’ve successfully added a cookie banner to your HubSpot site using iubenda.

FAQs

See also

• How to add Terms and Conditions on HubSpot
• How to add a Privacy Policy on HubSpot
• HubSpot Analytics and the GDPR – How to be compliant
• Consent Database for Hubspot

The post HubSpot Cookie Banner: How to Add a Cookie Banner on HubSpot with iubenda appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Google Analytics for Firebase offers a consent mode that allows you to adjust the SDK’s behavior based on your user’s consent status. This guide will walk you through integrating Google Consent Mode v2 for Firebase Analytics using the iubenda SDK.

Integrating Google Consent Mode v2 in your App

Before starting, ensure Firebase SDK is correctly integrated into your app. Find more information here for Android and iOS. Follow this guide to integrate the iubenda SDK with your app.

Setting Up Consent Mode

To set up Consent Mode v2 in your app, you need to:

1. Set the default consent state: By default, no consent mode values are set. You need to define these in your app’s manifest (Android) or Info.plist (iOS) file.
2. Update consent values: Based on user preferences captured through the iubenda SDK, update the consent values in Firebase Analytics.

Consider that consent types indicate the type of storage being used. These types include:

You can find the official documentation for using Consent mode with Firebase SDK here.

Let’s see how it works:

For Android Apps

1. Set default consent state

First, you need to set the default consent state for your app since by default, no consent mode values are set

To set them, open the manifest file (the AndroidManifest.xml) and add the consent mode key-value pairs.

The keys provided are: 

• google_analytics_default_allow_analytics_storage
• google_analytics_default_allow_ad_storage
• google_analytics_default_allow_ad_user_data
• google_analytics_default_allow_ad_personalization_signals

The keys are set with a value that indicates the consent state:

– true, meaning consent was granted, or 
– false, meaning consent was denied.

In the example below, we added all the default values set to false:

<meta-data android:name="google_analytics_default_allow_analytics_storage" android:value="false" />
<meta-data android:name="google_analytics_default_allow_ad_storage" android:value="false" />
<meta-data android:name="google_analytics_default_allow_ad_user_data" android:value="false" />
<meta-data android:name="google_analytics_default_allow_ad_personalization_signals" android:value="false" />

Next, you need to implement the consent values update method.

2. Update consent values

• Open the Activity/Fragment where you prompt the cookie notice with the iubenda SDK, 
• implement “IubendaCMPChangeListener” interface with this code:

public class MainActivity extends AppCompatActivity implements IubendaCMPChangeListener

• add “onConsentChanged()” override method to get consent changes:

@Override
public void onConsentChanged() {
}

Doing so, the iubenda SDK will trigger onConsentChanged() whenever a user sets their consent preferences (e.g. with the IubendaCMP.askConsent() method.

After capturing consent settings, you need to send them to Firebase Analytics SDK

To update consent values after the user has expressed their preferences, you need to call the setConsent method.

Use this code to update the different consent values to granted:
@Override
public void onConsentChanged() {
Map<FirebaseAnalytics.ConsentType, FirebaseAnalytics.ConsentStatus> consentMap = new EnumMap<>(FirebaseAnalytics.ConsentType.class);
if(IubendaCMP.isPurposeEnabled(4)){
consentMap.put(FirebaseAnalytics.ConsentType.ANALYTICS_STORAGE, FirebaseAnalytics.ConsentStatus.GRANTED);
}
if(IubendaCMP.isPurposeEnabled(5)){
consentMap.put(FirebaseAnalytics.ConsentType.AD_STORAGE, FirebaseAnalytics.ConsentStatus.GRANTED);
consentMap.put(FirebaseAnalytics.ConsentType.AD_USER_DATA, FirebaseAnalytics.ConsentStatus.GRANTED);
consentMap.put(FirebaseAnalytics.ConsentType.AD_PERSONALIZATION, FirebaseAnalytics.ConsentStatus.GRANTED);
}
mFirebaseAnalytics.setConsent(consentMap);
} 

As you can see, the ANALYTICS_STORAGE consent type is mapped with the purpose 4 of the Privacy Controls and Cookie Solution (Measurement), while the others (AD_STORAGE, AD_USER_DATA and AD_PERSONALIZATION) are mapped on the purpose 5 of the Privacy Controls and Cookie Solution (Marketing).

Verify consent settings

To verify that your consent settings are working as expected,  enable verbose logging on your device, and in the Android Studio logcat, find the log message that starts with Setting consent. 

For iOS Apps

1. Set default consent state

First, you need to set the default consent state for your app since, by default, no consent mode values are set.

To set them, open the Info.plist file and add the consent mode key-value pairs.

The keys provided are: 

• GOOGLE_ANALYTICS_DEFAULT_ALLOW_ANALYTICS_STORAGE
• GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_STORAGE
• GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_USER_DATA
• GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_PERSONALIZATION_SIGNALS

The keys are set with a value that indicates consent state:

– true, meaning consent was granted, or 
– false, meaning consent was denied.

In the example below, we added all the default values set to false:

<key>GOOGLE_ANALYTICS_DEFAULT_ALLOW_ANALYTICS_STORAGE</key> <false/>
<key>GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_STORAGE</key> <false/>
<key>GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_USER_DATA</key> <false/>
<key>GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_PERSONALIZATION_SIGNALS</key> <false/>

Next, you need to implement the consent values update method.

2. Update consent values

• Open the ViewController where you prompt the cookie notice with the iubenda SDK, 
• implement “NSNotification.Name.ConsentChanged” selector with this code:

NotificationCenter.default.addObserver(self, selector: #selector(consentDidChange), name: NSNotification.Name.ConsentChanged, object: nil)

• add “consentDidChange()” method to get consent changes:

@objcfunc consentDidChange() {
}

Doing so, the iubenda SDK will trigger consentDidChange() whenever a user sets their consent preferences (e.g. with the IubendaCMP.askConsent(from: self) method.

After capturing consent settings, you need to send them to Firebase Analytics SDK.

To update consent values after the user has expressed their preferences, you need to call the setConsent method.

Use this code to update the different consent values to granted:

@objc func consentDidChange() {

var analyticsStorageGranted = false
var adStorageGranted = false
var adUserDataGranted = false
var adPersonalizationGranted = false

if(IubendaCMP.isPurposeEnabled(id: 4)){
analyticsStorageGranted = true
}else{
analyticsStorageGranted = false
}
if(IubendaCMP.isPurposeEnabled(id: 5)){
adStorageGranted = true
adUserDataGranted = true
adPersonalizationGranted = true
}else{
adStorageGranted = false
adUserDataGranted = false
adPersonalizationGranted = false
}

Analytics.setConsent([
.analyticsStorage: analyticsStorageGranted ? .granted : .denied,
.adStorage: adStorageGranted ? .granted : .denied,
.adUserData: adUserDataGranted ? .granted : .denied,
.adPersonalization: adPersonalizationGranted ? .granted : .denied,
])
}

As you can see, the analyticsStorage consent type is mapped with the purpose 4 of the Privacy Controls and Cookie Solution (Measurement), while the others (adStorage, adUserData and adPersonalization) are mapped on the purpose 5 of the Privacy Controls and Cookie Solution (Marketing).

Verify consent settings

To verify that your consent settings are working as expected, enable verbose logging on your device, and in the Xcode, find the log message related to the parameters. For example:

ad_storage is granted. 
analytics_storage is granted. 
ad_user_data is granted. 
ad_personalization is granted.

Remember, these settings help tailor your app’s functionality to respect user preferences and legal requirements. For detailed steps and code snippets, refer to the official documentation and ensure your app is set up correctly.

The post iubenda mobile SDK – Integration with Google Consent Mode v2 for Firebase Analytics appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Short on time? Jump to: How Iubenda’s Whistleblowing Management Tool Works.

Directive (EU) 2019/1937, also known as the Whistleblower Directive, came into effect on December 16, 2019. This directive marked the beginning of heightened protections for those who report breaches of EU law within their professional environment. It required Member States to align their national laws, guaranteeing a consistent protection level for whistleblowers throughout the EU.

This Directive emphasizes the significance of safeguarding whistleblowers and ensures that entities have appropriate channels for reporting breaches of Union law.

Understanding the EU Whistleblower Directive

Objective: Its primary intent is to set a baseline and align national legislations across the EU regarding the protection of individuals who disclose violations of Union law.

Implementation Timeline

• General Adoption: EU Member States had a deadline until December 17, 2021, to enact laws and regulations in line with the Directive’s requirements.
• Specific Provisions for Medium-Sized Entities: The Directive stipulates that private sector and legal entities employing between 50 and 249 individuals have until December 17, 2023, to implement an Internal Reporting Channel (IRC).

Key aspects and objectives of the EU Whistleblower Directive

• Broad Scope of Application: The directive covers a wide range of areas, including public procurement, financial services, money laundering, product and transport safety, nuclear safety, public health, consumer protection, environmental protection, and more.
• Multiple Reporting Channels: Whistleblowers are encouraged to use internal reporting channels within their organizations first, but if these are not effective or could lead to retaliation, they can also report directly to competent national authorities or even make a public disclosure in certain circumstances.
• Protection Measures: The directive sets out that member states should prohibit any form of retaliation against whistleblowers, including dismissal, demotion, harassment, and other forms of unfair treatment.
• Confidentiality: The identity of whistleblowers must remain confidential unless they give their express consent to disclose their identity.
• Public and Private Sector: The directive applies to both the public and private sectors. In the private sector, it applies to entities with more than 50 employees, unless a special provision is made for entities with fewer employees.
• Burden of Proof: If any adverse actions are taken against the whistleblower, presumably in retaliation to a report, then the burden of proof shifts to the person who has carried out the detrimental action to demonstrate that they acted for reasons other than retaliation.
• Support and Assistance: Member states are required to provide information, advice, and even free legal aid to whistleblowers to ensure they know their rights and are supported throughout the process.

IMPORTANT: iubenda has built a dedicated tool to help you manage written whistleblower reports, but the Directive also requires businesses to set up in-person and oral reporting methods within their internal channel (and to provide all the same protections to whistleblowers who use it).

iubenda’s Whistleblowing Management Tool

iubenda’s Whistleblowing Management Tool helps EU businesses ensure compliance. We’ve designed our product to streamline management within organizations, protect whistleblowers, and ensure businesses consistently adhere to the law.

Our tool offers an easy-to-use reporting form for employees and other stakeholders and allows businesses to manage the entire process from an intuitive all-in-one dashboard.

Haven’t used our solutions yet? Start generating here.

How It Works

1. Activate the Whistleblowing Management Tool

From your iubenda Dashboard, simply click on “Activate“

2. Embedding

Remember, a clearly visible form ensures that anyone who wishes to report can easily do so.

After activation, click on “Embed” to integrate the reporting form for easy access by employees or other potential reporting persons.

Next, in this section, you’ll find all the options to embed the form:

• Direct link: Use a direct link if you wish to send your users to your form directly, rather than using a modal window. Copy it, and then paste it strategically on your website, intranet, whistleblower policy, or wherever else you need it.

• Add a widget to the footer: Use the provided code to embed the form directly on your site. You can choose to have the button in white, black, or remove the styling altogether. Just copy and paste it in the body of your website, wherever you wish to display the button. When users click this button, the form will open in a modal.

• Embed the form in the body: Embedding the form directly into the body of your webpage integrates it as if it were part of your website. For this, copy the JavaScript snippet and paste it into the HTML of the specific page you’ve designated for this purpose.

• Printable PDF with QR code: It serves as an offline extension of the online form. Designed for physical distribution. Simply print the PDF and display or distribute it as needed. The PDF includes a QR code that, when scanned, directs users to the associated online whistleblower reporting form.

Tips:

• Using a direct link guarantees that the form displays consistently across different platforms.
• Ensure the form is easily noticeable, regardless of the chosen embedding method.
• While the site’s footer is recommended for universal access, consider other strategic locations based on your organization’s structure.

Where do I put the iubenda Whistleblowing link?

That depends entirely on you. But the rule of thumb is your site’s footer. It’s a good way for it to be seen from every page.

3. User Reporting

Once activated, reporting persons can choose to report either anonymously or by providing their identity using the form embedded on your website. They can specify details such as the type of wrongdoing or misconduct, provide an exact date, and describe the facts. Once completed, they simply click on “Submit report” to send it.

After submitting the form, reporting persons will automatically receive an acknowledgment of receipt.

3.1 Appointing a Whistleblowing Manager

Direct Appointment Through Our Tool

Appoint a Whistleblowing Manager efficiently and seamlessly within our tool, making the process smoother and more integrated. This eliminates the need for a separate appointing form.

Dashboard Access Message

When someone without the necessary permissions tries to access the Whistleblowing Dashboard, they’ll see this message:

Steps for Admins

1. Go to ‘Teams’: This is found in the ‘Account & Billing Info‘ page in the top right drop-down menu.
2. Assign the Role: Click on “+ Add user” and then choose the appropriate team member to be the Whistleblowing Manager by entering their email address.
3. Send Invitation: The chosen member will receive an email to accept this role.
4. Role Acceptance: Once accepted, they can access the Whistleblowing Dashboard.

Note for Admins

Admins can’t be Whistleblowing Managers due to specific role restrictions. This ensures a clear separation of duties within the organization for better compliance and management.

4. Whistleblower dashboard

When a reporting person submits a report, the Whistleblowing Manager immediately receives an email notification. The Whistleblowing Manager can then access all reports from the Dashboard, and quickly identify the status of each.

In your Whistleblowing Management Dashboard you have full access to all the requests, with all the necessary details — the Creation Date, Type, Reporting Person, Status and a Detail Icon.

When you click on a report, all report details become visible. This allows you to promptly address any reported issues while ensuring a secure and confidential channel for whistleblowers.

From this “Report details” panel, you have the capability to assign different statuses, add notes, and see the full history for each report, helping you track the different phases of report processing.

The status of each report is now clearly marked, making it easier to track where each report stands in the process.

Step-by-Step Status Confirmation

• Review Before Proceeding: A Whistleblowing Manager must review and confirm the current status before moving to the next. This ensures that each phase of the report is properly handled.
• Confirmation Required: It’s no longer possible to skip ahead without confirming the current status. This adds an extra layer of diligence to the process.

Option to Leave Notes

• Add Context: Whistleblowing Managers can now leave notes for each status. This is great for adding details or context, making the report handling more transparent and informative.
• Easy Tracking: These notes help keep a clear record of thoughts, actions, and decisions made at each stage.

Detailed Log for Every Report

• Chronological Order: At the bottom of the details modal of each report, you’ll find a detailed log. This log lists all the status changes in chronological order.
• Full History: This feature provides a complete history of each report’s journey through the process, making it easier to review and understand the actions taken.

These updates to status management and the addition of a detailed log improve the overall process of managing whistleblowing reports. They provide clarity, ensure accountability, and make it easier to maintain a thorough record of each report’s handling.

Consider that each status in the whistleblowing report process represents a specific stage. Here’s what they mean and how to manage them:

• Received: Once a report is received, review it and advance to the next step. Remember that upon submission, by default, the online form displays an acknowledgment receipt to the whistleblower. For non-anonymous reports, consider reaching out to the whistleblower in writing within 7 days.
• Admissibility → Admissible/Not admissible: Your initial task is to assess the report’s admissibility. If the report meets the set criteria and is deemed admissible, continue with its processing. However, if it’s found inadmissible, consider the processing complete. For non-anonymous reports, inform the reporting person.
• Processing (relevant only if admissible): After marking a report as admissible, ensure diligent follow-up. As per the Whistleblower Directive, advance to the subsequent step and provide feedback to the reporting individual within 3 months from the acknowledgment date.
• Feedback Provided (relevant for non-anonymous reports only): Upon completion of the follow-up activities, share your assessment and subsequent steps taken with the reporting person, if their identity is known. As stipulated by the Whistleblower Directive, offer this feedback within 3 months of acknowledgment.
• Processed: At this point, you’ve executed all requisite actions, deeming the report processed. Assess if additional steps are necessary for further follow-up or internal purposes before contemplating deletion.
• Information Deleted: In accordance with the Whistleblower Directive, reports must be retained only for the duration necessary and proportionate to comply with the requirements of the directive or other mandates from Union or national law. In instances where national legislation specifies deletion requirements, ensure compliance. Exercise caution when deleting, as this action is irreversible.

Additional Resources

To help our users and enhance the efficiency of managing whistleblowing, we’ve prepared a set of downloadable resources:

• Customizable Whistleblowing Policy Template — The whistleblower policy serves as a foundational blueprint for organizations to personalize, featuring a section that allows for the addition of a link to the form for online submissions, while offering flexibility for customization to meet the organization’s unique needs and operational style. It establishes clear guidelines, ensuring that the team knows exactly how to proceed when encountering unethical or illegal behavior.

• Appointment Template: Assigning Responsibility — We prepared an appointment template for the designation of a person or department to handle whistleblowing reports. It helps streamline the reporting and investigation process, ensuring accountability and that concerns are addressed by those best equipped to handle them.

The post iubenda’s Guide to the EU Whistleblower Directive & Our Dedicated Tool appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

“Terms and Conditions” is the document governing the contractual relationship between the provider of a service and its user. On the web, this document is often also called “Terms of Service” (ToS), “Terms of Use“, EULA (“End-User License Agreement”), “General Conditions” or “Legal Notes”.

Particular emphasis should be given to the limitation of liability clauses (and disclaimers) , for example in cases of malfunctions of the app/ website, or user generated content. You can see an example of a Terms and Conditions clause below.

The Terms and Conditions therefore, represent the document that helps in dealing with problems or preventing them in the first place. Because of that, the Terms and Conditions are fundamental in many cases in order to mount an adequate and proper defense.

Terms of Service set the way in which your product , service or content may be used, in a legally binding way. They are crucial for protecting your content from a copyright perspective as well as for protecting you from potential liabilities.

How iubenda can help you generate and manage a Terms and Conditions document

Customizable from over 100 clauses, available in 11 languages, drafted by an international legal team and up to date with the main international legislations, our Terms and Conditions Generator is capable of handling even the most complex, individual scenarios and customization needs.

Our solution works for businesses of any size, from the single blogger to enterprise level organizations, protecting their interests and their content.It’s optimized for e-commerce, marketplace, SaaS, mobile apps, blogs, publications and more.

For more information on how to create your terms of use for your site/app

---

read our guide on How to Generate a Terms and Conditions document.

See also

• What should basic Terms and Conditions include?
• Can I use a Terms and Conditions template?
• How to generate Terms and Conditions

The post What Are the Terms and Conditions and When Are They Needed? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In addition to displaying a cookie banner and in accordance with laws like the GDPR, you must obtain consent for any cookies that are not essential for the technical functions of a website. This means that any cookie that is not considered strictly necessary should not be placed on users’ browsers until they have given their consent.

In this guide, we will show you how to automate the process of setting your cookies, scripts, and tags to respond to the preferences selected by your site visitors.

We’re continually fine-tuning the auto-blocking feature to provide the best possible experience. However, please be aware that it remains experimental, and its accuracy may not be flawless. For a safer approach, consider relying on other methods for prior blocking.

What is Automatic Blocking?

Auto-blocking is a feature that automatically blocks the scripts that may install cookies/trackers on the website until the user gives consent. It’s required for compliance with privacy laws such as the GDPR by preventing the setting of third-party cookies.

The purpose of auto-blocking is to ensure that only strictly necessary cookies are set by a website. This is crucial because regulations like the GDPR require opt-in consent before placing any cookies on a user’s device, unless they are considered strictly necessary or essential.

Our Privacy Controls and Cookie Solution takes care of automatically blocking third-party scripts that install cookies, so you don’t have to do it manually.

Which Cookie-installing Scripts Should be blocked?

This depends on the legal jurisdiction applicable to your site. In Europe, you’re legally required to block cookie scripts and similar technologies until informed user consent is obtained. Almost all cookies must be blocked, however, there are a few specific exemptions, the so-called strictly necessary cookies.

If you’re not sure if the cookies running on your site falls into this category, it’s always better to take a safe approach and block until consent is received.

How Automatic Blocking Works

The iubenda scanner crawls your website, identifying all cookies, services, scripts, iframes, videos, images, and other tracking methods employed to track users and set cookies. Using this information, the automatic blocking feature loads domains associated with these services and prevents requests from them until the user provides consent.

iubenda automatically blocks selected sources from setting cookies on the user’s browser based on the results from the site scanner with consideration to the cookie classifications listed in the Cookie Policy, as well as commonly used scripts and tracking technologies.

In cases where there are cookies that are not automatically blocked, you have the option to block custom domains by directly adding them or choosing to exempt specific domains from being blocked.

How to Implement Automatic Blocking

If instead, you want to use the Advanced implementation of “Google Consent Mode”, and allow Google services to dynamically adapt based on changes in consent set by the user, simply follow these steps:

Note that this method offers flexibility, but requires careful consideration to ensure privacy compliance.

Once the site/project is selected in the “Dashboard”, you can configure automatic blocking by clicking on the settings icon located in the site info panel:

Next, in the tab: “Block scripts prior to consent“, you will find the configuration option for Automatic blocking:

Once you activate “Automatic blocking,” you can choose to enable or disable the pre-set toggles, allowing you to block cookies from selected sources according to your specific requirements and the legal jurisdiction applicable to your site:

Block scripts detected from site scanner:

When this option is enabled, “perfect match” third-party scripts identified by our site scanner will be automatically blocked to prevent them from installing cookies on your site.

Block scripts related to services listed in your Privacy and Cookie Policy:

Enable this option to automatically block scripts linked to services listed in your Privacy and Cookie Policy. Exclusively available for policies created with the Privacy and Cookie Policy Generator.

To fine-tune how these services are categorized and influence how they are blocked, check out Customize Service Categorization.

Block well-known scripts and tracking technologies:

Enable this option to block widely recognized scripts and tracking technologies. Note: if a script is blocked in this manner, it may not be loaded by the Privacy Controls and Cookie Solution, making it impossible to associate it with the relevant purpose. If you are using one of these technologies on your website, we highly recommend that you add them to your iubenda Privacy and Cookie Policy.

Do not block Google’s services that adhere to Consent Mode:

When this option is enabled, our Privacy Controls and Cookie Solution will automatically activate advanced implementation of Google’s Consent Mode. This method allows Google services to adapt dynamically based on changes in consent set by the user.

For example, if a user initially denies consent for certain data processing activities, Google services will respect this choice and adjust their behavior accordingly. Even if consent is denied, certain user data, such as IP addresses, may still be processed by Google services. Please note that this method offers flexibility but requires careful consideration to ensure compliance with privacy regulations.

Do not block vendors that adhere to the TCF when the TCF is enabled:

When this feature is enabled, ad delivery is driven by the TCF consent string, reflecting the user’s preferences. We recommend that you check with your associated vendors to find the best strategy that balances optimal performance with compliance.

Customize Service Categorization

Our Privacy and Cookie Policy Generator now lets you customize how services are categorized in your Privacy and Cookie Policy, giving you more control over auto-blocking behavior within the Privacy Controls and Cookie Solution (Cookie Banner), and automatically updating your cookie policy to reflect these changes.

Why It Matters

Auto-blocking: Auto-blocking prevents third-party cookies and trackers from loading until users give explicit consent, as required by laws like GDPR. By adjusting a service’s category, you decide which consent is needed to unblock it.

Legal documents (Cookie Policy): Your Cookie Policy dynamically reflects these categorizations, and any changes you make are automatically updated in your cookie policy.

How It Works

• Services are grouped into five categories: Necessary (1), Functionality (2), Experience (3), Measurement (4), and Marketing (5).
• By default, iubenda assigns categories, but you can now reassign them.
• A service under Marketing (5) stays blocked until marketing cookies are accepted.
• If you change it to Experience (3), it requires only experience cookies.
• If moved to Necessary (1), it loads immediately without consent.

Simply open the Privacy and Cookie Policy Generator, select a service, click the edit icon, update its category in the “Change the default purpose categorization inside the Cookie Policy” section, and save—your policy and cookie banner behavior will update accordingly.

Advanced settings

Block Custom Domains

Please note that if you want to use the “Advanced Settings” you will need to upgrade your plan.

You can manually add a domain that may contain a script that installs cookies or trackers, if this domain has not been detected by our system. This way, requests from that domain will be restricted until consent is given for the specific purpose mentioned.

In this case, you’ll need to specify the relevant purpose (e.g. Necessary, Functionality, Experience, Measurement, Marketing) that must be accepted by the user when collecting consent for the manually added script. This is because manually add scripts are not initially categorized under one of the predefined purposes.

To do this, enable the “Block custom domains” toggle and select “Add domain”. At this point, you can specify the domain and indicate the purpose. Finally, click “Save domain” to block any requests until consent is given for the specified purpose.

Additional settings

• Block inline scripts: When this option is enabled, scripts that are directly integrated within your website’s HTML will be blocked prior to consent
• Block synchronous scripts: When this option is enabled, synchronous scripts will be blocked on your website prior to consent.
• Block images: When this option is enabled, images from third-party sources will be blocked on your website
• Block stylesheets: When this option is enabled, third-party stylesheets will be blocked on your website
• Block content from same domain: When this option is enabled, content from your own domain will be blocked on your website. This includes scripts, images, stylesheets, and other resources originating from your own domain. Please use caution when enabling this option, as it may impact the functionality and appearance of your site.

Note that the default configuration of the checkboxes will be set as shown below:

Ignore specific domains from automatic blocking

Enable this option to exempt specific domains from being blocked, allowing their scripts, resources, and content to remain unaffected on your website. This feature ensures that selected domains are exempted from the blocking mechanism, maintaining their intended functionality.

Embedding section

Remember, in the event that you make changes to the automatic blocking status (enabled/disabled), the embedded code snippet will be modified accordingly. Therefore, it is necessary to copy and embed your code again.

And you’re done! Get started implementing iubenda’s automatic blocking now for effortless legal compliance.

The post Prior Blocking of Cookies: Automatic Blocking (auto-blocking) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Have a website and need to meet GDPR consent requirements?

Well, you’re in the right place. In this guide, we’ll take a look at:

• GDPR consent proof requirements, and
• how to add iubenda’s Consent Database to your website platform of preference.

GDPR consent proof requirements

Maintaining comprehensive records of consent is a vital part of privacy compliance in general, but is specifically required under the GDPR. These records should include a way of identifying the user, proof of consent, a record of the consenting action, and the legal documents available to the user at the time of consent, among other things.

How to record and manage GDPR consent with the Consent Database

The Consent Database allows you to record consent preferences performed by your users (subjects), storing the information necessary for proof of consent according to the GDPR. The database captures a series of legally required values about your users’ consent preferences, which you can easily review within a visual dashboard. These values include the user’s consent status, time stamps, which legal documents were available to the user on your site at the time, the consent collection mechanism, and more.

The Consent Database provides you with an API to:

• Add, revoke, and manage user consent
• For each consent, get a certified timestamping
• Store multiple preferences for each user (e.g. if you have multiple newsletters or opt-ins)
• Store whether a user was verified with double opt-in
• Store additional information about the user, allowing you to identify him/her in the future
• For each consent, track the legal or privacy notice the user has accepted
• For each consent, track the form/wording the user was prompted with
• Flexibly upload any form of proof of consent or legal notice, including a PDF if consent was collected on paper
• For each user, get the latest preferences and which consent action is the proof of consent

How to integrate the Consent Database

At iubenda, we strive to make the integration process as easy as possible. That’s why we offer multiple integration options, including some that are no-scripting required, all compatible with a wide range of platforms.

No matter what platform you’re using, our integrations are designed to be user-friendly, and our guides are easy to follow, so you can get up and running in no time.

Setting up your Consent Database is easy! Let’s take a look at the individual integrations available

Platform-specific Integrations

To make it easier for you to integrate the iubenda Consent Database with your preferred platform, we’ve compiled a list of guides that you can use to get started. In short, the process involves 3 main steps, which we’ll walk you through. Some integrations are no-scripting required, while others may need a bit of scripting.

Step 1

Simply select your platform from the list below, and you’ll be directed to a dedicated guide that provides step-by-step instructions on how to integrate the iubenda Consent Database with your platform.

Prefer to use an API? Use the private API key (select the dedicated guide below) and install the Consent Database via Zapier or Make (no scripting required, no programming experience necessary).

or

If you prefer a backend integration, check our HTTP API documentation.

Step 2

Once you’ve selected the platform you’re using, you’ll find step-by-step instructions on how to integrate iubenda’s Consent Database into your website. These instructions are easy to follow and guide you through the process smoothly.

Step 3

After you’ve followed the integration guide: Test your configuration and fill out your form — you should see your consent data in the Consent Database Dashboard.

There you have it! Now, you will be able to see your subjects’ consent records in your iubenda dashboard!

The post Consent Database Integration Guide (All Major Platforms) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In some cases, when iubenda’s inline JavaScript is delayed due to:

• External JavaScript is loaded, and that relies on inline JavaScript.
• JavaScript minification is active, which saves files locally.
• Default exclusions are in place.

This could occur specifically when a feature called “JS Optimizations” is configured in cache plugins. Like for example: WP-Rocket, Autoptimize, and similar.

Since our Cookie Solution is written in JavaScript, if other plugins try to optimize it, sometimes our script gets broken – so you should configure each cache plugin so that it “ignores” our “inline” script, which refers to the part that the user pastes into the <head> tag when installing our Cookie Solution or use our plugin.

For example, in the case where the default exclusions are in place, a JavaScript error pops up:

How to avoid the delay of JavaScript execution with iubenda’s default exclusions?

WP-Rocket plug-in

In this case, you just need to do the following:

1. exclude _iub from the “combine” and “minification” feature in the WP-Rocket settings, to do so, add it in the exclusion field, as shown below:

Since our script was broken due to previous JS Optimization, now we need to re-add the original Cookie Solution script in the <head> tag (as the first element) or in our all-in-One WordPress plugin:

Note

If you use WP-Rocket from version 3.13 and the “Delay JavaScript execution” feature is enabled, you can exclude our plugin from the “One-click exclusion” area by selecting our plugin in this way:

2. Re-add the original Cookie Solution script in the <head> section as the first element:

<script type="text/javascript">
var _iub = _iub || [];
_iub.csConfiguration = {"enableCcpa":true,"countryDetection":true,"askConsentAtCookiePolicyUpdate":true,"consentOnScroll":false,"consentOnDocument":true,"ccpaAcknowledgeOnDisplay":false,"whitelabel":false,"lang":"en","siteId":1264045,"cookiePolicyId":93663998, "banner":{ "position":"bottom" }};
</script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/ccpa/stub.js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

3. make sure the default exclusions are in place;

4. and check the JavaScript console for the error.

Autoptimize plug-in

This same problem can happen when you are using the Autoptimize plugin and you can solve it by adding only the attribute data-noptimize to our inline Cookie Solution script.

Autoptimize recognizes a script attribute, data-noptimize, which means the inline script won’t be inlined or anyway it should be ignore by autoptimize and many users add it in our inline script in this way:

<script data-noptimize="true">
var _iub = _iub || [];
_iub.csConfiguration = {"enableCcpa":true,"countryDetection":true,"askConsentAtCookiePolicyUpdate":true,"consentOnScroll":false,"consentOnDocument":true,"ccpaAcknowledgeOnDisplay":false,"whitelabel":false,"lang":"en","siteId":1264045,"cookiePolicyId":93663998, "banner":{ "position":"bottom" }};
</script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/ccpa/stub.js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

Doing these steps, the expected behavior is that there should be no errors when JavaScript Execution Delay is active.

See also

• How to Customize the Look and Behavior of the Cookie Banner, Consent Banner and Privacy Controls (Beginner’s Guide)
• Introduction to the Prior Blocking of Cookies
• Cookie Solution changelog

The post How to solve common Cookie Solution issues with cache plugins and optimization features appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Well, you’re in the right place. In this guide, we’ll take a look at GDPR consent proof requirements and how to add iubenda’s Consent Database to your Prestashop site.

→ Jump to How to add the Consent Database on Prestashop

How to add iubenda’s Consent Database on Prestashop 1.7 

Using Prestashop 1.6? See here →

This guide is in two parts; please select and follow one of the processes provided below.

1. How to add Consent Database to the default Contact Us page on Prestashop
2. How to add Consent Database to the default Newsletter form on Prestashop

Contact us page on Prestashop 

To begin, head to your Prestashop dashboard and click on advance parameters.

Next, click on Performance.

After that, in the Template Compilation drop-down menu, select > Recompile templates if the files have been updated from Template compilation.

Then toggle the Cache button to No in order to disable cache.

After that, scroll down to the bottom of the page and select the “Use Cache” setting and toggle to No. Finally, click on Save.

Next, we need to connect Contact US Page to your iubenda Consent Database. Here we are referring to the default ‘contact us page’ that Prestashop adds on the home page (usually at the top of the homepage, depending on your Theme) 

For example:

Which would link to a contact page like the one below: 

From here, we need to manually add IDs to the <form> tag and submit button of the form; to do this, follow the next steps:

1. Open contactform.tpl from your theme folder

You can find it in prestashop_folder\themes\YOUR_THEME\modules\contactform\views\templates\widget

(Replace YOUR_THEME, with the name of your theme in use)

2. Now, add id="form_contact" to <form> tag.

3. After that, add id="submit_button" to submit button.

4. Now the form is ready; we need to add the Load function of your Consent Database after the </form> closing tag

Please remember that the Load should be customized in this way: 

You can find a demo here.

The script should be added between the {literal} {/literal} tags

You will add in the load function as described below: 

• ID "submit_button" in the submitElement:

submitElement: document.getElementById("submit_button"),

• ID "form_contact" in the form object:

form: {
selector: document.getElementById("form_contact"),

• in the subject, we should add the name attribute of the email field of our form; in this case, it is "from":

subject: {

email: "from"

How to find it? Go to your contact us page, click on the email field, right-click with your mouse, then click Inspect.

A tab with the HTML of that field will show you the name attribute:

The final Load script will look like the following: 

{literal}
<script type="text/javascript">
_iub.cons_instructions.push(["load",{
submitElement: document.getElementById("submit_button"),
form: {
selector: document.getElementById("form_contact"),
map: {
subject: {
email: "from"
}
}
},
consent: {
legal_notices: [
{
identifier: 'privacy_policy',
},
{
identifier: 'cookie_policy',
},
{
identifier: 'terms',
}
],
}}]);
</script>
{/literal}

Lastly, you will paste it after the </form> closing tag:

Next, we need to add the INIT function in the <head> of the website. 

Without modifying your theme’s template, we suggest you use a module that allows you to add scripts in the head tag. We recommend HTML box or something similar. 

After installing the HTML box or something similar, you can copy the INIT function from your iubenda’s dashboard → Consent Database → Embed

Before copying our INIT function, HTML BOX suggests disabling the HTML Purifier library; you can find it in Shop Parameters → General.

Copy INIT function in the HTML BOX module. Click on Module Manager.

Type in “html box” into the search bar. 

Then click on the Configure button.

After that, paste the INIT function into the text box provided and click on Save, and you’re done! 

Default Newsletter form on Prestashop

This step-by-step guide explains how to install Consent Database on the Newsletter form created using the default ps_emailsubscription module.

If ps_emailsubscription module is enabled, Prestashop creates a newsletter subscription form at the website’s footer.

Here is an example: 

Now we need to add IDs to the form and submit button of our form. To do so, you will need to open the ps_emailsubcription.tpl file and modify it.

You can find it in the folder themes/YOUR_THEME/modules/ps_emailsubscription/views/templates/hook/

(Replace YOUR_THEME, with the name of your theme in use)

After that, add id="newsletter_subscription" to the <form> tag.

Next, add id="submit_button" to the submit button.

Now the form is ready; we need to add the “submit” function of your Consent Database after the </form> closing tag. 

Please note that the Submit function should be customized in this way:

Please note that Prestashop requires you to paste the script between {literal} {/literal} tags. 

1. ID "submit_button" here:
   document.getElementById("submit_button").onclick=function (e) {
2. ID newsletter_subscription in the form object:
   form: {
selector: document.getElementById("newsletter_subscription"),
3. in the subject-object, we should add the name attribute of the email field of our form; in this case, it is “email”:
   subject: {
email: "email"

How to find it? Go to your contact us page, click on the email field, right-click with your mouse, then click Inspect. 

A tab with the HTML of that field will show you the name attribute.

The final submit script will be:

{literal}
<script type="text/javascript">
document.getElementById("submit_button").onclick=function (e) {
_iub.cons_instructions.push(["submit",{
form: {
selector: document.getElementById("newsletter_subscription"),
map: {
subject: {
email: "email"
}
}
},
consent: {
legal_notices: [
{
identifier: 'privacy_policy',
},
{
identifier: 'cookie_policy',
},
{
identifier: 'terms',
}
],

}}])
};
</script>
{/literal}

You will paste it after the </form> closing tag

We need to add the INIT function in the <head> of the website.

Without modifying your theme’s template, we suggest you use a module that allows you to add scripts in the head tag. We recommend HTML box or something similar. 

After installing the HTML box or something similar, you can copy the INIT function from your iubenda’s dashboard → Consent Database → Embed

Before copying our INIT function, HTML BOX suggests disabling the HTML Purifier library; you can find it in Shop Parameters → General.

Copy INIT function in the HTML BOX module. Click on Module Manager.

Type in “html box” into the search bar. 

Then click on the Configure button.

After that, paste the INIT function into the text box provided and click on Save, and you’re done! 

Prestashop 1.6 with iubenda’s Consent Database

You can install iubenda’s Consent Database on the contact-us page of Prestashop 1.6.

{literal}
<script type="text/javascript">
document.getElementById("submitMessage").onclick=function(e){

_iub.cons.sendData();
}
</script>

<script type="text/javascript">

_iub.cons_instructions.push(["load",{


form: {

selector: document.getElementById("contact-form"),

map: {

subject: {

email: "from"

}

}

},

consent: {

legal_notices: [

{

identifier: 'privacy_policy',

},

{

identifier: 'cookie_policy',

},

{

identifier: 'terms',

}

],

}}]);

</script>

{/literal}

<!-- start init cons -->
{literal}
<script type="text/javascript">var _iub = _iub || {}; _iub.cons_instructions = _iub.cons_instructions || []; _iub.cons_instructions.push(["init", {api_key: "PUBLIC_TEST_API_KEY", *sendFromLocalStorageAtLoad**: false* }]);</script><script type="text/javascript" src="https://cdn.iubenda.com/cons/iubenda_cons.js" async></script>
{/literal}
<!-- end consent solution iubenda -->

The post Consent Database for Prestashop appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Google Consent Mode: With Google Tag Manager (GTM), you can simplify the process of tag configuration by using pre-configured templates created specifically for your GTM configuration.

In the GTM Gallery you can choose from a library of templates that you can easily add to your installation.

Short on time? Jump straight to How To Start!

What Is Google Tag Manager?

Google Tag Manager (GTM) is a powerful tool used for efficiently managing website tracking codes, commonly referred to as GTM tags. But what is GTM, and how can you use it to your advantage?

What is GTM?

GTM stands for Google Tag Manager, a free tool offered by Google. GTM tags are snippets of code that serve various purposes, such as collecting data and facilitating communication between your website or app and external analytics and marketing platforms.

What is Google Tag Manager Used For?

Google Tag Manager is primarily used for simplifying and centralizing the management of these tags on your website or app. It eliminates the need for manual code implementation, streamlining the process and reducing the risk of errors. It’s a versatile tool that helps you manage and deploy tags more efficiently.

How to Use Google Tag Manager:

1. Code Installation: GTM provides a container-specific code snippet. Insert this code into your website or app’s header or body section, as required by the tags you wish to implement.
2. Tag Implementation: Begin adding tags to your container. These tags can include tracking codes for various tools, such as Google Analytics, Google Ads, and more. GTM offers pre-built templates to simplify this process.
3. Trigger Definition: Determine when and where your tags should activate by creating triggers. Customize triggers based on specific events or conditions, such as user interactions or page views.
4. Variable Creation: Variables are used to store and retrieve data for tags and triggers. You can use existing variables or create custom ones to capture dynamic data.
5. Preview and Debug: Before making your changes live, use GTM’s preview and debug mode to test your tags and ensure they function correctly.
6. Publish Your Container: Once you’re satisfied with your setup and testing, publish your container. This action makes your changes live on your website or app.

How to Set Up Google Tag Manager

How To Start

First, you have to create a GTM account and set up a container.

Then, you’ll be required to paste the GTM snippet into your website’s <head> section.

Finally, you’ll reach the GTM dashboard.

Adding iubenda Privacy Controls and Cookie Solution template

Once in the dashboard, click on Add a new tag.

Then, click on the Tag configuration area, select “Discover more tag types in the Community Template Gallery”, click on the magnifier icon, and search: iubenda

Select “iubenda Privacy Controls and Cookie Solution” and click “Add to workspace” to add it to your GTM installation.

Adding iubenda Privacy Controls and Cookie Solution template (manual method)

Import the template

Before setting up the template, you need to import it. Here’s how:

1. Download the template from here
2. On your GTM dashboard, click on Templates
3. Under Tag Templates, click on “New.”
   
4. Click on the three dots icon at the top right of the page and select Import.
   
5. Unzip the file you downloaded and select the template.tpl file from the folder
6. Click on Save at the top right of the page and close the template editor

Add the tag

Once back in the dashboard, click on Add a new tag.

Then, click on the Tag configuration area, scroll down to the Custom section, and click on iubenda Privacy Controls and Cookie Solution to add it to your GTM installation.

Tag Configuration

Once you have added the template, you will get to the Tag configuration page.

Here you will have to:

1. Set the default consent options

The defaults are all set to Denied to ensure the best privacy protection for your users. 

We suggest being extremely careful in modifying such parameters to ensure they align with best practices for obtaining user consent through positive action.
For more information about Consent types, you can check the Google official documentation here.

Optional parameters

• URL passthrough is an optional parameter, useful to improve the quality of your measurements when ad_storage is denied (Targeting & Advertising purpose). It can be used to send event and session-based analytics (including conversions) without cookies across pages. 
• Ads data redaction is a parameter that allows redacting Ad click identifiers sent in network requests by associated Google Ads and Floodlight when ad_storage is denied .

You can see the official Google Tags documentation for further information about these parameters.

2. Privacy Controls and Cookie Solution embedding

There are now two main auto-embedding options for integrating the Privacy Controls and Cookie Solution in Google Tag Manager (GTM):

1. Option 1: Unified Snippet (With remote configuration active) – Recommended option
2. Option 2: Extended Snippet (Used when remote configuration is not active)

Additionally, manual embedding is still available as an alternative.

Auto embedding

Option 1: Unified Snippet (With Remote Configuration)

When remote configuration is enabled, the method uses the unified snippet. This option allows you to manage the Privacy Controls and Cookie Solution settings remotely, this means, updates and changes made in the Privacy Controls and Cookie solution will automatically apply to your website without needing to re-embed the snippet and republish in GTM.

• How it works:
  • When remote configuration is enabled, the unified snippet is used. This short snippet points to a URL hosted remotely by iubenda.
  • The advantage of this method is that any updates made in your iubenda Dashboard (e.g. changes to the banner design, TCF tile, or support for US laws) will automatically reflect on your website without needing to update the GTM configuration or republish the container.
• Steps to embed using the unified snippet (with remote configuration):

1. In the Privacy Controls and Cookie Solution settings, you should have enable remote configuration.



2. Copy the unified snippet URL from your iubenda Dashboard. It will look something like this:



3. In your GTM dashboard, choose the option “Unified snippet via GTM template,” then paste the URL embeds.iubenda.com/widgets/[sitecode].js into the GTM template Embedding URL box. Make sure to add https:// at the beginning to include the full URL.

Important

As you may notice, the code to paste for the unified snippet is slightly different from the code included on your iubenda embedding page.

Here’s an example of the parts not to paste into the configuration box (strikethrough):

‹script type="text/javascript"
src="//embeds.iubenda.com/widgets/[site-code].js"></script>

4. Save the changes in GTM and publish the container.
5. Once this is set up, any changes made to your configuration (like adjusting the banner appearance, enabling TCF, or updating US laws) will automatically apply to your website, with no need to re-embed or republish the tag in GTM.

Option 2: Extended Snippet (Used when remote configuration is not active)

This method uses the extended snippet and is used when remote configuration is not enabled. Updates to the Privacy Controls and Cookie Solution will require manual updates in GTM whenever changes are made to the Privacy Controls and Cookie Solution configuration.

• How it works:
  • When remote configuration is not enabled, the extended snippet is used, and a portion of it with the parameters should be inserted into the GTM template. This means, any changes made to your Privacy Controls and Cookie Solution settings will require you to manually update the snippet in GTM and republish the container to apply those changes, as updates are not applied automatically.
• Steps to embed using the extended snippet (no remote configuration):

1. Copy the embedding code (extended snippet) from your iubenda Dashboard.



2. In your GTM dashboard, choose the option “Extended snippet via GTM template”, then paste only the part after var _iub = _iub || []; and within the _iub.csConfiguration = {...} into the GTM CS configuration box.

Important

As you may notice, the code to paste for the extended snippet is slightly different from the code included on your iubenda embedding page.

Here’s an example of the parts not to paste into the configuration box (strikethrough):

<script type="text/javascript">
var _iub = _iub || [];
_iub.csConfiguration = 
{
 "ccpaAcknowledgeOnDisplay": true,
 "ccpaAcknowledgeOnLoad": true,
 "ccpaAppliesToEntireUSA": true,
 "consentOnContinuedBrowsing": false,
 "countryDetection": true,
 "enableCcpa": true,
 "gdprAppliesGlobally": false,
 "lang": "it",
 "perPurposeConsent": true,
 "siteId": 2398592,
 "whitelabel": false,
 "cookiePolicyId": 55062451,
 "banner": {
 "acceptButtonDisplay": true,
 "backgroundColor": "#FF0000",
 "closeButtonDisplay": false,
 "customizeButtonDisplay": true,
 "logo": null,
 "position": "float-top-center",
 "rejectButtonDisplay": true
 }
}
</script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/ccpa/stub.js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

3. Save the changes and publish the GTM container.
4. Whenever you make changes to the configuration, you will need to copy the updated extended snippet and re-paste the corresponding portion in GTM, followed by re-publishing the container.

Manual embedding

You can also embed the Privacy Controls and Cookie Solution code manually. To do that, you have to follow the standard embedding method described in this guide.

To make sure this method works correctly, remember to add the parameter: "googleConsentMode": "template" to your Privacy Controls and Cookie Solution configuration. Follow these steps to add it properly:

In your Privacy Controls and Cookie Solution settings, make sure to uncheck the “Enable remote configuration” option. This is essential for manual embedding to work properly.

After disabling remote configuration, copy the updated snippet and add the following parameter:

"googleConsentMode": "template"

Your updated snippet with the added parameter should look like this example:

<script type="text/javascript">
 var _iub = _iub || [];
 _iub.csConfiguration = {
 "countryDetection": true,
 "consentOnContinuedBrowsing": false,
 "perPurposeConsent": true,
 "lang": "en",
 "siteId": 11111111, //use your siteId
 "cookiePolicyId": 11111111, //use your cookiePolicyId
 "floatingPreferencesButtonDisplay": "bottom-right",
 "banner": {
 "acceptButtonDisplay": true,
 "customizeButtonDisplay": true,
 "rejectButtonDisplay": true,
 "position": "float-top-center"
 "googleConsentMode": "template"
 }
 };
</script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

Finally, you can choose the Privacy Controls and Cookie Solution channel (Beta, Current, Stable).

Use collected preferences to set default consents

You can optionally enable a feature that sets default consent values by reading stored user preferences from cookies or localStorage.

How does this feature work?

When this option is enabled, the tag checks for specific storage items to determine whether to automatically grant consent. Consent is set to “granted” only if all the defined items confirm the user has opted in (or hasn’t opted out) for that purpose.

To configure this:

1. Enable Default consent from storage (experimental).
2. Choose the Storage type: Cookie or Local Storage.
3. Choose the ID type and enter the ID value:
   • Site ID (preferred)
   • Cookie Policy ID (use only if you have a single Cookie Policy configured)

Important notes

• Works only with a single Cookie Policy ID or if storage.useSiteId = true.
• As GTM does not support country detection, the safest assumption is applied: consent is granted only if all relevant storage items indicate an opt-in or no opt-out.

Remember, this is an experimental feature intended to improve consent handling before the iubenda banner is shown. Use it carefully due to its experimental nature and current limitations.

Advanced Settings

In this section, some advanced settings can be set up, such as the Tag firing priority, Tag Sequencing, and advanced Consent settings. Please note that there’s no need to edit these settings for the template to work, so if you’re unfamiliar with them, you can ignore them. 

3. Triggering

After configuring the tag, you need to set up the trigger to make the tag fire. 
You can select “Consent Initialization – All Pages” as the trigger.

Publish the Container

After completing the configuration, click the Save button at the top right of the page. The tag is now ready to be published.

From the GTM dashboard, click on Submit at the top right of the page:

Finally, add a version name and description, click on Publish, and that’s it! The tag is up and running, seamlessly integrated with our Privacy Controls and Cookie Solution!

How to control cookies

Built-in consent checks

Tags like Google Ads, Analytics, Floodlight, and Conversion Linker have built-in consent checks. They are natively compatible with Google Consent Mode.

This implies that these tags possess a mechanism that alters their functionality in response to the user’s consent status.

Please note that no consent configuration is needed for this type of tags.

You can simply assign “All pages” trigger to tags that have built-in consent checks like Google Ads, Google Analytics, Floodlight or Conversion Linker

Example:

Additional consent checks

Some tags — like Google Ads, Google Analytics, Floodlight, and Conversion Linker — are natively compatible with Google Consent Mode. These tags include built-in consent checks, meaning they automatically adapt their behavior based on the user’s consent status.

For these tags, no extra configuration is required: you can safely use the “All pages” trigger.

However, tags that do not support built-in consent checks (for example, Custom HTML tags embedding Facebook Pixel, Hotjar, LinkedIn Insight, or other third-party scripts) must be configured with additional consent checks.

Step 1: Enable emitGtmEvents

To make additional consent checks possible, you need the event iubenda_gtm_consent_event to be sent whenever user preferences change.

You now have two options:

• Recommended: enable the emitGtmEvents toggle directly in the iubenda GTM template. This automatically handles event emission with no need to edit code.
• Alternative (manual method): add "emitGtmEvents": true inside your _iub.csConfiguration snippet. This is only needed if you prefer not to use the template option.

Step 2: Create your Custom HTML tag

1. In GTM, add a new Custom HTML tag.
2. Paste the script you want to use (e.g. Hotjar, Facebook Pixel, LinkedIn Insight Tag).

Example (Hotjar script as placeholder):

Step 3: Configure consent requirements

Go to Consent Settings in your Custom HTML tag and select:
“Require additional consent for tag to fire”

Then, choose the relevant purpose based on the type of script. For example:

Step 4: Assign the trigger

Instead of using “All pages,” create a Custom Event trigger with the following settings:

Event name:

iubenda_gtm_consent_event

This ensures that the Custom HTML tag fires only after the user has given valid consent for the selected purpose(s).

Note: when the user preferences change, the Privacy Controls and Cookie Solution sends the event iubenda_gtm_consent_event to GTM

Prior-blocking is set for the tag!

With these steps, you can safely integrate third-party tracking tools that don’t natively support Google Consent Mode.

Keep in mind, the new template-level emitGtmEvents option streamlines this process by removing the need to edit your configuration code manually.

For US users, things to know: how to honor opt-out

The explanation for built-in and additional consent checks is also valid in this case. If you enable US Law in the ‘Privacy Controls and Cookie Solution’ configurator, the default behavior for a US user is that the Cookie Solution sets all the GCM (Google Consent Mode) purposes to ‘granted‘.

Note: If you are on a “Free” Plan, this is true if you disable GDPR and apply only US Law in the configurator. Alternatively, if you want to apply GDPR for EU Users and US Law for US users, you’ll need at least an “Advanced” plan.

When the user opts out of a specific purpose under US Law, we adjust the settings for ‘ad_storage‘ and ‘analytics_storage‘ accordingly.

Specifically:

‘ad_storage‘ is granted when the user either hasn’t opted out of any of the following USPR (US Privacy Rights) purposes or when they are not relevant (e.g., USPR does not apply):

• Sale of my personal information (purpose s)
• Sharing of my personal information (purpose sh)
• Processing of personal information for targeted advertising (purpose adv)

‘analytics_storage‘ is set to granted when the user either hasn’t opted out of the US purpose ‘Sale of my personal information’ (purpose s) or when it’s not relevant (e.g., USPR does not apply).

How to Set Up iubenda’s GTM Template for Multilingual Sites

If you manage a multilingual website and are implementing Google Consent Mode with the iubenda GTM template, it’s essential to ensure that your cookie consent banner adapts seamlessly to different languages. Here’s how you can configure the iubenda GTM template for multilingual sites:

CS Configuration Textarea

In the first textarea related to CS Configuration, insert the JSON of the main script, which will also be used as a fallback. However, it is important to remove the “lang” parameter from this script. This script can contain the siteID and cookiePolicyId parameters.

CS Language Configuration Textarea

In the CS Language Configuration textarea, insert the initial language code and, if possible, only the cookiePolicyId that identifies the language in the configuration. Do not include the “lang” parameter in this configuration.

Visual Example

Below is an example of how the setup looks in the GTM interface:

Code Example to Copy

For CS Configuration, use this example code:

{
  "askConsentAtCookiePolicyUpdate": true,
  "floatingPreferencesButtonDisplay": "bottom-right",
  "perPurposeConsent": true,
  "siteId": "your-site-id", // <-- Replace with your actual site ID
  "whitelabel": false,
  "cookiePolicyId": "your-cookie-policy-id", // <-- Replace with your actual cookie policy ID
  "emitGtmEvents": true,
  "banner": {
    "acceptButtonDisplay": true,
    "closeButtonRejects": true,
    "customizeButtonDisplay": true,
    "explicitWithdrawal": true,
    "listPurposes": true,
    "position": "float-top-center",
    "showTitle": false
  }
}

For CS Language Configuration, use this example code:

{
  "it": {
    "cookiePolicyId": "your-cookie-policy-id", // <-- Replace with your actual IT cookie policy ID,
    "emitGtmEvents": true
  },
  "es": {
    "cookiePolicyId": "your-cookie-policy-id", // <-- Replace with your actual ES cookie policy ID,
    "emitGtmEvents": true
  }
}

Note: You can copy and paste these examples into the respective textareas. Be sure to replace "your-site-id" and "your-cookie-policy-id" with your specific values, ensuring the lang parameter is removed.

How it Works:

• The Privacy Controls and Cookie Solution detects the correct language from the HTML code of the page (lang attribute in the <html> tag).
• If the attribute is not available, it uses the main language set in the user’s browser.
• If both are unavailable, the default language is English.

See Also

• How to Configure Your Privacy Controls and Cookie Solution (beginner’s guide)
• Google Consent Mode: how to manage cookies for ads and analytics
• How to Use Google Tag Manager to Simplify the Blocking of Cookies
• How to Configure Your Privacy Controls and Cookie Solution (Advanced Guide)

Feature	Advanced Implementation	Basic Implementation
Tag Behavior	Google tags are loaded before the consent dialog appears, sending cookieless pings when cookie consent is declined.	Google tags are blocked until consent is explicitly granted.
Behavioral Modeling in GA4	Enabled	Not Available
Conversion Modeling in GA4	Enabled	Enabled, but limited*
Conversion Modeling in Ads	Enabled	Enabled, but limited*
* When tags are blocked due to consent choices, no data is collected, and conversion modeling in Ads relies on a general model. This model uses non-identifying variables such as browser type, key event action type, and time of day.

What are the benefits of Google Consent Mode, and why should you consider using it?

One way that Google Consent Mode can help website owners increase their advertising revenue is by providing better targeting and bidding optimization for Google Ads campaigns.

By using the consent signals provided by Google Consent Mode, website owners can ensure that their ads are only shown to users who have given their consent for their data to be used for advertising purposes. This means that website owners can deliver more relevant ads to users who are interested in their products or services, leading to higher engagement rates and better ROI for advertisers.

For example, let’s say a website owner runs a Google Ads campaign promoting a new line of athletic shoes. With Google Consent Mode, the website owner can ensure that the ads are only shown to users who have given their consent for their data to be used for advertising purposes.

This means that the ads will only be shown to users who are interested in athletic shoes and are more likely to engage with the ad.

Can I use Google Consent Mode with iubenda?

Yes, iubenda is among the Partner CMPs of Google. Our CMP is integrated with Google Consent Mode v2 and Google Tag Manager, allowing seamless implementation and helping to address technical challenges and comply with Google’s latest requirements.

iubenda’s Privacy Controls and Cookie Solution is designed to manage the consent to cookies on a website or app and allows you to adjust how your Google tags behave based on the consent status of your users, particularly in relation to advertising and analytics cookies.

Wondering if Google Consent Mode is already active on your website or just installed it and want to check if it’s working correctly?

---

Here are your options to verify Google Consent Mode status:

1. Use iubenda to Scan Your Site [Recommended]

iubenda makes checking easy:

1. Go to the iubenda site scan page
2. Type in your website’s URL for the scan
3. Enter your email address to get the results
4. Check your inbox to find out if your site is using Google Consent Mode

2. Check Manually

To manually check if Google Consent Mode is working on your site, follow these steps:

1. Open your website in Incognito or Private Browsing mode to ensure a clear cache
2. Use your developer console and type in dataLayer and open the relative object
3. Search for the very first consent event. The analytics_storage parameter should have a value equal to denied
4. Accept all cookies on your cookie banner (or at least the categories related to the Google services).
5. Find the consent event that changed in the dataLayer; analytics_storage should have a value equal to granted.
6. If everything matches up, Google Consent Mode is up and running on your site!

3. Via Google Tag Manager (GTM)

To verify your consent mode implementation:

1. Start
   Tag Assistant
   and enter your site’s URL. If Tag Assistant can’t connect, your Tag Manager might be blocked
2. Open the cookie banner on your site and accept all cookies. If your container was blocked, Tag Assistant should connect now
3. Check Consent Settings
   • Go to the Summary in Tag Assistant and click the first Consent event
   • In the  API Call section, make sure ad_storage, ad_personalization, ad_user_data, analytics_storage are correctly set
   • Alternatively, in your tag’s Output section, click the Consent tab and check the On-page Default column
4. Check for Consent Updates:
   • Go to the Summary and click the latest Consent event
   • Make sure the consent parameters updated correctly, either in the API Call section or in the On-page Update column under the Consent tab
5. Test Tags:
   • Look under the Tags tab to see if tags behave according to the consent settings

How to implement Google Consent Mode v2 with iubenda

Google’s Consent Mode marks a significant step forward in simplifying the management of cookies for ads and analytics. This latest version removes the need for code adjustments, providing an even more user-friendly approach to ensure compliance and optimize user experience.

To effectively implement Google Consent Mode with iubenda, efficiently manage cookies and obtain user consent for ads and analytics, you have these options:

1. Autoblocking [Preferred Method]

The preferred method for implementing Google’s Consent Mode is to use the auto-blocking feature (enabled by default), which allows you to automatically trigger and manage Google’s Consent Mode on scripts related to Google services without requiring any additional action.

This method allows the auto-blocking feature to set the default consent states, while the Privacy Controls and Cookie Solution works with the Consent Mode to enable or disable Google services based on user consent.

If instead, you want to use the Advanced implementation of “Google Consent Mode”, and allow Google services to dynamically adapt based on changes in consent set by the user, simply follow these steps:

Note that this method offers flexibility, but requires careful consideration to ensure privacy compliance.

Once the site/project is selected in the “Dashboard”, you can configure or edit automatic blocking by clicking on the settings icon located in the site info panel:

On the site info section “Block scripts prior to consent” under “Automatic blocking” you can find these two checkboxes:

Do not block Google’s services that adhere to Consent Mode: When this option is enabled, our Privacy Controls and Cookie Solution will automatically activate advanced implementation of Google’s Consent Mode. This method allows Google services to adapt dynamically based on changes in consent set by the user.
For example, if a user initially denies consent for certain data processing activities, Google services will respect this choice and adjust their behavior accordingly. Even if consent is denied, certain user data, such as IP addresses, may still be processed by Google services.

Do not block vendors that adhere to the TCF when the TCF is enabled: When this feature is enabled, ad delivery is driven by the TCF consent string, reflecting the user’s preferences. We recommend that you check with your associated vendors to find the best strategy that balances optimal performance with compliance.

2. For Users with Existing Configurations [Legacy Users]:

Users who already have our solutions integrated (known as ‘legacy users’) need only a simple code update.

Copy and paste the new iubenda code to replace the existing code on your site.

To do this, once the site/project is selected in the “Dashboard”, click Embed:

Copy and place this new script in the <head> section of your website’s HTML, as the first element, to ensure the consent management functions load before any other scripts, and you’re done!

This way, our Privacy Controls and Cookie Solution will automatically set the default consent state for Google services, allowing you to manage them directly through ‘Consent Mode’ without any further action.

3. Via Google Tag Manager

Google Tag Manager (GTM) allows you to use already-configured templates for your GTM installation to simplify tag configuration. The iubenda Privacy Controls and Cookie Solution template is now listed in the Featured Community CMP Templates.

By using the Google Tag Manager Template, you can manage Google Consent Mode (GCM) automatically for tags that are natively compatible with Google Consent Mode, such as Google Analytics, Google Ads, Floodlight, and Conversion Linker. Currently, the template allows you to manage prior consent for custom HTML tags using the ‘additional consent checks’ feature in a few simple steps.

For more information on integrating Google Consent Mode with the iubenda Privacy Controls and Cookie Solution, see our guide here.

Troubleshooting Google Consent Mode Misconfigurations

If your Site Scanner shows an “Attention Required” alert, or you encounter issues with Google Consent Mode, a misconfiguration likely needs fixing. Here are some common reasons why:

1. Outdated Snippet or Missing DataLayer

Problem:
Your website is using an old version of the iubenda snippet. This outdated snippet doesn’t support important features like autoblocking or managing user consent with Google Consent Mode. Your website might also be missing the required dataLayer configuration. (The dataLayer sends user consent choices to Google, and without it, your tags may not work correctly.)

How to fix it:
Re-embed the updated code snippet on your site to ensure proper functionality.

2. Incorrect Script Placement

Problem:
The iubenda snippet might be placed incorrectly, such as after Google’s script, causing Google Consent Mode to not function as expected.

How to fix it:
Ensure the Iubenda snippet is positioned correctly in the code—ideally, for example, before any Google-related scripts.

Correct placement:

<!-- iubenda snippet placed before Google script -->
<script src="https://embeds.iubenda.com/widgets/[site-code].js"></script>

<!-- Google script -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-XXXXXX-X"></script>

This ensures that the iubenda Consent Mode activates first and properly manages user consent before other scripts load.

For US users, things to know: how to honor opt-out

If you enable US Law in the ‘Privacy Controls and Cookie Solution’ configurator, the default behavior for a US user is that the Cookie Solution sets all the GCM (Google Consent Mode) purposes to ‘granted‘.

Note: If you are on a “Free” plan, this is true if you disable GDPR and apply only US Law in the configurator. Alternatively, if you want to apply GDPR for EU Users and US Law for US users, you’ll need at least an “Advanced” plan.

When the user opts out of a specific purpose under US Law, we adjust the settings for ‘ad_storage‘ and ‘analytics_storage‘ accordingly.

Specifically:

‘ad_storage‘ is granted when the user either hasn’t opted out of any of the following USPR (US Privacy Rights) purposes or when they are not relevant (e.g., USPR does not apply):

• • Sale of my personal information (purpose s)

• • Sharing of my personal information (purpose sh)

• • Processing of personal information for targeted advertising (purpose adv)

‘analytics_storage‘ is set to granted when the user either hasn’t opted out of the US purpose ‘Sale of my personal information’ (purpose s) or when it’s not relevant (e.g., USPR does not apply).

See also

• • Introduction to the Prior Blocking of Cookies

• • How to Use Google Tag Manager to Simplify the Blocking of Cookies

• • GDPR Cookie Consent Cheatsheet

The post Google Consent Mode: How to Manage Cookies for Ads and Analytics appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

➜ Jump directly to How to add iubenda’s Privacy Controls and Cookie Solution to your Ucraft site.

How to add iubenda’s Privacy Controls and Cookie Solution to Ucraft

Once you’ve generated and customized your Privacy Controls and Cookie Solution you can follow these steps to integrate it with your Ucraft website:

To install the Privacy Controls and Cookie Solution you’ll need to modify the HEAD of your site, a Ucraft premium feature available only on their paid plans. More info here.

To get started first head over to your iubenda dashboard click on [Your website] > Privacy Controls and Cookie Solution > Embed.

Here you can customize and then click on copy to copy your Privacy Controls and Cookie Solution.

Next, go to your Ucraft dashboard and select your Site settings.

Then, click on the Code Injection tab and scroll down until you find the Before </head> tag text box.

After that, paste your Privacy Controls and Cookie Solution code in the Before </head> tag section, (as shown above) click on Save and you’re done!

Please note: the code will go live once you’ve connected a Custom Domain to your Ucraft website.

Set up prior blocking of cookie scripts

Few categories of cookies are exempt from the consent requirement. Therefore, you’ll need to block scripts from running until you get valid user consent.

How to implement prior blocking via manual tagging on your Ucraft site

Manual tagging is the method of prior-block we’ll be using for the tutorial below. You can view other methods here.

In this tutorial, we are going to block a Twitter follow button.

Not sure which services you need to block? If you’re using a Cookie Policy generated by iubenda, the services listed in your Cookie Policy are most likely the ones you need to modify now.

Step 1: Identify the script

In your Ucraft site editor,, find the script you need to modify (simply search for the service you want to block, in this case, it is the Twitter follow button)

Then click on the EDIT CUSTOM HTML icon to open the code editor.

Step 2: Modify your script

Now, we’re going to change the script. To do this, we will make 3 simple changes:

• add this class: _iub_cs_activate to the script tags, and change the “type” attribute from text/javascript → text/plain
• replace the src with data-suppressedsrc or suppressedsrc
• specify the categories of the scripts/iframes with a special comma-separated data-iub-purposes attribute, e.g. data-iub-purposes="2" or data-iub-purposes="2, 3"

More about categories and purposes

Purposes are your legal reasons for processing the particular type of user data. Different scripts on your site will fall into different categories and serve different purposes. For example, Google Analytics may be used for measurement, while the Pinterest button may be used for Experience (Purpose 3 below). Purposes are grouped into 5 categories each with an id (1, 2, 3, 4, and 5):

• Necessary (id: 1)
• Functionality (id: 2)
• Experience (id: 3)
• Measurement (id: 4)
• Marketing (id: 5)

For even more detailed info on categories and purposes, see our guide here.

Let’s take the Twitter follow button as an example:

We need to 1. Add the class and change the “type” attribute, 2. replace the src and 3. specify the categories.

And the code structure should be like this:

<p>Twitter follow button:</p>

        <!-- please note type="text/plain" class="_iub_cs_activate" data-suppressedsrc="..." (manual tagging) and data-iub-purposes="3" (per-category consent) -->
<a href="https://twitter.com/iubenda" class="twitter-follow-button" data-show-count="false">Follow @iubenda</a>
  <script async type="text/plain" class="_iub_cs_activate" data-suppressedsrc="https://platform.twitter.com/widgets.js" data-iub-purposes="3" charset="utf-8"></script>

See also

• iubenda Privacy Controls and Cookie Solution – Introduction and Getting Started
• How to Customize the Look and Behavior of the Cookie Banner (Beginner’s Guide)
• Introduction to the Prior Blocking of Cookie Scripts
• How to Integrate iubenda’s Privacy Policy on a Website Made in Ucraft

The post How to embed the Privacy Controls and Cookie Solution on a Ucraft site appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

1. take advantage of iubenda’s free version by using our widget;
2. add a direct link to your Ucraft site that will then lead your users to your iubenda-hosted privacy policy; or
3. directly embed the privacy policy text into your Ucraft privacy policy page.

1. Widget

• Access your iubenda dashboard
• Click on [Your website] > Privacy and Cookie Policy > Embed
• Copy the code under the Add a widget to the footer tab

Now:

• Go to your Ucraft project
• Add an Custom HTML element to your footer (more info on this Ucraft support article)

  

• Paste your iubenda snippet and click Embed code (please note that the embedded code will become available once you have connected a domain to your website)

What does this look like?

Here is a working example. Click on the button to open the policy:

2. Direct link

• Access your iubenda dashboard
• Click on [Your website] > Privacy and Cookie Policy > Embed
• Copy the privacy policy URL you find under the Use a direct link tab

Now:

• Go to your Ucraft project
• Add a Paragraph to your footer or edit an existing one (if you need help with Ucraft blocks, take a look at the this guide)
• Insert the text “Privacy Policy” and highlight it
• Click on the Insert/edit link button
• Paste the privacy policy URL in the link settings URL field

And you’re done.

3. Direct text embedding

The direct text embedding option makes your privacy policy look as if it were natively a part of your own site:

• Access your iubenda dashboard
• Click on [Your website] > Privacy and Cookie Policy > Embed
• Copy the code under the Embed the text in the body tab

Now:

• Go to your Ucraft project
• Add a new page and name it “Privacy Policy” (or empty an existing one of all its contents)
• Add a Custom HTML element to your Privacy Policy page (check the Ucraft support for more info about custom code embedding)

  

• Paste your iubenda snippet and click Embed code (please note that the embedded code will become available once you have connected a domain to your website)

  

And you’re done.

See also

• How to Generate a Privacy Policy
• How to Add Services to Your Privacy Policy
• Ways to Use iubenda’s Privacy Policy on Your Site and App
• How to embed the Privacy Controls and Cookie Solution on a Ucraft site

The post How to Integrate iubenda’s Privacy Policy on a Website Made with Ucraft appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Following the European Court of Justice’s ruling on the Planet49 case, it’s very likely that the various EU Data Protection Authorities will soon match the Court’s decision. This likely means requiring website and app owners that use cookies and trackers, to display cookie lifetime details in their cookie policy.

To comply with this recommendation, you’ll need to specify how long the cookies you use – directly or through third parties – are active before they expire (cookies generally last for a determined amount of time).

In both the case of first-party or third-party cookies, iubenda can help.

Cookie database – automatic detection of cookies’ and trackers’ lifetime

With this feature, when you add/edit a service inside the generator, the lifetime for every cookie/tracker is automatically prefilled and added into your cookie policy.

As you can see, the default setting is “Auto”, and the storage duration of cookies and trackers will be sourced and kept updated from our central database.

If you select the “Custom” option, you can define a maximum storage duration across all cookies and trackers, or define a storage duration for each cookie or tracker:

If using the custom option, to find out how long third-party cookies last, you can:

• use the browser console, or
• check the cookie policies of the related services

If the service added doesn’t require any customization (i.e. types of personal data collected, region, and so on) when you add the service, the generator will automatically use the “Auto” setting. If you want to customize the lifetime of cookies and trackers, you can click on the customize button within the corresponding service.

*Not all services install cookies/trackers. In those cases (where a tracker or cookie is not installed by the service) the cookie lifetime section will be empty.

Technical Cookies – Cookie Policy Settings

Lastly, once you’ve generated your privacy policy, you can activate your cookie policy by clicking on the Activate cookie policy button you’ll find under “Cookie policy” label in the right column of the Privacy and Cookie Policy Generator.

Next, indicate whether or not the cookies or trackers that you use are strictly necessary for the operation or delivery of your service (this includes technical cookies). You can do this by selecting the related option under “Cookie Policy settings”.

If you use first-party technical cookies, you can specify a generic maximum lifetime or for each cookie/tracker in hours, days, months, or years.
Furthermore, our solution will detect any cookie/tracker found by our site scanner that is not linked to a service in your privacy policy. These cookies will be shown inside the cookie policy settings, with the option to add them within your documents.

The result? Your iubenda cookie policy will show the cookie lifetime of the various cookies attached to the services in use by your site/app.

See also

• How to generate a cookie policy for the cookie banner
• How to add services to your privacy policy
• How to use the site scanner from within the generator

The post How to Display the Cookie Lifetime in Your Cookie Policy appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In accordance with the Cookie Law, if you operate in the EU (or could potentially have EU users) and you’re using cookies on your site, you must:

1. provide a cookie policy (this can be done by adding a section about your site’s cookies in your privacy policy – Learn more about creating a Privacy and Cookie Policy for Wix);
2. display a cookie banner at the user’s first visit;
3. block non-exempt cookies (e.g. via Google Analytics) before obtaining user consent;
4. release cookies only after informed consent has been provided.

On the Cookies and Your Wix Site guide, Wix invites you to consider adding a third-party tool to notify your site visitors of cookies, since their Cookie Alert App only alerts your site visitors of cookies placed on their browsers, and it doesn’t address all Cookie Law requirements (like the prior blocking). 

How to add the iubenda cookie banner on your Wix website

Here’s where our Privacy Controls and Cookie Solution comes in very handy: it allows you to display a fully customizable cookie banner, collect cookie consent, implement prior blocking and more. It’s easy to run, fast and free up to 25k pageviews/month.

1. Generate your cookie banner:
2. Copy and paste the resulting code snippet within the HEAD tag of your pages as the first element (learn more about embedding custom code on Wix) and you’re done!

This above is an example of a cookie banner created with our Privacy Controls and Cookie Solution. Remember that cookie notices are just one part of the requirements: in order to be fully compliant, you must also link to an accurate cookie policy and block cookies prior to consent.

Set up prior blocking of cookie scripts

Few categories of cookies are exempt from the consent requirement. Therefore, you’ll need to block scripts from running until you get valid user consent.

How to implement prior blocking via manual tagging on your Wix site

Manual tagging is the method of prior-block we’ll be using for the tutorial below. You can view other methods here.

In this tutorial, we are going to block a Twitter follow button.

Not sure which services you need to block? If you’re using a Cookie Policy generated by iubenda, the services listed in your Cookie Policy are most likely the ones you need to modify now.

Step 1: Identify the script

In your Wix dashboard, click on Edit Site

Then, open your Page Code tab to find the script you need to modify (simply search for the service you want to block, in this case, it is the Twitter follow button) and then click Edit Code to open the code editor.

Step 2: Modify your script

Now, we’re going to change the script. To do this, we will make 3 simple changes:

• add this class: _iub_cs_activate to the script tags, and change the “type” attribute from text/javascript → text/plain
• replace the src with data-suppressedsrc or suppressedsrc
• specify the categories of the scripts/iframes with a special comma-separated data-iub-purposes attribute, e.g. data-iub-purposes="2" or data-iub-purposes="2, 3"

More about categories and purposes

Purposes are your legal reasons for processing the particular type of user data. Different scripts on your site will fall into different categories and serve different purposes. For example, Google Analytics may be used for Measurement, while the Pinterest button may be used for Experience (Purpose 3 below). Purposes are grouped into 5 categories each with an id (1, 2, 3, 4, and 5):

• Necessary (id: 1)
• basic interactions & functionalities (id: 2)
• Experience enhancement (id: 3)
• Measurement (id: 4)
• Marketing (id: 5)

For even more detailed info on categories and purposes, see our guide here.

Let’s take the Twitter follow button as an example:

We need to 1. Add the class and change the “type” attribute, 2. replace the src and 3. specify the categories.

And the code structure should be like this:

<p>Twitter follow button:</p>

        <!-- please note type="text/plain" class="_iub_cs_activate" data-suppressedsrc="..." (manual tagging) and data-iub-purposes="3" (per-category consent) -->
<a href="https://twitter.com/iubenda" class="twitter-follow-button" data-show-count="false">Follow @iubenda</a>
  <script async type="text/plain" class="_iub_cs_activate" data-suppressedsrc="https://platform.twitter.com/widgets.js" data-iub-purposes="3" charset="utf-8"></script>

See also

• Privacy Policy for Wix websites
• How to customize the look and behavior of the iubenda cookie banner
• Introduction to the prior blocking of cookies

The post Cookie Banner for Wix Websites appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

postMessage format

The API needs to receive a postMessage call in the following JSON format:

{ 
    __iubCsCall: { 
        command: <api-function-name>, 
        parameters: [...], 
        callId: <a-string-or-integer> 
   } 
}

Where:

• command (string) is the name of the API function you want to call
• parameters (array) is a list of parameters you’re sending to the API function
• callId (string | int) is the Id used to verify that the returned output is for the same API call

Examples

Assuming that the target iframe is on https://example.com, we can send this API call:

ifr.postMessage(
    JSON.stringify({
        __iubCsCall: {
            command: 'isConsentGiven',
            parameters: [],
            callId: 1
        }
    }),
    'https://example.com'
);

This will call the Privacy Controls and Cookie Solution API function isConsentGiven() with no parameters. The output will be returned via postMessage as a JSON string.

In order for the message event to capture this output you’ll need a listener. Depending on the current Privacy Controls and Cookie Solution state, the listener will look like this:

{
    "__iubCsReturn": {
        "returnValue": false,
        "success": true,
        "callId": 1
    }
}

Example with parameters

Here’s how you can pass parameters to your postMessage call:

ifr.postMessage(
    JSON.stringify({
        __iubCsCall: {
            command: 'storeConsent',
            parameters: [{
                consent: false
            }],
            callId: 2
        }
    }),
    'http://localhost:3012'
);

This call to the storeConsent() function will set consent to false and store a consent cookie.

Refresh the page to see the effects of this call. After that, you can verify that the consent is set to false by evaluating _iub.cs.consent.consent in the console (it should output false).

The postMessage JSON output should look like this:

{
    "__iubCsReturn": {
        "success": true,
        "callId": 2
    }
}

Example of a malformed postMessage call

Here’s an output of a malformed postMessage call (e.g. an API function that doesn’t exist):

ifr.postMessage(
    JSON.stringify({
        __iubCsCall: {
            command: 'Consent',
            parameters: [{
                consent: false
            }],
            callId: 1
        }
    }),
    'http://localhost:3012'
);

Since there’s no API function called Consent in the Privacy Controls and Cookie Solution, as a result you should get an error like this:

{
    "__iubCsReturn": {
        "returnValue": null,
        "success": false,
        "callId": 1
    }
}

See also

• How to Configure Your Privacy Controls and Cookie Solution (Advanced Guide)

The post How to invoke Cookie Solution API methods from an iframe appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

This guide will help you to understand all the new features and benefits that come with the TCF v2.0 (v1.1 is no longer supported by IAB), and what action you need to take in order to make the switch.

Ask our experts live

---

View a live demo and have your questions answered in real time by attending our free english “Consent management for publishers” webinar. Discover in practice how you can meet both compliance and advertising industry requirements while ensuring that your ad-reach is maximized.

Attend our free webinar

TCF 2.0 Changes and Updates

TCF 2.0 includes increased functionality, across various aspects of the Framework, for both consumers & publishers. The main changes are listed below.

Banner text updated

The v2 banner text has been made significantly longer to meet IAB’s requirements. The additional text contains essential disclosures related to the enhanced options that we mention in the sections below.

Right to object option included with legitimate interest

While the legal basis of legitimate interest has always been enabled by default, now, the right to object * (to processing based on legitimate interest) is also included as a checkbox directly within the TCF interface.

As with most of our features, you have full customization control and can choose to:

• disable legitimate interest (which will also remove vendors that only rely on this as a legal interest),
• only rely on legitimate interest (which will remove all vendors that only rely on consent), or
• keep the default settings in place.

* On the right to object: Within the TCF, when a user objects using the dedicated checkbox, the objection is handled similarly to a withdrawal/rejection of consent and registered immediately. Therefore, no manual action is required on your part as the Publisher.

googleAdsPreferenceManagement

googleAdsPreferenceManagement is no longer supported in v2 (however, it will stay supported in v1 for as long as v1 is supported by IAB). Separate Google ad personalization settings are no longer needed (or supported) as Google has officially integrated TCF 2.0 and is now included on the global vendor list.

Any modifications you’ve made to your AdSense and Publisher Tag accounts to support the separate Google Ads preference management settings should be undone as they are no longer needed and are now redundant.

Enhanced publisher options

You may now benefit from more fine-tuned control over the behavior of the TCF functionality. Specifically, you can now:

• Support consent only
  Publishers can determine that, for certain purposes, only consent and not legitimate interest is a viable legal basis.
• Support legitimate interest only
  Publishers can determine that, for certain purposes, only legitimate interest and not consent is a viable legal basis.
• Limit the vendors supported to only those which appear in your Privacy and Cookie policy
  Please note, this option must be enabled within the Privacy Controls and Cookie Solution configurator (and not just manually written into the code) for it to be effective.
• Extended purposes
  The list of purposes has been extended to include more options – with categories like “Ad selection, delivery, reporting” transformed into separate categories like – “Select basic ads”, “Create a personalized ads profile”, “Select personalized ads” etc. Giving you more opportunities to collect consent.
• Limit purposes
  You can now choose which purposes are presented to the user – disabling certain purposes entirely if needed.
• PurposeOneTreatment
  When this option is enabled, end-users are not allowed to disable purpose 1: “Store and/or access information on a device”, meaning that the user’s consent is not required. This option should only be enabled if legally supported by the legislation that applies to you (e.g. German legislation). More on the advanced guide.
• enableCMP replaced by enableTcf
  The enableCMP boolean within the Privacy Controls and Cookie Solution is now enableTCF. In general, this doesn’t directly affect you as all parameters and settings that use enableCMP have been automatically updated to support the new name. Furthermore, as enableCMP is integrated with TCF v1, it will remain supported for as long as v1 is supported by IAB.

Which action is required on your part

In order to make the transition:

1. In the Privacy Controls and Cookie Solution configurator, enable the “IAB TCF” Transparency and Consent Framework tab

   

   and ensure that when you click “Edit” the consent checkboxes are checked: “Support Google’s Additional Consent Mode, to gather consent for Google’s advertising partners that do not adhere to the TCF”; and “Request new consent from users that had previously provided consent, if the IAB Framework preference is not found”.

   

   This will add "tcfVersion": 2 and update the stub.js script on your Privacy Controls and Cookie Solution snippet. For example:

   <script type="text/javascript">
   ...
   _iub.csConfiguration = {
       "lang": "en",
       "siteId": XXXXXX, //use your siteId     
       "cookiePolicyId": YYYYYY, //use your cookiePolicyId     
       "enableTcf": true,
       "tcfVersion": 2,
       ...
   };
   </script>
   <script type="text/javascript" src="//cdn.iubenda.com/cs/tcf/stub-v2.js"></script>
   <script>...</script>
   

   In addition, if you’ve enabled the synchronous activator option (required if you’re not directly blocking the vendor scripts), you’ll notice that the safe-tcf.js script will be replaced by safe-tcf-v2.js

2. If you had Google ads personalization set up on your site and made modifications to support it, please undo these modifications as they are now obsolete (as mentioned above, Google has now integrated TCF 2.0).

You can view IAB’s transition timeline here.

Will the update require any action from end-users?

Because the banner text and some internal options have been modified for v2.0, all end-users will be served with a fresh banner on their first visit to your site (post switch-over) as legally required.

If you’ve enabled “remember consent” within the configurator, once consent is granted by a particular user, the Privacy Controls and Cookie Solutionn will remember that consent, as per usual, for up to 12 months, after which time, the user will again be served with a fresh banner.

As with all features, these settings can be customized within your Privacy Controls and Cookie Solution configurator.

If you have any questions or need help at any time, please feel free to reach out to us via chat, or at info@iubenda.com

See also

• The complete guide to IAB GDPR Framework and iubenda’s Consent Management Platform
• IAB TCF v2.0 Transition Timeline

The post TCF 2.0 Transition Guide appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Does my Wix website need a privacy policy?

In accordance with international privacy laws, if your Wix website collects and uses any personal information from users, you’ll need a privacy policy. Here’s what Wix recommends in their own privacy policy:

Wix cannot provide legal advice to Users or their Users-of-Users, however we do recommend that all Users publish and maintain clear and comprehensive privacy policies on their User Websites, in accordance with the applicable laws and regulations, and that all Users-of-Users carefully read those policies and make sure that they consent to them.

How to create a privacy policy for Wix

Here’s where our Privacy and Cookie Policy Generator comes in very handy: customizable from thousands of clauses, available in 15+ languages, and automatically updated if the law changes, our generator allows you to create a legal document in minutes and seamlessly integrate it with your Wix website.

Our privacy policies contain all elements commonly required across many regions and services, and they are created by lawyers, monitored by our lawyers and hosted on our servers to ensure that they are always up-to-date with the latest legal changes and third-party requirements.

How to add a privacy policy to your Wix website

Once you’ve generated your privacy policy with iubenda, you have two ways to integrate it on your Wix website. You can either:

• Add a direct link to your Wix site that will then lead your users to your iubenda-hosted privacy policy; or
• Directly embed the privacy policy text into your Wix privacy policy page.

Keep in mind that whatever method you choose, it’s a common best practice to place the link to your privacy policy in the footer of your website (as we’ll show you below).

Direct link

Access your iubenda dashboard, click on [Your website] > Privacy and Cookie Policy > Embed and copy the privacy policy URL you find under the Use a direct link tab.

Now go to your Wix editor, add a text link to your footer (or edit an existing one) and name it “Privacy Policy”.

Paste the privacy policy URL in the link settings Web Address field and you’re done.

Direct text embedding

The direct text embedding option makes your privacy policy look as if it were natively a part of your own Wix site. Access your iubenda dashboard, click on [Your website] > Privacy and Cookie Policy > Embed and copy the code under the Embed the text in the body tab.

Now go to your Wix editor, click on Menus & Pages > Add Page, name it “Privacy Policy” and click Done (to avoid showing the page link in the main menu, select Hide from menu). Next, click on Add > Embed > Custom Embeds > Embed a widget > Enter code and add your iubenda snippet.

Lastly, add a text link to your footer (or edit an existing one) and name it “Privacy Policy”. Choose the privacy policy page in the link settings and you’re done.

See also

• How to generate a privacy policy with iubenda
• Cookie banner for Wix websites

The post Privacy Policy for Wix Websites appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Collecting cookie consent on AMP pages requires some work. Luckily, iubenda can help. Let’s break down the steps you’ll need to take and see how to integrate our Privacy Controls and Cookie Solution with Google’s Accelerated Mobile Pages, including blocking cookies before user consent and some useful tips for WordPress (our WP plugin supports AMP).

We’ll start with WordPress, as it’s the most popular option for AMP pages. If you’re using a different solution, skip to this section.

iubenda and Google AMP – How to collect cookie consent in WordPress

Our WordPress plugin is fully compatible with Google AMP (it works with both the AMP and AMP for WP plugins), and it allows you to easily collect GDPR cookie consent and block cookies before the user grants consent as required by the Cookie Law.

Step 1 – Download our Cookie and Consent Database plugin

If you haven’t already, download and install our WordPress plugin. For more information, take a look at our installation guide.

Step 2 – Enable the Google AMP support

AMP requires specific configuration parameters and a page hosted on your domain where the configuration is loaded from. 

Once you’ve added the Privacy Controls and Cookie Solution code and enabled the Google AMP support, our plugin will auto-generate the amp.html configuration file.

Step 3 – Block components

As stated on amp.dev/documentation, once enabled the Google AMP support, you’ll have 3 alternative options:

• If you have not enabled per-category consent (with the CS configuration perPurposeConsent: false):
  • use amp-consent-blocking meta tag in the head OR,
  • add data-block-on-consent on all elements that need to be blocked based on consent.
• If you have enabled per-category consent (with the CS configuration perPurposeConsent: true) use instead the data-block-on-consent-purposes attribute with a comma-separated list of consent purposes to set the categories to be prior-blocked (e.g. data-block-on-consent-purposes="1,2,3,4,5")

iubenda and Google AMP – How to collect cookie consent on websites not powered by WordPress

If you’re not using WordPress, follow these steps to integrate our Privacy Controls and Cookie Solution with Google AMP.

Step 1 – Create an HTML file

First of all, copy this HTML code and host it on your HTTPS site in an HTML file (be sure to edit the Privacy Controls and Cookie Solution configuration to reflect your own):

<!doctype html>
<html lang="en">

<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta http-equiv="X-UA-Compatible" content="ie=edge">
    <meta name="robots" content="noindex">
    <title>AMP Cookie Consent</title>
</head>

<body class="iubenda-cookie-solution">
    <span class="iubenda-cs-preferences-link"></span>
    <script type="text/javascript">
        var _iub = _iub || [];

        // Your own Privacy Controls and Cookie Solution configuration
        _iub.csConfiguration = {
            lang: 'en',
            siteId: 896537, // Your own site ID
            cookiePolicyId: 8207462, // Your own cookie policy ID
            enableTcf: true,
            askConsentIfCMPNotFound: true,
            googleAdditionalConsentMode: true,
            googleAdsPreferenceManagement: true,
            floatingPreferencesButtonDisplay: false,
            banner: {
                acceptButtonDisplay: true, // Recommended
                customizeButtonDisplay: true, // Recommended
                rejectButtonDisplay: true // Advisable
            },
        };
    </script>
    <script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>
</body>

</html>

In production, you can host this file on: 

• the same domain, or
• a subdomain, or
• a different domain (in this case you’ll have to enable remoteConsent)

Step 2 – Edit your AMP pages

Now add a copy of this <amp-consent> to your AMP pages:

<amp-consent id="iubenda" layout="nodisplay" type="iubenda">
    <script type="application/json">
        {
            "promptUISrc": "<uri-to-your-cs-page>",
            "postPromptUI": "post-consent-ui"
        }
    </script>
</amp-consent>

Next, add the code for the update preferences button, visible only when preferences are already expressed (to change the position, use the class iubenda-tp-btn--bottom-left, iubenda-tp-btn--top-left or iubenda-tp-btn--top-right instead of iubenda-tp-btn--bottom-right):

<div id="post-consent-ui">
    <button class="iubenda-tp-btn iubenda-tp-btn--bottom-right" on="tap:iubenda.prompt()"></button>
</div>

Finally, add the following <style amp-custom> to your document head:

<style amp-custom>
    .iubenda-tp-btn {
        position: fixed;
        z-index: 2147483647;
        background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='32' height='32' viewBox='0 0 32 32'%3E%3Cpath fill='%231CC691' fill-rule='evenodd' d='M16 7a4 4 0 0 1 2.627 7.016L19.5 25h-7l.873-10.984A4 4 0 0 1 16 7z'/%3E%3C/svg%3E");
        background-repeat: no-repeat;
        background-size: 32px 32px;
        background-position: top .5px left 1px;
        width: 34px;
        height: 34px;
        border: none;
        cursor: pointer;
        margin: 16px;
        padding: 0;
        box-shadow: 0 0 0 1px rgba(0, 0, 0, .15);
        background-color: #fff;
        display: inline-block;
        height: 34px;
        min-width: 34px;
        border-radius: 4px;
        bottom: 0;
        right: 0;
    }

    .iubenda-tp-btn--top-left {
        top: 0;
        left: 0;
    }

    .iubenda-tp-btn--top-right {
        top: 0;
        right: 0;
    }

    .iubenda-tp-btn--bottom-left {
        bottom: 0;
        left: 0;
    }

    .iubenda-tp-btn--bottom-right {
        bottom: 0;
        right: 0;
    }
</style>

Wrapping up, here’s an AMP page example:

<!doctype html>
<html ⚡>

<head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width">
    <meta name="description" content="This is the AMP Boilerplate.">
    <link rel="preload" as="script" href="https://cdn.ampproject.org/v0.js">
    <script async src="https://cdn.ampproject.org/v0.js"></script>
    <script async custom-element="amp-consent" src="https://cdn.ampproject.org/v0/amp-consent-0.1.js"></script>
    <style amp-boilerplate>
        body {
            -webkit-animation: -amp-start 8s steps(1, end) 0s 1 normal both;
            -moz-animation: -amp-start 8s steps(1, end) 0s 1 normal both;
            -ms-animation: -amp-start 8s steps(1, end) 0s 1 normal both;
            animation: -amp-start 8s steps(1, end) 0s 1 normal both
        }

        @-webkit-keyframes -amp-start {
            from {
                visibility: hidden
            }

            to {
                visibility: visible
            }
        }

        @-moz-keyframes -amp-start {
            from {
                visibility: hidden
            }

            to {
                visibility: visible
            }
        }

        @-ms-keyframes -amp-start {
            from {
                visibility: hidden
            }

            to {
                visibility: visible
            }
        }

        @-o-keyframes -amp-start {
            from {
                visibility: hidden
            }

            to {
                visibility: visible
            }
        }

        @keyframes -amp-start {
            from {
                visibility: hidden
            }

            to {
                visibility: visible
            }
        }
    </style>
    <noscript>
        <style amp-boilerplate>
            body {
                -webkit-animation: none;
                -moz-animation: none;
                -ms-animation: none;
                animation: none
            }
        </style>
    </noscript>
    <style amp-custom>
        .iubenda-tp-btn {
            position: fixed;
            z-index: 2147483647;
            background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='32' height='32' viewBox='0 0 32 32'%3E%3Cpath fill='%231CC691' fill-rule='evenodd' d='M16 7a4 4 0 0 1 2.627 7.016L19.5 25h-7l.873-10.984A4 4 0 0 1 16 7z'/%3E%3C/svg%3E");
            background-repeat: no-repeat;
            background-size: 32px 32px;
            background-position: top .5px left 1px;
            width: 34px;
            height: 34px;
            border: none;
            cursor: pointer;
            margin: 16px;
            padding: 0;
            box-shadow: 0 0 0 1px rgba(0, 0, 0, .15);
            background-color: #fff;
            display: inline-block;
            height: 34px;
            min-width: 34px;
            border-radius: 4px;
            bottom: 0;
            right: 0;
        }

        .iubenda-tp-btn--top-left {
            top: 0;
            left: 0;
        }

        .iubenda-tp-btn--top-right {
            top: 0;
            right: 0;
        }

        .iubenda-tp-btn--bottom-left {
            bottom: 0;
            left: 0;
        }

        .iubenda-tp-btn--bottom-right {
            bottom: 0;
            right: 0;
        }
    </style>
    <link rel="canonical" href=".">
    <title>My AMP Page</title>
</head>

<body>
    <amp-consent id="iubenda" layout="nodisplay" type="iubenda">
        <script type="application/json">
            {
                "promptUISrc": "<uri-to-your-cs-page>",
                "postPromptUI": "post-consent-ui"
            }
        </script>
    </amp-consent>
    <!-- This is the update preferences button, visible only when preferences are already expressed -->
    <div id="post-consent-ui">
        <button class="iubenda-tp-btn iubenda-tp-btn--bottom-right" on="tap:iubenda.prompt()"></button>
    </div>
</body>

</html>

Note:

• Add <script async="" custom-element="amp-geo" src="https://cdn.ampproject.org/v0/amp-geo-latest.js"></script> only if you want to limit consent collection to EU
• If these resources are already added to the page, an harmless error will be raised

Step 3 – Block components

As stated on amp.dev/documentation, once enabled the Google AMP support, you’ll have 3 alternative options:

• If you have not enabled per-category consent (with the CS configuration perPurposeConsent: false):
  • use amp-consent-blocking meta tag in the head OR,
  • add data-block-on-consent on all elements that need to be blocked based on consent.
• If you have enabled per-category consent (with the CS configuration perPurposeConsent: true) use instead the data-block-on-consent-purposes attribute with a comma-separated list of consent purposes to set the categories to be prior-blocked (e.g. data-block-on-consent-purposes="1,2,3,4,5").

See also

• Privacy Controls and Cookie Solution – WordPress Plugin Installation Guide
• How to collect cookie consent on AMP pages
• GDPR Cookie Consent Cheatsheet

The post How to integrate iubenda Privacy Controls and Cookie Solution with Google AMP (WordPress method included) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Confused about state privacy laws? Here’s what you need to do:

1. Not sure if US laws apply to you? Do this free 1-min quiz
2. How to activate the US State law Text
3. How to activate/modify a Service’s declaration of sale within the generator
4. Examples of state-specific text additions to our privacy policy generator

State laws in the United States, including the California Consumer Privacy Act (CCPA), are privacy regulations that vary from state to state. These laws aim to protect the privacy rights of individuals within their respective states. It is important to understand and comply with the specific privacy laws applicable to your state.

When generating privacy policies with iubenda or any other service, ensure that the generated documents comply with the relevant state laws. These documents should include provisions that align with the legal standards defined by the specific state’s privacy laws. The added provisions should apply only to users to whom you are required to offer specific rights and protections under the applicable state law.

When enabling specific options related to state laws, the generator should indicate which services or activities may be considered a sale under the state’s definition. This helps ensure transparency and compliance with the respective state’s privacy regulations.

How to activate the US State law Text

To ensure compliance with applicable state privacy laws, follow these general steps to activate the relevant provisions in your privacy policy generator:

By enabling these disclosures, you are indicating your intent to comply with the privacy standards defined by US State laws. This feature helps ensure that the generated privacy policy aligns with the specific requirements and rights afforded to users in the respective state.

How to activate/modify a Service’s declaration of sale within the generator

The solution will also indicate and highlight services that may be considered to be a sale under the definitions – as consumers must be able to identify and opt out of these services.

In the services panel, whenever you add a service that could be considered a sale, the following options will be made available. If the service has fields that require customization, you will see these checkboxes within the usual customization screen (which typically appears after adding that service).

Once enabled, your policy will display a section that informs readers that a sale is happening, that they have the right to opt out and will likely also give several options to do so. The current opt-out options given within the privacy policy are opt-out via links or via getting in touch.

If you deselect the pre-checked “consider as sale …” checkboxes or the generator determines that no sale is happening (based on the services you selected when creating your policy), your privacy policy will display a small statement to that effect. 

Once activated and saved within the generator, your embedded privacy policy is automatically updated with the text – no need to re-integrate the code on your site!

Examples of state-specific text additions to our privacy policy generator

California Consumer Privacy Act (CCPA)

Important note regarding the personal information of minors

If your processing activities constitute as sale (as mentioned above) under the CCPA, and this processing potentially includes the personal information of minors, you will need to make some additional disclosures by selecting from the following services within the generator.

Please note that 2) and 3) are not mutually exclusive, they can be used at the same time. Additionally, be sure to review your processes to ensure that you meet CCPA requirements regarding minors.

Additional CCPA Requirements

Toll-free number indication

If you run a business that doesn’t operate exclusively online and has a direct relationship with the user, then you must indicate “two or more designated methods” for submitting CCPA requests. One of these methods must be a toll-free telephone number. You can easily add this information via the “Owner field” within the generator. 
Update your privacy policy every 12 months
The CCPA also requires the following: 

What changes have been made to the policy text?

In addition to the above information, you can find a summary of the changes introduced to meet CCPA requirements here.

CCPA policy additions

• plain-language clauses as recommended under US law;
• a section that holds the bulk of CCPA-relevant disclosures:
  • outlining the purposes of processing,
  • outlining the sources of the data collection,
  • outlining the particular categories of personal information collected over the last 12 months,
  • which informs users of their rights under the CCPA and how those rights can be exercised,
  • which details how and when exercised rights will be honored,
  • informing consumers on how they can opt out;
• information added to the privacy policy highlighting the services that constitute a sale under the CCPA;
• information added to the privacy policy regarding what category of personal information a particular activity belongs to; and
• any other CCPA terminology and definitions.

Once activated and saved within the generator, your embedded privacy policy is automatically updated with the CCPA text – no need to re-integrate the code on your site!

Want to learn more about the CCPA and its full requirements? Read the How to Comply section of our detailed CCPA guide.

Virginia Consumer Data Protection (VCDPA)

VCDPA policy additions

• Categories of personal data processed by your organization. 
• Organization’s purpose for processing personal data.
• How users may exercise their rights, including how they can appeal a decision on their requests. You must provide one or more methods for users to submit a request.
• Categories of personal data that your organization shares with third parties if any.
• Categories of third parties, if any, with whom your organization shares personal data.

Additional information

Specific service clauses related to the VCDPA include:

1. Profiling of Virginia consumers;
2. Collection of personal data about Virginia consumers below the age of 13; and
3. We do not collect personal data about Virginia consumers below the age of 13.

To enable the new US-specific clauses, simply click “Enable disclosures for Users Residing in the United States” from within the Privacy and Cookie Policy Generator. This will allow you to meet the strictest of US standards.

Colorado Privacy Act (CPA)

CCPA policy additions

CPA privacy notice includes the following:

1. Categories of personal data collected or processed.
2. Purposes for which the categories of personal data are processed.
3. How and where consumers can exercise their rights, including the contact information and how to appeal a controller’s action with regard to a consumer’s request.
4. Categories of personal data that are shared with third parties, if any;
5. Categories of third parties with whom the personal data are shared, if any.

Utah Consumer Privacy Act (UCPA)

UCPA policy additions

1. Categories of Personal Data Processed: Identify the types of personal data that your organization collects and processes, such as names, email addresses, and payment information.
2. Purposes for Processing Personal Data: Describe the reasons why your organization collects and processes personal data, such as to fulfill orders, provide customer support, or improve products or services.
3. Consumer Rights: Explain how consumers can exercise their rights, such as the right to access and delete their personal data. Note that the UCPA does not grant consumers the right to request the correction of inaccurate personal data.
4. Sharing of Personal Data: Disclose the categories of personal data that your organization shares with third parties, if any. For example, you may share payment information with a payment processor or mailing addresses with a shipping provider.
5. Third Parties: Identify the categories of third parties with whom your organization shares personal data, if any. This could include vendors, service providers, or marketing partners.

Additional information

Unlike other US state-level privacy legislations, it’s important to note that, under UCPA, opt-out links come into consideration only in relation to consumers’ right to opt out of the processing of sensitive data.

To ensure compliance with the UCPA, you should include a clear and accessible opt-out process in your privacy policy.

Connecticut Data Privacy Act (CTDPA)

CTDPA policy additions

• Categories of Personal Data: Your privacy policy must include a list of the categories of personal data that you process.
• Purposes for Processing: Your privacy policy must clearly state the purposes for processing personal data. This includes any reason why you collect and use personal data, such as to fulfill a contract or provide a service.
• Consumer Rights: Your privacy policy must explain how consumers can exercise their rights under the law. This includes how a consumer can access, correct, delete, or restrict the processing of their personal data. You must also include information on how a consumer can appeal a decision related to their request.
• Third-Party Sharing: If you share personal data with third parties, your privacy policy must specify the categories of personal data that you share. 
• Third-Party Categories: Your privacy policy must also specify the categories of third parties with which you share personal data.
• Contact Information: Your privacy policy must provide an active electronic mail address or other online mechanism that consumers can use to contact you with questions or concerns about their personal data.
• Sale or Targeted Advertising: If you process personal data for the purposes of sale or targeted advertising, your privacy policy must clearly and conspicuously disclose this fact. You must also provide information on how consumers can exercise their right to opt out of such processing.

Additional information

Effective January 1, 2025, you must also allow consumers to opt out of the processing of their personal data for targeted advertising or sale through an opt-out preference signal sent via a platform, technology, or mechanism, with the consumer’s consent.

Texas Data Privacy and Security Act (TDPSA)

Texas Data Privacy and Security Act (TDPSA) Policy Additions

• Categories of Personal Data: List the types of personal data your organization processes, including names, email addresses, payment info, and sensitive data (e.g., biometric data, precise geolocation).
• Purpose for Processing Personal Data: State why personal data is collected, such as fulfilling orders, providing services, or marketing.
• Consumer Rights: Describe how consumers can exercise their rights to:
  • Access, correct, delete, or obtain a copy of their data.
  • Opt out of targeted advertising, sale of personal data, or certain profiling.
• How Users May Exercise Their Rights: Provide a method for submitting requests, such as an online form or contact email, and explain the process for appeals.
• Data Sharing: Disclose the categories of personal data shared with third parties and identify these third-party categories (e.g., vendors, service providers).

Additional Information

The TDPSA applies broadly to businesses in Texas, with exemptions for small businesses as defined by the U.S. Small Business Administration. Include an opt-out process for data sales and targeted advertising. 

Oregon Consumer Privacy Act (OCPA) 

Oregon Consumer Privacy Act (OCPA) Policy Additions

• Categories of Personal Data: List the personal data your business collects, including sensitive data (e.g., biometric data, precise location).
• Purpose for Processing: State why personal data is collected, including for targeted advertising or profiling.
• Consumer Rights: Explain how Oregon consumers can:
  • Access, transfer, correct, or delete their data.
    • Opt out of data sales, targeted advertising, and profiling.
• Use the Global Privacy Control (from July 1, 2026) to opt out of data sales or targeted ads.
• How Users May Exercise Their Rights: Provide a method (e.g., online form, email) for submitting requests and outline how to withdraw consent.
• Data Sharing: Disclose categories of personal data shared with third parties and identify these third-party categories.

Additional Information

Obtain explicit consent before processing sensitive data. Starting July 1, 2026, recognize “Global Privacy Control” signals for opt-outs.

Montana Consumer Data Privacy Act (MTCDPA) 

• Categories of Personal Data: List the types of personal data processed, including sensitive data (e.g., biometric data, health conditions, children’s data).
• Purpose for Processing: State why personal data is collected, such as fulfilling services, targeted advertising, or profiling.
• Consumer Rights: Describe how Montana consumers can:
  • Access, correct, delete, and obtain a copy of their data.
  • Opt out of data sales, targeted advertising, and profiling.
  • Submit requests without needing an account.
• How Users May Exercise Their Rights: Provide a method (e.g., online form, contact email) for submitting requests. Explain the appeal process if requests are denied.
• Data Sharing: Disclose categories of personal data shared with third parties and identify these third-party categories.

Additional Information

Obtain explicit consent before processing sensitive data or selling data of young consumers (13–16 years). Starting January 1, 2025, honor universal opt-out signals for data sales or targeted advertising.

Rhode Island Data Transparency and Privacy Protection Act (DTPPA) Policy Additions

Categories of Personal Data: List the categories of personal data collected/processed and sensitive data.

Purpose for Processing Personal Data: Describe the purposes for collection/use (service delivery, customer support, security, personalization). Explicitly describe whether you process data for targeted advertising, the sale of personal data, or profiling, and why.

Consumer Rights: Explain Rhode Island consumers’ rights to access, correct, delete, and obtain a portable copy of personal data, and opt out of: targeted advertising, sale of personal data, and profiling that produces legal or similarly significant effects

How Users May Exercise Their Rights: Provide secure, reliable methods to submit requests (webform/email) and explain authorized agent submission if you allow it. Include that you respond within 45 days (free once per year), and provide an appeal process with written responses given within 60 days. If you process sensitive data, explain how consumers can grant and revoke consent, and that you will honor consent revocation within 15 days.

Data Sharing: Disclose the categories of personal data shared and of third parties receiving data (processors/service providers, analytics). If personal data is or may be sold, identify categories of third parties to whom it is (or may be) sold. Provide opt-out methods for targeted advertising and data sales, including any authorized agent route you support.

Additional Information: If you are a commercial website or internet service provider subject to Rhode Island jurisdiction, note that you must designate a controller (and provide controller contact information in the notice). Please note that the DTPPA does not mention the controllers’ obligation to honor universal opt-out signals.

Further reading:

See also

• CCPA Guide
• CCPA: How to add a notice of collection and a “Do not sell” link

The post How to Apply State-Specific US Standards within the Generator appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

It boasts built-in compatibility with Contact Form 7, WP Forms, WordPress comment, WooCommerce checkout forms and Elementor Forms, but can be manually integrated with any type of web-form and can even store consent proofs for consents collected offline (e.g in-store sign-ups) via WP media upload.

Key features:

• The plugin detects and identifies all supported forms that are embedded in the website.
• It’s auto-compatible with and allows super easy mapping of Contact Form 7, WP Forms, WordPress comment and WooCommerce checkout forms.
• It allows manual integration with any type of web-form.
• For each consent, track the form/wording the user was prompted with.
• Flexibly upload any form of proof of consent or legal notice, including a PDF if consent was collected offline.
• It provides a high granularity: map individual form fields, exclude fields (like password inputs), add legal notices available at the time of consent collection, indicate double opt-in, set preferences and more.
• REST HTTP API and JS SDK, to give you total control and how and when consent is stored.
• Store multiple preferences for each user (e.g. if you have multiple newsletters or opt-ins).
• Features an easy-to-use interface for entering custom scripts and iframes.
• It provides API input field for quick and easy activation.

Installation and configuration

Once you’ve installed our Cookie and Consent Database Plugin for the GDPR & ePrivacy, you can start configuring it.

Unlike when using the JavaScript method, there’s no need to include the Consent Database code in your head, or to provide a script with a load/submit function: the plugin will take care of it.

Input the API key

Select the Consent Database tab and input the Public API key ( you can find this in your iubenda dashboard > [Your website] > Consent Database > Embed).

Detect your forms

Once clicked on Autodetect Forms, the plugin will show all supported forms installed on your site, listing them either under “All“, “Mapped” and “To Map“.

Map your forms

To map a form, simply click on the form title to open up the Mapping window and select the fields that you’d like the Consent Database to record the data from.

Indicate your legal documents

The plugin also lets you indicate your legal documents, including privacy policies, cookie policies, terms and conditions, and custom documents.

When you’re done editing, just click on Save Settings at the bottom-right of the page.

Once you’ve collected your consents, you’ll be able to sort and analyze your data in the Consent Dashboard.

See also

• Consent Database – Introduction and Methods
• How to use the Consent Database with WordPress & Contact Form 7 (JavaScript method)
• Privacy Controls and Cookie Solution– WordPress Plugin Installation Guide

The post Consent Database – WordPress Plugin Installation Guide appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

US state privacy laws impose significant requirements on businesses with considerable legal and technical implications.

The US state privacy laws provide consumers with more control over their personal information, by granting dedicated consumer rights and requiring businesses to be transparent about their privacy practices. Although generally consistent, there may be, however, differences in scope, consumers’ rights, and enforcement among the different state laws. Check our US privacy cheatsheet for more information.

Our solutions take the guesswork out of compliance by doing the heavy technical and legal lifting.

With iubenda, you can simplify compliance with these legal requirements

Privacy and Cookie Policy Generator →

US state privacy laws require you, among others, to provide your users with an up-to-date Privacy Policy, including specific information, such as US users’ privacy rights and a description of your personal information processing practices.

With our Privacy and Cookie Policy Generator, you can now enable, with a single US toggle, a compliance solution for all US state privacy laws that we currently support and ALL upcoming US state legislations that we will support in the future.

For an overview of the US state privacy laws that we currently support and the main related requirements you can check our guide

Generate your US Privacy Policy or update your existing policy by clicking “Enable disclosures for users residing in the United States” to activate the new US-specific sections and clauses.

You can find the switch here:

• log into your privacy policy admin area;
• enter the editing of your privacy policy, which can be found via our Dashboard, then click on your policy and go to Edit from the privacy policy section;
• under the heading “Enable disclosures for users residing in the United States” choose Enable.

This allows you to cover your specific needs and react based on where your users/clients are located and choose accordingly.

Once you have enabled it, you will see that the link to the US-specific section of your privacy policy has been added to your Privacy Policy.

Take a look at this example of a Privacy Policy generated with iubenda

New options available for US state privacy laws

When you activate “Enable disclosures for users residing in the United States” within the legislation-specific standards, various US-related options will appear on all services you add to your Privacy and Cookie Policy: 

• Mark as a service provider/processor or contractor
• Mark as a third-party service

If you select the option “Mark as a third-party service” you will see the following sub-options: 

• Consider as a Sale in California
• Consider as a Sale in [list of all applicable US state privacy laws]
• Consider as Sharing in California
• Consider as Targeted Advertising in [list of all applicable US state privacy laws]

Under US state privacy laws, third parties are generally defined as a person or legal entity who is not any of the following:
(1) The business/controller with whom the consumer intentionally interacts and collects personal information from the consumer.
(2) A service provider/processor to the business.
(3) A contractor.

If the service is not flagged as a third-party service according to the above definition, the sub-options for sale/sharing and target advertising do not apply.

We introduced an automated services mapping feature that displays the checkboxes as pre-selected according to the definitions of sale, sharing, and targeted advertising set by applicable laws.

When marking the processing performed through a service as falling within one or more of the categories listed above, the related wording will be automatically added or removed in the privacy policy section dedicated to the relevant US state we cover

Any predefined setup can be easily overwritten and you may customize it according to your specific needs.

Sensitive Personal Data types 

When you activate “Enable disclosures for users residing in the United States” within the legislation-specific standards, for some services, where applicable, you will see a new field at the service level called “Sensitive Personal Data”.

For each of these services, you can select one or multiple categories of sensitive personal data being processed, as shown below:

Addition of new US-specific clauses 

Our Privacy and Cookie Policy Generator offers additional clauses related to specific processing activities, as required by some US state privacy laws.

This includes, among others, clauses related to the processing of children’s personal information and the processing of personal data for profiling purposes. Here are some examples of US-specific clauses:

• Collection of Personal Information about California consumers below the age of 13
• Collection of Personal Information about Users below the age of 13 in the United States
• We do not collect Personal Information about California consumers below the age of 16
• We do not collect Personal Information about Users below the age of 13 in the United States
• Profiling of Users in [list of all applicable US state privacy laws]

These additional clauses can be beneficial but are intended as broad and generic descriptions, as we do not know exactly how you process your users’ personal information. Therefore, we highly recommend that you check if they apply to your case and, if needed, describe your processing activities in more detail byadding custom clauses.

For more information on privacy policies click here.

Privacy Controls and Cookie Solution →

US privacy controls 

If you process consumers’ personal information for certain purposes, including but not limited to, targeted advertising or engage in the sale or sharing of personal data, under certain US state privacy laws, you are likely required to:

• clearly and prominently inform users about these processing activities and their right to opt out of them;
• provide users with easily accessible privacy controls to exercise their right to opt out at any time; and 
• respect their preferences.

Our Privacy Controls and Cookie Solution help you comply with these requirements.

How do I start complying?

Once you have completed the activation of the new US-specific clauses within the Privacy and Cookie Policy Generator, make sure the “US State Laws” tile within the Privacy Controls and Cookie Solution is enabled: the solution will auto-configure to help you meet the new US requirements allowing your users to exercise their right to opt out.

Simply select where you and your users are based while configuring the Privacy Controls and Cookie Solution, and the solution will do the rest!

Haven’t generated a Privacy Policy with us, or want to customize things yourself?

Within the Privacy Controls and Cookie Solution Generator simply enable the US State Laws option and the support to manage users’ opt-out preferences (if applicable).

To do this, make sure you toggle on US State Laws and click on the Edit button.

Next, click on Manual configuration and select the options that apply to your case:

• Allow users to opt out of the sale of their personal information [list of all applicable US state privacy laws]
• Allow users to opt out of the sharing of their personal information [list of all applicable US state privacy laws]
• Allow users to opt out of targeted advertising [list of all applicable US state privacy laws]

“Your Privacy Choices” link

The Privacy Controls must be easily accessible, in order to allow your users to freely exercise their privacy preferences at any time. Furthermore, some US state laws, such as the CCPA, as amended by the CPRA, set a mandatory predefined format (the white and blue icon shown below) and label (“Your privacy choices”) for the link to the Privacy Controls.

How do I start complying?

Our Privacy widget helps you comply with all these requirements in the easiest way possible: a small, unobtrusive widget, with a predefined format and label, will be displayed on every page of your website after your user has set their preferences.

Don’t want to use our Privacy widget and prefer a manual link to place wherever you like?

To do this, under the Style & Text section, click Edit on the Privacy widget box, then simply choose the option to add it Manually.

If you choose to add the link manually, remember to place it on your website/app in an easily accessible spot, for example, the footer or the application settings.

Direct link to the Notice at Collection for California consumers 

The CCPA, as updated by the CPRA, requires you to make the Notice at Collection readily available where consumers will encounter it at or before the point of collection of any personal information, including sensitive personal information (if applicable). For example, by posting a conspicuous link to the notice on the home page of your website, in the settings menu of your app, and on all web pages where personal information is collected.

The purpose of the Notice at Collection is to provide consumers with timely notice about, among others, the categories of personal information, including sensitive personal information, collected and processed, the purposes for which such information is collected and processed, and whether that information is sold or shared, so that consumers have a tool to understand, and therefore control, your use of their personal information.

To learn more about what should be included in the Notice at Collection, read our guide.

Thanks to an advanced feature of our Privacy Policy generator you can easily align with with this requirement (and its 12-month look-back period).

If you delete all the services that were using a specific personal information category, the Notice at Collection will automatically update to clarify that you collected that category in the past 12 months but you are no longer collecting it. Once the 12-month period lapses the category will be permanently removed from the Notice at Collection. 

You can also manually permanently remove a category by deleting the service from the “Recently deleted” services tile in the Privacy Policy Generator.

How do I start complying?

Our Privacy and Cookie Policy Generator, together with our Privacy Controls and Cookie Solution helps you comply with this CCPA/CPRA requirement.

To do so:

1. Make sure you have set the Enable disclosures for users residing in the United States as ENABLED in the legislation-specific standards inside the Privacy and Cookie Policy generator;
2. Make sure you have enabled the US State Laws option in the Privacy Controls and Cookie Solution;
3. Under the Style & Text section, click Edit on the Privacy widget box, then simply choose whether you want to automatically add the widget or manually embed the link to the Notice at Collection.

Sensitive personal information 

Under certain US state laws, in order to process consumers’ sensitive personal information, you need to obtain their prior consent.

That’s why you should provide a choice mechanism on your website/app that allows users to freely give (or withdraw) their consent to the processing of their sensitive personal information.

How do I start complying?

Our Privacy and Cookie Policy Generator, together with our Privacy Controls and Cookie Solution helps you comply with this requirement. To know how and learn more about the definition of sensitive personal information according to the different US state privacy laws, read our dedicated guide.

How to make sure that “Do Not Sell” signal is honored

If the user expresses the choice to opt out of the sale of their data, this choice must be honored. There are three ways to make sure of this.

1. If the sale is performed by a service/vendor that adheres to the IAB Global Privacy Platform (GPP) and CCPA/CPRA Compliance Framework

In this case, our integration with the IAB Global Privacy Platform (GPP) and CCPA/CPRA Compliance Framework will take care of notifying the vendors that an opt-out from sale has occurred.

2. If the sale is performed by a service/vendor that provides a specific configuration to signal that the user has opted out of sale

This is, for instance, the case with Google, which allows you to send a specific signal whenever an opt-out has occurred. The instructions are provided in this article and apply to Google Ads and Google Analytics.

Other vendors may provide similar instructions.

3. If the sale is performed by a service/vendor that does not adhere to the IAB Global Privacy Platform (GPP) and CCPA Compliance Framework nor provides a way to communicate the opt-out

In this case, you’ll have to apply the class _iub_cs_activate to the script tag of each of these services, change the type attribute from text/javascript to text/plain and add the applicable data-iub-purposes="..." attribute comma separated IDs: e.g. data-iub-purposes="s,sh,adv,sd8"

This is the list of purposes handled by the Privacy Controls and Cookie Solution:

• s → selling of personal info
• sh → sharing of personal info
• adv → targeted advertising
• sd8 → sensitive Data, Precise Geolocation Data

<script class="_iub_cs_activate" type="text/plain" data-iub-purposes="..." src="...">
...
</script>

This can be done manually or via a tag manager like Google Tag Manager.

For further information on US state privacy laws:

• The Upcoming Connecticut Law: What you need to know
• Utah Law: What you Need to Know
• The Upcoming Colorado Law: What you Need to Know

The post How iubenda can help with US state privacy laws compliance appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

The Long answer

The contents of a terms and conditions document typically spans multiple laws (everything from consumer law to copyright law). They should allow you to set your rules for user behavior, including appropriate disclaimers for any misuse of your product or service. This is trickier than it seems as even businesses with the same model may have different processes, needs, and user behavior. Let’s look at some examples to better illustrate this.

Business Model

First, let’s look at how business model influences the content of your terms and conditions by exploring a few questions.
These are some of the questions you should ask yourself when evaluating your business model:

• Is your business mostly concerned with monetizing content?
• If you run an e-commerce site, do you sell digital products, physical products, or both?
• Do you sell primarily to other businesses, or only to consumers (b2b vs. b2c)?
• Can your users sell to other users?

Not only do each one of these business models have different needs, but specific or various laws may apply depending on which model you use. For example, under many countries’ laws, consumers have certain mandatory rights that you’re legally required to disclose. As you can imagine, where multiple laws and regulations are concerned, it’s best to leave the drafting to legal experts.

Business Processes

Business processes can vary widely even within the same general business model.
For example, two eCommerce stores, selling the exact same products can have different:

• sign-up processes; account types (e.g. guest vs logged in);
• user roles (can users sell to other users, up-vote ratings, leave comments, report other users);
• payment options (paypal, credit card, bitcoin, in-store virtual credit, gift cards);
• return and shipping policies; and more.

Needless to say, your actual business processes heavily determine how users interact with your service, and by effect, the rights you grant, rules you implement and the disclaimers that you make.

Business Needs

Lastly, considering that terms and conditions are meant to protect you, the business owner, it’s critically important that you set rules specific to your actual needs. Let’s take a look at some popular situations in which terms and conditions are used to set legally binding rules.

Businesses often choose to set explicit rules where:

• different user levels exist (eg. registered vs non-registered);
• the business facilitates or otherwise process payments and/or other sensitive user data;
• the business wants to communicate expectations for user behavior (including comments) and state grounds for termination of accounts;
• users are allowed to upload their own content;
• the business participates in affiliate programs;
• the business would like to have some legally enforceable control over, and set rules about, how their product, service or content may be used;
• the business provides content or products which can potentially cause harm if misused;
• the business would like to formally set the governing law; and more.

As you can imagine, business needs are entirely individual and evolve with time.

Considering the above, a more accurate way to rephrase the original question would be: Should I just use a template for the only legally binding agreement between myself and my users that allows me to set rules specific to my business processes and to protect my business from liabilities? We strongly suggest that you do not.

A terms and conditions document is more than just a formality, it is a valuable tool that protects you as a business owner.

How iubenda can help

Our Terms & Conditions generator lets you to easily generate and manage Terms and Conditions that are professional, customizable from over 100 clauses, drafted by an international legal team, available in 8 languages, and up to date with the main international legislations. It is powerful, precise, and capable of handling even the most complex, individual scenarios and customization needs.

It comes with:

• guided set-up;
• hundreds of possible personalizations;
• legislation monitoring;
• plug-and-go integrations for popular store platforms such as Shopify and WooCommerce;
• pre-defined scenarios: buildable text modules for marketplace, affiliate programs, copyright, e-commerce, mobile, and more.

The solution is optimized for everything from e-commerce, blogs, and apps, to complex scenarios like marketplace and, SaaS.

Getting started is easy. Simply create a free account, activate the Terms and Conditions (requires 1 Ultra license) within the dashboard and start generating.

For a list of the full features of the Terms and Conditions Generator, click here or read the guide here.

See also

• What are the Terms and Conditions and when are they needed?
• What should basic Terms and Conditions include?
• How to generate Terms and Conditions

The post Can I Use a Terms and Conditions Template? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

iOS

Add the iubenda SDK to your project

To integrate the iubenda SDK into your iOS project, you have two options depending on your preference and project setup: CocoaPods or Swift Package Manager.

• Using CocoaPods
• Using Swift Package Manager

platform :ios, '10.0'
source "https://github.com/iubenda/cocoapods.git"
target 'MyApp' do
  use_frameworks!
  pod 'IubendaMobileSDK', '2.6.4'
end

Initialize the SDK

In your AppDelegate class, inside the didFinishLaunchingWithOptions method, create a configuration object with your settings and call IubendaCMP.initialize()

let config = IubendaCMPConfiguration()
config.gdprEnabled = true
config.googleAds = true
config.siteId = "12341234"
config.cookiePolicyId = "56785678"
config.applyStyles = true
config.cssFile = Bundle.main.path(forResource: "custom_style", ofType: "css")
config.jsonFile = Bundle.main.path(forResource: "config", ofType: "json")
IubendaCMP.initialize(with: config)

Settings

Configuration example with custom CSS

let config = IubendaCMPConfiguration()
config.gdprEnabled = true
config.forceConsent = true
config.googleAds = true
config.siteId = "12341234"
config.cookiePolicyId = "56785678"
config.acceptIfDismissed = true
config.applyStyles = false
config.cssFile = Bundle.main.path(forResource: "custom_style", ofType: "css")
config.jsonFile = Bundle.main.path(forResource: "config", ofType: "json")
IubendaCMP.initialize(with: config)

custom_style.css:

/***************************************************************************
// * iubenda Privacy Controls and Cookie Solution                                              *
// *                                                                       *
// * Sample CSS v2.2.6                                                     *
// *                                                                       *
// * (c) 2019 iubenda srl <info@iubenda.com>                               *
// * All Rights Reserved.                                                  *
// *                                                                       *
// *************************************************************************
//
// CHANGELOG
//
// 2.2.7 - 2020-06-18
// - Fix container breaking on mobile.
//
// 2.2.6 - 2020-05-27
// - Hide scroll bar visibility.
// - Fix brand image height on mobile.
//
// 2.2.5 - 2020-05-06
// - Fix IE flex content.
// - Fix text overflow.
//
// 2.2.3 - 2020-04-21
// - Cursor pointer
// - Button text ellipsis
// - Equalize shadows top/bottom modal bar
//
// 2.2.2 - 2020-04-06
// - Add pointer events auto to the overlay
//
// 2.2.1 - 2020-03-06
// - Introduce popover.
//
// 2.2.0 - 2019-11-07
// - Introduce brand customizations
//
// 2.1.5 - 2019-11-22
// - Add class to go fullscreen.
//
// 2.1.4 - 2020-03-25
// - Make the banner shadow darker
//
// 2.1.3 - 2020-01-22
// - Fix banner not appearing on iPhone.
//
// 2.1.2 - 2019-11-07
// - Fix buttons height on IE.
//
// 2.1.1 - 2019-10-30
// - Fix buttons margin and customize-advertising-tracking button width on mobile.
//
// 2.1.0 - 2019-10-24
// - Introduce text overflowing mask and style for reject button.
//
// 2.0.4 - 2019-06-24
// - Convert close button width to min-width
//
// 2.0.3 - 2019-05-24
// - Introduce new positioning options
//
// 2.0.2 - 2019-05-02
// - Fix text spaces when custom content
//
// 2.0.1 - 2019-04-09
// - Add rules for buttons group
//
// 2.0.0 - 2019-02-01
// - Full rewrite to accommodate the new markup
//
// 0.0.1 - 2015-04-01
// - First implementation of the sample CSS
*/

/*
-----------------
IMPORTANT: Changing the following values may prevent the notice from being displayed properly.
-----------------
*/
#iubenda-cs-banner {
  font-size: 15px !important;
  background: none !important;
  line-height: 1.4 !important;
  position: fixed !important;
  z-index: 99999998 !important;
  top: 0 !important;
  left: 0 !important;
  width: 100% !important;
  height: 100% !important;
  border: 0 !important;
  margin: 0 !important;
  padding: 0 !important;
  overflow: hidden !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  will-change: opacity, visibility;
  opacity: 0 !important;
  visibility: hidden !important;
  pointer-events: none !important;
  -webkit-transition: opacity 0.4s ease, visibility 0.4s ease !important;
  -o-transition: opacity 0.4s ease, visibility 0.4s ease !important;
  transition: opacity 0.4s ease, visibility 0.4s ease !important;
  /* default */
}

#iubenda-cs-banner [class*=" iub"],
#iubenda-cs-banner [class^=iub],
#iubenda-cs-banner .iubenda-banner-content:not(.iubenda-custom-content) * {
  font-size: 100% !important;
  width: auto !important;
  -webkit-appearance: none !important;
  -moz-appearance: none !important;
  appearance: none !important;
  background: none !important;
  -webkit-box-sizing: border-box !important;
  box-sizing: border-box !important;
  -webkit-tap-highlight-color: rgba(0, 0, 0, 0) !important;
  -webkit-backface-visibility: hidden !important;
  backface-visibility: hidden !important;
  font-family: -apple-system, sans-serif !important;
  text-decoration: none !important;
  color: currentColor !important;
  background-attachment: scroll !important;
  background-color: transparent !important;
  background-image: none !important;
  background-position: 0 0 !important;
  background-repeat: repeat !important;
  border: 0 !important;
  border-color: #000 !important;
  border-color: currentColor !important;
  border-radius: 0 !important;
  border-style: none !important;
  border-width: medium !important;
  bottom: auto !important;
  clear: none !important;
  clip: auto !important;
  counter-increment: none !important;
  counter-reset: none !important;
  direction: inherit !important;
  float: none !important;
  font-style: inherit !important;
  font-variant: normal !important;
  font-weight: inherit !important;
  height: auto !important;
  left: auto !important;
  letter-spacing: normal !important;
  line-height: inherit !important;
  list-style-type: inherit !important;
  list-style-position: outside !important;
  list-style-image: none !important;
  margin: 0 !important;
  max-height: none !important;
  max-width: none !important;
  min-height: 0 !important;
  min-width: 0 !important;
  opacity: 1;
  outline: 0 !important;
  overflow: visible !important;
  padding: 0 !important;
  position: static !important;
  quotes: "" "" !important;
  right: auto !important;
  table-layout: auto !important;
  text-align: left !important;
  text-indent: 0 !important;
  text-transform: none !important;
  top: auto !important;
  unicode-bidi: normal !important;
  vertical-align: baseline !important;
  visibility: inherit !important;
  white-space: normal !important;
  width: auto !important;
  word-spacing: normal !important;
  z-index: auto !important;
  background-origin: padding-box !important;
  background-origin: padding-box !important;
  background-clip: border-box !important;
  background-size: auto !important;
  -o-border-image: none !important;
  border-image: none !important;
  border-radius: 0 !important;
  border-radius: 0 !important;
  -webkit-box-shadow: none !important;
  box-shadow: none !important;
  -webkit-column-count: auto !important;
  -moz-column-count: auto !important;
  column-count: auto !important;
  -webkit-column-gap: normal !important;
  -moz-column-gap: normal !important;
  column-gap: normal !important;
  -webkit-column-rule: medium none #000 !important;
  -moz-column-rule: medium none #000 !important;
  column-rule: medium none #000 !important;
  -webkit-column-span: none !important;
  -moz-column-span: none !important;
  column-span: none !important;
  -webkit-column-width: auto !important;
  -moz-column-width: auto !important;
  column-width: auto !important;
  -webkit-font-feature-settings: normal !important;
  font-feature-settings: normal !important;
  overflow-x: visible !important;
  overflow-y: visible !important;
  -webkit-hyphens: manual !important;
  -ms-hyphens: manual !important;
  hyphens: manual !important;
  -webkit-perspective: none !important;
  perspective: none !important;
  -webkit-perspective-origin: 50% 50% !important;
  perspective-origin: 50% 50% !important;
  text-shadow: none !important;
  -webkit-transition: all 0s ease 0s !important;
  -o-transition: all 0s ease 0s !important;
  transition: all 0s ease 0s !important;
  -webkit-transform: none !important;
  -ms-transform: none !important;
  transform: none !important;
  -webkit-transform-origin: 50% 50% !important;
  -ms-transform-origin: 50% 50% !important;
  transform-origin: 50% 50% !important;
  -webkit-transform-style: flat !important;
  transform-style: flat !important;
  word-break: normal !important;
  -ms-text-size-adjust: 100%;
  -webkit-text-size-adjust: 100%;
}

#iubenda-cs-banner .iub-popover-trigger {
  display: inline-block !important;
  text-decoration: underline !important;
  -webkit-text-decoration-style: dashed !important;
  text-decoration-style: dashed !important;
  position: relative !important;
  margin-right: 16px !important;
  cursor: pointer !important;
  line-height: 1.25 !important;
}

#iubenda-cs-banner .iub-popover-trigger:before, #iubenda-cs-banner .iub-popover-trigger:after {
  content: "";
  display: inline-block;
  width: 14px;
  height: 14px;
  border-radius: 12px;
  vertical-align: middle;
  background-size: 4px;
  position: absolute;
  left: calc(100% + 2px);
  top: 3px;
}

#iubenda-cs-banner .iub-popover-trigger:before {
  background-color: currentColor;
  opacity: 0.35;
}

#iubenda-cs-banner .iub-popover-trigger:after {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='7' height='13' viewBox='0 0 7 13'%3E%3Cg fill='%23FFF' fill-rule='evenodd'%3E%3Cpath d='M2.779 1.288a1.287 1.287 0 112.574 0 1.287 1.287 0 01-2.574 0zM5.467 10.422l.903 1.851-.7.341a2.496 2.496 0 01-3.545-2.717l.818-3.252a.42.42 0 00-.178-.382.422.422 0 00-.452-.041l-.844.412-.902-1.852.843-.412a2.491 2.491 0 012.576.233 2.49 2.49 0 01.989 2.389 1.105 1.105 0 01-.02.095l-.817 3.253a.42.42 0 00.178.382c.08.059.244.142.451.041l.7-.341z'/%3E%3C/g%3E%3C/svg%3E");
  background-position: center;
  background-repeat: no-repeat;
}

#iubenda-cs-banner .iub-popover {
  position: absolute !important;
  top: 24px !important;
  bottom: 0 !important;
  left: 0 !important;
  right: 0 !important;
  border-radius: 4px !important;
  background-color: white !important;
  color: #222 !important;
  z-index: 2 !important;
  -webkit-box-shadow: 0 0 32px rgba(0, 0, 0, 0.1) !important;
  box-shadow: 0 0 32px rgba(0, 0, 0, 0.1) !important;
  opacity: 0 !important;
  visibility: hidden !important;
  -webkit-transform: translateY(24px) !important;
  -ms-transform: translateY(24px) !important;
  transform: translateY(24px) !important;
  -webkit-transition: opacity 0.3s ease, visibility 0.3s ease, -webkit-transform 0.3s ease !important;
  transition: opacity 0.3s ease, visibility 0.3s ease, -webkit-transform 0.3s ease !important;
  -o-transition: opacity 0.3s ease, visibility 0.3s ease, transform 0.3s ease !important;
  transition: opacity 0.3s ease, visibility 0.3s ease, transform 0.3s ease !important;
  transition: opacity 0.3s ease, visibility 0.3s ease, transform 0.3s ease, -webkit-transform 0.3s ease !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-orient: vertical !important;
  -webkit-box-direction: normal !important;
  -ms-flex-direction: column !important;
  flex-direction: column !important;
  z-index: 99 !important;
  pointer-events: none !important;
  overflow: hidden !important;
}

#iubenda-cs-banner .iub-popover-header {
  -ms-flex-negative: 0 !important;
  flex-shrink: 0 !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-pack: justify !important;
  -ms-flex-pack: justify !important;
  justify-content: space-between !important;
  z-index: 1 !important;
  -webkit-box-shadow: 0 16px 16px #FFF !important;
  box-shadow: 0 16px 16px #FFF !important;
}

#iubenda-cs-banner .iub-popover-header > * {
  padding: 24px !important;
  padding-bottom: 0 !important;
}

#iubenda-cs-banner .iub-popover-header-title {
  font-size: 18px !important;
  font-weight: bold !important;
}

#iubenda-cs-banner .iub-popover-header-close {
  font-size: 24px !important;
  font-weight: 300 !important;
  cursor: pointer !important;
  line-height: 1 !important;
  position: relative !important;
  top: -2px !important;
}

#iubenda-cs-banner .iub-popover-content {
  font-size: 14px !important;
  -webkit-box-flex: 1 !important;
  -ms-flex: 1 !important;
  flex: 1 !important;
  font-weight: 300 !important;
  line-height: 1.5 !important;
  position: relative !important;
}

#iubenda-cs-banner .iub-popover-content > div {
  padding: 0 24px !important;
  overflow-y: auto !important;
  height: 100% !important;
}

#iubenda-cs-banner .iub-popover-content > div:before, #iubenda-cs-banner .iub-popover-content > div:after {
  content: "";
  display: block;
  height: 24px;
}

#iubenda-cs-banner .iub-popover-content h3 {
  margin-bottom: 16px !important;
  font-weight: bold !important;
}

#iubenda-cs-banner .iub-popover-content p:not(:last-of-type) {
  margin-bottom: 16px !important;
}

#iubenda-cs-banner .iub-popover-content a {
  text-decoration: underline !important;
  cursor: pointer !important;
  opacity: 0.8 !important;
}

#iubenda-cs-banner .iub-popover-content b, #iubenda-cs-banner .iub-popover-content strong {
  font-weight: bold !important;
}

#iubenda-cs-banner .iub-popover-content i, #iubenda-cs-banner .iub-popover-content em {
  font-style: italic !important;
}

#iubenda-cs-banner .iub-popover-content:after {
  position: absolute;
  content: "";
  display: block;
  height: 24px;
  pointer-events: none;
  left: 0;
  right: 0;
  bottom: 0;
  background: -webkit-gradient(linear, left top, left bottom, from(rgba(255, 255, 255, 0)), to(white));
  background: -o-linear-gradient(top, rgba(255, 255, 255, 0) 0%, white 100%);
  background: linear-gradient(180deg, rgba(255, 255, 255, 0) 0%, white 100%);
}

#iubenda-cs-banner.iubenda-cs-default-floating .iub-popover {
  left: 8px !important;
  right: 8px !important;
}

@media (min-width: 640px) {
  #iubenda-cs-banner.iubenda-cs-default .iub-popover {
    max-width: 992px !important;
    margin: 0 auto !important;
  }
  #iubenda-cs-banner.iubenda-cs-default.iubenda-cs-top .iub-popover {
    top: 16px !important;
    bottom: -16px !important;
  }
  #iubenda-cs-banner.iubenda-cs-default.iubenda-cs-bottom .iub-popover {
    top: -16px !important;
    bottom: 16px !important;
  }
}

#iubenda-cs-banner.iub-popover-visible .iub-popover {
  opacity: 1 !important;
  visibility: visible !important;
  -webkit-transform: translateY(0) !important;
  -ms-transform: translateY(0) !important;
  transform: translateY(0) !important;
  pointer-events: auto !important;
}

#iubenda-cs-banner.iubenda-cs-overlay:before {
  content: "" !important;
  position: fixed !important;
  top: 0 !important;
  left: 0 !important;
  width: 100% !important;
  height: 100% !important;
  background-color: rgba(0, 0, 0, 0.5) !important;
  z-index: 1 !important;
  pointer-events: auto !important;
}

#iubenda-cs-banner.iubenda-cs-center {
  -webkit-box-align: center !important;
  -ms-flex-align: center !important;
  align-items: center !important;
  -webkit-box-pack: center !important;
  -ms-flex-pack: center !important;
  justify-content: center !important;
}

#iubenda-cs-banner.iubenda-cs-top {
  -webkit-box-align: start !important;
  -ms-flex-align: start !important;
  align-items: flex-start !important;
}

#iubenda-cs-banner.iubenda-cs-bottom {
  -webkit-box-align: end !important;
  -ms-flex-align: end !important;
  align-items: flex-end !important;
}

#iubenda-cs-banner.iubenda-cs-left {
  -webkit-box-pack: start !important;
  -ms-flex-pack: start !important;
  justify-content: flex-start !important;
}

#iubenda-cs-banner.iubenda-cs-right {
  -webkit-box-pack: end !important;
  -ms-flex-pack: end !important;
  justify-content: flex-end !important;
}

#iubenda-cs-banner.iubenda-cs-visible {
  opacity: 1 !important;
  visibility: visible !important;
}

#iubenda-cs-banner.iubenda-cs-visible .iubenda-cs-container {
  pointer-events: auto !important;
}

#iubenda-cs-banner.iubenda-cs-slidein .iubenda-cs-container {
  -webkit-transition: -webkit-transform 0.4s ease !important;
  transition: -webkit-transform 0.4s ease !important;
  -o-transition: transform 0.4s ease !important;
  transition: transform 0.4s ease !important;
  transition: transform 0.4s ease, -webkit-transform 0.4s ease !important;
}

#iubenda-cs-banner.iubenda-cs-slidein.iubenda-cs-top .iubenda-cs-container {
  -webkit-transform: translateY(-48px) !important;
  -ms-transform: translateY(-48px) !important;
  transform: translateY(-48px) !important;
}

#iubenda-cs-banner.iubenda-cs-slidein.iubenda-cs-bottom .iubenda-cs-container {
  -webkit-transform: translateY(48px) !important;
  -ms-transform: translateY(48px) !important;
  transform: translateY(48px) !important;
}

#iubenda-cs-banner.iubenda-cs-slidein.iubenda-cs-visible .iubenda-cs-container {
  -webkit-transform: translateY(0) !important;
  -ms-transform: translateY(0) !important;
  transform: translateY(0) !important;
}

#iubenda-cs-banner .iubenda-cs-container {
  position: relative !important;
  z-index: 2 !important;
}

#iubenda-cs-banner .iubenda-cs-brand {
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  padding: 16px !important;
  -ms-flex-negative: 0 !important;
  flex-shrink: 0 !important;
}

#iubenda-cs-banner .iubenda-cs-brand > div {
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-pack: start !important;
  -ms-flex-pack: start !important;
  justify-content: flex-start !important;
}

#iubenda-cs-banner .iubenda-cs-brand img {
  max-width: 192px !important;
  max-height: 56px !important;
}

#iubenda-cs-banner .iubenda-cs-content {
  position: relative !important;
  z-index: 1 !important;
  overflow: hidden !important;
  -webkit-transition: -webkit-transform 0.4s ease !important;
  transition: -webkit-transform 0.4s ease !important;
  -o-transition: transform 0.4s ease !important;
  transition: transform 0.4s ease !important;
  transition: transform 0.4s ease, -webkit-transform 0.4s ease !important;
}

#iubenda-cs-banner .iubenda-cs-rationale {
  position: relative !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-orient: vertical !important;
  -webkit-box-direction: normal !important;
  -ms-flex-direction: column !important;
  flex-direction: column !important;
}

#iubenda-cs-banner .iubenda-cs-close-btn {
  position: absolute !important;
  top: -2px !important;
  padding: 16px !important;
  right: 0 !important;
  min-width: 48px !important;
  height: 48px !important;
  font-size: 24px !important;
  line-height: 0 !important;
  font-weight: lighter !important;
  cursor: pointer !important;
  text-align: center !important;
}

#iubenda-cs-banner .iubenda-cs-close-btn:hover {
  opacity: 0.5 !important;
}

#iubenda-cs-banner .iubenda-banner-content {
  font-weight: 300 !important;
  margin: 16px !important;
  margin-bottom: 0 !important;
  -webkit-box-flex: 1 !important;
  -ms-flex: 1 1 auto !important;
  flex: 1 1 auto !important;
  overflow-y: auto !important;
  mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 16px) !important;
  -webkit-mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 16px) !important;
  padding-bottom: 32px !important;
}

#iubenda-cs-banner .iubenda-banner-content-padded {
  padding-right: 32px !important;
}

#iubenda-cs-banner .iubenda-banner-content a {
  cursor: pointer !important;
  color: currentColor !important;
  opacity: 0.7 !important;
  text-decoration: underline !important;
}

#iubenda-cs-banner .iubenda-banner-content a:hover {
  opacity: 1 !important;
}

#iubenda-cs-banner #iubenda-cs-title {
  font-weight: bold !important;
  margin-bottom: 16px !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group {
  margin: 16px !important;
  z-index: 1 !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  margin-top: 0 !important;
  -ms-flex-negative: 0 !important;
  flex-shrink: 0 !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group > div {
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
}

@media (min-width: 640px) {
  #iubenda-cs-banner .iubenda-cs-opt-group {
    -webkit-box-align: center !important;
    -ms-flex-align: center !important;
    align-items: center !important;
    -webkit-box-pack: justify !important;
    -ms-flex-pack: justify !important;
    justify-content: space-between !important;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-custom {
    margin-right: auto !important;
    -ms-flex-item-align: start !important;
    align-self: start !important;
    -webkit-box-pack: start !important;
    -ms-flex-pack: start !important;
    justify-content: flex-start !important;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-consent {
    margin-left: auto !important;
    -ms-flex-item-align: end !important;
    align-self: end !important;
    -webkit-box-pack: end !important;
    -ms-flex-pack: end !important;
    justify-content: flex-end !important;
  }
}

@media (max-width: 639px) {
  #iubenda-cs-banner .iubenda-cs-opt-group {
    margin: 12px !important;
    -webkit-box-orient: vertical !important;
    -webkit-box-direction: normal !important;
    -ms-flex-direction: column !important;
    flex-direction: column !important;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-custom {
    -webkit-box-ordinal-group: 3;
    -ms-flex-order: 2;
    order: 2;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-consent {
    -webkit-box-ordinal-group: 2;
    -ms-flex-order: 1;
    order: 1;
  }
}

#iubenda-cs-banner .iubenda-cs-opt-group button {
  -webkit-appearance: none !important;
  -moz-appearance: none !important;
  appearance: none !important;
  padding: 8px 32px !important;
  border-radius: 64px !important;
  cursor: pointer !important;
  font-weight: bold !important;
  font-size: 100% !important;
  margin-top: 4px !important;
  margin-bottom: 4px !important;
  text-align: center !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button:focus {
  opacity: 0.8 !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button:hover {
  opacity: 0.5 !important;
}

@media (min-width: 640px) {
  #iubenda-cs-banner .iubenda-cs-opt-group button:not(:last-of-type) {
    margin-right: 8px !important;
  }
}

@media (max-width: 639px) {
  #iubenda-cs-banner .iubenda-cs-opt-group button {
    padding: 8px 24px !important;
    width: 100% !important;
    display: block;
    text-align: center !important;
    margin: 6px 3px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand {
  margin: 0 -8px 0 !important;
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand {
    margin: -8px -8px 0 !important;
  }
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand div {
    margin: 0 auto !important;
    width: calc(992px - 32px) !important;
  }
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand div {
    margin: 0 8px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default .iubenda-cs-container {
  width: 100% !important;
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-rationale {
    width: 992px !important;
    margin: 16px auto !important;
  }
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-content {
    padding: 8px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-brand {
  margin: -8px -8px 0 !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-brand div {
  margin: 8px !important;
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-container {
    width: 992px !important;
  }
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center.iubenda-cs-top .iubenda-cs-container, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center.iubenda-cs-bottom .iubenda-cs-container {
    width: 100% !important;
  }
}

@media (min-width: 640px) {
  #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-container, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-container, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-container {
    width: 480px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group {
  -webkit-box-orient: vertical !important;
  -webkit-box-direction: normal !important;
  -ms-flex-direction: column !important;
  flex-direction: column !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group > div, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group > div, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group > div {
  width: 100% !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group button, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group button, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group button {
  display: block !important;
  width: 100% !important;
  text-align: center !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group-custom, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group-custom, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group-custom {
  -webkit-box-ordinal-group: 3;
  -ms-flex-order: 2;
  order: 2;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group-consent, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group-consent, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group-consent {
  -webkit-box-ordinal-group: 2;
  -ms-flex-order: 1;
  order: 1;
}

#iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-content {
  -webkit-box-shadow: 0 8px 48px rgba(0, 0, 0, 0.15) !important;
  box-shadow: 0 8px 48px rgba(0, 0, 0, 0.15) !important;
  padding: 8px !important;
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-content {
    border-radius: 4px !important;
    margin: 16px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-container,
#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-content,
#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-rationale {
  height: 100% !important;
}

#iubenda-cs-banner.iubenda-cs-fix-height.iubenda-cs-default-floating .iubenda-cs-content {
  height: calc(100% - 32px) !important;
}

#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-brand img {
  max-width: 75% !important;
}

#iubenda-cs-banner .iubenda-cs-content {
  background-color: #000000 !important;
  color: #FFFFFF !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group {
  color: #000000 !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button {
  background-color: rgba(255, 255, 255, 0.1) !important;
  color: #FFFFFF !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button.iubenda-cs-btn-primary {
  background-color: #0073CE !important;
  color: #FFFFFF !important;
}


/*
-----------------
MOBILE SDK
-----------------
*/

.iubenda-mobile-sdk #iubenda-cs-banner.iubenda-cs-visible {
  justify-content: center!important;
  align-items: center!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-container {
  max-height: 100%!important;
  display: flex!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-container .iubenda-cs-content {
  height: auto!important;
  border-radius: 0!important;
  margin: 0!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-opt-group {
  text-align: center!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-close-btn {
  display: none!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-rationale {
  display: flex!important;
  flex-direction: column!important;
  height: 100%!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-banner-content {
  flex: 1;
  overflow-y: auto!important;
  margin: 0!important;
  padding: 16px 16px 48px!important;
  max-height: inherit!important;
  mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 15%) !important;
  -webkit-mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 15%) !important;
}

@media (min-width: 992px) {
  .iubenda-mobile-sdk #iubenda-cs-banner .iubenda-banner-content,
  .iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-opt-group {
    margin: 24px!important;
  }
  .iubenda-mobile-sdk #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-rationale {
    width: 100% !important;
    margin: 0 !important;
  }
}

.no-banner #iubenda-cs-banner {
  display: none!important;
}

/** fix scrolling in iOS 10 **/
.iubenda-mobile-sdk #iubenda-cs-banner.iubenda-cs-visible .iubenda-cs-container,
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-container .iubenda-cs-content,
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-rationale {
  height: 100%!important;
}
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-top-container {
  position: relative!important;
}
.iubenda-mobile-sdk #iubenda-iframe #iab-container {
  position: absolute!important;
  top: 0!important;
  bottom: 0!important;
  left: 0!important;
  right: 0!important;
}

/** iframe **/
.iubenda-mobile-sdk #iubenda-iframe #iubenda-iframe-popup {
  height: 100%!important;
  width: 100%!important;
}
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-close-btn {
  display: none!important;
}
.iubenda-mobile-sdk #iubenda-iframe {
  background-color: transparent!important;
}

/* Fix cookie policy trimming on older Android devices */
.iubenda-mobile-sdk #iubenda-iframe iframe {
  background-color: transparent!important;
  position:absolute!important;
  bottom:0!important;
  top:0!important;
}
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-spinner {
  top: 50px !important;
}
/* Fix TCF widget overlapping footer in older Android devices */
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-footer {
  z-index: 9999!important;
}

config.json:

{
    "banner": {
        "acceptButtonDisplay": "true",
        "customizeButtonDisplay": "true",
        "backgroundColor": "#000000",
        "textColor": "#FFFFFF",
        "acceptButtonColor": "#FD1D1D",
        "acceptButtonCaptionColor": "white",
        "customizeButtonColor": "transparent",
        "customizeButtonCaptionColor": "#FFF"
    }
}

TCF option

Unlike the CS standard version, the TCF option is enabled by default in the SDK. If you don't run third-party personalized ads and you want to disable the TCF support, set enableTcf: false inside the config.json file.

Example:

{
    …
    enableTcf: false,
    "banner": {
        …
    }
}

Google Additional Consent Mode

Google Additional Consent Mode is disabled by default. If you want to add Google Additional Consent Mode, set googleAdditionalConsentMode": true inside the config.json file.

Example:

{
    …
    "googleAdditionalConsentMode": true,
    "banner": {
        …
    }
}

Parameters "invalidateConsentBefore" and "expireAfter"

invalidateConsentBefore Accepts a Date, and if valued, it should check if there is a preference already expressed, and if there is and the timestamp is lesser than the day of the configured date then it should not consider the preference anymore. Accepted formats: dd/MM/yyyy - yyyy/MM/dd - dd-MM-yyyy - yyyy-MM-dd - dd.MM.yyyy - yyyy.MM.dd

expireAfter If valued, number of days of the consent timestamp and the integer value of expireAfter parameter will be compared, if consent date is passed, the data on device will be cleared (Default: 360 days)

Example:

{
    …
    "invalidateConsentBefore": "08/11/2022",
    "expireAfter": 100,
        …
    }
}

Show the consent UI

To present the consent UI at app launch, call IubendaCMP.askConsent(from: self) from your main ViewController's viewDidLoad method:

• if there’s no internet connection, the call won't have any effect (provided that skipNoticeWhenOffline is not set to false); 
• if consent has already been given, the call won't have any effect; 
• if consent has not already been given and a connection is available, IubendaCMP.askConsent(from: self) will make the consent request appear.

Please note that if you’ve set forceConsent to false, IubendaCMP.askConsent(from: self) won’t have any effect if the user dismisses the consent request after the first launch: to show the consent UI again you’ll have to call IubendaCMP.openPreferences(from: self). 

So, if your goal is to maximize consents:

• set forceConsent to true, and 
• call IubendaCMP.askConsent(from: self)

Otherwise, if you prefer to give the user the chance to dismiss the consent request without being prompted again whenever IubendaCMP.askConsent(from: self) is called again:

• set forceConsent to false
• call IubendaCMP.askConsent(from: self), but note that it won’t have any effect after the first launch
• to ask for consent again, call IubendaCMP.openPreferences(from: self)

Notes about IubendaCMP.openPreferences():

• if consent has not already been given, IubendaCMP.openPreferences() will open the consent request.
• If consent has already been given, IubendaCMP.openPreferences() will allow users to change their consent preferences:
  • If "perPurposeConsent": true, it will show the per-category preferences.
  • If "perPurposeConsent": false, it will show the TCF consent preferences.
  • Otherwise, if "perPurposeConsent": false and "enableTcf": false, it will show the cookie policy.

To have complete control of when to show the consent request, you could rely entirely on IubendaCMP.openPreferences(from: self), but you’ll have to implement a way to check if consent has been given. 

Custom consent UI

You can use a custom UI to ask for user consent, without showing the provided popup; in this case, you can take advantage of the following methods of IubendaCMP:

Notes about IubendaCMP.accept():

• if the user has not expressed any preferences, then it accepts everything.
• This method should be used when developing a custom UI that doesn't use the default notice used by the SDK.

When using an open* method, you can use the notification observer (see below) to detect when the user has given consent.

Example:

import UIKit
import iubenda

class ConsentViewController: UIViewController {
        
    override func viewDidLoad() {
        super.viewDidLoad()

        NotificationCenter.default.addObserver(
                        self,
                        selector: #selector(consentDidChange),
                        name: NSNotification.Name.ConsentChanged,
                        object: nil
                )
    }

    @IBAction func acceptClick(_ sender: Any) {
        IubendaCMP.accept()
        dismiss(animated: true)
    }
    
    @IBAction func optionsClick(_ sender: Any) {
        IubendaCMP.openTcfPreferences(from: self)
    }
    
    @objc func consentDidChange() {
        if IubendaCMP.isConsentGiven() {
            dismiss(animated: true)
        }
    }

}

Listening for changes

If necessary, you can listen to changes of user consent through the NotificationCenter by adding an observer for NSNotification.Name.ConsentChanged:

private func observeConsentNotification() {
    NotificationCenter.default.addObserver(
            self,
            selector: #selector(consentDidChange),
            name: NSNotification.Name.ConsentChanged,
            object: nil
    )
}

@objc func consentDidChange() {
    // ...
}

For detailed changes and events, use NSNotification.Name.OnStartupFailed, NSNotification.Name.OnError, NSNotification.Name.OnFatalError, NSNotification.Name.OnReady, NSNotification.Name.OnBannerShown, NSNotification.Name.On2ndLayerShown, NSNotification.Name.OnPreferenceExpressed.

Accessing to IAB Transparency and Consent Framework settings

You can access IAB TCF settings such as the encoded consent string, either directly as IAB specs, or through the convenience methods offered by IubendaCMP.storage.

Available settings

For more information about the TCF and its advanced settings, such as the ability to restrict purposes and determine the viable legal basis (consent and/or legitimate interest), read our TCF guide.

Initializing libraries that do not adhere to the IAB TCF

Third-party libraries that do not directly adhere to the IAB Transparency and Consent Framework, may need to be initialized separately depending on the consent status and preferences.

To achieve that, you can implement a change listener in your AppDelegate and call IubendaCMP.isConsentGiven(), and other methods, to evaluate the consent status.

Example:

import UIKit

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

        let config = IubendaCMPConfiguration()
        config.gdprEnabled = true
        config.googleAds = true
        config.siteId = "12345"
        config.cookiePolicyId = "252372"
        IubendaCMP.initialize(with: config)

        observeConsentNotification()
        initializeLibraries()

       return true	

       }
       private func observeConsentNotification() {	
       NotificationCenter.default.addObserver(	
       self,	
       selector: #selector(consentDidChange),	
       name: NSNotification.Name.ConsentChanged,	
       object: nil	
       )	
      }

    @objc func consentDidChange() {
        initializeLibraries()
    }

    private func initializeLibraries() {
        if (IubendaCMP.isPurposeEnabled(id: 2)) {
            // Activate libraries that use "Functionality" purpose
        }
        if (IubendaCMP.isPurposeEnabled(id: 3)) {
            // Activate libraries that use "Measurement" purpose
        }
    }
}

App Tracking Transparency (iOS 14.5+)

Starting with iOS 14.5 (April 2021), Apple requires that your app provides transparency on the data that it uses and on the third parties that will track the user in your app.

To request permission to track the user and access the device's advertising identifier, you need to use the AppTrackingTransparency (ATT) framework. You can add other permission requests in order to comply with regulations, such as ePrivacy or GDPR. However, your app must always respect the user's response to the AppTrackingTransparency prompt, even if their response to other prompts conflicts. 

Guideline 5.1.1 (iv) states: “Apps must respect the user’s permission settings and not attempt to manipulate, trick, or force people to consent to unnecessary data access.”

This includes altering a user's AppTrackingTransparency response by only respecting their response to other permission requests. You can use third-party Consent Management Platforms to add these permission requests, as long as no tracking takes place from such use.

How to meet Apple's ATT requirements and comply with law regulations

To be fully compliant with Apple’s App Tracking Transparency rules (and avoid App Store rejection) and ePrivacy/GDPR requirements, you must ask for the user permission through ATT and ask for user consent through our CMP.

To combine our CMP and Apple’s ATT, you may ask for user permission via ATT manually or you must set automaticHandlingOfAtt to true, then collect consent from the CMP if, (and if only) the user has given permission via ATT.

If you want iubenda SDK handle ATT (system-permission alert), set up NSUserTrackingUsageDescription. For more information on how to do this, refer to Apple's Documentation. Then set IubendaCMPConfiguration object's automaticHandlingOfAtt parameter to true in AppDelegate class.

Keep in mind that your app must always respect the user’s response to the AppTrackingTransparency prompt, even if their response through our CMP conflicts.

For example, If the user doesn’t provide permission via the ATT, they are assumed to also not give consent via the CMP.
In this case, you may avoid calling the askConsent method to not display the CMP and consider consent rejected for all the declared purposes. If you use automaticHandlingOfAtt = true, then askConsent method will first open Apple's ATT system-permission alert and depending on user's choice the SDK will ask Consent via pop-up

Also, if the user changes expressed preferences by denying permissions previously given via application settings, you may invoke the clearData() method, that clears the CMP consent signals collected in the previous user interaction. If you use automaticHandlingOfAtt = true, then iubenda SDK will invoke the clearData() method.
The CMP will not be resurfaced until the user changes again their preferences and provides permission via the application settings.

Offline and errors

The library requires an internet connection to display the consent popup, hence to generate or update the consent string, while the latest consent string is always available on local storage through IubendaCMP.storage.

By default, the askConsent method checks for internet connection before launching the popup activity, so, if there is no connection, the popup is not shown, but will be presented on the next launch.

If an error occurs during the consent flow, instead, an error message is shown with the option to retry or close the popup. In this case, setting forceConsent=true ensures that the popup will be presented again if no consent has been given.

Compliance with US State Privacy Laws

Our SDK supports features to manage compliance with state-specific laws. You can handle opt-out requests for the sale, sharing, and targeted advertising of personal information, in accordance with applicable state laws.

Methods for US Privacy Compliance

We introduce three methods that return an UsprOptOut object, providing the user's opt-out preference regarding their personal data. The UsprOptOut can be NOTAPPLICABLE, indicating no action needed; YES, signaling an opt-out; or NO, indicating no opt-out.

1. getSaleOptOut(): Evaluates the opt-out status for the sale of personal information.
2. getSharingOptOut(): Determines the opt-out status for sharing personal data with third parties.
3. getTargetedAdvertisingOptOut(): Assesses the opt-out preference for targeted advertising.

The returned UsprOptOut value from each method provides a clear directive on how to proceed with the user's data based on their preferences and applicable laws.

1. NOTAPPLICABLE: The user's preference is not applicable under the current circumstances or legal requirements.
2. YES: Indicates an active opt-out by the user from the specific data processing activity.
3. NO: Indicates that the user has not opted out, allowing the data processing activity to continue.

Consent preferences across different devices

Read this guide to learn how to implement the Consent Database API to synchronize consent preferences between sites and apps for each authenticated user.

Android

Add the iubenda SDK to your project

Add the following repository and dependency to your build.gradle file:

repositories {
    maven { url "https://libraries.iubenda.com/android" }
}

dependencies {
    implementation "com.iubenda:mobile-sdk:2.6.4"  
}

To automatically update the library version on build, you can set the dependency as:

• "com.iubenda:mobile-sdk:2.6.+" for trivial updates
• "com.iubenda:mobile-sdk:2.+" for minor updates
• "com.iubenda:mobile-sdk:+" for all updates

Application class

Create a new class that extends android.app.Application and set it in the app's manifest, if you don't already have such class in your project

<application
            android:name=".App"
            ...>
        ...
</application>

Initialize the SDK

In your Application class, inside the onCreate method, create a configuration object with your settings and call IubendaCMP.initialize()

@Override
    public void onCreate() {
        super.onCreate();

        IubendaCMPConfig config = IubendaCMPConfig.builder()
                .gdprEnabled(true)
                .siteId("12341234")
                .cookiePolicyId("56785678")
                .googleAds(true)
                .cssResource(R.raw.custom_style)
                .jsonResource(R.raw.config_json)
                .applyStyles(true)
                .build();
        IubendaCMP.initialize(this, config);
    }

Settings

Configuration example with custom CSS

IubendaCMPConfig config = IubendaCMPConfig.builder()
.gdprEnabled(true)
.siteId("12341234")
.cookiePolicyId("56785678")
.forceConsent(true)
.googleAds(true)
.applyStyles(false)
.cssResource(R.raw.custom_style)
.jsonResource(R.raw.config)
.acceptIfDismissed(true)
.build();

custom_style.css:

/***************************************************************************
// * iubenda Privacy Controls and Cookie Solution                                               *
// *                                                                       *
// * Sample CSS v2.2.6                                                     *
// *                                                                       *
// * (c) 2019 iubenda srl <info@iubenda.com>                               *
// * All Rights Reserved.                                                  *
// *                                                                       *
// *************************************************************************
//
// CHANGELOG
//
// 2.2.7 - 2020-06-18
// - Fix container breaking on mobile.
//
// 2.2.6 - 2020-05-27
// - Hide scroll bar visibility.
// - Fix brand image height on mobile.
//
// 2.2.5 - 2020-05-06
// - Fix IE flex content.
// - Fix text overflow.
//
// 2.2.3 - 2020-04-21
// - Cursor pointer
// - Button text ellipsis
// - Equalize shadows top/bottom modal bar
//
// 2.2.2 - 2020-04-06
// - Add pointer events auto to the overlay
//
// 2.2.1 - 2020-03-06
// - Introduce popover.
//
// 2.2.0 - 2019-11-07
// - Introduce brand customizations
//
// 2.1.5 - 2019-11-22
// - Add class to go fullscreen.
//
// 2.1.4 - 2020-03-25
// - Make the banner shadow darker
//
// 2.1.3 - 2020-01-22
// - Fix banner not appearing on iPhone.
//
// 2.1.2 - 2019-11-07
// - Fix buttons height on IE.
//
// 2.1.1 - 2019-10-30
// - Fix buttons margin and customize-advertising-tracking button width on mobile.
//
// 2.1.0 - 2019-10-24
// - Introduce text overflowing mask and style for reject button.
//
// 2.0.4 - 2019-06-24
// - Convert close button width to min-width
//
// 2.0.3 - 2019-05-24
// - Introduce new positioning options
//
// 2.0.2 - 2019-05-02
// - Fix text spaces when custom content
//
// 2.0.1 - 2019-04-09
// - Add rules for buttons group
//
// 2.0.0 - 2019-02-01
// - Full rewrite to accommodate the new markup
//
// 0.0.1 - 2015-04-01
// - First implementation of the sample CSS
*/

/*
-----------------
IMPORTANT: Changing the following values may prevent the notice from being displayed properly.
-----------------
*/
#iubenda-cs-banner {
  font-size: 15px !important;
  background: none !important;
  line-height: 1.4 !important;
  position: fixed !important;
  z-index: 99999998 !important;
  top: 0 !important;
  left: 0 !important;
  width: 100% !important;
  height: 100% !important;
  border: 0 !important;
  margin: 0 !important;
  padding: 0 !important;
  overflow: hidden !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  will-change: opacity, visibility;
  opacity: 0 !important;
  visibility: hidden !important;
  pointer-events: none !important;
  -webkit-transition: opacity 0.4s ease, visibility 0.4s ease !important;
  -o-transition: opacity 0.4s ease, visibility 0.4s ease !important;
  transition: opacity 0.4s ease, visibility 0.4s ease !important;
  /* default */
}

#iubenda-cs-banner [class*=" iub"],
#iubenda-cs-banner [class^=iub],
#iubenda-cs-banner .iubenda-banner-content:not(.iubenda-custom-content) * {
  font-size: 100% !important;
  width: auto !important;
  -webkit-appearance: none !important;
  -moz-appearance: none !important;
  appearance: none !important;
  background: none !important;
  -webkit-box-sizing: border-box !important;
  box-sizing: border-box !important;
  -webkit-tap-highlight-color: rgba(0, 0, 0, 0) !important;
  -webkit-backface-visibility: hidden !important;
  backface-visibility: hidden !important;
  font-family: -apple-system, sans-serif !important;
  text-decoration: none !important;
  color: currentColor !important;
  background-attachment: scroll !important;
  background-color: transparent !important;
  background-image: none !important;
  background-position: 0 0 !important;
  background-repeat: repeat !important;
  border: 0 !important;
  border-color: #000 !important;
  border-color: currentColor !important;
  border-radius: 0 !important;
  border-style: none !important;
  border-width: medium !important;
  bottom: auto !important;
  clear: none !important;
  clip: auto !important;
  counter-increment: none !important;
  counter-reset: none !important;
  direction: inherit !important;
  float: none !important;
  font-style: inherit !important;
  font-variant: normal !important;
  font-weight: inherit !important;
  height: auto !important;
  left: auto !important;
  letter-spacing: normal !important;
  line-height: inherit !important;
  list-style-type: inherit !important;
  list-style-position: outside !important;
  list-style-image: none !important;
  margin: 0 !important;
  max-height: none !important;
  max-width: none !important;
  min-height: 0 !important;
  min-width: 0 !important;
  opacity: 1;
  outline: 0 !important;
  overflow: visible !important;
  padding: 0 !important;
  position: static !important;
  quotes: "" "" !important;
  right: auto !important;
  table-layout: auto !important;
  text-align: left !important;
  text-indent: 0 !important;
  text-transform: none !important;
  top: auto !important;
  unicode-bidi: normal !important;
  vertical-align: baseline !important;
  visibility: inherit !important;
  white-space: normal !important;
  width: auto !important;
  word-spacing: normal !important;
  z-index: auto !important;
  background-origin: padding-box !important;
  background-origin: padding-box !important;
  background-clip: border-box !important;
  background-size: auto !important;
  -o-border-image: none !important;
  border-image: none !important;
  border-radius: 0 !important;
  border-radius: 0 !important;
  -webkit-box-shadow: none !important;
  box-shadow: none !important;
  -webkit-column-count: auto !important;
  -moz-column-count: auto !important;
  column-count: auto !important;
  -webkit-column-gap: normal !important;
  -moz-column-gap: normal !important;
  column-gap: normal !important;
  -webkit-column-rule: medium none #000 !important;
  -moz-column-rule: medium none #000 !important;
  column-rule: medium none #000 !important;
  -webkit-column-span: none !important;
  -moz-column-span: none !important;
  column-span: none !important;
  -webkit-column-width: auto !important;
  -moz-column-width: auto !important;
  column-width: auto !important;
  -webkit-font-feature-settings: normal !important;
  font-feature-settings: normal !important;
  overflow-x: visible !important;
  overflow-y: visible !important;
  -webkit-hyphens: manual !important;
  -ms-hyphens: manual !important;
  hyphens: manual !important;
  -webkit-perspective: none !important;
  perspective: none !important;
  -webkit-perspective-origin: 50% 50% !important;
  perspective-origin: 50% 50% !important;
  text-shadow: none !important;
  -webkit-transition: all 0s ease 0s !important;
  -o-transition: all 0s ease 0s !important;
  transition: all 0s ease 0s !important;
  -webkit-transform: none !important;
  -ms-transform: none !important;
  transform: none !important;
  -webkit-transform-origin: 50% 50% !important;
  -ms-transform-origin: 50% 50% !important;
  transform-origin: 50% 50% !important;
  -webkit-transform-style: flat !important;
  transform-style: flat !important;
  word-break: normal !important;
  -ms-text-size-adjust: 100%;
  -webkit-text-size-adjust: 100%;
}

#iubenda-cs-banner .iub-popover-trigger {
  display: inline-block !important;
  text-decoration: underline !important;
  -webkit-text-decoration-style: dashed !important;
  text-decoration-style: dashed !important;
  position: relative !important;
  margin-right: 16px !important;
  cursor: pointer !important;
  line-height: 1.25 !important;
}

#iubenda-cs-banner .iub-popover-trigger:before, #iubenda-cs-banner .iub-popover-trigger:after {
  content: "";
  display: inline-block;
  width: 14px;
  height: 14px;
  border-radius: 12px;
  vertical-align: middle;
  background-size: 4px;
  position: absolute;
  left: calc(100% + 2px);
  top: 3px;
}

#iubenda-cs-banner .iub-popover-trigger:before {
  background-color: currentColor;
  opacity: 0.35;
}

#iubenda-cs-banner .iub-popover-trigger:after {
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='7' height='13' viewBox='0 0 7 13'%3E%3Cg fill='%23FFF' fill-rule='evenodd'%3E%3Cpath d='M2.779 1.288a1.287 1.287 0 112.574 0 1.287 1.287 0 01-2.574 0zM5.467 10.422l.903 1.851-.7.341a2.496 2.496 0 01-3.545-2.717l.818-3.252a.42.42 0 00-.178-.382.422.422 0 00-.452-.041l-.844.412-.902-1.852.843-.412a2.491 2.491 0 012.576.233 2.49 2.49 0 01.989 2.389 1.105 1.105 0 01-.02.095l-.817 3.253a.42.42 0 00.178.382c.08.059.244.142.451.041l.7-.341z'/%3E%3C/g%3E%3C/svg%3E");
  background-position: center;
  background-repeat: no-repeat;
}

#iubenda-cs-banner .iub-popover {
  position: absolute !important;
  top: 24px !important;
  bottom: 0 !important;
  left: 0 !important;
  right: 0 !important;
  border-radius: 4px !important;
  background-color: white !important;
  color: #222 !important;
  z-index: 2 !important;
  -webkit-box-shadow: 0 0 32px rgba(0, 0, 0, 0.1) !important;
  box-shadow: 0 0 32px rgba(0, 0, 0, 0.1) !important;
  opacity: 0 !important;
  visibility: hidden !important;
  -webkit-transform: translateY(24px) !important;
  -ms-transform: translateY(24px) !important;
  transform: translateY(24px) !important;
  -webkit-transition: opacity 0.3s ease, visibility 0.3s ease, -webkit-transform 0.3s ease !important;
  transition: opacity 0.3s ease, visibility 0.3s ease, -webkit-transform 0.3s ease !important;
  -o-transition: opacity 0.3s ease, visibility 0.3s ease, transform 0.3s ease !important;
  transition: opacity 0.3s ease, visibility 0.3s ease, transform 0.3s ease !important;
  transition: opacity 0.3s ease, visibility 0.3s ease, transform 0.3s ease, -webkit-transform 0.3s ease !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-orient: vertical !important;
  -webkit-box-direction: normal !important;
  -ms-flex-direction: column !important;
  flex-direction: column !important;
  z-index: 99 !important;
  pointer-events: none !important;
  overflow: hidden !important;
}

#iubenda-cs-banner .iub-popover-header {
  -ms-flex-negative: 0 !important;
  flex-shrink: 0 !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-pack: justify !important;
  -ms-flex-pack: justify !important;
  justify-content: space-between !important;
  z-index: 1 !important;
  -webkit-box-shadow: 0 16px 16px #FFF !important;
  box-shadow: 0 16px 16px #FFF !important;
}

#iubenda-cs-banner .iub-popover-header > * {
  padding: 24px !important;
  padding-bottom: 0 !important;
}

#iubenda-cs-banner .iub-popover-header-title {
  font-size: 18px !important;
  font-weight: bold !important;
}

#iubenda-cs-banner .iub-popover-header-close {
  font-size: 24px !important;
  font-weight: 300 !important;
  cursor: pointer !important;
  line-height: 1 !important;
  position: relative !important;
  top: -2px !important;
}

#iubenda-cs-banner .iub-popover-content {
  font-size: 14px !important;
  -webkit-box-flex: 1 !important;
  -ms-flex: 1 !important;
  flex: 1 !important;
  font-weight: 300 !important;
  line-height: 1.5 !important;
  position: relative !important;
}

#iubenda-cs-banner .iub-popover-content > div {
  padding: 0 24px !important;
  overflow-y: auto !important;
  height: 100% !important;
}

#iubenda-cs-banner .iub-popover-content > div:before, #iubenda-cs-banner .iub-popover-content > div:after {
  content: "";
  display: block;
  height: 24px;
}

#iubenda-cs-banner .iub-popover-content h3 {
  margin-bottom: 16px !important;
  font-weight: bold !important;
}

#iubenda-cs-banner .iub-popover-content p:not(:last-of-type) {
  margin-bottom: 16px !important;
}

#iubenda-cs-banner .iub-popover-content a {
  text-decoration: underline !important;
  cursor: pointer !important;
  opacity: 0.8 !important;
}

#iubenda-cs-banner .iub-popover-content b, #iubenda-cs-banner .iub-popover-content strong {
  font-weight: bold !important;
}

#iubenda-cs-banner .iub-popover-content i, #iubenda-cs-banner .iub-popover-content em {
  font-style: italic !important;
}

#iubenda-cs-banner .iub-popover-content:after {
  position: absolute;
  content: "";
  display: block;
  height: 24px;
  pointer-events: none;
  left: 0;
  right: 0;
  bottom: 0;
  background: -webkit-gradient(linear, left top, left bottom, from(rgba(255, 255, 255, 0)), to(white));
  background: -o-linear-gradient(top, rgba(255, 255, 255, 0) 0%, white 100%);
  background: linear-gradient(180deg, rgba(255, 255, 255, 0) 0%, white 100%);
}

#iubenda-cs-banner.iubenda-cs-default-floating .iub-popover {
  left: 8px !important;
  right: 8px !important;
}

@media (min-width: 640px) {
  #iubenda-cs-banner.iubenda-cs-default .iub-popover {
    max-width: 992px !important;
    margin: 0 auto !important;
  }
  #iubenda-cs-banner.iubenda-cs-default.iubenda-cs-top .iub-popover {
    top: 16px !important;
    bottom: -16px !important;
  }
  #iubenda-cs-banner.iubenda-cs-default.iubenda-cs-bottom .iub-popover {
    top: -16px !important;
    bottom: 16px !important;
  }
}

#iubenda-cs-banner.iub-popover-visible .iub-popover {
  opacity: 1 !important;
  visibility: visible !important;
  -webkit-transform: translateY(0) !important;
  -ms-transform: translateY(0) !important;
  transform: translateY(0) !important;
  pointer-events: auto !important;
}

#iubenda-cs-banner.iubenda-cs-overlay:before {
  content: "" !important;
  position: fixed !important;
  top: 0 !important;
  left: 0 !important;
  width: 100% !important;
  height: 100% !important;
  background-color: rgba(0, 0, 0, 0.5) !important;
  z-index: 1 !important;
  pointer-events: auto !important;
}

#iubenda-cs-banner.iubenda-cs-center {
  -webkit-box-align: center !important;
  -ms-flex-align: center !important;
  align-items: center !important;
  -webkit-box-pack: center !important;
  -ms-flex-pack: center !important;
  justify-content: center !important;
}

#iubenda-cs-banner.iubenda-cs-top {
  -webkit-box-align: start !important;
  -ms-flex-align: start !important;
  align-items: flex-start !important;
}

#iubenda-cs-banner.iubenda-cs-bottom {
  -webkit-box-align: end !important;
  -ms-flex-align: end !important;
  align-items: flex-end !important;
}

#iubenda-cs-banner.iubenda-cs-left {
  -webkit-box-pack: start !important;
  -ms-flex-pack: start !important;
  justify-content: flex-start !important;
}

#iubenda-cs-banner.iubenda-cs-right {
  -webkit-box-pack: end !important;
  -ms-flex-pack: end !important;
  justify-content: flex-end !important;
}

#iubenda-cs-banner.iubenda-cs-visible {
  opacity: 1 !important;
  visibility: visible !important;
}

#iubenda-cs-banner.iubenda-cs-visible .iubenda-cs-container {
  pointer-events: auto !important;
}

#iubenda-cs-banner.iubenda-cs-slidein .iubenda-cs-container {
  -webkit-transition: -webkit-transform 0.4s ease !important;
  transition: -webkit-transform 0.4s ease !important;
  -o-transition: transform 0.4s ease !important;
  transition: transform 0.4s ease !important;
  transition: transform 0.4s ease, -webkit-transform 0.4s ease !important;
}

#iubenda-cs-banner.iubenda-cs-slidein.iubenda-cs-top .iubenda-cs-container {
  -webkit-transform: translateY(-48px) !important;
  -ms-transform: translateY(-48px) !important;
  transform: translateY(-48px) !important;
}

#iubenda-cs-banner.iubenda-cs-slidein.iubenda-cs-bottom .iubenda-cs-container {
  -webkit-transform: translateY(48px) !important;
  -ms-transform: translateY(48px) !important;
  transform: translateY(48px) !important;
}

#iubenda-cs-banner.iubenda-cs-slidein.iubenda-cs-visible .iubenda-cs-container {
  -webkit-transform: translateY(0) !important;
  -ms-transform: translateY(0) !important;
  transform: translateY(0) !important;
}

#iubenda-cs-banner .iubenda-cs-container {
  position: relative !important;
  z-index: 2 !important;
}

#iubenda-cs-banner .iubenda-cs-brand {
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  padding: 16px !important;
  -ms-flex-negative: 0 !important;
  flex-shrink: 0 !important;
}

#iubenda-cs-banner .iubenda-cs-brand > div {
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-pack: start !important;
  -ms-flex-pack: start !important;
  justify-content: flex-start !important;
}

#iubenda-cs-banner .iubenda-cs-brand img {
  max-width: 192px !important;
  max-height: 56px !important;
}

#iubenda-cs-banner .iubenda-cs-content {
  position: relative !important;
  z-index: 1 !important;
  overflow: hidden !important;
  -webkit-transition: -webkit-transform 0.4s ease !important;
  transition: -webkit-transform 0.4s ease !important;
  -o-transition: transform 0.4s ease !important;
  transition: transform 0.4s ease !important;
  transition: transform 0.4s ease, -webkit-transform 0.4s ease !important;
}

#iubenda-cs-banner .iubenda-cs-rationale {
  position: relative !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  -webkit-box-orient: vertical !important;
  -webkit-box-direction: normal !important;
  -ms-flex-direction: column !important;
  flex-direction: column !important;
}

#iubenda-cs-banner .iubenda-cs-close-btn {
  position: absolute !important;
  top: -2px !important;
  padding: 16px !important;
  right: 0 !important;
  min-width: 48px !important;
  height: 48px !important;
  font-size: 24px !important;
  line-height: 0 !important;
  font-weight: lighter !important;
  cursor: pointer !important;
  text-align: center !important;
}

#iubenda-cs-banner .iubenda-cs-close-btn:hover {
  opacity: 0.5 !important;
}

#iubenda-cs-banner .iubenda-banner-content {
  font-weight: 300 !important;
  margin: 16px !important;
  margin-bottom: 0 !important;
  -webkit-box-flex: 1 !important;
  -ms-flex: 1 1 auto !important;
  flex: 1 1 auto !important;
  overflow-y: auto !important;
  mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 16px) !important;
  -webkit-mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 16px) !important;
  padding-bottom: 32px !important;
}

#iubenda-cs-banner .iubenda-banner-content-padded {
  padding-right: 32px !important;
}

#iubenda-cs-banner .iubenda-banner-content a {
  cursor: pointer !important;
  color: currentColor !important;
  opacity: 0.7 !important;
  text-decoration: underline !important;
}

#iubenda-cs-banner .iubenda-banner-content a:hover {
  opacity: 1 !important;
}

#iubenda-cs-banner #iubenda-cs-title {
  font-weight: bold !important;
  margin-bottom: 16px !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group {
  margin: 16px !important;
  z-index: 1 !important;
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
  margin-top: 0 !important;
  -ms-flex-negative: 0 !important;
  flex-shrink: 0 !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group > div {
  display: -webkit-box !important;
  display: -ms-flexbox !important;
  display: flex !important;
}

@media (min-width: 640px) {
  #iubenda-cs-banner .iubenda-cs-opt-group {
    -webkit-box-align: center !important;
    -ms-flex-align: center !important;
    align-items: center !important;
    -webkit-box-pack: justify !important;
    -ms-flex-pack: justify !important;
    justify-content: space-between !important;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-custom {
    margin-right: auto !important;
    -ms-flex-item-align: start !important;
    align-self: start !important;
    -webkit-box-pack: start !important;
    -ms-flex-pack: start !important;
    justify-content: flex-start !important;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-consent {
    margin-left: auto !important;
    -ms-flex-item-align: end !important;
    align-self: end !important;
    -webkit-box-pack: end !important;
    -ms-flex-pack: end !important;
    justify-content: flex-end !important;
  }
}

@media (max-width: 639px) {
  #iubenda-cs-banner .iubenda-cs-opt-group {
    margin: 12px !important;
    -webkit-box-orient: vertical !important;
    -webkit-box-direction: normal !important;
    -ms-flex-direction: column !important;
    flex-direction: column !important;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-custom {
    -webkit-box-ordinal-group: 3;
    -ms-flex-order: 2;
    order: 2;
  }
  #iubenda-cs-banner .iubenda-cs-opt-group-consent {
    -webkit-box-ordinal-group: 2;
    -ms-flex-order: 1;
    order: 1;
  }
}

#iubenda-cs-banner .iubenda-cs-opt-group button {
  -webkit-appearance: none !important;
  -moz-appearance: none !important;
  appearance: none !important;
  padding: 8px 32px !important;
  border-radius: 64px !important;
  cursor: pointer !important;
  font-weight: bold !important;
  font-size: 100% !important;
  margin-top: 4px !important;
  margin-bottom: 4px !important;
  text-align: center !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button:focus {
  opacity: 0.8 !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button:hover {
  opacity: 0.5 !important;
}

@media (min-width: 640px) {
  #iubenda-cs-banner .iubenda-cs-opt-group button:not(:last-of-type) {
    margin-right: 8px !important;
  }
}

@media (max-width: 639px) {
  #iubenda-cs-banner .iubenda-cs-opt-group button {
    padding: 8px 24px !important;
    width: 100% !important;
    display: block;
    text-align: center !important;
    margin: 6px 3px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand {
  margin: 0 -8px 0 !important;
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand {
    margin: -8px -8px 0 !important;
  }
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand div {
    margin: 0 auto !important;
    width: calc(992px - 32px) !important;
  }
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-brand div {
    margin: 0 8px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default .iubenda-cs-container {
  width: 100% !important;
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-rationale {
    width: 992px !important;
    margin: 16px auto !important;
  }
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-content {
    padding: 8px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-brand {
  margin: -8px -8px 0 !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-brand div {
  margin: 8px !important;
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-container {
    width: 992px !important;
  }
}

@media (max-width: 991px) {
  #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center.iubenda-cs-top .iubenda-cs-container, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center.iubenda-cs-bottom .iubenda-cs-container {
    width: 100% !important;
  }
}

@media (min-width: 640px) {
  #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-container, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-container, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-container {
    width: 480px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group {
  -webkit-box-orient: vertical !important;
  -webkit-box-direction: normal !important;
  -ms-flex-direction: column !important;
  flex-direction: column !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group > div, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group > div, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group > div {
  width: 100% !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group button, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group button, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group button {
  display: block !important;
  width: 100% !important;
  text-align: center !important;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group-custom, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group-custom, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group-custom {
  -webkit-box-ordinal-group: 3;
  -ms-flex-order: 2;
  order: 2;
}

#iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-top):not(.iubenda-cs-center) .iubenda-cs-opt-group-consent, #iubenda-cs-banner.iubenda-cs-default-floating:not(.iubenda-cs-bottom):not(.iubenda-cs-center) .iubenda-cs-opt-group-consent, #iubenda-cs-banner.iubenda-cs-default-floating.iubenda-cs-center:not(.iubenda-cs-top):not(.iubenda-cs-bottom) .iubenda-cs-opt-group-consent {
  -webkit-box-ordinal-group: 2;
  -ms-flex-order: 1;
  order: 1;
}

#iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-content {
  -webkit-box-shadow: 0 8px 48px rgba(0, 0, 0, 0.15) !important;
  box-shadow: 0 8px 48px rgba(0, 0, 0, 0.15) !important;
  padding: 8px !important;
}

@media (min-width: 992px) {
  #iubenda-cs-banner.iubenda-cs-default-floating .iubenda-cs-content {
    border-radius: 4px !important;
    margin: 16px !important;
  }
}

#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-container,
#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-content,
#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-rationale {
  height: 100% !important;
}

#iubenda-cs-banner.iubenda-cs-fix-height.iubenda-cs-default-floating .iubenda-cs-content {
  height: calc(100% - 32px) !important;
}

#iubenda-cs-banner.iubenda-cs-fix-height .iubenda-cs-brand img {
  max-width: 75% !important;
}

#iubenda-cs-banner .iubenda-cs-content {
  background-color: #000000 !important;
  color: #FFFFFF !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group {
  color: #000000 !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button {
  background-color: rgba(255, 255, 255, 0.1) !important;
  color: #FFFFFF !important;
}

#iubenda-cs-banner .iubenda-cs-opt-group button.iubenda-cs-btn-primary {
  background-color: #0073CE !important;
  color: #FFFFFF !important;
}


/*
-----------------
MOBILE SDK
-----------------
*/

.iubenda-mobile-sdk #iubenda-cs-banner.iubenda-cs-visible {
  justify-content: center!important;
  align-items: center!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-container {
  max-height: 100%!important;
  display: flex!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-container .iubenda-cs-content {
  height: auto!important;
  border-radius: 0!important;
  margin: 0!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-opt-group {
  text-align: center!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-close-btn {
  display: none!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-rationale {
  display: flex!important;
  flex-direction: column!important;
  height: 100%!important;
}
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-banner-content {
  flex: 1;
  overflow-y: auto!important;
  margin: 0!important;
  padding: 16px 16px 48px!important;
  max-height: inherit!important;
  mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 15%) !important;
  -webkit-mask-image: linear-gradient(to top, rgba(0, 0, 0, 0) 0%, black 15%) !important;
}

@media (min-width: 992px) {
  .iubenda-mobile-sdk #iubenda-cs-banner .iubenda-banner-content,
  .iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-opt-group {
    margin: 24px!important;
  }
  .iubenda-mobile-sdk #iubenda-cs-banner.iubenda-cs-default .iubenda-cs-rationale {
    width: 100% !important;
    margin: 0 !important;
  }
}

.no-banner #iubenda-cs-banner {
  display: none!important;
}

/** fix scrolling in iOS 10 **/
.iubenda-mobile-sdk #iubenda-cs-banner.iubenda-cs-visible .iubenda-cs-container,
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-container .iubenda-cs-content,
.iubenda-mobile-sdk #iubenda-cs-banner .iubenda-cs-rationale {
  height: 100%!important;
}
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-top-container {
  position: relative!important;
}
.iubenda-mobile-sdk #iubenda-iframe #iab-container {
  position: absolute!important;
  top: 0!important;
  bottom: 0!important;
  left: 0!important;
  right: 0!important;
}

/** iframe **/
.iubenda-mobile-sdk #iubenda-iframe #iubenda-iframe-popup {
  height: 100%!important;
  width: 100%!important;
}
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-close-btn {
  display: none!important;
}
.iubenda-mobile-sdk #iubenda-iframe {
  background-color: transparent!important;
}

/* Fix cookie policy trimming on older Android devices */
.iubenda-mobile-sdk #iubenda-iframe iframe {
  background-color: transparent!important;
  position:absolute!important;
  bottom:0!important;
  top:0!important;
}
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-spinner {
  top: 50px !important;
}
/* Fix TCF widget overlapping footer in older Android devices */
.iubenda-mobile-sdk #iubenda-iframe .iubenda-iframe-footer {
  z-index: 9999!important;
}

config.json:

{
    "banner": {
        "acceptButtonDisplay": "true",
        "customizeButtonDisplay": "true",
        "backgroundColor": "#000000",
        "textColor": "#FFFFFF",
        "acceptButtonColor": "#FD1D1D",
        "acceptButtonCaptionColor": "white",
        "customizeButtonColor": "transparent",
        "customizeButtonCaptionColor": "#FFF"
    }
}

TCF option

Unlike the CS standard version, the TCF option is enabled by default in the SDK. If you don't run third-party personalized ads and you want to disable the TCF support, set enableTcf: false inside the config.json file.

Example:

{
    …
    enableTcf: false,
    "banner": {
        …
    }
}

Google Additional Consent Mode

Google Additional Consent Mode is disabled by default. If you want to add Google Additional Consent Mode, set googleAdditionalConsentMode": true inside the config.json file.

Example:

{
    …
    "googleAdditionalConsentMode": true,
    "banner": {
        …
    }
}

Parameters "invalidateConsentBefore" and "expireAfter"

invalidateConsentBefore Accepts a Date, and if valued, it should check if there is a preference already expressed, and if there is and the timestamp is lesser than the day of the configured date then it should not consider the preference anymore. Accepted formats: dd/MM/yyyy - yyyy/MM/dd - dd-MM-yyyy - yyyy-MM-dd - dd.MM.yyyy - yyyy.MM.dd

expireAfter If valued, number of days of the consent timestamp and the integer value of expireAfter parameter will be compared, if consent date is passed, the data on device will be cleared (Default: 360 days)

Example:

{
    …
    "invalidateConsentBefore": "08/11/2022",
    "expireAfter": 100,
        …
    }
}

Show the consent UI

To present the consent UI at app launch, call IubendaCMP.askConsent() in you main activity's onCreate method:

• if there’s no internet connection, the call won't have any effect (provided that skipNoticeWhenOffline is not set to false); 
• if consent has already been given, the call won't have any effect; 
• if consent has not already been given and a connection is available, IubendaCMP.askConsent() will make the consent request appear.

Please note that if you’ve set forceConsent to false, IubendaCMP.askConsent() won’t have any effect if the user dismisses the consent request after the first launch: to show the consent UI again you’ll have to call IubendaCMP.openPreferences(). 

Example:

public class DemoActivity extends AppCompatActivity  {

    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);

        setContentView(R.layout.activity_main);

        // automatically show the consent popup when needed
        IubendaCMP.askConsent(this);
    }
}

So, if your goal is to maximize consents:

• set forceConsent to true, and 
• call IubendaCMP.askConsent()

Otherwise, if you prefer to give the user the chance to dismiss the consent request without being prompted again whenever IubendaCMP.askConsent() is called again:

• set forceConsent to false
• call IubendaCMP.askConsent(), but note that it won’t have any effect after the first launch
• to ask for consent again, call IubendaCMP.openPreferences()

Notes about IubendaCMP.openPreferences():

• if consent has not already been given, IubendaCMP.openPreferences() will open the consent request.
• If consent has already been given, IubendaCMP.openPreferences() will allow users to change their consent preferences:
  • If "perPurposeConsent": true, it will show the per-category preferences.
  • If "perPurposeConsent": false, it will show the TCF consent preferences.
  • Otherwise, if "perPurposeConsent": false and "enableTcf": false, it will show the cookie policy.

To have complete control of when to show the consent request, you could rely entirely on IubendaCMP.openPreferences(), but you’ll have to implement a way to check if consent has been given. 

Custom consent UI

You can use a custom activity to ask for user consent, without showing the provided popup; in this case, you can take advantage of the following methods of IubendaCMP:

Notes about IubendaCMP.accept():

• if the user has not expressed any preferences, then it accepts everything.
• This method should be used when developing a custom UI that doesn't use the default notice used by the SDK.

Also, it is advised to add a listener to detect when the user has given consent when calling the open* methods.

Example:

public class ConsentActivity extends Activity implements IubendaCMPChangeListener {
    
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);

        setContentView(R.layout.activity_consent);
    }
    
    @Override
    protected void onPostCreate(@Nullable Bundle savedInstanceState) {
        super.onPostCreate(savedInstanceState);
        IubendaCMP.registerChangeListener(this);
    }

    @Override
    protected void onDestroy() {
        IubendaCMP.unregisterChangeListener(this);
        super.onDestroy();
    }

    public void onAcceptClick(View view) {
        IubendaCMP.accept();
        finish();
    }
    
    public void onOptionsClick(View view) {
        IubendaCMP.openTcfPreferences(this);
    }

    @Override
    public void onConsentChanged() {
        if (IubendaCMP.isConsentGiven())
            finish();
    }
}

Listening for changes

If necessary, you can listen to changes of user consent by registering a listener, which is achieved by calling IubendaCMP.registerChangeListener(), for example inside the onCreate method of your Application or Activity.

You can remove a listener by calling IubendaCMP.unregisterChangeListener(), for example inside onDestroy(). For detailed changes and events, use IubendaCMP.registerCallback() and IubendaCMP.unregisterCallback(). Listeners are captured as a weak reference.

Listeners are captured as a weak reference.

Accessing to IAB Transparency and Consent Framework settings

You can access to the IAB TCF settings, such as the encoded consent string, either directly as IAB specs or through the convenience methods offered by a CMPStorage object. You can get an instance of the storage by calling IubendaCMP.getStorage().

Available settings Getters

For more information about the TCF and its advanced settings, such as the ability to restrict purposes and determine the viable legal basis (consent and/or legitimate interest), read our TCF guide.

Initializing libraries without IAB TCF support

Third-party libraries that do not directly adhere to the IAB Transparency and Consent Framework, may need to be initialized separately depending on the consent status and preferences.

To achieve that, you can implement a change listener in your Application class and call IubendaCMP.isConsentGiven(), and other methods, to evaluate the consent status.

Example:

public class MyApplication extends Application implements IubendaCMPChangeListener {

    @Override
    public void onCreate() {
        super.onCreate();

        IubendaCMPConfig config = IubendaCMPConfig.builder()
                .gdprEnabled(true)
                .siteId("12345678")
                .cookiePolicyId("ABCDE")
                .googleAds(true)
                .build();
        IubendaCMP.initialize(this, config);
        IubendaCMP.registerChangeListener(this);

        initializeLibraries();
    }

    private void initializeLibraries() {
        if(IubendaCMP.isPurposeEnabled(2)){
            // Activate libraries that use "Functionality" purpose
        }
        if(IubendaCMP.isPurposeEnabled(3)){
            // Activate libraries that use "Measurement" purpose
        }
    }

    @Override
    public void onConsentChanged() {
        initializeLibraries();
    }
}

Offline and errors

The library requires an internet connection to display the consent popup, hence to generate or update the consent string, while the latest consent string is always available on local storage through CMPStorage.

By default, the askConsent method checks for internet connection before launching the popup activity, so, if there is no connection, the popup is not shown, but will be presented on the next launch.

If an error occurs during the consent flow, instead, an error message is shown with the option to retry or close the popup. In this case, setting forceConsent(true) ensures that the popup will be presented again if no consent has been given.

Compliance with US State Privacy Laws

Our SDK supports features to manage compliance with state-specific laws. You can handle opt-out requests for the sale, sharing, and targeted advertising of personal information, in accordance with applicable state laws.

Methods for US Privacy Compliance

We introduce three methods that return an UsprOptOut object, providing the user's opt-out preference regarding their personal data. The UsprOptOut can be NOTAPPLICABLE, indicating no action needed; YES, signaling an opt-out; or NO, indicating no opt-out.

1. getSaleOptOut(): Evaluates the opt-out status for the sale of personal information.
2. getSharingOptOut(): Determines the opt-out status for sharing personal data with third parties.
3. getTargetedAdvertisingOptOut(): Assesses the opt-out preference for targeted advertising.

The returned UsprOptOut value from each method provides a clear directive on how to proceed with the user's data based on their preferences and applicable laws.

1. NOTAPPLICABLE: The user's preference is not applicable under the current circumstances or legal requirements.
2. YES: Indicates an active opt-out by the user from the specific data processing activity.
3. NO: Indicates that the user has not opted out, allowing the data processing activity to continue.

Consent preferences across different devices

Read this guide to learn how to implement the Consent Database API to synchronize consent preferences between sites and apps for each authenticated user.

See also

• How to configure your Privacy Controls and Cookie Solution (advanced guide)
• How to synchronize consent preferences between sites and apps (SDK guide)
• How to save proof of consent to cookies (Privacy Controls and Cookie Solution and Consent Database integration)

The post CS for mobile | Developer’s Guide appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Because the Terms & Conditions document is essentially a legally binding agreement; it is, therefore, not only important to have one in place, but also necessary to ensure that it meets legal requirements. This means that the document must be up-to-date with all applicable regulations, precise, visible and easily understandable so that users can both easily see it and agree to it. The “agreeing action” should be done in an unambiguous way (e.g. clicking a checkbox with a visible link to the document before being able to create an account or use the service).

While the full content may vary based on the particulars of your business, the Terms and Conditions should at least include the following:

• Identification of the business
• Description of the service that your site/app provides
• Information on risk allocation, liability, and disclaimers
• Warranty/Guarantee information (where applicable)
• The existence of a withdrawal right (if applicable)
• Safety information, including instructions for proper use (where applicable)
• Terms of delivery of product/service (where applicable)
• Rights of use (if applicable)
• Conditions of use/ purchase (eg. age requirements, location-based restrictions)
• Refund policy/exchange/termination of service and related info
• Info related to methods of payment
• Any additional applicable terms

You can learn more about Terms and Conditions here generate yours now by clicking below.

See also

• What are the Terms and Conditions and when are they needed?
• Can I use a Terms and Conditions template?
• How to generate Terms and Conditions

The post What Should Basic Terms and Conditions Include? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Generating and setting up your Terms and Conditions with iubenda is pretty straightforward, and you’re guided along the way. In this post, we’ll show you how to create your first Terms document from start to finish. If you need any additional help, please feel free to message us via the chat window (you can find it by clicking on the green help button on the right and then clicking on the live chat button at the top). We’re happy to answer any of your questions anytime.

First up, you’ll need to access your iubenda account. If you haven’t created one already, you can do so here. Once you’re signed up it’s time to get started. The process is simple. We’ll show you how to:

1. Generate your terms and conditions
2. Customize your terms and conditions
3. Add the terms to your site or app

1. Generate your terms of service

Once you’ve logged into your dashboard, it’s time to begin generating your Terms and Conditions.

If you’re adding the terms to a site area or project that already exists within your dashboard, then simply click on the particular website/app to enter into the management area.

If you haven’t yet added a website to your iubenda account, do so by clicking on the Start generating button at the top right of the dashboard to open up the generation modal, filling in the relevant details and then clicking on Start generating button at the bottom of the modal window. This will also take you into the management area.

Once there, scroll down and click on Generate now under the Terms and Conditions section.

This will take you to the edit area of the Generator where you can add and customize clauses.

Now, by default, a basic set-up was created when you clicked on “Generate” (you can view this by clicking on Preview in the right sidebar). However, it’s important to point out that, since Terms and Conditions are legally binding documents, it’s in your best interest and we strongly recommended that you customize your documents to suit your particular situation and business needs. We’ll show you how to do that in the next step.

2. Customize your terms and conditions

As mentioned above, your Terms of Use need to to be adapted to your business’ individual needs. You do this by editing and adding clauses.

First, click on the Add clauses button

This will open up a window which allows you to select and edit the clauses you’d like to add. If it’s your first time using the Terms and Conditions Generator, you see the following:

As indicated by the image above, the most commonly needed clauses are pre-selected by default as part of a basic set-up, but you can de-select or add additional clauses where necessary. The clauses are separated into intuitive modules, with on-click guides to help you throughout the set-up process.

To edit a particular clause, simply click on the Customize button. This takes you into the clause where you modify as needed, to fit your particular scenario.

As mentioned above, the on-click guides are available throughout to make sure that you choose the options that best fit your individual needs.

Click on the Apply changes button on the bottom right to save your customizations. This action will take you back to the main “clauses modal” window. If you’re finished customizing your terms, you can click on Save and close on the bottom right of this window and move on to the next step below.

How to preview your terms

×

in the side bar.

Owner & Service Info

Now that you’re finished editing, you’ll need to enter your business details into the Owner’s Field. To do so, simply click on the Next button on the bottom right of the screen.

This will take you to the Owner & Service info page.

Here you’ll need to enter your legally valid business and/or contact info.
The details of what’s required for your specific scenario might vary based on where your business is located and who it targets. The most commonly required information here usually includes the owner’s/business’ identity, contact details, postal address, and relevant codes of conduct that apply to your business model (if any).

Since Terms of Service are legally binding contracts, it’s important to state legitimate details here. Also, do consider that, in many cases, under Consumer Law, customers must be able to contact you if the need arises.
More details on what’s required can be found in the dedicated guide.

Once you’re finished entering the required info into the Owner’s field, click the Next button at the bottom right of the page. This will display the finished Terms document. Subsequently clicking on Next button at the bottom right of this modal window will then take you to the integration section of your site area. You can also access this integration area throughout the generation process by clicking on the Manage and Embed link at the top left of the Generator.

3. Add the terms of use to your site/app

The final step is to integrate the terms you’ve just generated with your website/ app. This is done by using the embedding code, or link provided on the “embed” page.

You can add the terms to your site/app in the following ways:

1. as a button which opens an elegant modal window;
2. as a direct link (e.g. for App Stores);
3. or as a direct site embed (best option if you’d like to add your own brand colors, custom fonts etc. to the document).

You can read more about how to add your terms and conditions to your site/app in the dedicated guide.

To access any of these methods, simply click on the relevant tab (if you already have a privacy policy active on that site, you’ll need to scroll to the Terms and Conditions section), copy the code snippet or text link depending on your chosen method, and follow the instructions in the guide linked above.

And you’re done!

Update and refine your terms when needed

We constantly monitor the major legislations to keep the clauses available to your documents valid and up-to-date, however, should you need to manually update clauses, personal details, contact details etc., you can simply log back into your iubenda dashboard and make changes at any time.

See also

• What are the Terms and Conditions and when are they needed?
• What should basic Terms and Conditions include?
• How to integrate Terms and Conditions with your site/app

The post How to Generate Terms and Conditions appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In order to edit a document, access your dashboard and select the site or app that you’d like to edit the terms for by clicking on it or on the Manage button. Next, click the Edit button in the Terms and Conditions section.

Customize existing clauses or add new ones, save and you’re done.

How to change the URL of the site or the name of the app

It can become necessary to edit the title of an iubenda generated document, either because you’ve changed your site’s URL or renamed your app.

For information on how to duplicate an existing site please see here

Adding a Link to an External Document

If you have an existing document drafted by your legal team, you can easily integrate it with your iubenda-generated policy by adding a link to your external document within the relevant section. 
This approach allows you to keep your original, lawyer-approved wording intact while still using iubenda to manage your compliance.

To add a link to your external Terms and Conditions document:

• Navigate to the relevant section in the Terms and Conditions editor and click on ‘Add clauses’
• After that click on ‘Add’ under the Advanced: Incorporation of other Documents section

• Then select ‘Add a document included by reference and add the name and link 

• Save your changes to ensure the link is visible on your published Terms and Conditions page.

For detailed instructions on how to customize a specific section of your Terms and Conditions, please follow this guide: Terms and Conditions Template Customization.

See also

• How to generate Terms and Conditions
• How to delete your Terms and Conditions

The post How to Edit your Terms and Conditions appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Dashboard > [select the site you’d like to delete the terms for] > Delete at bottom window (as pictured below)

The post How to Delete your Terms and Conditions appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

iubenda’s Terms and Conditions Generator offers three integration options which can be used for different purposes:

1. Standard embedding
2. Direct link
3. Direct text embedding and API

Where to find the embedding options

Head to your dashboard and click on the website that you’d like to get the embed code for. Next, click the Embed button in the Terms and Conditions section.

This is what you will find:

1. Standard embedding (all plans)

The standard and our simplest integration method is the one where you include the iubenda button/link on your site. This will open the terms and conditions in a modal window on your site when the link is clicked.

Make sure you’ve selected Add a widget to the footer and, after customizing as you’d like, you can copy the relevant code from the generator.

Where do I put the iubenda embedding code on my site?

The best idea is to add it to your site’s footer so that it is always visible and accessible. The footer is easy to find and is typically found towards the end of your html document. It appears in an html element similar to <footer>{YOUR IUBENDA CODE}</footer> or <div id="footer">{YOUR IUBENDA CODE}</div>.

What does this look like?

Here is a working example. Click on the button to open the terms and conditions:

2. Direct link (Starter, Essentials, Advanced and Ultimate plans)

The direct link option is appropriate if you do not mind that the document not be displayed on your site, as the link displays the terms and conditions on a page hosted by iubenda.com. This is a very useful option for app stores.

Once clicked the Embed button in the Terms and Conditions section, select Use a direct link as shown below (and add it in the appropriate place):

Where do I put the iubenda link?

That depends entirely on you. But the rule of thumb is your site’s footer, as it’s a good way for it to be seen from every page.

3. Direct text embedding and API (Advanced and Ultimate plan)

The direct text embedding option is the one option that will make your terms and conditions look as if it were part of your own site.

We offer two ways for embedding the terms and conditions into the body of one of your pages. You can:

• copy and paste the JavaScript into your page, or
• call our API from your backend.

Once clicked the Embed button in the Terms and Conditions section, select Embed the text in the body as shown below (and add it in the appropriate place):

Keep in mind that with the option Use plain HTML with no styling you can completely remove the document of all of iubenda’s styling and use your own.

Downloadable Terms and Conditions Option:

You can also offer a downloadable PDF of your Terms and Conditions. This feature allows users to download an updated copy directly from your T&C document.

Simply, in the embedding section, select the “Downloadable PDF” option. Once you enable this option, we’ll generate and keep updated a PDF version of your documents, which will be linked in the footer of the documents themselves.

API

The following API URLs are available:

• https://www.iubenda.com/api/terms-and-conditions/:public_id
• https://www.iubenda.com/api/terms-and-conditions/:public_id/no-markup

Notes:

• :public_id is the ID of your terms and conditions provided by your embedding options
• the JSON API doesn’t include the CSS provided by to the default iubenda terms and conditions

Example

curl --include --request GET 'https://www.iubenda.com/api/terms-and-conditions/:public_id'

Responses

Everything OK, response status 200:
{ :success => true, :content => "..." }

Required document is not found, response status 404:
{ :success => false, :error => "Document not found. If you are the owner of the site..." }

Application error, response status 500:
{ :success => false, :error => "Application Error. Please contact info@iubenda.com for support." }

See also

• Customize the Way Your Website or App Is Referred To in Your Document
• Can I Copy and Paste the Text of the Legal Documents into My Website?

The post How to Integrate iubenda’s Terms and Conditions on your Site and App appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

To access it, simply go to your Dashboard > [click on your chosen website] Privacy and Cookie Policy > Edit > Add service.

The Scanner button is located at the top of the services window:

Next, click on the scanner button and enter the address of the website you’d like to scan and click on the “Scan” button.

The Scanner will then perform a thorough check of the website you entered, and will send the scan-report to your iubenda account email address.

The report will highlight any services running on your website which are not included in your current policy.

Furthermore, the services detected are shown directly in the generator.

From the scan results box, you can check all the services that are found to be missing in your documents, already selected, and ready to be added.

See also

• How to Add Services to Your Privacy Policy
• How to Add a Custom Service and Customize to Your Needs

The post How to use the Site Scanner from within the Generator appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

This tutorial uses ChronoForms, a popular extension for Joomla!, to illustrate how you can integrate the Consent Database with your Joomla! forms. If you’re using another extension you may still refer to this tutorial as the implementation approach is generally the same.

To use the Consent Database with ChronoForms you’ll need to use the JavaScript method of implementation. 

In short, you must:

• embed the Consent Database code;
• create (or modify) your form in a way that includes the necessary id tags; and
• send the consent data to iubenda APIs.

1. Embed the Consent Database code

To begin, copy the code you find under Consent Database > Embed > Javascript.

Then paste this code inside the head of all your pages. You can do this via one of the following methods:

• access the Template Manager directly; or
• if you’re not comfortable with directly editing theme files, you can use a plugin for coding and scripts integration, like HeadTag. Once you’ve installed the plugin, you can access the head by going to Extensions > Plugins > System – Headtag > Menu Item Tags and paste the Consent Database script.

2. Create or modify your form

Once you’ve included the Consent Database’s code inside the head of your site, access your Joomla! dashboard and create a form (e.g. “contact”) using the ChronoForms extension.

If you’re already using ChronoForms on your site, simply head to your forms overview page (Components > ChronoForms6) and click on the form you’d like to integrate with the Consent Database.

Here’s the contact form we’ll be using in our implementation example (name, email, message and newsletter subscription):

On ChronoForms it will look something like this:

Once you’ve defined your form area, you’ll need to customize the form to map its various inputs so that the Consent Database can actually identify and pull the information that your users enter into the various input points.

To do the mapping you can use the load (or submit) function with the map object. In order for the load/submit function to work you’ll need:

• an id for the form element;
• different names for all the subject and preferences inputs; and
• an id for the submit element;

a. Click on the settings icon next to the form area and add an id to your form:

b. Similarly to the Form ID, add an id to the text fields (in our example, name, email and message):

And to the checkboxes (in our case, “generic” and “newsletter”):

For a mandatory checkbox like the generic above, be sure to:

• Disable the validation
• Disable ghost
• Add two triggering events that will enable/disable the submit button (note that we’re using #contact-submit, as indicated on the general configuration of the submit button):

c. Finally, add an id to the submit button as well:

You may also want to add a confirmation message to be shown to your users after they’ve filled out the form (submit > Actions):

Save your changes and make sure that your form is published.

Form embedding

If you’re modifying an already-existing form on your site, jump to the section below, otherwise (if you’ve only just created the form) copy the shortcode generated by ChronoForms:

{chronoforms6}contact{/chronoforms6}

And paste it in a page of your site (e.g., “Contact us”).

3. Send the Consent data to iubenda APIs

Now that your form is ready you need to make sure that it sends the information to the Consent Database when the user fills in and submits it. There are two ways to do this:

• the load method allows you to send the Consent data to iubenda APIs asynchronously;
• the submit method allows you to send the Consent data to iubenda APIs synchronously.

Load method

The load function allows you to bind fields of the consent object to input fields of your <form> and to automatically record the consent either by setting up a trigger function under submitElement: or programmatically via a dedicated trigger.

By default, this method writes into localStorage to protect from any loss of data in case a new page is loaded before the JavaScript has finished executing.

Here’s the load function with the map object:

<script>
    _iub.cons_instructions.push(["load", {
        submitElement: document.getElementById("contact-submit"),
        form: {
            selector: document.getElementById("contact-form"),
            map: {
                subject: {
                    first_name: "name",
                    email: "email"
                },
                preferences: {
                    generic: "generic",
                    newsletter: "newsletter"
                }
            }
        },
        consent: {
            legal_notices: [{
                    identifier: "privacy_policy",
                },
                {
                    identifier: "cookie_policy",
                }
            ],
        }
    }])
</script>

In the code above please note:

• the contact-submit and contact-form ids;
• the first_name and email subject mapping (remember that you have four non-editable options: first_name, last_name, full_name and email);
• the checkbox preferences, where you’re free to use the keys you like (in our case, generic and newsletter);
• the legal_notices, which are automated if you sync your iubenda legal documents with the Consent Database (just use the standard identifiers privacy_policy and cookie_policy).

Be sure to include the load method after the form (for example inside the footer of your contact page), and you’re done!

Once you’ve collected your consents, you’ll be able to sort and analyze your user consent data in the Consent Dashboard.

Submit method

The submit method allows you to send the Consent data to iubenda APIs synchronously.

<script>
    document.getElementById("contact-submit").onclick = function() {
        sendToConsentSolution()
    };

    function sendToConsentSolution() {
        var inputName = document.getElementById("name").value;
        var inputEmail = document.getElementById("email").value;
        var inputMessage = document.getElementById("message").value;
        var subjectId = inputEmail.toLowerCase().replace(/\W/g, '-'); //optional
        _iub.cons_instructions.push(["submit", {
            form: {
                selector: document.getElementById("contact-form"),
                map: {
                    subject: {
                        first_name: "name",
                        email: "email"
                    },
                    preferences: {
                        generic: "generic",
                        newsletter: "newsletter"
                    }
                }
            },
            consent: {
                subject: {
                    id: subjectId
                },
                legal_notices: [{
                        identifier: "privacy_policy"
                    },
                    {
                        identifier: "cookie_policy"
                    }
                ]
            }
        }])
    }
</script>

In the code above please note:

• the contact-submit and contact-form ids;
• the first_name and email subject mapping (remember that you have four non-editable options: first_name, last_name, full_name and email);
• the checkbox preferences, where you’re free to use the keys you like (in our case, generic and newsletter);
• the legal_notices, which are automated if you sync your iubenda legal documents with the Consent Database (just use the standard identifiers privacy_policy and cookie_policy);
• optional: instead of letting it be generated automatically, we can customize the subjectId with the email address – for example – of the subject, all lowercase and with the symbol “-” instead of “.” and “@” (this way for john.doe@iubenda.com the subjectId would become john-doe-iubenda-com).

Be sure to include the submit method after the form (e.g., inside the footer of your contact page), and you’re done!

Once you’ve collected your consents, you’ll be able to sort and analyze your user consent data in the Consent Dashboard.

See also

• Consent Database – Introduction and Methods
• Consent Database – JS Documentation

The post How to Implement the Consent Database in Joomla! with ChronoForms appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

There are two ways to do this, depending on whether the “old” platform provides a cookie (synchronous method) or requires a call to its API (asynchronous method).

Synchronous method

Before embedding the Privacy Controls and Cookie Solution you’ll need to define a synchronous function (e.g. isConsentGivenByOtherPlatform) to get the consent from the other platform:

<script type="text/javascript">
    function readLocalCookie(cookieName) {
        var cookies = document.cookie.split(';');
        for (var i = 0; i < cookies.length; i++) { 
            var e=cookies[i].split('=');
            if (e[0] === cookieName) {
                return e[1];
            }
        }
        return null;
    }
    function isConsentGivenByOtherPlatform() {
        var otherPlatformCookieName = 'cookie_from_other_platform'; // use the actual cookie name saved by the other platform 
        var prevConsent = readLocalCookie(otherPlatformCookieName); 
        if (prevConsent) { 
            return true; 
        } else { 
            return false; 
        } 
    }
</script>

Next, add the Privacy Controls and Cookie Solution snippet, invoking the onReady callback:

<script type="text/javascript">
    var _iub = _iub || [];
    _iub.csConfiguration = {
        "lang": "en",
        "siteId": XXXXXX, // use your siteId
        "cookiePolicyId": YYYYYY, // use your cookiePolicyId
        "banner": {
            "acceptButtonDisplay": true,
            "customizeButtonDisplay": true,
            "position": "float-top-center"
        },
        "callback": {
            "onReady": function() {
                if (typeof window.isConsentGivenByOtherPlatform === 'function' && isConsentGivenByOtherPlatform()) {
                    _iub.cs.api.setPreferences({
                        consent: true,
                        ccpa: true,
                        uspr: {
                            'all': true,
                            'sd8': true,
                            'sd9': true,
                        },
                        purposes: {
                            '1': true,
                            '2': true,
                            '3': true,
                            '4': true,
                            '5': true,
                        },
                        tcfv2: {
                            'all': true,
                        },
                        gac: {
                            'all': true,
                        },
                    }, true);
                }
            }
        }
    };
</script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

The onReady callback checks if consent is already given on another platform and, if so, stores it calling the _iub.cs.api.setPreferences() method.

Asynchronous method

Before embedding the Privacy Controls and Cookie Solution code you’ll need to define a function that:

1. accepts a callback;
2. detects the consent;
3. saves the consent in a global variable; and
4. invokes the callback afterward.

Here’s a sample:

<script type="text/javascript">
    // fetch consent asynchronously from 3rd party 
    function getConsentByOtherPlatform(cb) {
        $.getJSON('http://otherplatform.com/api/get-consent', function(result) {
            if (result.given) {
                window.consentByOtherPlatform = true;
            } else {
                window.consentByOtherPlatform = false;
            }
            cb();
        });
    }
    function isConsentGivenByOtherPlatform() {
        return !!window.consentByOtherPlatform;
    }
</script>

Next, add the Privacy Controls and Cookie Solution snippet, invoking the onReady callback:

<script type="text/javascript">
    var _iub = _iub || [];
    _iub.csConfiguration = {
        "lang": "en",
        "siteId": XXXXXX, // use your siteId
        "cookiePolicyId": YYYYYY, // use your cookiePolicyId
        "banner": {
            "acceptButtonDisplay": true,
            "customizeButtonDisplay": true,
            "position": "float-top-center"
        },
        "callback": {
            "onReady": function() {
                if (typeof window.isConsentGivenByOtherPlatform === 'function' && isConsentGivenByOtherPlatform()) {
                    _iub.cs.api.setPreferences({
                        consent: true,
                        ccpa: true,
                        uspr: {
                            'all': true,
                            'sd8': true,
                            'sd9': true,
                        },
                        purposes: {
                            '1': true,
                            '2': true,
                            '3': true,
                            '4': true,
                            '5': true,
                        },
                        tcfv2: {
                            'all': true,
                        },
                        gac: {
                            'all': true,
                        },
                    }, true);
                }
                }
            }
        }
    };
</script>
<script type="text/javascript">
    // ask for 3rd party consent before including the CS
    getConsentByOtherPlatform(function() {
        var s = document.createElement('script');
        s.src = '//cdn.iubenda.com/cs/iubenda_cs.js';
        document.head.appendChild(s);
    });
</script>

The onReady callback will check if consent is already given on another platform and, if so, stores it calling the _iub.cs.api.setPreferences() method.

_iub.cs.api.setPreferences(consentObj, hideBanner)

The _iub.cs.api.setPreferences method, expected two arguments: consentObj (required) and hideBanner (optional)

consentObj

It’s an object with follow preferences items:

• consent – required – accepts true or false – It refers to general consent
• ccpa – required if CCPA is enabled – accepts true or false – it refers to US privacy and it will be applied only if CCPA is enabled in Cookie Solution
• uspr – required if USPR is enabled – accepts an object with the following options – it refers to USPR consent and it will be applied only if USPR is enabled in Cookie Solution
  • all – accepts true or false – this option sets the same value for all purposes