2 ms·
It seems like, since these labels are structured, it should be possible for them to really determine the sandboxing. Maybe Apple intends to move in this directi
by morelisp 6y ago
It seems like, since these labels are structured, it should be possible for them to really determine the sandboxing. Maybe Apple intends to move in this direction in the future but doesn't want to say it yet - maybe they're happy just having some basic marketing in place about how much they care - but this is definitely how things should be heading. Your label says "data not collected"? Then the SDK will return all-zero for any hardware and vendor ID, use a fixed user agent and no non-standard headers for all HTTP requests, clear caches hyper-frequently, and report every location at Cupertino.
- Nextgrid 6y agoA better solution would be to expand the privacy labels to a list of URLs/hostnames the app is allowed to access and have that list actually enforced by the system. This would make it impossible to accidentally or maliciously "forget" to declare a tracker, and working around it would become difficult because it breaks the economics of tracking (you can proxy those through your own backend, but the ad company wouldn't trust this data as it would enable you to do ad fraud very easily).
- morelisp 6y ago> you can proxy those through your own backend, but the ad company wouldn't trust this data as it would enable you to do ad fraud very easily The is only true for the actual showing of ads; data brokers and bidding services already often work this way. (Hell, some data brokers are nothing more than an Excel dump of their internal usage table they'll mail you for a fee.)