We understand that under Google’s EU User Consent Policy, we must make certain disclosures to your users in the European Economic Area (EEA) and the UK, and obtain their consent for the use of cookies or other local storage where legally required and for the collection, sharing, and use of personal data for ads personalization.
We intend to adhere to all international regulations and compliance as and when it is applicable to our business and use of website. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).
Using Privacy & messaging and its integrated Funding Choices functionality, we do create and display a message to our users to help gather consents required under the General Data Protection Regulation.
The message with Privacy & messaging lists the ad technology providers of our site or app uses, and asks users to consent to the use of data to show personalized ads (if any) and for other purposes. We also request consent for the use of data by our own site or app.
We make the following adherence to messages to make sure they meet legal requirements:
-
Structure of a message
A GDPR message contains multiple “screens” (or “pages”) that are shown to users depending on which buttons and links they click in your messages. The button options presented to users are based upon your selections in the “User consent options” section during message creation. - GDPR messages with two buttons (Manage options, Consent)
GDPR messages with three buttons (Do not consent, Consent, Manage options)
Additional information
Support for the IAB TCF specification
GDPR messages created in Privacy & messaging have been updated to support the IAB TCF v2.2 specification. - Using Google’s Additional Consent technical specification
Privacy & messaging GDPR messages you create using the IAB Transparency and Consent Framework utilize Google’s “Additional Consent” technical specification. This is how Privacy & messaging transmits consent decisions to vendors that are not tagged with the “TCF” icon in the IAB Europe Transparency and Consent vendor list (Ad Manager, AdMob, AdSense).
The Additional Consent specification sends transparency and/or consent signals to vendors that have not yet registered on the IAB Europe Global Vendor List (GVL) (these vendors do not have the “TCF” icon in the vendor list).
This specification enables publishers, Consent Management Platforms (CMPs), and partners to gather and propagate additional consent—alongside their TCF v2.2 implementation—for companies that are not yet registered with the IAB Europe Global Vendor List but are on Google’s Ad Tech Providers (ATP) list.
Additional Consent can include: in Ad Manager, AdMob, or AdSense
Ad Manager help center
AdMob help center
AdSense help center
Request consent for your own use of data
Additionally, we also use the GDPR message to establish transparency and consent for a set of IAB TCF data purposes—with a basis of either consent or legitimate interest—for your own use of data. Learn how to request consent for your own use of data.
EU user consent policy
If and when we have an agreement with Google, it would incorporate this policy, or otherwise use a Google product that incorporates this policy, you must ensure that certain disclosures are given to, and consents obtained from, end users in the European Economic Area along with the UK. If you fail to comply with this policy, we may limit or suspend your use of the Google product and/or terminate your agreement.
Properties under your control
For Google products used on any site, app or other property that is under our control, or that of our affiliate or our client, we understand the following duties apply for end users in the European Economic Area along with the UK.
We will obtain end users’ legally valid consent to:
the use of cookies or other local storage where legally required; and
the collection, sharing, and use of personal data for personalization of ads.