Web analytics, cookies, tag managers, CMPs, ad pixels, and session-replay tools as deployed on websites and apps targeting Finland. Sectoral rules (healthcare KanTa, banking, employment Yksityisyyden suoja työelämässä) are touched only where they intersect with the analytics layer.
Applicable laws
The legal framework that governs personal data processing here.
National addons
Country-specific statutes layered on the EU baseline.
- § 5 Child consent age — lowered to 13 (GDPR Art 8 opening clause used)
- § 8–9 Special-category data — research, statistics, archiving carve-outs
- § 8–10 Tietosuojavaltuutettu (Ombudsman) + Seuraamuslautakunta (sanctions board) — institutional split
- § 24 Tietosuojarikkomus — criminal liability for intentional violation (fine or up to 1 year imprisonment)
- § 200 Direct marketing — opt-in baseline for natural persons (email/SMS); soft opt-in for existing-customer + similar products
- § 201 Storage / read access on terminal equipment — informed consent required (ePrivacy Art 5(3) transposition)
- § 202 Strictly-necessary exception — narrowly construed, analytics/marketing never qualify
- § 205 Confidentiality of electronic communications — supervised by Traficom
- § 3 Necessity requirement — employer may process only data directly necessary for the employment relationship
- § 4 Collection from third parties — employee consent required for most non-direct sources
- § 21 Co-operation procedure — mandatory consultation before deploying technical monitoring of staff
- Kielilaki § 2 Bilingual provision — Finnish + Swedish for public bodies and bilingual municipalities
- Yhdenvertaisuuslaki § 8 Discrimination by language — relevant where critical service information is withheld in user's language
Regulators
Supervisory authorities that interpret and enforce privacy law here.
Coordination body
- 2020-05-19 · First Art 83 fines — Seuraamuslautakunta issues Finland's first GDPR fines — Posti €100K + transport company €72K + online retailer €16K. Unblocked the post-constitutional-review pipeline.
- 2021-05-26 · Cookie guidance — Tietosuojavaltuutettu + Traficom joint guidance — opt-in baseline reaffirmed under SVPL §201; analytics never strictly-necessary.
- 2024-09 · Verohallinto fine — Seuraamuslautakunta imposes €750K on Tax Administration for unlawful processing of taxpayer data — among Finland's largest administrative fines.
Notable enforcement
Finland's GDPR enforcement pipeline was delayed by a 2018–2019 constitutional-law debate over whether the Tietosuojavaltuutettu could simultaneously investigate and fine — resolved by creating the separate Seuraamuslautakunta inside the Ombudsman's office. Since 2020, fines have been steady but moderate by EU standards, with the Verohallinto €750K (2024) marking the high-water mark. The Ombudsman is widely seen as pragmatic and dialogue-oriented relative to LfDI BW or the French CNIL.
-
Verohallinto (Tax Administration) Seuraamuslautakunta · Art 5, 6 stood
Unlawful processing of taxpayer data — among Finland's largest administrative fines and the first significant fine against a public authority.
-
Vastaamo psychotherapy clinic (in liquidation) Seuraamuslautakunta · Art 5, 32 stood
Catastrophic patient-data breach affecting 33,000+ therapy clients. Largest sectoral-impact case in Finnish data-protection history; fine assessed against the bankrupt entity.
-
Online retailer (anonymised) Seuraamuslautakunta · Art 5, 6, 32 stood
Improper retention of customer purchase history beyond stated purpose + insufficient access controls.
-
Healthcare provider (anonymised) Seuraamuslautakunta · Art 32, 33 stood
Late breach notification + insufficient pseudonymisation of patient identifiers in research datasets.
-
Posti Group Seuraamuslautakunta · Art 12, 13, 14 stood
Finland's first GDPR fine — failure to provide transparent information about address-change processing and to honour data-subject rights.
GA4 status
GA4 is usable in Finland with prior, informed consent under SVPL § 201. Tietosuojavaltuutettu is pragmatic post-DPF — transfers to Google's US servers are accepted in principle while Google LLC remains DPF-certified. There is no Finnish equivalent of the Austrian/French 2022 Schrems-II GA4 ban; the Ombudsman has not issued a categorical adverse decision against GA4.
| DPA | Stance |
|---|---|
| Tietosuojavaltuutettu | Permissive post-DPF — opt-in via SVPL §201 + DPF certification suffice. Documented TIA recommended for defensive purposes. |
| Traficom | Co-supervisor on the cookie layer — joint 2021 guidance with Tietosuojavaltuutettu reaffirms opt-in baseline. |
| Seuraamuslautakunta | No GA4-specific Art 83 fine to date; all enforcement has targeted controllers' broader cookie-banner / transparency failures. |
Cross-border transfers + Schrems II
Tietosuojavaltuutettu accepts adequacy for DPF-certified US importers post-DPF (10 Jul 2023). Finnish position is pragmatic — controllers are expected to verify DPF certification status at onboarding and at material processor changes, and to keep a documented Transfer Impact Assessment for non-DPF US recipients. No public Finnish equivalent of the LfDI BW maximalist TIA stance.
EU 2021/914 SCCs are the standard fallback when DPF certification is absent or revoked. Tietosuojavaltuutettu has not issued bespoke template clauses; controllers use the EU SCCs with Module-2 onward-transfer scrutiny.
Employee data
Key thresholds
Vendor signals
Red / yellow / green markers are an editorial reading of public regulator guidance and published enforcement actions, applied to vendor behavior we can observe or that the vendor documents. They are not legal conclusions, not endorsements, and not advice about your specific processing. Configuration changes the picture — a "yellow" vendor in one configuration may be defensible in another.
Analytics tools · 4 · 0 green · 3 yellow · 1 red
| Vendor | Status | Rationale |
|---|---|---|
| YELLOW | Visitor ID cookie + cross-suite stitching with Experience Platform. DPIA strongly recommended; configure ECID + IP obfuscation. | |
| YELLOW | EU residency available on paid plans; default cloud is US. Persistent user IDs require config + DPA + DPF chain. | |
| YELLOW | EU cloud helps but session recording + autocapture default to PII collection. Disable autocapture and recordings or self-host for green. | |
| RED | Auto-capture grabs every click and form value — broad PII risk under GDPR Art 5(1)(c) data minimization. |
Consent management platforms · 5 · 5 green · 0 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | Danish-based, EU-hosted. Auto-blocks third-party scripts pre-consent — verify your manual scripts also gate. | |
| GREEN | Italian-based, EU-hosted. Free tier limits 5k pageviews/mo; granular per-vendor controls require paid plan. | |
| GREEN | Open-source, self-hosted. No managed updates — site owner maintains vendor list. | |
| GREEN | GDPR + CCPA + multi-region templates available. Common config error: GDPR/CCPA mode mismatch — verify per-region defaults. | |
| GREEN | German-based, EU-hosted. v3 SDK required for Consent Mode v2; TCF flow can over-collect for non-AdTech sites. |
Ad pixels · 3 · 0 green · 0 yellow · 3 red
| Vendor | Status | Rationale |
|---|---|---|
| RED | Loads pre-consent if naively placed; cross-device matching broad. Block until consent + IAB TCF string set. | |
| RED | Schrems II concerns persist; advanced matching hashes PII but does not fix EU→US transfer problem. | |
| RED | PRC-parent ownership flagged by Italian Garante and EDPB; transfers to China contested. Consent + risk acknowledgement required. |
Server-side · 3 · 2 green · 1 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | EU-only datacenters strong for FR/DE compliance; per-event pricing scales steeply at high traffic. | |
| GREEN | EU server containers handle the routing — but server-side tagging does NOT auto-fix consent. CMP must still gate browser-side pings. | |
| YELLOW | "EU server" ≠ EU data — clients still transmit to Google ad backends downstream. Use only for Google-ecosystem first-party-routing. |
Compare with neighbors
Side-by-side rule comparison.
Common questions
Is Google Analytics legal in Finland in 2026?
Who is Finland's data protection authority?
Why does Finland have two bodies — Tietosuojavaltuutettu and Seuraamuslautakunta?
What is the child-consent age in Finland?
Do I need a Finnish DPO?
What language must my privacy notice be in?
Is 'legitimate interest' a valid basis for analytics in Finland?
What about employee monitoring and analytics?
Do I need a Finnish Article 27 representative?
Can a public authority be fined in Finland under GDPR?
// EDITORIAL · NOT LEGAL ADVICE This page summarises Finland's privacy framework as of 2026-05-05. Rules vary by sector, establishment, and DPA position. For binding interpretation, consult counsel admitted here.