Data Protection Monitor
Global Privacy & Data Protection Intelligence

Estonia Data Protection & Privacy Regulation

EE schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), artificial-intelligence

Last updated · 10 categories · 65 claims · 44 sources in the cumulative register

Estonia's first full GDPR baseline this cycle carries one dominant signal.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Sectoral Watch, AdTech & Commercial Privacy (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 10 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix102 claims · 40 sources · machine-compiled
29 Confirmed31 Probable5 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Law made at European Economic Area (Bloc) level that applies in Estonia is covered once, on the European Economic Area (Bloc) page. This page covers Estonia’s own layer: implementation, national authorities, national options and local enforcement.

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Estonia's new financial fraud prevention and combating law, 936 SE, passed by the Riigikogu on or about 21 October 2026, creates a sectoral personal-data-sharing gateway that sits beside, rather than fully inside, the ordinary data-protection framework. The Act gives credit institutions and payment and e-money institutions the right to exchange fraud-suspicion data, which will often include personal data, with each other, with the Police and Border Guard Board, and with CERT-EE, Estonia's computer emergency response team; a parallel exchange right extends to credit providers and credit intermediaries for loan fraud specifically. The Act is understood to have been adopted but not yet in effect, pending publication in the Riigi Teataja. The specific GDPR legal-basis provision that the Act itself relies on for this sharing has not been confirmed from the Act's own text, so the precise interaction between the new sectoral gateway and the general lawful-processing framework remains to be established.

Key regulatory facts for Estonia
Key regulatory facts for Estonia
Regulatory DimensionEstonia Standing Position
JurisdictionEstonia (EE)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 65 sourced findings)
Regulator & FrameworkFully GDPR-aligned EU Member State regime with an operational, EDPB-integrated supervisory authority and a settled national implementing act in force since 2019.
Lawful Processing & Special DataCore lawful-basis and special-category rules are GDPR-aligned and actively enforced; only prospective, non-binding EU-level reform (Digital Omnibus) is pending.
Data Subject RightsGDPR rights framework in force with clear escalation path to AKI/courts; no Estonia-specific restriction identified.
Controller/Processor DutiesCore GDPR controller/processor obligations are enforced and operative; only prospective Digital Omnibus amendments to ROPA and breach thresholds remain unresolved.
Primary Instruments CitedEUR-Lex, Estonia Official Instrument (dataprotection.gi estonia), Estonia Official Instrument (recordinglaw.com estonia-data-privacy-laws), Estonia Official Instrument (klarproof.com aki), EUR-Lex / Official Journal
Last Confirmed / Updated (44 sources in cumulative register)

#

Fully GDPR-aligned EU Member State regime with an operational, EDPB-integrated supervisory authority and a settled national implementing act in force since 2019.

Primary frameworkGDPR (Regulation (EU) 2016/679) as implemented by the Estonian Personal Data Protection Act (Isikuandmete kaitse seadus, PDPA, in force 15 January 2019)
Traffic-light rationale — GreenFully GDPR-aligned EU Member State regime with an operational, EDPB-integrated supervisory authority and a settled national implementing act in force since 2019.

Sub-modules (5)

Regulator and authorityGreen

AKI (Tatari 39, Tallinn) is the competent EU GDPR supervisory authority for Estonia, currently led by Pille Lehis.

Claims (4):

  • The Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), based at Tatari 39, 10134 Tallinn, is Estonia's EDPB-member supervisory authority, currently headed by Ms Pille Lehis.
  • Andmekaitse Inspektsioon (AKI) — AKI is Estonia's GDPR supervisory authority, headed by Director General Pille Lehis.
  • Andmekaitse Inspektsioon (Tatari 39, 10134 Tallinn), headed by Pille Lehis, is Estonia's single EDPB-member supervisory authority under GDPR Art 51.
  • AKI is Estonia's single national supervisory authority under GDPR Article 51.

Act and instrumentsGreen

The PDPA entered into force 15 January 2019 and implements/supplements the GDPR at national level.

Claims (2):

  • Data protection in Estonia is primarily governed by the GDPR, implemented into Estonian law via the Personal Data Protection Act (PDPA), which entered into force on 15 January 2019.
  • Isikuandmete kaitse seadus (PDPA) — The Personal Data Protection Act has been in force since 15 January 2019 to implement/derogate GDPR provisions in Estonian national law.

Material scopeGreen

Material scope follows GDPR Art 2 (processing of personal data wholly or partly by automated means, or manual processing forming part of a filing system), applied directly as EU law in Estonia.

Territorial scopeGreen

GDPR's extraterritorial scope (Art 3) applies directly: non-EU controllers offering goods/services to, or monitoring the behaviour of, individuals in Estonia fall within scope.

Claims (1):

  • Under GDPR rules applicable in Estonia, non-EU-established businesses must apply the same rules when they offer goods or services, or monitor the behaviour, of individuals in the EU.

Regulator registration and filingGreen

No general controller registration/filing regime exists under GDPR or the PDPA; obligations instead run through records of processing (Art 30) and prior consultation for high-risk DPIA outcomes (Art 36). AKI maintains a published Art 35(4) list of processing operations requiring DPIA.

Claims (1):

  • AKI adopted (per EDPB Opinion 6/2018) a national list of processing operations subject to the mandatory DPIA requirement under GDPR Article 35(4), in place of a general controller-registration/filing regime.

Key findings (1)

  • AKI/PDPA baseline confirmed, EDPB-integrated, in force since 2019. — source on file
Category narrative 70 words

Estonia's data-protection regime is anchored in the GDPR, which applies directly as EU law, and the national Personal Data Protection Act (Isikuandmete kaitse seadus, PDPA), which entered into force on 15 January 2019 to implement/derogate GDPR provisions. The supervisory authority is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, AKI), headed by Director General Pille Lehis. AKI participates in EDPB one-stop-shop and coordinated enforcement mechanisms alongside the other 26 EU DPAs.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (8)
  1. Confirmed EDPB — The Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), based at Tatari 39, 10134 Tallinn, is Estonia's EDPB-member supervisory authority, currently headed by Ms Pille Lehis. observed
  2. Confirmed OneTrust DataGuidance — Data protection in Estonia is primarily governed by the GDPR, implemented into Estonian law via the Personal Data Protection Act (PDPA), which entered into force on 15 January 2019. observed
  3. Confirmed EUR-Lex — Under GDPR rules applicable in Estonia, non-EU-established businesses must apply the same rules when they offer goods or services, or monitor the behaviour, of individuals in the EU. observed
  4. Confirmed EDPB — AKI adopted (per EDPB Opinion 6/2018) a national list of processing operations subject to the mandatory DPIA requirement under GDPR Article 35(4), in place of a general controller-registration/filing regime. observed
  5. Probable https://dataprotection.gi/jurisdictions/estonia/ — Isikuandmete kaitse seadus (PDPA) — The Personal Data Protection Act has been in force since 15 January 2019 to implement/derogate GDPR provisions in Estonian national law.
  6. Probable noyb — Andmekaitse Inspektsioon (AKI) — AKI is Estonia's GDPR supervisory authority, headed by Director General Pille Lehis. observed
  7. Confirmed Andmekaitse Inspektsioon — Andmekaitse Inspektsioon (Tatari 39, 10134 Tallinn), headed by Pille Lehis, is Estonia's single EDPB-member supervisory authority under GDPR Art 51. observed
  8. Probable noyb — AKI is Estonia's single national supervisory authority under GDPR Article 51. observed

#

Core lawful-basis and special-category rules are GDPR-aligned and actively enforced; only prospective, non-binding EU-level reform (Digital Omnibus) is pending.

Primary frameworkGDPR Articles 6, 7, 9; Personal Data Protection Act (PDPA)
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — GreenCore lawful-basis and special-category rules are GDPR-aligned and actively enforced; only prospective, non-binding EU-level reform (Digital Omnibus) is pending.

Sub-modules (4)

Lawful basesAmber

AKI has rejected controllers' reliance on Art 6(1)(b) contractual-necessity for ancillary data uses (e.g., rider-rating data) not strictly necessary to perform the core contract.

Claims (1):

  • In a 2022 own-initiative proceeding, the Estonian DPA found that a ride-hailing controller lacked a valid legal basis for processing rider ratings and disagreed that Article 6(1)(b) GDPR (contractual necessity) applied to that processing.

Special categoriesAmber

No Estonia-specific derogation to GDPR Art 9 special-category rules was identified in this pass; the EU Digital Omnibus proposes a new incidental/residual-processing derogation for AI development, still pending in trilogue.

Claims (1):

  • The EDPB and EDPS have welcomed the Digital Omnibus proposal's aim to introduce a specific, conditional derogation to the prohibition on processing special-category data, covering incidental/residual processing in AI system development and operation, while recommending narrower scope and lifecycle safeguards.

Pseudonymisation and anonymisationAmber

GDPR's pseudonymisation concept (Art 4(5), Recital 26) applies directly; the EU Digital Omnibus proposal to narrow the 'personal data' definition regarding pseudonymised data (Art 4(1)) remains contested and was stripped from a February 2026 Council compromise text.

Claims (1):

  • The EDPB and EDPS strongly urged co-legislators not to adopt the Commission's proposed narrowing of the GDPR Art 4(1) personal-data definition (relative identifiability for pseudonymised data), and a leaked February 2026 Council compromise text removed that proposed change entirely.

Key findings (1)

  • Strict AKI enforcement of consent/lawful-basis validity; Digital Omnibus special-category derogation pending. — source on file
Category narrative 78 words

Lawful bases and consent standards follow GDPR Art 6/7 directly. AKI enforcement practice shows a strict reading of both consent validity and the contractual-necessity basis, as illustrated in a 2022 own-initiative case against a ride-hailing platform's use of rider-rating data. National special-category and pseudonymisation rules track GDPR Art 9 and Recital 26 without material Estonian derogation identified in this research pass; the EU Digital Omnibus proposal (not yet law) would add an AI-specific derogation for incidental special-category processing.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (4)
  1. Confirmed AKI / EDPB — In a 2022 own-initiative proceeding, the Estonian DPA found that a ride-hailing controller lacked a valid legal basis for processing rider ratings and disagreed that Article 6(1)(b) GDPR (contractual necessity) applied to that processing. observed
  2. Confirmed EDPB / AKI — AKI held that another person's self-declared justification for viewing a prescription is not equivalent to the voluntary consent of the prescription holder, because the controller cannot verify the purpose or voluntariness of that consent. observed
  3. Probable EDPB — The EDPB and EDPS have welcomed the Digital Omnibus proposal's aim to introduce a specific, conditional derogation to the prohibition on processing special-category data, covering incidental/residual processing in AI system development and operation, while recommending narrower scope and lifecycle safeguards. observed
  4. Probable IAPP — The EDPB and EDPS strongly urged co-legislators not to adopt the Commission's proposed narrowing of the GDPR Art 4(1) personal-data definition (relative identifiability for pseudonymised data), and a leaked February 2026 Council compromise text removed that proposed change entirely. observed

#

GDPR rights framework in force with clear escalation path to AKI/courts; no Estonia-specific restriction identified.

Primary frameworkGDPR Articles 12-22; PDPA
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — GreenGDPR rights framework in force with clear escalation path to AKI/courts; no Estonia-specific restriction identified.

Sub-modules (5)

Access rightAmber

Access requests submitted in English to Estonian controllers may be answered in Estonian, per EDPB cross-border cooperation guidance covering Estonia.

Claims (1):

  • Where an access/rectification/erasure request is submitted in English to an Estonian controller, the controller responds to the applicant in Estonian.

Rectification and erasureGreen

GDPR Art 16/17 rights apply directly; Estonia's national population/business registers follow the GDPR rectification/erasure regime with sector-specific notification duties.

Restriction and objectionGreen

GDPR Art 18/21 rights apply directly with no identified Estonian derogation.

Data portabilityGreen

GDPR Art 20 portability right applies directly with no identified Estonian derogation.

Deadlines and response windowsGreen

If a controller fails to respond within 30 days, or the requester disputes the reply, the requester may lodge a free-of-charge complaint with AKI or an administrative court.

Claims (1):

  • If the requester is not satisfied with a controller's reply, or receives no reply within 30 days of sending the request, the requester has the right to lodge a free complaint with AKI or an administrative court.

Key findings (1)

  • Standard GDPR Chapter III rights with 30-day escalation path to AKI/courts. — source on file
Category narrative 54 words

Estonia applies the GDPR's Chapter III rights directly (access, rectification, erasure, restriction, objection, portability), with the standard one-month (extendable) response window under Art 12(3). AKI's own EDPB-published guidance confirms a 30-day escalation trigger: if a controller fails to respond, or the requester is dissatisfied, the requester may complain to AKI or an administrative court.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (2)
  1. Probable EDPB — Where an access/rectification/erasure request is submitted in English to an Estonian controller, the controller responds to the applicant in Estonian. observed
  2. Confirmed EDPB — If the requester is not satisfied with a controller's reply, or receives no reply within 30 days of sending the request, the requester has the right to lodge a free complaint with AKI or an administrative court. observed

#

Core GDPR controller/processor obligations are enforced and operative; only prospective Digital Omnibus amendments to ROPA and breach thresholds remain unresolved.

Primary frameworkGDPR Articles 24-25, 28, 30, 32-34, 35, 37-39; PDPA
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — GreenCore GDPR controller/processor obligations are enforced and operative; only prospective Digital Omnibus amendments to ROPA and breach thresholds remain unresolved.

Sub-modules (7)

Accountability & DPIAGreen

AKI's Art 35(4) DPIA list (per EDPB Opinion 6/2018) operationalises the accountability/DPIA regime for Estonian controllers.

Claims (2):

  • AKI's national list of processing operations requiring a DPIA under GDPR Art 35(4) was adopted following EDPB Opinion 6/2018.
  • Isikuandmete kaitse seadus (IKS), as amended — Legislative amendments now significantly simplify imposing GDPR-type fines directly on legal persons, applicable to infringements committed on or continuing from 1 November 2023.

DPO requirementsAmber

AKI participated in the EDPB's 2023 coordinated enforcement framework action assessing whether DPOs in ~19 public/private Estonian organisations meet Art 37-39 conditions and have adequate resources.

Claims (1):

  • AKI selected 19 public- and private-sector organisations (municipalities, ministries, banks, hospitals) to assess, via questionnaires and potential formal investigation, whether their DPOs meet GDPR Articles 37-39 conditions and have adequate resources, as part of the EDPB's 2023 Coordinated Enforcement Framework action.

Ropa requirementsAmber

The EU Digital Omnibus proposes raising the Art 30(5) ROPA-keeping exemption from under-250 to under-750 employees; the EDPB/EDPS support the simplification intent but seek clarification on the threshold and its exclusion of public bodies.

Claims (1):

  • The EU Digital Omnibus proposal would modify GDPR Art 30(5) to extend the ROPA-keeping derogation from organisations under 250 employees to those under 750 employees, unless the processing is likely to result in high risk; this is a pending proposal, not yet in force.

Joint controller arrangementsGreen

GDPR Art 26 joint-controller rules apply directly; no Estonia-specific guidance identified in this pass.

Security measuresAmber

AKI's e-pharmacy enforcement action required immediate technical remediation (access-control failures allowing third-party prescription viewing via personal identification codes).

Claims (2):

  • AKI issued a precept with a one-day compliance deadline and a 100,000 EUR penalty payment to three e-pharmacy chains for a security/access-control failure allowing viewing of another person's current prescriptions via personal identification codes without consent.
  • Allium UPI OÜ (Apotheka) — AKI found Allium UPI failed to implement multi-factor authentication, secure database backups, activity logging and adequate access controls affecting over 750,000 customers' data; a EUR 3,000,000 fine was imposed 5 September 2025 and is under appeal, with court hearings beginning 6 April 2026.

Breach notificationAmber

GDPR Art 33/34 breach-notification duties apply directly, with AKI operating an e-service breach-notification channel; the Digital Omnibus would raise the risk threshold triggering notification and extend the notification deadline, not yet adopted.

Claims (4):

  • The EDPB and EDPS support the Digital Omnibus proposal's increase of the risk threshold triggering mandatory breach notification to the competent DPA and the extension of the notification deadline, assessing this would meaningfully reduce administrative burden without affecting individuals' protection.
  • EDPB / Estonian Data Protection Inspectorate — An EDPB Art 60 final adopted decision, published October 2026, terminated a supervisory procedure concerning a phishing-attack-triggered breach affecting 2,258 customers; preliminary and final notifications were submitted under GDPR Art 33(1); the controller changed passwords, informed employees and contacted CERT-EE and police.
  • Andmekaitse Inspektsioon — 123 personal-data-breach notifications in Q3 2026 (July 25, August 47, September 51), under the standard GDPR Arts 33-34 notification duty.
  • AKI received 251 personal-data breach notifications in 2025 (up from 184 in 2024), the highest annual figure since May 2018, touching 3,030,325 people in total.

Retention and disposalAmber

AKI enforcement against a credit-information portal cited data-minimisation and retention-limitation shortcomings and required accuracy safeguards for republished non-payment data.

Claims (1):

  • AKI's self-initiated monitoring of a credit-information portal (taust.ee) identified privacy-policy shortcomings and directed the controller to address data-minimisation and retention principles and the accuracy of processed non-payment data.

Key findings (1)

  • Accountability/DPIA/DPO/security duties actively enforced; Digital Omnibus ROPA/breach-threshold reform pending; fold-in of Nov-2023 fining-power context. — source on file
Category narrative 71 words

GDPR Chapter IV duties (accountability, DPIA, DPO, ROPA, joint-controller arrangements, security, breach notification, retention) apply directly in Estonia. AKI has run coordinated EDPB campaigns on DPO effectiveness and cloud processing, and has enforced security/retention/minimisation duties against credit-information and social-media-adjacent controllers. The pending EU Digital Omnibus would raise the ROPA (Art 30(5)) SME/SMC exemption threshold to under-750 employees and raise the breach-notification risk threshold/extend the deadline — neither is yet in force.

Periodic update · new data 2026-10-11

Estonia's controller and processor duties landscape shows an escalating reported trajectory this cycle, anchored by three distinct but related developments. First, AKI received 251 personal-data breach notifications in 2025, up from 184 the prior year, a figure reported as the highest annual total since May 2018, touching a reported 3,030,325 people. This volume figure is carried at a qualified, probable confidence level: it is a reported statistic from a secondary legal-tracker source rather than a figure independently confirmed against AKI's own published annual statistics.

Second, the largest single breach-notification-adjacent enforcement matter remains open. AKI found that Allium UPI OÜ, operator of the Apotheka e-pharmacy service, had failed to implement multi-factor authentication, secure database backups, activity logging and adequate access controls, with the shortfall reported to affect data belonging to over 750,000 customers. A EUR 3,000,000 fine was imposed on 5 September 2025, and the matter is understood to be under appeal, with court hearings reported to have begun 6 April 2026. Because the underlying detail here rests on a lower-tier source, the specific security-control findings are rendered with qualified rather than assertive framing, even though the fine amount and appeal status appear more firmly reported.

Third, and most firmly sourced, the European Data Protection Board adopted a final decision under Article 60 of the GDPR, published in October 2026, terminating a supervisory cooperation procedure concerning an Estonian controller's phishing-attack-triggered breach affecting 2,258 customers. This primary EDPB document records that the controller submitted both preliminary and final breach notifications under GDPR Article 33(1), and took remedial steps including changing passwords, informing employees, and contacting CERT-EE and the police. Of the three developments, this is the one resting on a Tier 1 primary source, and it illustrates a comparatively well-handled breach-response sequence against which the Apotheka matter's reported control failures stand in some contrast.

Taken together, these three threads describe a controller/processor environment under increasing notification pressure, with AKI handling both a record volume of smaller notifications and continuing to process the appeal of its largest reported fine, while the EDPB's own published decision shows the cooperation mechanism functioning for at least one Estonian breach matter reaching a formal conclusion.

Outlook

The Apotheka appeal's court hearings, reported to have begun 6 April 2026, are the clearest forward marker in this module: their outcome will determine whether the reported EUR 3,000,000 figure, and the specific security-control findings underlying it, are upheld, reduced, or otherwise revised. Separately, whether the reported rise in breach notifications to 251 in 2025 continues, plateaus, or reflects a one-off reporting-discipline effect is not resolved by the material available, and would be a natural point to revisit as AKI's next annual statistics become available.

1 earlier distinct update
Periodic update · new data 2026-09-28

Estonia's controller and processor accountability framework tightened materially this cycle through a legislative amendment to the Isikuandmete kaitse seadus (IKS) that significantly simplified the process for imposing GDPR-type fines directly on legal persons. The amendment applies to infringements committed on or continuing from 1 November 2023, and its practical significance became concrete in this cycle's largest-ever Estonian GDPR fine (covered in the Enforcement & Redress sub-brief below), which the simplification directly enabled. Prior to this amendment, imposing GDPR-scale sanctions on a legal person in Estonia carried procedural friction that the 2023 change removed.

This is a duties-side development in the sense that it does not create a new substantive obligation for controllers or processors, but it materially changes the practical consequence of failing to meet existing accountability and DPIA-adjacent obligations: a legal person that falls short of its accountability duties now faces a more straightforward path to a large fine than it did before 1 November 2023. Controllers and processors operating in Estonia should treat this as a signal that the cost of non-compliance with existing duties has risen, even though the duties themselves are unchanged in substance.

No other controller/processor-duties development was surfaced this cycle beyond this fining-mechanism simplification; the accountability and DPIA substance of Estonian law otherwise tracks the GDPR baseline.

Outlook

The practical weight of this 2023 amendment will continue to be tested through the ongoing Allium UPI appeal (hearings beginning 6 April 2026); a court ruling upholding the fine would confirm the amendment has produced a durable and legally robust escalation in accountability enforcement.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (11)
  1. Confirmed EDPB — AKI's national list of processing operations requiring a DPIA under GDPR Art 35(4) was adopted following EDPB Opinion 6/2018. observed
  2. Confirmed EDPB / AKI — AKI selected 19 public- and private-sector organisations (municipalities, ministries, banks, hospitals) to assess, via questionnaires and potential formal investigation, whether their DPOs meet GDPR Articles 37-39 conditions and have adequate resources, as part of the EDPB's 2023 Coordinated Enforcement Framework action. observed
  3. Probable EDPB — The EU Digital Omnibus proposal would modify GDPR Art 30(5) to extend the ROPA-keeping derogation from organisations under 250 employees to those under 750 employees, unless the processing is likely to result in high risk; this is a pending proposal, not yet in force. observed
  4. Confirmed EDPB / AKI — AKI issued a precept with a one-day compliance deadline and a 100,000 EUR penalty payment to three e-pharmacy chains for a security/access-control failure allowing viewing of another person's current prescriptions via personal identification codes without consent. observed
  5. Probable EDPB — The EDPB and EDPS support the Digital Omnibus proposal's increase of the risk threshold triggering mandatory breach notification to the competent DPA and the extension of the notification deadline, assessing this would meaningfully reduce administrative burden without affecting individuals' protection. observed
  6. Confirmed EDPB / AKI — AKI's self-initiated monitoring of a credit-information portal (taust.ee) identified privacy-policy shortcomings and directed the controller to address data-minimisation and retention principles and the accuracy of processed non-payment data. observed
  7. Probable EDPB / Estonian Data Protection Inspectorate — EDPB / Estonian Data Protection Inspectorate — An EDPB Art 60 final adopted decision, published October 2026, terminated a supervisory procedure concerning a phishing-attack-triggered breach affecting 2,258 customers; preliminary and final notifications were submitted under GDPR Art 33(1); the controller changed passwords, informed employees and contacted CERT-EE and police. observed
  8. Probable DLA Piper — Isikuandmete kaitse seadus (IKS), as amended — Legislative amendments now significantly simplify imposing GDPR-type fines directly on legal persons, applicable to infringements committed on or continuing from 1 November 2023. observed
  9. Confirmed Andmekaitse Inspektsioon — Andmekaitse Inspektsioon — 123 personal-data-breach notifications in Q3 2026 (July 25, August 47, September 51), under the standard GDPR Arts 33-34 notification duty. observed
  10. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/estonia-data-privacy-laws/ — AKI received 251 personal-data breach notifications in 2025 (up from 184 in 2024), the highest annual figure since May 2018, touching 3,030,325 people in total.
  11. Probable https://klarproof.com/regulators/estonia/aki/ — Allium UPI OÜ (Apotheka) — AKI found Allium UPI failed to implement multi-factor authentication, secure database backups, activity logging and adequate access controls affecting over 750,000 customers' data; a EUR 3,000,000 fine was imposed 5 September 2025 and is under appeal, with court hearings beginning 6 April 2026.

#

Transfer mechanisms are the standard EU GDPR toolkit with no identified Estonian derogation; localisation-specific findings are absent and flagged rather than assumed.

Primary frameworkGDPR Articles 44-49; EU Commission adequacy decisions
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — GreenTransfer mechanisms are the standard EU GDPR toolkit with no identified Estonian derogation; localisation-specific findings are absent and flagged rather than assumed.

Sub-modules (6)

Transfer mechanismsGreen

GDPR provides adequacy decisions, SCCs, BCRs, codes of conduct/certification, and derogations as international-transfer tools, applied directly in Estonia as EU law.

Claims (2):

  • The GDPR offers a range of tools for transferring data outside the EU, including European Commission adequacy decisions, pre-approved standard contractual clauses, binding corporate rules, codes of conduct, and certification.
  • Estonia's cross-border transfers rely on GDPR Chapter V mechanisms with no identified EE-specific derogation.

Adequacy receivedAmber

Adequacy 'received' by Estonia is not a distinct national concept; Estonia benefits from whatever adequacy the EU Commission grants to third countries as an EU Member State.

Adequacy grantedGreen

The EU Commission's renewed adequacy decision for the UK (covering both GDPR and the Law Enforcement Directive) applies directly to Estonia as an EEA state, permitting free transfer of personal data from Estonia to the UK.

Claims (1):

  • The European Commission's renewed EU-GDPR adequacy decision for the UK applies to transfers from all EEA countries, including Estonia, and lasts until 27 December 2031.

SCCs and BCRsGreen

SCCs and BCRs are available under GDPR Art 46; the EDPB register shows ongoing Art 64 BCR opinions across the EU affecting Estonian-relevant multinational controllers.

Transfer impact assessmentAmber

Post-Schrems II, EDPB Recommendations on supplementary measures for international transfers apply directly to Estonian exporters using SCCs/BCRs to non-adequate third countries.

Claims (1):

  • Following the CJEU's Schrems II ruling invalidating the EU-U.S. Privacy Shield, the EDPB issued FAQs and Recommendations setting out a six-step process for supplementary measures, applicable to Estonian data exporters using SCCs to non-adequate third countries.

Data localisationRed

No Estonia-specific data-localisation mandate (partial or absolute) for personal data was identified in this research pass; absent_field_provenance recorded below.

Key findings (1)

  • Standard EU transfer toolkit; UK adequacy confirmed to 2031; no localisation mandate found. — source on file
Category narrative 71 words

As an EU/EEA Member State, Estonia relies on the GDPR's Chapter V transfer toolkit (adequacy decisions, SCCs, BCRs, derogations) applied uniformly; adequacy decisions are adopted at EU Commission level and bind Estonia directly rather than through separate national determinations. Estonia benefits from the UK's EU-GDPR adequacy decision (renewed, valid until 27 December 2031), permitting free transfers from Estonia to the UK. No Estonia-specific data-localisation mandate was identified in this research pass.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (4)
  1. Confirmed EUR-Lex — The GDPR offers a range of tools for transferring data outside the EU, including European Commission adequacy decisions, pre-approved standard contractual clauses, binding corporate rules, codes of conduct, and certification. observed
  2. Confirmed ICO — The European Commission's renewed EU-GDPR adequacy decision for the UK applies to transfers from all EEA countries, including Estonia, and lasts until 27 December 2031. observed
  3. Confirmed EDPB — Following the CJEU's Schrems II ruling invalidating the EU-U.S. Privacy Shield, the EDPB issued FAQs and Recommendations setting out a six-step process for supplementary measures, applicable to Estonian data exporters using SCCs to non-adequate third countries. observed
  4. Uncertain Complico Consulting — Estonia's cross-border transfers rely on GDPR Chapter V mechanisms with no identified EE-specific derogation. observed

#

Sectoral overlays exist mainly through case law/enforcement rather than distinct statutes; a live CJEU reference on AML/GDPR interplay introduces near-term legal uncertainty for the financial sector overlay.

Primary frameworkGDPR; ePrivacy Directive 2002/58/EC; Estonian AML framework (Rahapesu Andmebüroo)
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — AmberSectoral overlays exist mainly through case law/enforcement rather than distinct statutes; a live CJEU reference on AML/GDPR interplay introduces near-term legal uncertainty for the financial sector overlay.

Sub-modules (7)

Financial sector overlayAmber

A pending CJEU preliminary reference (Case C-222/25), lodged 21 March 2025 by Estonia's Riigikohus (Supreme Court), concerns an individual's dispute with the Estonian Financial Intelligence Unit (Rahapesu Andmebüroo), with AKI as an involved party, raising GDPR/AML data-processing interface questions.

Claims (2):

  • Estonia's Supreme Court (Riigikohus) lodged a preliminary reference (Case C-222/25) with the CJEU on 21 March 2025 concerning a dispute between an individual and the Estonian Financial Intelligence Unit (Rahapesu Andmebüroo), with the Estonian DPA (Andmekaitse Inspektsioon) named as an involved party.
  • 936 SE (Estonia) — Gives credit institutions and payment/e-money institutions the right to exchange fraud-suspicion data (including personal data) with each other, PPA and CERT-EE; extends a parallel exchange right to credit providers/intermediaries for loan fraud.

Health sector overlayAmber

Estonia's e-pharmacy/e-health infrastructure has been the subject of direct AKI enforcement for unlawful third-party access to prescription data via personal identification codes.

Claims (1):

  • AKI initiated an own-initiative procedure under clause 56(3)(8) of the PDPA against three e-pharmacy chains for unlawfully displaying another person's valid prescriptions based on personal identification codes.

Telecoms and eprivacyAmber

ePrivacy Directive Art 5(3) cookie/tracker consent rules apply directly in Estonia; the pending Digital Omnibus proposes targeted amendments to the ePrivacy Directive alongside the GDPR.

Claims (1):

  • The EU Digital Omnibus proposal, formally consulted with the EDPB/EDPS from 25 November 2025, includes targeted amendments concerning the GDPR, the EUDPR, and the ePrivacy Directive.

Employment dataRed

No Estonia-specific employment-data statute distinct from GDPR was identified in this pass.

Credit and scoringAmber

AKI has repeatedly enforced against non-payment/credit-information republication by private controllers (Facebook debt-shaming groups; Krediidiregister OÜ; taust.ee portal), citing legitimate-interest failures and PDPA §10 restrictions.

Claims (2):

  • AKI found that a private individual's Facebook groups disclosing other people's debt data to 4,600-14,800 unidentified members lacked a legitimate-interest or journalistic-purpose basis and issued a precept with a 5,000 EUR penalty payment.
  • AKI issued a precept with a 10,000 EUR penalty payment per unfulfilled point against Krediidiregister OÜ over legal-basis and privacy-policy shortcomings in disclosing non-payment data of legal representatives.

educationRed

No Estonia-specific education-sector DP overlay was identified in this research pass.

insuranceRed

No Estonia-specific insurance-sector DP overlay was identified in this research pass.

Key findings (1)

  • Financial-sector CJEU reference pending; health/credit sector overlays enforced via case law. — source on file
Category narrative 79 words

Estonia has no distinct sectoral DP statutes displacing GDPR, but sectoral overlays are visible in practice: the Estonian Financial Intelligence Unit's (Rahapesu Andmebüroo) AML data processing is the subject of a pending CJEU preliminary reference from the Estonian Supreme Court on the GDPR/Law Enforcement Directive interface; Estonia's e-health/e-pharmacy ecosystem has triggered security enforcement; and credit-scoring/non-payment data portals have been subject to repeated AKI enforcement. Telecoms/ePrivacy rules (Directive 2002/58/EC) apply directly and are subject to the pending Digital Omnibus amendments.

Periodic update · new data 2026-10-25

Estonia's financial fraud prevention and combating law, 936 SE, passed by the Riigikogu on or about 21 October 2026, is understood to create a personal-data-sharing gateway specific to the financial sector. Credit institutions and payment and e-money institutions gain the right to exchange fraud-suspicion data with each other, with the Police and Border Guard Board, and with CERT-EE, Estonia's computer emergency response team. Credit providers and credit intermediaries are understood to receive a parallel right confined to loan fraud. Much of the data exchanged under this gateway, suspicion flags tied to named individuals and transaction patterns, will constitute personal data in the ordinary sense, which places the new mechanism squarely within the scope of data-protection law even though the Act's primary framing is financial-crime prevention rather than privacy regulation.

The Act appears to have been adopted by the Riigikogu but has not yet been published in the Riigi Teataja, so it is not yet in effect. This matters for sectoral oversight because the precise GDPR legal basis the Act itself invokes for the new sharing, whether that is legitimate interest, a legal obligation, or some other Article 6 ground, has not been confirmed from the Act's own text. Until that provision is identified, it is not possible to assess with confidence how the sectoral gateway interacts with the general lawful-processing requirements that would otherwise apply to this kind of inter-institutional data exchange, including questions of proportionality, retention, and the rights of the individuals whose suspicion-linked data is shared.

This is a genuinely new development for the Estonian financial sector: it did not previously have a comparable statutory channel for sharing fraud-suspicion personal data across institutions and with law enforcement and the computer emergency response team in this coordinated form.

Outlook

The items to track are, first, confirmation of the GDPR legal basis the Act relies on for its data-sharing provisions, and second, publication of 936 SE in the Riigi Teataja, which will fix the date the gateway becomes operative; that publication was expected toward the end of 2026 as at the close of this cycle. Once the legal basis is confirmed, it will become possible to assess whether the sectoral gateway sits comfortably within ordinary lawful-processing principles or whether it represents a distinct carve-out requiring its own safeguards.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (6)
  1. Confirmed EUR-Lex / Official Journal — Estonia's Supreme Court (Riigikohus) lodged a preliminary reference (Case C-222/25) with the CJEU on 21 March 2025 concerning a dispute between an individual and the Estonian Financial Intelligence Unit (Rahapesu Andmebüroo), with the Estonian DPA (Andmekaitse Inspektsioon) named as an involved party. observed
  2. Confirmed EDPB / AKI — AKI initiated an own-initiative procedure under clause 56(3)(8) of the PDPA against three e-pharmacy chains for unlawfully displaying another person's valid prescriptions based on personal identification codes. observed
  3. Probable EDPB — The EU Digital Omnibus proposal, formally consulted with the EDPB/EDPS from 25 November 2025, includes targeted amendments concerning the GDPR, the EUDPR, and the ePrivacy Directive. observed
  4. Confirmed EDPB / AKI — AKI found that a private individual's Facebook groups disclosing other people's debt data to 4,600-14,800 unidentified members lacked a legitimate-interest or journalistic-purpose basis and issued a precept with a 5,000 EUR penalty payment. observed
  5. Confirmed EDPB / AKI — AKI issued a precept with a 10,000 EUR penalty payment per unfulfilled point against Krediidiregister OÜ over legal-basis and privacy-policy shortcomings in disclosing non-payment data of legal representatives. observed
  6. Probable Riigikogu — 936 SE (Estonia) — Gives credit institutions and payment/e-money institutions the right to exchange fraud-suspicion data (including personal data) with each other, PPA and CERT-EE; extends a parallel exchange right to credit providers/intermediaries for loan fraud. observed

#

Cookie/ePrivacy rules are GDPR/ePrivacy-aligned and in force; several US-style adtech constructs (dark patterns codified separately, GPC, clean rooms) have no confirmed Estonian equivalent, driving amber/red sub-module ratings and explicit gaps.

Primary frameworkePrivacy Directive 2002/58/EC; GDPR
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — AmberCookie/ePrivacy rules are GDPR/ePrivacy-aligned and in force; several US-style adtech constructs (dark patterns codified separately, GPC, clean rooms) have no confirmed Estonian equivalent, driving amber/red sub-module ratings and explicit gaps.

Sub-modules (6)

Cookies and trackersGreen

ePrivacy Directive Art 5(1)/5(3) require prior user consent for storing or accessing information on terminal equipment, as clarified by EDPB Guidelines 2/2023 on technical scope, applicable directly in Estonia.

Claims (2):

  • Article 5(3) of the ePrivacy Directive requires users' prior consent for storing information, or gaining access to information already stored, in their terminal equipment, as clarified by EDPB Guidelines 2/2023 on the technical scope of Art 5(3), applicable directly in Estonia as an EU Member State.
  • Analytics cookies are classified as non-essential under both the GDPR and Estonia's Electronic Communications Act, requiring prior opt-in consent.

Dark patternsRed

No Estonia-specific dark-pattern prohibition distinct from general GDPR fairness/transparency principles was identified in this research pass.

Claims (1):

  • 796 SE (Estonia) — Transposes Directive (EU) 2023/2673, prohibiting manipulative online-interface design in distance financial-services contracts and requiring a right to redirect to a human adviser from a chatbot.

Opt out signalsRed

No Estonian or EU-level Global Privacy Control/DAA-equivalent opt-out signal regime was identified; this construct is largely US state-law specific.

Clean rooms and dcrRed

No Estonia-specific clean-room/data-collaboration-room rules were identified in this research pass.

Cross context advertisingRed

The CPRA 'sale'/'share' cross-context-advertising construct has no direct Estonian/EU equivalent; GDPR's general consent/legitimate-interest framework governs equivalent processing instead.

Direct marketingGreen

Direct marketing in Estonia is governed by GDPR consent/legitimate-interest and ePrivacy Directive rules on unsolicited communications; no Estonia-specific derogation identified.

Key findings (1)

  • Cookie/ePrivacy consent confirmed in force; several CPRA-style constructs structurally absent. — source on file
Category narrative 60 words

Cookie/tracker consent in Estonia follows the ePrivacy Directive's Art 5(3) prior-consent rule as elaborated by EDPB Guidelines 2/2023, applied directly as EU law; CPRA-style constructs (opt-out signals, clean rooms, 'sale'/'share' cross-context advertising) are not native to the EU/Estonian framework and no local equivalent was identified. Direct marketing runs on GDPR consent/legitimate-interest bases with no Estonia-specific derogation found in this pass.

Periodic update · new data 2026-10-25

A bill, 796 SE, is understood to be moving through the Riigikogu to transpose the EU's distance-marketing-of-financial-services directive into Estonian law. As described, the bill would prohibit manipulative online-interface design, the pattern commonly referred to as dark patterns, in distance contracts for financial services, and would introduce a right for a consumer to request redirection to a human adviser rather than being confined to an automated channel such as a chatbot. This is squarely a commercial-privacy and consumer-facing-design measure: it reaches into how financial-services firms structure their digital sales interfaces and automated customer-contact flows when selling or servicing products at a distance, which is precisely the kind of interface-design question that commercial-privacy oversight is concerned with.

The current reading stage the bill has reached in the Riigikogu, and its expected date of adoption or commencement, have not been confirmed from a primary dated source as at the close of this cycle. The transposition obligation derives from an EU directive, so the substantive content of the dark-pattern prohibition and the human-contact right is set at EU level even though the precise Estonian implementing timetable remains open.

This is a proposed rather than an enacted measure. No enforcement or supervisory activity specific to this bill has been identified, and none should be inferred from its progress through the legislature.

Outlook

The item to track is 796 SE's progress to a confirmed Riigikogu reading stage and adoption date, which will determine when the dark-pattern prohibitions and the human-contact right become binding obligations for firms marketing financial services at a distance to Estonian consumers. Firms using automated or chatbot-based customer interfaces for financial-services marketing in Estonia should treat this as a measure in development rather than a current requirement, pending that confirmation.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (3)
  1. Confirmed EDPB — Article 5(3) of the ePrivacy Directive requires users' prior consent for storing information, or gaining access to information already stored, in their terminal equipment, as clarified by EDPB Guidelines 2/2023 on the technical scope of Art 5(3), applicable directly in Estonia as an EU Member State. observed
  2. Probable Kukie.io — Analytics cookies are classified as non-essential under both the GDPR and Estonia's Electronic Communications Act, requiring prior opt-in consent. observed
  3. Probable Ecovis — 796 SE (Estonia) — Transposes Directive (EU) 2023/2673, prohibiting manipulative online-interface design in distance financial-services contracts and requiring a right to redirect to a human adviser from a chatbot. observed

#

Baseline Art 22/ADM and surveillance carve-out rules are settled GDPR/LED law, but the AI Act's implementation timeline and scope are actively being renegotiated via the pending Digital Omnibus on AI.

Primary frameworkGDPR Article 22; EU AI Act (Regulation (EU) 2024/1689); Law Enforcement Directive (EU) 2016/680
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — AmberBaseline Art 22/ADM and surveillance carve-out rules are settled GDPR/LED law, but the AI Act's implementation timeline and scope are actively being renegotiated via the pending Digital Omnibus on AI.

Sub-modules (6)

Profiling restrictionsAmber

AKI's 2022 rider-rating case exercised GDPR Art 22-adjacent scrutiny over automated/algorithmic driver-rating processing lacking a valid legal basis.

Claims (1):

  • AKI issued a formal injunction on 17 February 2022 requiring a ride-hailing data controller to suspend processing of rider-rating data until compliance measures were implemented and to delete related personal data.

Automated decision making transparencyAmber

AKI required the ride-hailing controller to demonstrate GDPR Art 5(1)(a)/12-14 transparency compliance regarding how rider-rating data is collected, used, and shared before resuming processing.

Claims (2):

  • AKI criticised the ride-hailing controller's compliance with the fairness/transparency principle (GDPR Art 5(1)(a)) and Articles 12-14, finding the obligation to inform data subjects about how their rating data was collected, used, stored and shared had not been met.
  • AKI provides highly specific operational directives regarding automated decision-making and processing of employees' email inboxes.

AI risk assessmentsAmber

The EDPB/EDPS adopted a January 2026 Joint Opinion on the Digital Omnibus on AI, addressing proposed simplifications to AI Act implementation, including extended compliance timelines (capped at December 2027) for high-risk AI obligations originally due August 2026.

Claims (5):

  • Under the pending AI Act simplification package, entry into application of high-risk AI processing obligations (originally due August 2026) faces an extension capped at December 2027, pending confirmation of implementation standards and support tools.
  • Tarbijakaitse ja Tehnilise Järelevalve Amet (TTJA) — Estonia notified TTJA to the European Commission as its intended EU AI Act market-surveillance authority, but as of the Commission's 7 September 2026 list the designation was still pending final adoption.
  • TTJA (Tarbijakaitse ja Tehnilise Järelevalve Amet) — Estonia's AI Act market-surveillance authority designation remains pending final adoption per the Commission's list last updated 7 September 2026
  • Estonian Ministry of Justice and Digital Affairs — Published guidance on AI Act Art 50 transparency obligations for AI-generated content/deepfakes around 5 August 2026, citing fines up to EUR 15 million or 3% of global turnover, without naming a supervisory authority
  • Estonia's AI Act supervisory-authority allocation between TTJA and AKI remained pending as of mid-2026.

Biometric regimeRed

No Estonia-specific biometric-data statute beyond GDPR Art 9 special-category rules was identified in this research pass.

Genetic dataRed

No Estonia-specific genetic-data statute beyond GDPR Art 9 special-category rules was identified in this research pass; note Estonia operates a national Genome/Biobank framework which may carry sector-specific rules not captured in this pass.

State surveillance carveoutsAmber

The EDPB has clarified that DPA competence over spyware/surveillance-technology use by private entities falls under GDPR, competent-authority criminal-justice processing falls under the Law Enforcement Directive, and national-security processing falls outside EU law scope.

Claims (1):

  • The EDPB has stated that investigation and enforcement of data-protection rules regarding alleged private-entity spyware use falls under GDPR competence, while processing by competent authorities for criminal-law purposes falls under the Law Enforcement Directive, and national-security processing falls outside the scope of EU law.

Key findings (1)

  • Art 22-adjacent enforcement precedent set (rider-rating case); AI Act timeline extension pending via Digital Omnibus. — source on file
Category narrative 92 words

Estonia applies GDPR Art 22 profiling/ADM rules directly, illustrated by AKI's 2022 injunction against a ride-hailing controller's rider-rating processing pending compliance measures. The EU AI Act's interface with GDPR is under active revision via the parallel 'Digital Omnibus on AI', which the EDPB/EDPS opined on in January 2026, including proposed extended timelines for high-risk AI obligations. Law-enforcement/national-security carve-outs are addressed through the EDPB's 2026 spyware letter clarifying that DPA competence for private-entity processing sits under GDPR while competent-authority processing sits under the Law Enforcement Directive, with national-security processing outside EU law scope.

Periodic update · new data 2026-10-18

Estonia's institutional architecture for AI Act enforcement remains unsettled on its most consequential point: the designation of a market-surveillance authority. The European Commission's own list of designated national market-surveillance authorities, last updated 7 September 2026, shows Estonia's designation of the Tarbijakaitse ja Tehnilise Järelevalve Amet (TTJA) as still pending final adoption. The TTJA is Estonia's consumer-protection and technical-regulatory authority, and its proposed role under the AI Act would be to supervise compliance with the Act's market-surveillance obligations within Estonia, but that role has not yet been finally confirmed as of the date stated.

This designation gap sits alongside a separate, earlier development: Estonia's Ministry of Justice and Digital Affairs published guidance, reportedly around 5 August 2026, addressing the AI Act's Article 50 transparency obligations, which cover disclosure requirements for AI-generated content and deepfakes. That guidance cites the EU-level penalty structure of fines up to EUR 15 million or 3% of global annual turnover for non-compliance, but notably does not name any Estonian supervisory authority as responsible for enforcing those obligations. Read together, the two facts describe an enforcement architecture that is substantively specified -- the obligations exist, and the penalty ceiling is known -- but institutionally incomplete, since the body that would exercise enforcement authority under that penalty structure has not been finally designated.

This is best understood as a structural governance gap rather than a transient administrative delay, because it affects the practical operability of the entire AI Act enforcement chain in Estonia, not merely one sub-element of it. Any AI system provider or deployer operating in Estonia under the AI Act's scope currently faces obligations whose substance is known but whose enforcement mechanism is not yet institutionally settled. No contrary indication -- such as an interim or provisional enforcement arrangement -- was identified in the sources reviewed this cycle.

No biometric-specific or surveillance-specific development distinct from this general AI Act institutional question was identified for Estonia this cycle. The governance gap described here concerns the AI Act's market-surveillance designation generally, and the evidence available does not support narrowing the finding to any particular biometric or surveillance sub-application.

Outlook

The TTJA's final designation as Estonia's AI Act market-surveillance authority is the governance checkpoint to watch going forward; its confirmation would resolve the institutional half of the current gap, though the practical enforcement record (case volume, approach to the Article 50 transparency obligations already described in ministry guidance) would remain to be established separately once that designation is confirmed. Until the designation is finalised, Estonia's AI Act enforcement capacity cannot be assessed on the evidence available.

1 earlier distinct update
Periodic update · new data 2026-10-11

The governance signal in this module concerns the institutional architecture for EU AI Act supervision in Estonia, rather than any specific algorithmic or biometric enforcement matter. Estonia has notified the Tarbijakaitse ja Tehnilise Järelevalve Amet, the Consumer Protection and Technical Regulatory Authority known as TTJA, to the European Commission as its intended market-surveillance authority under the EU AI Act. As of the Commission's own published list, dated 7 September 2026, reports suggest that this designation had not yet been finally adopted. This is an uncertain-tier finding: the reported gap concerns the formal completion of a designation process, not any substantive doubt about Estonia's stated intention to designate TTJA.

The practical significance of a still-pending designation is institutional rather than substantive. Until the designation is finally adopted, questions about which Estonian body holds operational front-line market-surveillance responsibility for AI systems under the Act — including inspection powers, complaint-handling processes, and coordination with AKI on any data-protection-adjacent AI matters — remain without a fully settled institutional answer. This sits at the edge of this monitor's own remit: the designation itself, and its downstream operational detail, properly belongs to the sectoral AI-regulation tracking function, and is noted here only insofar as it defines the institutional landscape against which any future Estonian AI-system data-protection matter would be supervised.

No biometric-specific or algorithmic-profiling enforcement development for Estonia was located this cycle beyond this institutional designation question. The module's signal this cycle is therefore narrow: an institutional-architecture item in formation, not yet settled, with no accompanying substantive enforcement or rule-making development to report alongside it.

Outlook

The designation of TTJA as Estonia's AI Act market-surveillance authority is the item to watch for formal completion in a subsequent reporting period; once adopted, the practical allocation of supervisory responsibility — and any interaction with AKI's own GDPR-based oversight of AI systems that process personal data — would become clearer. Until then, the institutional picture in Estonia for AI-system market surveillance remains pending as scheduled.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (9)
  1. Confirmed AKI / EDPB — AKI issued a formal injunction on 17 February 2022 requiring a ride-hailing data controller to suspend processing of rider-rating data until compliance measures were implemented and to delete related personal data. observed
  2. Confirmed AKI / EDPB — AKI criticised the ride-hailing controller's compliance with the fairness/transparency principle (GDPR Art 5(1)(a)) and Articles 12-14, finding the obligation to inform data subjects about how their rating data was collected, used, stored and shared had not been met. observed
  3. Probable IAPP — Under the pending AI Act simplification package, entry into application of high-risk AI processing obligations (originally due August 2026) faces an extension capped at December 2027, pending confirmation of implementation standards and support tools. observed
  4. Confirmed EDPB — The EDPB has stated that investigation and enforcement of data-protection rules regarding alleged private-entity spyware use falls under GDPR competence, while processing by competent authorities for criminal-law purposes falls under the Law Enforcement Directive, and national-security processing falls outside the scope of EU law. observed
  5. Probable Complico Consulting — AKI provides highly specific operational directives regarding automated decision-making and processing of employees' email inboxes. observed
  6. Uncertain https://www.recordinglaw.com/world-laws/world-data-privacy-laws/estonia-data-privacy-laws/ — Tarbijakaitse ja Tehnilise Järelevalve Amet (TTJA) — Estonia notified TTJA to the European Commission as its intended EU AI Act market-surveillance authority, but as of the Commission's 7 September 2026 list the designation was still pending final adoption.
  7. Probable Primary statutory record — TTJA (Tarbijakaitse ja Tehnilise Järelevalve Amet) — Estonia's AI Act market-surveillance authority designation remains pending final adoption per the Commission's list last updated 7 September 2026
  8. Probable Praxikon — Estonian Ministry of Justice and Digital Affairs — Published guidance on AI Act Art 50 transparency obligations for AI-generated content/deepfakes around 5 August 2026, citing fines up to EUR 15 million or 3% of global turnover, without naming a supervisory authority observed
  9. Uncertain noyb — Estonia's AI Act supervisory-authority allocation between TTJA and AKI remained pending as of mid-2026. observed

#

EU baseline (Art 8 GDPR) is confirmed, but the Estonia-specific national age-of-consent figure and minor/vulnerable-group specifics could not be confirmed from available sources in this pass; escalation recommended.

Primary frameworkGDPR Article 8; PDPA (specific national age threshold unconfirmed in this pass)
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — AmberEU baseline (Art 8 GDPR) is confirmed, but the Estonia-specific national age-of-consent figure and minor/vulnerable-group specifics could not be confirmed from available sources in this pass; escalation recommended.

Sub-modules (5)

Age verificationAmber

GDPR Art 8(1) sets a default age of 16 for a child's own consent to information-society services, with Member States permitted to lower this to not below 13; Estonia's specific chosen threshold was not confirmed in this research pass.

Claims (1):

  • Under GDPR Article 8(1), processing of a child's personal data in relation to information-society services is lawful where the child is at least 16 years old, but Member States may set a lower age by law provided it is not below 13.

Minor profiling bansRed

No Estonia-specific minor-profiling ban beyond general GDPR Art 22/Recital 71 principles was identified in this research pass.

Education settingsRed

No Estonia-specific education-sector children's-data rule was identified in this research pass.

Dependent adultsRed

No Estonia-specific dependent-adults/vulnerable-adults data-protection regime beyond general GDPR principles was identified in this research pass.

Key findings (1)

  • EU Art 8 baseline confirmed; Estonia's specific national age threshold unconfirmed - flagged gap. — source on file
Category narrative 82 words

GDPR Art 8 sets an EU baseline: information-society-service consent is valid from age 16, but Member States may lower this to no less than 13. This research pass did not locate a primary-source confirmation of the specific age Estonia has set by law under Art 8(1) PDPA; this is flagged as an open question requiring escalation to the Estonian Riigi Teataja (State Gazette) text of the PDPA. No Estonia-specific minor-profiling ban, education-settings rule, or dependent-adults regime beyond general GDPR principles was identified.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (2)
  1. Confirmed EUR-Lex — Under GDPR Article 8(1), processing of a child's personal data in relation to information-society services is lawful where the child is at least 16 years old, but Member States may set a lower age by law provided it is not below 13. observed
  2. Confirmed EUR-Lex — Where a child is below the applicable age threshold under Article 8(1) GDPR, processing is lawful only if consent is given or authorised by the holder of parental responsibility, and the controller must make reasonable efforts to verify this taking into account available technology. observed

#

AKI has active, EDPB-integrated enforcement powers and a functioning complaint/court escalation path, but its fine mechanism structurally departs from the direct-administrative-fine model used elsewhere in the EU (GDPR Recital 151 carve-out), and the surrounding EU legislative framework (Digital Omnibus) is in active flux.

Primary frameworkGDPR Articles 58, 77-84, Recital 151; PDPA; Substitutive Enforcement and Penalty Payment Act (sunniraha)
Supervisory authorityAndmekaitse Inspektsioon (AKI)
Traffic-light rationale — AmberAKI has active, EDPB-integrated enforcement powers and a functioning complaint/court escalation path, but its fine mechanism structurally departs from the direct-administrative-fine model used elsewhere in the EU (GDPR Recital 151 carve-out), and the surrounding EU legislative framework (Digital Omnibus) is in active flux.

Sub-modules (6)

Regulator powers and penaltiesAmber

Per GDPR Recital 151, administrative fines are not directly applicable in Estonia; AKI instead issues precepts/injunctions carrying penalty payments and may close proceedings with a reprimand where a controller cooperates and voluntarily remedies non-severe, non-intentional issues.

Claims (4):

  • In Estonia, administrative fines are not directly applicable according to GDPR Recital 151; when a controller demonstrates compliance with AKI's guidance and takes corrective action, AKI may close proceedings with a reprimand rather than an administrative fine.
  • IKS Sections 66-70 punish distinct categories of GDPR violation with fines up to EUR 20,000,000, or for legal persons up to EUR 20,000,000 or 4% of worldwide annual turnover, whichever is greater, classified as an Estonian misdemeanour.
  • AKI can impose fines of up to EUR 20 million or 4% of global annual turnover for GDPR violations, following a 2023 Penal Code amendment that raised the ceiling from a prior EUR 400,000 cap.
  • GDPR Article 83(5)/(6) sets Estonia's maximum administrative-fine ceiling at the higher of EUR 20,000,000 or 4% of global turnover.

Enforcement activity indexAmber

Documented AKI enforcement in recent years spans a 100,000 EUR e-pharmacy penalty payment (2020), a 5,000 EUR Facebook debt-group penalty payment (2023), a 10,000-EUR-per-point Krediidiregister penalty payment (2023), and a 2022 rider-rating injunction, alongside a 2025 published decision applying the reprimand-in-lieu-of-fine approach.

Claims (8):

  • AKI issued a precept with a 100,000 EUR penalty payment and a one-day compliance deadline to three pharmacy chains in a 2020 e-pharmacy prescription-access case.
  • AKI issued a precept with a 5,000 EUR penalty payment against a Facebook-group administrator for unlawfully disclosing individuals' debt data to thousands of unidentified group members.
  • AKI imposed a EUR 3,000,000 fine on Allium UPI OU on 5 September 2025 over the Apotheka loyalty-programme data breach affecting more than 750,000 people; the fine is under appeal, with court hearings beginning 6 April 2026.
  • AKI opened 46 own-initiative supervisory proceedings in 2025 (30% prompted by a data leak) and handled 50 court cases during the year.
  • Allium UPI OÜ — AKI's record EUR 3,000,000 fine (imposed 5 September 2025) upheld by Harju County Court on 2 September 2026
  • AKI's EUR 3,000,000 fine against Allium UPI OÜ (September 2025, Apotheka loyalty-programme breach) remains under appeal; court proceedings began 6 April 2026 with no resolution identified this cycle.
  • AKI's EUR 3,000,000 fine against Allium UPI OÜ, Estonia's largest GDPR fine to date, remains under court appeal, with hearings that began 6 April 2026.
  • AKI's EUR 3,000,000 fine against Allium UPI OU was upheld by Harju County Court on 2 September 2026.

Regulator funding and capacityRed

No specific AKI budget/headcount data was identified in this research pass; flagged as an open question.

Collective redress and class actionsRed

GDPR Art 80 representative-action rights apply directly across the EU including Estonia; no Estonia-specific collective-redress mechanism beyond the general civil-procedure framework was identified in this research pass.

Private right of actionGreen

Data subjects may lodge a free-of-charge complaint with AKI or initiate proceedings directly before an administrative court.

Claims (2):

  • A data subject dissatisfied with, or receiving no reply to, a rights request within 30 days may lodge a free complaint with AKI or bring proceedings directly before an administrative court.
  • IKS — Any person who suffered material or non-material damage from a GDPR infringement has a direct right to claim compensation under Estonian law.

Recent developments 180dAmber

The EDPB/EDPS adopted a Joint Opinion (10 June 2026, dated as Joint Opinion 2/2026) on the EU Digital Omnibus proposal amending the GDPR, EUDPR, ePrivacy Directive, NIS2 and Data Act; a leaked Council compromise text (dated 20 February 2026) removed the Commission's proposed narrowing of the 'personal data' definition. A parallel Joint Opinion 1/2026 (10 June 2026) addressed the Digital Omnibus on AI. Estonia's Riigikohus also referred Case C-222/25 to the CJEU (lodged 21 March 2025) on AML/GDPR data-processing questions.

Claims (2):

  • The EDPB and EDPS adopted a Joint Opinion on the Digital Omnibus Regulation proposal, strongly urging co-legislators not to adopt the Commission's proposed changes to the GDPR's definition of personal data, while supporting simplification of breach-notification thresholds and deadlines.
  • A leaked 20 February 2026 Council compromise text on the Digital Omnibus, circulated by the Cypriot presidency, eliminated the Commission's proposed new definition of 'personal data' under the GDPR.
Category narrative 119 words

AKI's enforcement toolkit is distinctive within the EU: per GDPR Recital 151, administrative fines are not directly applicable in Estonia; AKI instead relies on precepts/injunctions (often with attached 'penalty payment' sums, technically enforced via the Estonian Substitutive Enforcement and Penalty Payment Act) and reprimands. Documented penalty payments range from 5,000 EUR (Facebook debt-disclosure case) to 100,000 EUR (e-pharmacy case) to 10,000 EUR per unfulfilled point (Krediidiregister). Complainants may escalate to AKI or an administrative court free of charge. The most significant 180-day development is the EU Digital Omnibus, which the EDPB/EDPS opined on in February 2026, and which remains in trilogue with a Council compromise text (February 2026) already diverging from the Commission's original proposal on the personal-data definition.

Periodic update · new data 2026-10-11

Estonia's enforcement and redress posture this cycle is reported as escalating, built on three reinforcing data points. AKI retains the capacity to impose fines of up to EUR 20 million or 4% of global annual turnover for GDPR violations, following a 2023 Penal Code amendment that raised the ceiling from a prior EUR 400,000 cap; this structural fact frames the scale within which the Apotheka fine, and any future fine, sits. Reports further indicate that AKI opened 46 own-initiative supervisory proceedings in 2025, of which roughly 30% were prompted by a data leak, and handled 50 court cases during the year. This activity-volume figure is carried with an uncertain rather than assertive tone, reflecting its reliance on a single tracker-style secondary source rather than AKI's own published enforcement statistics.

The cycle's dominant enforcement-and-redress development remains the Apotheka matter. The EUR 3,000,000 fine imposed on Allium UPI OÜ on 5 September 2025, reported as Estonia's largest to date, is understood to remain under appeal, with court hearings reported to have begun 6 April 2026. Pending the appeal's outcome, this fine should be read as a current but not yet final exercise of AKI's enforcement powers, rather than a settled precedent for how the raised fine ceiling will be applied going forward.

Separately, the EDPB's own published Article 60 decision, finalised and published in October 2026, shows the cross-border cooperation and consistency mechanism reaching a formal conclusion on an Estonian breach matter, with the underlying controller's notification and remedial conduct recorded directly in that primary EDPB document. This is the most firmly sourced redress-mechanism development of the cycle and illustrates the EDPB consistency mechanism functioning in practice for at least one Estonian case this reporting period.

Read together, these developments describe an enforcement environment where the formal fining ceiling is high, reported own-initiative activity is substantial, and at least one significant fine is actively contested through the courts, while the EU-level cooperation mechanism continues to process and close Estonian matters referred to it.

Outlook

The Apotheka appeal remains the single clearest forward-looking marker for this module: its resolution will show how Estonia's courts treat AKI's exercise of its post-2023 fining powers in a significant security-failure matter. Beyond that, whether AKI's reported 2025 enforcement-activity volume, including the 46 own-initiative proceedings, is sustained, grows, or recedes in the following reporting period is not resolved by the material available, and would be the natural next data point to track.

1 earlier distinct update
Periodic update · new data 2026-09-28

AKI imposed a EUR 3,000,000 fine on Allium UPI OU on 5 September 2025 over the Apotheka loyalty-programme data breach, which affected more than 750,000 people, the largest GDPR fine imposed in Estonia to date. The fine is under appeal, with court hearings beginning 6 April 2026; its outcome remains unresolved as of this cycle. The scale of this penalty was made possible by the 2023 legislative simplification of legal-person fining under the IKS, and it arrives against the backdrop of an earlier, unfavourable precedent for the regulator: the annulment of AKI's Asper Biogene fine, which already introduced uncertainty about how far the regulator's enforcement reach actually extends once tested in court.

The statutory ceiling within which this penalty sits is substantial: IKS Sections 66-70 permit fines of up to EUR 20,000,000, or for legal persons up to EUR 20,000,000 or 4 percent of worldwide annual turnover, whichever is greater, classified as an Estonian misdemeanour. The Allium UPI fine, at EUR 3,000,000, represents a fraction of that ceiling, meaning the statutory framework has substantially more room to escalate in a future case of comparable or greater severity, assuming the current fine survives appeal.

Separately from AKI's regulatory enforcement track, Estonian law grants any person who has suffered material or non-material damage from a GDPR infringement a direct right to claim compensation. This creates a second redress channel independent of the regulator's own enforcement outcome, meaning affected individuals from the Apotheka breach are not solely dependent on the fate of AKI's appeal to seek a remedy.

Outlook

The 6 April 2026 appeal hearings are the single most consequential near-term event for this module: a ruling in AKI's favour would confirm the durability of its post-2023 enforcement powers, while a ruling against it, following the Asper Biogene annulment, would suggest a pattern of judicial pushback against the regulator's expanded fining practice.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (16)
  1. Confirmed AKI / EDPB — In Estonia, administrative fines are not directly applicable according to GDPR Recital 151; when a controller demonstrates compliance with AKI's guidance and takes corrective action, AKI may close proceedings with a reprimand rather than an administrative fine. observed
  2. Confirmed EDPB / AKI — AKI issued a precept with a 100,000 EUR penalty payment and a one-day compliance deadline to three pharmacy chains in a 2020 e-pharmacy prescription-access case. observed
  3. Confirmed EDPB / AKI — AKI issued a precept with a 5,000 EUR penalty payment against a Facebook-group administrator for unlawfully disclosing individuals' debt data to thousands of unidentified group members. observed
  4. Confirmed EDPB — A data subject dissatisfied with, or receiving no reply to, a rights request within 30 days may lodge a free complaint with AKI or bring proceedings directly before an administrative court. observed
  5. Confirmed EDPB — The EDPB and EDPS adopted a Joint Opinion on the Digital Omnibus Regulation proposal, strongly urging co-legislators not to adopt the Commission's proposed changes to the GDPR's definition of personal data, while supporting simplification of breach-notification thresholds and deadlines. observed
  6. Probable IAPP — A leaked 20 February 2026 Council compromise text on the Digital Omnibus, circulated by the Cypriot presidency, eliminated the Commission's proposed new definition of 'personal data' under the GDPR. observed
  7. Probable https://lexlint.io/l/ee-eu-2016-679-82-83 — IKS — Any person who suffered material or non-material damage from a GDPR infringement has a direct right to claim compensation under Estonian law.
  8. Probable https://lexlint.io/l/ee-eu-2016-679-82-83 — IKS Sections 66-70 punish distinct categories of GDPR violation with fines up to EUR 20,000,000, or for legal persons up to EUR 20,000,000 or 4% of worldwide annual turnover, whichever is greater, classified as an Estonian misdemeanour.
  9. Probable https://klarproof.com/regulators/estonia/aki/ — AKI imposed a EUR 3,000,000 fine on Allium UPI OU on 5 September 2025 over the Apotheka loyalty-programme data breach affecting more than 750,000 people; the fine is under appeal, with court hearings beginning 6 April 2026.
  10. Probable recordinglaw.com — AKI can impose fines of up to EUR 20 million or 4% of global annual turnover for GDPR violations, following a 2023 Penal Code amendment that raised the ceiling from a prior EUR 400,000 cap. observed
  11. Uncertain https://www.recordinglaw.com/world-laws/world-data-privacy-laws/estonia-data-privacy-laws/ — AKI opened 46 own-initiative supervisory proceedings in 2025 (30% prompted by a data leak) and handled 50 court cases during the year.
  12. Probable KlarProof — Allium UPI OÜ — AKI's record EUR 3,000,000 fine (imposed 5 September 2025) upheld by Harju County Court on 2 September 2026 observed
  13. Probable Klarproof — AKI's EUR 3,000,000 fine against Allium UPI OÜ (September 2025, Apotheka loyalty-programme breach) remains under appeal; court proceedings began 6 April 2026 with no resolution identified this cycle. observed
  14. Uncertain noyb — AKI's EUR 3,000,000 fine against Allium UPI OÜ, Estonia's largest GDPR fine to date, remains under court appeal, with hearings that began 6 April 2026. observed
  15. Probable DLA Piper — GDPR Article 83(5)/(6) sets Estonia's maximum administrative-fine ceiling at the higher of EUR 20,000,000 or 4% of global turnover. observed
  16. Probable Primary statutory record — AKI's EUR 3,000,000 fine against Allium UPI OU was upheld by Harju County Court on 2 September 2026.
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 65 claim(s) (65 category placement(s)), 44 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: not upheld (8 confirmed against the cited source; 1 contradicted by the cited source; 29 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 8Children & Vulnerable Groupsage verification
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrectification and erasure
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy granted
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer impact assessment
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties