Code and Law - A legal session on privacy, know-how and open source, Part I
summary
GDPR applies if the app touches identifiers like IP, IMSI or analytics; the session says developers must document, document, document, map data flows and adopt privacy by design; breaches require a 72-hour notification to authorities and a prebuilt incident process; consent vs legitimate interest for Google Analytics/Firebase is unresolved and Facebook fan‑page ECJ guidance makes platforms’ processing part of publisher obligations. For know‑how, treat core algorithms and business plans as trade secrets, classify access, use NDAs with contractual penalties, and exclude reverse engineering in contracts.
AI-written summary · about
chapters (10)
- 0:00Welcome and introduction
- 1:44GDPR overview and compliance
- 10:13Obligations under GDPR
- 13:04Steps to GDPR compliance
- 18:41Introduction to know-how protection
- 19:25What is know-how
- 22:18Protecting trade secrets
- 26:36Legal steps for know-how protection
- 35:48Common ground between GDPR and know-how
- 36:09Q&A session
related talks
01h 00mPrivacy and GDPR: What all developers should know
01h 15mAcademic Session I The GDPR within a continuously reforming digital environment
32mGDPR Impact
46mDeveloping for Privacy
01h 01mAcademic sessions on data protection law and privacy
48mGDPR Design for Websites, Apps and (Ro)Bots
39mHot Legal Issues
01h 02mThe GDPR and New Technologies: Enough, or do we need more?