The MediaGrid and GDPR¶
Following General Data Protection Regulation (GDPR) definitions, The MediaGrid is considered to be a separate and independent data controller for the personal data it receives and processes in connection with The MediaGrid services. The MediaGrid processes such personal data as required for performance of its agreements, to carry out its services and as described in the Grid Inc. Privacy Policy.
As The MediaGrid does not directly provide any services to end users/data subjects, The MediaGrid does not gather GDPR consent and relies on publishers to obtain and document user consent for its stated purposes and to include The MediaGrid as a declared data controller.
Publishers (or their Consent Management Provider) being the ones who gather user consent should include it in bid requests sent to The MediaGrid using the user consent string.
The MediaGrid passes this information to buyers in its protocol using
regs.gdpr
anduser.ext.consent
fields. The MediaGrid supports the TCF v2.0 consent string format for the processing of its own consented to purposes. For more information see the following links:For user syncing, The MediaGrid supports the
gdpr
,gdpr_pd
, andgdpr_consent
macros in the sync URL.
Transparency & Consent Framework 2.0¶
The Transparency & Consent Framework (TCF) has one current valid version, TCF v2.0, v1.1 having been sunset on September 30, 2020. You can read more about that in this Dates You Need To Know For The TCF V2.0 Switchover article. Use the following information to update your integration with The MediaGrid to use TCF 2.0.
You need to adopt the TCF 2.0 consent string when sending or receiving bid requests. Buyers can expect to get version 2.0 of the string when their Suppliers start to send it to The MediaGrid. You can read more about the information encoded within the consent string here: Transparency and Consent String with Global Vendor & CMP List Formats
You need to be registered with the IAB and listed in the Global Vendors List v2 so that any user consent granted to you and the purposes for which it has been granted can be validated.
For user syncing:
You need to update the user syncing URL that The MediaGrid uses to sync cookies with you to include your Global Vendors List ID as part of the consent macro
You need to support v2.0 of the consent string
It is recommended to support the new optional
gdpr_pd
macro
# v2.0 syncing macros. 686 is The MediaGrid's GVL ID. You will need to use yours
your.sync.url?bidswitch_ssp_id=${SSP}&gdpr=${GDPR}&gdpr_consent=${GDPR_CONSENT_686}&gdpr_pd=${GDPR_PD}
The MediaGrid TCF 2.0 Position¶
The MediaGrid uses the following TCF 2.0 framework components to comply with the GDPR. The information given below can be verified within The MediaGrid’s node in the IAB’s Global Vendors List v2 (GVL). The MediaGrid Vendor ID is 686, and the The Media Grid’s TCF 2.0 Global Vendors List Entry section is a copy of this entry.
In addition to The MediaGrid’s ID of 686, it is important that the following IDs are granted user consent:
BidSwitch 128
IPONWEB 129
We strongly advise that those IDs are present in the approved vendors list in order for The MediaGrid to be able to properly match and monetise requests/impressions coming from a particular user
Purposes¶
For all of the purposes which the framework covers, The MediaGrid uses user consent as the sole legal basis for processing their data.
Purpose 1 - Store and/or access information on a device
Purpose 2 - Select basic ads
Purpose 3 - Create a personalised ads profile
Purpose 4 - Select personalised ads
Purpose 5 - Create a personalised content profile
Purpose 6 - Select personalised content
Purpose 7 - Measure ad performance
Purpose 8 - Measure content performance
Purpose 9 - Apply market research to generate audience insights
Purpose 10 - Develop and improve products
Special Purposes¶
The MediaGrid does not process user data for TCF 2.0 Special Purpose 1.
Special Purpose 1 - Ensure security, prevent fraud, and debug
However, as the provider of an online media trading platform, The MediaGrid does process user data for TCF 2.0 Special Purpose 2.
Special Purpose 2 - Technically deliver ads or content
Features¶
The MediaGrid relies solely upon user consent as the legal basis for processing user data for Features 1, 2 and 3.
Feature 1 - Match and combine offline data sources
Feature 2 - Link different devices
Feature 3 - Receive and use automatically-sent device characteristics for identification
Special Features¶
The MediaGrid does not process user data for any of the TCF 2.0 special features.
Special Feature 1 - Use precise geolocation data
Special Feature 2 - Actively scan device characteristics for identification
{
"686":{
"id":686,
"name":"The MediaGrid Inc.",
"purposes":[
1,
2,
3,
4,
5,
6,
7,
8,
9,
10
],
"legIntPurposes":[
],
"flexiblePurposes":[
],
"specialPurposes":[
],
"features":[
1,
2,
3
],
"specialFeatures":[
],
"policyUrl":"https://www.themediagrid.com/privacy-policy/",
"cookieMaxAgeSeconds":31536000,
"usesNonCookieAccess":true
}
}