French regulators call out Apple’s ATT | Pocket Gamer.biz
Apple’s App Tracking Transparency may be going too far, or not far enough, as French regulators from the country’s Autorité de la concurrence are launching an investigation into their ad tracking systems.
In a statement from the French competition authority (via finance outlet Pymnt) they state that Apple wasn’t playing fair by forcing ATT prompts on third-party apps, but not properly displaying them on their own. “Apple is accused of having abused its dominant position by implementing discriminatory, non-objective and non-transparent conditions for the use of user data for advertising purposes.”
Apple’s ATT has of course been referred to as the “Adpocalypse” specifically because of how it restricts access to user data for purposes like attribution, utilities many developers and publishers rely on.
In a statement provided to Pymnt, Apple replied “Apple’s apps do not show an ATT prompt because they do not track, meaning they do not link user or device data with user or device data collected from other companies’ apps, websites, or offline properties for targeted advertising or advertising measurement purposes, nor do they share user or device data with data brokers.”
Over the garden wall
Of course, while ATT has been considered a broad positive from a consumer privacy point of view, a key aspect many have pointed out is that what it mainly facilitates is the so-called “walled garden” approach to privacy on iOS. Whereas many third-parties are blocked from accessing this data unless cleared to, Apple has access from the get-go, which they arguably use to their advantage and even have their own ad network to use it. By effectively monopolising this data, Apple is arguably protecting user privacy, but also maintaining their own access.
It’s unclear just what resolution the French competition authorities could seek, however it’s an interesting wrinkle to the ongoing ATT story and a possible vindication for those who objected to Apple’s ATT on the grounds of it monopolising data. Although ATT rates have begun to climb, for many navigating the world of this new privacy and data-tracking environment is still cause for concern.
window.fbAsyncInit = function() {
// init the FB JS SDK FB.init( appId : 250161755076617, // App ID //channelUrl : '//'+window.location.hostname+'/channel.php', // Path to your Channel File status : true, // check login status cookie : true, // enable cookies to allow the server to access the session xfbml : true // parse XFBML );
FB._PG = url: "/useractions/loginfb/", response: "allowed",
// Common handler to fetch FB details and reload the page process: function(me) $.post( FB._PG.url, username: me.username, uname: me.name, uid: me.id, uimg: 'https://graph.facebook.com/' + me.id + '/picture?type=large' ) .done(function(xml) if ( $("status", xml).text() == FB._PG.response ) window.location.reload(); else alert('Error: Something bad just happened. Our tech department has been notified. Please try again later.');
) .fail(function(xml)
alert("Error: something wasn't right there, please try again.");
); ,
// Used by event subscriptions to handle the response handleResponse: function(response) if (response.authResponse) FB.api('/me', function(me) if (me.name) FB._PG.process(me); );
,
post: function(text, image) image = image ;
FB.Event.subscribe('auth.statusChange', FB._PG.handleResponse);
FB.Event.subscribe('edge.create', function(response) $.post('/ajax/social-links/', site: 'facebook' ); ); };
(function(d, s, id) var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "http://connect.facebook.net/en_US/all.js"; fjs.parentNode.insertBefore(js, fjs); (document, 'script', 'facebook-jssdk'));