Privacy in SDKs
summary
NOYB is running compliance campaigns and now targets SDKs, explaining that many SDKs send identifiers and location data (IDFA, cookies) which are personal data, that e‑privacy requires opt‑in consent and GDPR demands data minimization and named recipients. Regulators treat app and SDK makers as joint controllers — see Grindr €10m decision — and transfers to the US need SCCs after Schrems II. Exodus Privacy scanning and a campaign of 10,000 cookie complaints are used to find violations; one e‑signature app withdrew Google Analytics.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:32About NOYB
- 3:50What is NOYB
- 5:00SDKs and GDPR
- 6:56EPrivacy
- 11:36Processing personal data
- 13:41Consent
- 16:05Sensitive Data
- 17:22By Default
- 18:30Copyright infringement
- 19:18Data minimization
- 20:41NOYB action
- 21:42Resources
- 22:05Contact
- 22:44QA
related talks
01h 09mWearing your privacy on your sleeve
28mEmbracing innovation by building privacy friendly apps
36mPrivacy, Consent and Security Within Modern Applications
25mImplementing a Privacy First Strategy
15mAvoiding Security and Privacy Issues in SDK Integration
01h 15mEnforcement of GDPR – A reality check.
37mHey, You, Get off My Private Data: Do Apps Respect Your Privacy as They Claim?
01h 00mPrivacy and GDPR: What all developers should know