With the introduction of SDK Runtime, third-party libraries will operate in a separate, thoroughly monitored and regulated virtual "sandbox", hence the name. This diagram shows that the SDK-calling code, along with the SDKs that receive the calls from this code, all reside in the app's process. And this wasn't the only trouble - should some kind of a problem occur with the library, the app was at risk of suffering the consequences too (, ).
Needless to say, libraries' vendors were abusing this scheme left and right, collecting all sorts of data. For example, let's say that the app has access to the device's location - the library has it too now. Developers would insert third-party libraries in their apps (think Facebook, Google), and those libraries would inherit all the permissions that the app itself was granted. This SDK - which stands for Software Development Kit - creates a dedicated environment for third-party SDKs to run in. This is an extremely useful technology that will definitely have a positive effect. You can dive deep into the matter yourself, but I'll try to describe the key points about each of the new initiatives here. Privacy Sandbox includes several separate technologies. But at the same time, Google is making it clear that they'd like advertisers to keep as many options as possible - and this is a tough balance to strike. Google has announced a new suite of technologies called Privacy Sandbox that should (at least theoretically) make Android devices better in terms of privacy. Follow our blog and social media so you don't miss its release. Now we are continuing to explore the topic, and a large research article will be published soon. This article is a brief overview of the situation made by Andrey Meshkov, CTO and co-founder of AdGuard. Google recently introduced the Privacy Sandbox which will largely determine the future of privacy of Android users. AdGuard always keeps a close eye on industry news that affects privacy issues.
0 kommentar(er)
