In Android, most apps include functionality from third-party libraries (SDKs) in an attempt by developers to reduce the cost of building an app. However, it is important to understand the privacy risks that these SDKs can pose to the users of the app. In this blog post, we discuss these risks, as well as why it is important that developers understand the type of content that third-party libraries are including in their app.
TRUST aWARE mission is to provide a holistic and effective digital security and privacy framework to identify, audit, analyse, prevent, and mitigate the impact of the various S&P threats associated with citizen’s digital activities.
By providing tools for key Protecting privacy and digital security are becoming increasingly important in everyday life. A lack of trust in software and how it deals with or exposes personal information could negatively impact consumers and the wider EU digital market. Privacy, security and trust in software are promoted by the TRUST aWARE project. They are also, in themselves, philosophical and ethical concepts, but what do they mean in the context of TRUST aWARE?
By providing tools for key stakeholders along the whole cycle, and supporting cooperation and intelligence sharing, TRUST aWARE will minimise the impact of cyberthreats, empowering users, promoting collective awareness, and encouraging trustworthy S&P-preserving digital products in compliance with regulation.
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 101021377.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
This cookie is set by Statcounter. It is used to determine whether a user is a first-time or a returning visitor and to estimate the accumulated unique visits per site.
This cookie is set by StatCounter Analytics. It is used to determine whether a user is a first-time or a returning visitor.
This cookie is set by the website that you visit. When it is first set, a random id is generated and stored in the cookie in order to avoid counting you as a visitor more than once. Similarly to the is_unique cookie, this cookie also stores a count of your returning visits.