This is the best summary I could come up with:
But Olejnik’s assessment is likely to be welcomed at Google and by other organizations looking to adopt the Chocolate Factory’s purportedly privacy-preserving ad tech.
There is still the possibility that Europe’s ePrivacy Directive could require user consent prior to ad delivery because it covers “information” collection, rather than the narrower category “personal data.”
Beyond the adversarial possibilities that won’t become apparent until this technology is widely deployed and challenged by efforts to break it, there are concerns about the impact of shifting ad tech auctions onto mobile devices.
Appelquist told The Register that while he doesn’t have any data to quantify the resource usage of Protected Audience, “We remain concerned with the processing burden that this spec proposes to place on the user’s device (in terms of battery life, bandwidth, performance in general).”
In this way, users will pay for a bit more privacy with their device resources: speed, available memory, and battery life will take major hits.”
The Register asked Google whether it has any data to share about the resource usage and battery impact of Privacy Sandbox APIs.
The original article contains 1,166 words, the summary contains 180 words. Saved 85%. I’m a bot and I’m open source!
LWD@lemm.ee 10 months ago
Petition to rename “Privacy Sandbox” to “Google AdSense@Home” or something similar, since it’s never been about privacy… breaking competing ad networks in order to serve ads in a way prescribed by Google.
You know, Google. The advertising company.
TheGrandNagus@lemmy.world 10 months ago
Privacy sandbox makes sense once you realise they mean sandboxing privacy away from us.