After almost a year of anticipation, Apple has released its latest software update, iOS 14.5, along with its new privacy tool, AppTrackingTransparency (ATT). All apps must now use this framework to obtain consent from users to access their location information. We sat down with Lawrence Chan, EVP, Business Development at Cuebiq, to get his take on this change. Continue reading to learn about his views on why Cuebiq is well-positioned for this change and why Named Consent is so important right now.
What is Cuebiq doing to comply with Apple’s IDFA opt-in enforcement?
We worked with our app partners to increase IDFA opt-ins where possible, leveraged first-party identifiers to offset the loss of IDFA grants, and we worked with partners to innovate the user flow to meet future updates to mobile operating systems. We’re confident that our direct relationships with apps and experience navigating previous OS updates (e.g. iOS 13 and Android X) will help our app partners mitigate some of the risk of losing users not opting into the IDFA. We believe that Named Consent and our privacy framework, along with our direct app relationships, will allow us to effectively avoid any significant changes to our scale or quality of location data.
What did the delay of Apple’s IDFA opt-in enforcement mean for Cuebiq?
The delay had no impact on Cuebiq, as we’ve been fully prepared for IDFA opt-in enforcement for months. That said, with the delay we had some more time to build out processes we put in place and refined them even more.
Will Cuebiq be employing identifiers outside the IDFA?
Yes, but this is nothing new for us. We have always employed identifiers outside the IDFA, such as hashed-IDs and cookies. What’s more, we are increasing our device linkages by adding more cross-device partners.
As the industry creates standards for ID resolution, we’re in constant talks with the industry groups and technology partners that will be driving this new reality.
Why is Named Consent so important right now?
In a post-CCPA-and-GDPR world, Named Consent is the only way to prove that a location provider has consent rights to location data as well as prove how, when, what, and where that consent was created and captured. Proving consent is paramount — if a location provider can’t prove consent, they should not be using that data. Cuebiq is the only location provider with Named Consent for all of our app partners. Cuebiq takes a global approach to privacy and meets GDPR explicit consent requirements. This approach exceeds compliance in every U.S. state law and regulation, including the CCPA. In order for the consumer’s consent to meet this bar, we include specific use cases in the consent language so that the user knows exactly what uses they are consenting to share their data for prior to continuing. And of course, users can easily opt out of our data collection at any time.
What is Cuebiq’s stance on consumer privacy?
Consumer privacy is a global issue, and we believe that a future-proof approach to privacy and transparency is beneficial to all stakeholders, users, marketers, data and tech partners alike. At Cuebiq, we hold privacy as a core tenet and take a principled approach to ensure our products, services, and relationships reflect this. Privacy at Cuebiq can be described in four powerful principles: Consent, Transparency, Control, and Accountability.
Cuebiq has end-to-end tech to support privacy management and consent, and we will continue to invest in this.
Connect with our team to learn more.
