Finland Data Protection Act (Tietosuojalaki, 1050/2018)
Finland DPA: Sectoral Acts (Working Life 759/2004, SVTSL 917/2014, Cybersecurity Act 2024)

Finland Data Protection Act (Tietosuojalaki, 1050/2018) FiDPA-Status-AIAct-Nordic: Implementation Status, EU AI Act Interplay, Nordic-Baltic Coordination

Tietosuojalaki implementation status + EU coordination + 2024-2025 trends. STATUS: Tietosuojalaki 1050/2018 in force since 1 January 2019 + amended 2019 + 2021 + 2023 (Henkilotunnus reform) + 2024 (Cybersecurity Act integration). EU AI ACT INTERPLAY (Regulation (EU) 2024/1689): Finland designates Traficom + Tukes (Safety and Chemicals Agency) + Tietosuojavaltuutettu as competent authorities for the AI Act; the Tietosuojavaltuutettu covers AI systems processing personal data + biometric identification + emotion recognition + automated decision-making; the AI Act phases in 2025-2027 + coordinates with GDPR Article 22 + the Tietosuojalaki. NORDIC-BALTIC WORKING GROUP ON DATA PROTECTION: Finland + Sweden + Norway + Denmark + Iceland + Estonia + Latvia + Lithuania coordinate on common positions at EDPB + cross-border-cooperation + sectoral interpretations. EU ONE-STOP-SHOP: Finnish controllers operating cross-border under GDPR may use the Tietosuojavaltuutettu as lead supervisory authority where Finland is the place of main establishment. RECENT PRIORITIES (2024-2025): Henkilotunnus reform + child online safety + AI Act preparation + ransomware response + cross-border enforcement actions against major US tech platforms (cookie consent + behavioural advertising). NO substantive Tietosuojalaki amendment pending; legislative + regulatory attention focuses on Cybersecurity Act 2024 implementation + EU NIS2 + AI Act + DSA coordination.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Finland DPA: Sectoral Acts (Working Life 759/2004, SVTSL 917/2014, Cybersecurity Act 2024)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.