What is the AKI in Estonia?
Estonia’s AKI, the Andmekaitse Inspektsioon or Data Protection Inspectorate, operates as the national supervisory authority for data protection across the country. This body enforces the GDPR in Estonia, handles complaints from data subjects, performs audits, issues guidance on data protection and imposes fines for GDPR violations.
Data protection compliance is a mandatory obligation for every company operating in the European Union, and Estonian companies are:
- no exception. The General Data Protection Regulation (GDPR) applies directly in Estonia as an EU regulation
- supplemented by the Estonian Personal Data Protection Act (Isikuandmete kaitse seadus) which addresses Estonia-specific provisions. For e-Resident companies processing personal data of EU residents
- GDPR compliance is not optional and the enforcement framework has matured significantly since the regulation took effect in 2018
This guide covers GDPR compliance requirements for Estonian companies as of 2026, including the role of the AKI (Data Protection Inspectorate), data processing principles, legal bases for processing, DPO requirements, data subject rights, breach notification obligations, cross-border processing rules and practical compliance strategies.
The focus is on the specific Estonian context and how the AKI interprets and enforces GDPR requirements.
The AKI: Estonia’s Data Protection Authority
Role and Powers
Estonia’s national supervisory authority under GDPR Article 51 is the Andmekaitse Inspektsioon, or Data Protection Inspectorate (AKI). Independent in its operations, the AKI monitors and enforces GDPR compliance across the Estonian jurisdiction. Powers at its disposal include:
- Investigating complaints from data subjects
- Conducting audits and inspections of data controllers and processors
- Issuing corrective measures, including orders to bring processing into compliance
- Imposing administrative fines for GDPR violations
- Guidance and advisory opinions on data protection matters are provided.
- Representing Estonia in the European Data Protection Board (EDPB)
Enforcement Approach
Reputably balancing enforcement, the AKI targets education and corrective measures at smaller firms and first-time violations. Repeat offenders and organizations showing negligence or intentional non-compliance face stronger action from the AKI.
Several thousand inquiries, hotline calls and complaints reach the AKI annually. Most are resolved via guidance and corrective orders instead of fines, though the inspectorate has shown willingness to impose substantial penalties when justified.
Cooperating companies that work with AKI during investigations and show good-faith compliance efforts typically receive more favorable outcomes than those remaining unresponsive or obstructive.
Contact and Reporting
Companies can contact the AKI through its website (aki.ee) for guidance, to report data breaches, or to respond to investigations. Data breach notifications must be submitted to the AKI within 72 hours of becoming aware of a breach that poses a risk to data subjects’ rights and freedoms. The AKI provides an online notification form for this purpose.
GDPR Fundamentals for Estonian Companies
Who Must Comply
GDPR applies to:
- Any company established in Estonia that processes personal data, regardless of where the data subjects are located
- Any company (regardless of location) that processes personal data of individuals in the EU when offering goods or services to them or monitoring their behavior
For e-Resident companies, this means GDPR compliance is triggered by the company’s Estonian establishment and further reinforced if the company serves EU customers or processes EU residents’ data.
Data Processing Principles
The GDPR establishes seven core principles that must guide all personal data processing:
| Principle | Description |
|---|---|
| Lawfulness, fairness, transparency | Data must be processed lawfully, fairly, and in a transparent manner |
| Purpose limitation | Data must be collected for specified, explicit, and legitimate purposes |
| Data minimization | Only data necessary for the stated purpose should be collected |
| Accuracy | Personal data must be accurate and kept up to date |
| Storage limitation | Data must not be kept longer than necessary for its purpose |
| Integrity and confidentiality | Data must be protected against unauthorized access, loss, or destruction |
| Accountability | The controller must be able to demonstrate compliance with all principles |
Legal Bases for Processing
Every processing activity must have a valid legal basis. The GDPR provides six legal bases:
Consent. The data subject has given clear, informed consent for specific processing purposes. Consent must be freely given, specific, informed and unambiguous. It must be as easy to withdraw as it was to give.
Contract. Processing is necessary for the performance of a contract with the data subject or to take pre-contractual steps at their request. This is the most common basis for B2B service companies processing client data.
Legal obligation. Processing is necessary to comply with a legal obligation (tax reporting, employment law, AML requirements).
Vital interests. Processing is necessary to protect someone’s life. This is rarely applicable in a business context.
Public interest. Processing is necessary for a task carried out in the public interest. Primarily applicable to government bodies.
Legitimate interests. Processing is necessary for the legitimate interests of the controller or a third party, provided those interests are not overridden by the data subject’s rights. This requires a documented balancing test.
For most e-Resident businesses, the primary legal bases will be contract performance (processing client data to deliver services), legal obligation (processing employee and financial data for tax and compliance purposes), and legitimate interests (marketing to existing clients, fraud prevention, network security).
Consent should be used sparingly and only when no other legal basis applies, because consent can be withdrawn at any time, creating operational uncertainty.
Data Protection Officer (DPO)
When a DPO Is Required
GDPR Article 37 requires a DPO when:
- The processing is carried out by a public authority or body
- The core activities of the controller or processor consist of processing operations that require regular and systematic monitoring of data subjects on a large scale
- Large-scale processing of special categories including health, biometric, genetic and criminal records forms the core activity.
When a DPO Is Not Required
Thresholds for mandatory DPO appointment rarely get triggered in small and medium-sized e-Resident businesses. Firms like software development shops, consulting firms and online retailers handling routine customer and employee data do not make “large-scale systematic monitoring” their core business practice.
Voluntary Appointment
Companies that do not meet the mandatory threshold may voluntarily appoint a DPO. If a DPO is appointed (whether mandatory or voluntary), they must be given genuine independence, direct access to the highest management level, and adequate resources to perform their role.
DPO Qualifications
The DPO must have expert knowledge of data protection law and practices. There is no formal certification requirement, but practical expertise in GDPR, familiarity with the company’s data processing activities, and understanding of IT security are essential. The DPO can be an employee or an external service provider.
Data Subject Rights
Estonian companies must be prepared to respond to data subject rights requests within the timelines specified by GDPR. The key rights are:
Right of Access (Article 15)
Data subjects can request confirmation of whether their data is being processed and, if so, access to the data along with information about the processing purposes, data categories, recipients and retention periods. Response deadline: one month (extendable by two further months for complex or numerous requests).
Right to Rectification (Article 16)
Data subjects can request correction of inaccurate personal data or completion of incomplete data. Response deadline: one month (extendable by two further months for complex or numerous requests).
Right to Erasure (Article 17)
Data subjects can request deletion of their personal data when it is no longer necessary for the original purpose, consent is withdrawn, or the data was unlawfully processed. This right is not absolute, legal obligations (tax records, for example) override it.
Right to Data Portability (Article 20)
Data subjects can request their data in a structured, commonly used, machine-readable format and have it transmitted to another controller. This applies only to data processed based on consent or contract and only to data provided by the data subject.
Right to Object (Article 21)
Data subjects can object to processing based on legitimate interests or public interest grounds. If the controller cannot demonstrate compelling legitimate grounds, processing must cease. Data subjects have an absolute right to object to processing for direct marketing purposes.
| Right | Response Deadline | Can Be Refused? |
|---|---|---|
| Access | 1 month (extendable) | Only if manifestly unfounded or excessive |
| Rectification | 1 month (extendable) | No (if data is inaccurate) |
| Erasure | 1 month (extendable) | Yes (if legal obligation requires retention) |
| Restriction | 1 month (extendable) | Limited circumstances |
| Portability | 1 month (extendable) | Only applies to consent/contract-based processing |
| Objection | 1 month (extendable) | If compelling legitimate grounds exist |
Data Breach Notification
Notification to AKI
When a personal data breach occurs that is likely to result in a risk to individuals’ rights and freedoms, the company must notify the AKI within 72 hours of becoming aware of the breach. The notification must include:
- Nature of the breach (categories and approximate number of data subjects affected)
- Details for the DPO or alternative contact point must be provided.
- Likely consequences of the breach
- Measures taken or proposed to address the breach and mitigate adverse effects
Notification to Data Subjects
When a breach poses a high risk to individuals’ rights and freedoms, the company must inform affected data subjects without unnecessary delay. Notification should use clear, plain language and should contain all elements of the AKI notification plus recommendations that individuals can follow to protect themselves.
Documentation
All breaches must be documented, including those that do not require notification to the AKI. The documentation must include the facts of the breach, its effects and the remedial action taken. This documentation serves as evidence of compliance during AKI audits.
The 72-hour notification requirement starts from the moment the company becomes “aware” of the breach, not from when the breach occurred. Awareness means the company has a reasonable degree of certainty that a breach has taken place. Companies should have incident response procedures in place to ensure breaches are identified and escalated quickly.
Delayed awareness due to inadequate monitoring does not extend the notification deadline and may itself constitute a compliance failure.
Cross-Border Data Processing
When Estonia Is the Lead Authority
If an Estonian company processes personal data of individuals across multiple EU member states, the AKI may serve as the lead supervisory authority under the GDPR’s one-stop-shop mechanism. This occurs when the company’s main establishment (where decisions about data processing purposes and means are made) is in Estonia.
Estonia serves as the main establishment for e-Resident companies because that is where registration occurs. Yet if decision-making about data processing actually happens elsewhere - such as where the e-Resident physically works - authorities determining the lead jurisdiction may become disputed.
Data Transfers Outside the EU
Moving personal data beyond the EU/EEA demands a lawful transfer mechanism per GDPR Chapter V.
- Adequacy decisions. Transfers to countries the European Commission has deemed adequate (including the UK, Japan, South Korea and others)
- Standard Contractual Clauses (SCCs).
- Binding Corporate Rules. Multinational companies use these rules for managing intra-group data transfers internally.
- Derogations. Explicit consent, contractual necessity, or public interest (limited circumstances)
Certified US organizations can transfer data under the EU-US Data Privacy Framework. Legal challenges ahead, however, call for ongoing monitoring of this framework.
E-Privacy and Electronic Communications
Current Rules
Estonia’s Electronic Communications Act operationalizes the EU ePrivacy Directive across cookie management, electronic marketing and communications metadata policies. Essential requirements cover:
- Cookie consent. Websites must obtain informed consent before placing non-essential cookies on users’ devices. Essential cookies (strictly necessary for the website to function) do not require consent but must be disclosed.
- Electronic marketing. Direct marketing via email requires prior consent (opt-in), except for existing customer relationships where soft opt-in may apply.
- Communications confidentiality. The confidentiality of electronic communications must be protected. Interception or monitoring is prohibited without consent or legal authorization.
Upcoming ePrivacy Regulation
Development of the EU ePrivacy Regulation, designed to supersede the ePrivacy Directive, has spanned multiple years in negotiation. Once adopted, it will take effect directly in Estonia and harmonizes electronic communications privacy rules across the entire EU. Businesses need to follow developments and prepare for shifts to cookie consent and electronic marketing rules.
Practical Compliance Steps
For Small E-Resident Companies
- Map your data processing. Document what personal data you collect, why, how it is processed, where it is stored and who has access
- Identify legal bases. Every processing activity requires a documented valid legal basis to be recorded.
- Create a privacy policy. Your site must feature a clear, comprehensive privacy policy that covers the full range of GDPR disclosure requirements.
- Implement data subject request procedures. Have a process for receiving and responding to access, deletion and other requests within the 30-day deadline
- Secure your data. Apply technical and organizational measures including encryption, access controls, secure passwords and regular backups.
- Prepare for breach response. Have a documented incident response plan that enables 72-hour notification to the AKI
- Review data processor agreements. Ensure all third-party processors (cloud providers, email services, analytics tools) have GDPR-compliant data processing agreements in place
Data Processing Agreements
When an Estonian company uses third-party services that process personal data on its behalf (cloud hosting, email marketing platforms, CRM systems, analytics tools), a Data Processing Agreement (DPA) must be in place. The DPA must include:
- Subject matter and duration of processing
- Nature and purpose of processing
- Kinds of personal data and groups of data subjects.
- Obligations and rights that controllers hold.
- Security measures required
- Sub-processor management rules
- Audit rights
- Data deletion or return upon termination.
Most major service providers (AWS, Google Cloud, Microsoft, Mailchimp, HubSpot) provide standard DPAs that meet GDPR requirements.
Fines and Enforcement
Fine Framework
Under GDPR, administrative fines come in two tiers:
| Tier | Maximum Fine | Applicable Violations |
|---|---|---|
| Lower tier | EUR 10 million or 2% of global turnover | Technical and organizational measure failures, DPO-related violations, processor obligations |
| Upper tier | EUR 20 million or 4% of global turnover | Breach of processing principles, legal basis violations, data subject rights violations, cross-border transfer violations |
AKI Enforcement Practice
The AKI considers several factors when determining whether to impose a fine and at what level:
- Nature, gravity and duration of the infringement matter.
- Whether the violation was intentional or negligent matters.
- Actions taken to mitigate damage
- Degree of cooperation with the AKI remains important.
- Previous violations
- Categories of personal data affected
- How the AKI became aware (complaint vs. self-disclosure)
Small and medium businesses receiving AKI notifications generally face warnings, corrective orders or modest fines for initial violations, with fines increasing for subsequent non-compliance.
Demonstrable compliance effort provides the best shield from substantial GDPR fines. Firms showing documented data processing logs, privacy frameworks, data processing addendums, breach Response blueprints and signs of continuous compliance management receive far kinder AKI treatment than those with no compliance structure at all.
Perfect compliance is not demanded, but reasonable and documented compliance effort is.
Conclusion
GDPR compliance for Estonian companies requires a systematic approach to data protection that is proportionate to the nature and scale of data processing activities.
For most e-Resident companies, the compliance burden is manageable: document your processing activities, ensure valid legal bases, implement reasonable security measures, have a privacy policy and be prepared to respond to data subject requests and breach incidents.
The AKI functions as a measured supervisory body that prefers education and corrective action to punitive fines for sincere compliance efforts. Yet the threat of substantial fines under GDPR makes ignoring data protection obligations a risky financial decision.
For related guidance, see our articles on Estonia business laws and compliance, Estonia employment law, and Estonia’s digital single market position.
