FADP vs GDPR Estonia
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 4 of 8 topics. Each verdict names what it rests on; read the wording before relying on it.
- FADP Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- GDPR Estonia Asks more on 0 topics Alone on 0 topics More detailed on 4 topics
| Topic | FADP | GDPR Estonia | Verdict |
|---|---|---|---|
| Protection | |||
| Data security | FADP: 1 | GDPR Estonia: 2 | Both cover itread the wording below |
| Privacy and data protection | |||
| Lawful processing | FADP: 1 | GDPR Estonia: 7 | GDPR Estonia more detailedmore requirements on this, not necessarily stricter |
| Transparency | FADP: 1 | GDPR Estonia: 2 | Both cover itread the wording below |
| Rights of individuals | FADP: 1 | GDPR Estonia: 7 | GDPR Estonia more detailedmore requirements on this, not necessarily stricter |
| Privacy by design and by default | FADP: 1 | GDPR Estonia: 2 | Both cover itread the wording below |
| Impact assessment | FADP: 1 | GDPR Estonia: 3 | GDPR Estonia more detailedmore requirements on this, not necessarily stricter |
| Records of processing | FADP: 1 | GDPR Estonia: 2 | Both cover itread the wording below |
| International transfers | FADP: 1 | GDPR Estonia: 4 | GDPR Estonia more detailedmore requirements on this, not necessarily stricter |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Included
- FADP Federal Act on Data Protection of 25 September 2020, SR 235.1; Data Protection Ordinance, SR 235.11
Status
Reviewed against the official texts.
Included
- GDPR Regulation (EU) 2016/679
National requirements
None recorded yet, so the Directive is shown as it is. The national law may go further.
Status
Reviewed against the official texts.
Key Numbers
Deadline
FADP: Not in the acts covered
GDPR Estonia: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Threshold
FADP: Not in the acts covered
GDPR Estonia: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)
Goes to
FADP: Not in the acts covered
GDPR Estonia: Controller (Processors); Data subjects (Controllers)
Evidence to keep
FADP: Not in the acts covered
GDPR Estonia: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Incident reports go to
FADP: Not in the acts covered
GDPR Estonia: Competent supervisory authority (Controllers)
First notice of an incident
FADP: Not in the acts covered
GDPR Estonia: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)
Intermediate report
FADP: Not in the acts covered
GDPR Estonia: In phases, without undue further delay (Controllers)
External assessment or certification
FADP: Not in the acts covered
GDPR Estonia: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Review of the risk framework
FADP: Not in the acts covered
GDPR Estonia: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)
Testing of critical systems
FADP: Not in the acts covered
GDPR Estonia: Regularly
Maximum fines
FADP: Not in the acts covered
GDPR Estonia: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher
Protection
Data security
Both cover it read the wording below
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12
Data security
Security appropriate to the risk.
Integrity and confidentiality
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
GDPR, Article 5(1)(f) · applies as in the Directive
Security of systems and services
Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
GDPR, Article 32(1)(b) · applies as in the Directive
Privacy and data protection
Lawful processing
GDPR Estonia more detailed more requirements on this, not necessarily stricter
NIST Privacy Framework CT.PO-P
Principles
Lawful, good faith, proportionate processing for purposes that are recognisable, with accurate data kept only as long as needed.
Purpose limitation and data minimisation
Applies to: Controllers
Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.
GDPR, Article 5(1)(b) and (c) · applies as in the Directive
Accuracy and storage limitation
Applies to: Controllers
Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.
GDPR, Article 5(1)(d) and (e) · applies as in the Directive
Accountability
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.
GDPR, Article 5(2) · applies as in the Directive
Lawful basis
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.
GDPR, Articles 5(1)(a) and 6(1) · applies as in the Directive
Conditions for consent
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.
GDPR, Article 7 · applies as in the Directive
Children's consent to online services
Applies to: Controllers offering information society services directly to children
Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.
GDPR, Article 8(1) and (2) · applies as in the Directive
Special category and criminal offence data
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.
GDPR, Articles 9 and 10 · applies as in the Directive
Transparency
Both cover it read the wording below
NIST Privacy Framework CM.AW-P
Duty to inform
Inform people when collecting their data, including about automated individual decisions.
Information when collecting from the person
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.
GDPR, Articles 12(1) and 13 · applies as in the Directive
Information when data comes from elsewhere
Applies to: Controllers
Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.
GDPR, Article 14 · applies as in the Directive
Rights of individuals
GDPR Estonia more detailed more requirements on this, not necessarily stricter
NIST Privacy Framework CT.DM-P
Rights of the people concerned
Access, delivery or transfer of data, and the right to have data corrected or deleted.
Answer rights requests in time
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.
GDPR, Article 12(3) to (5) · applies as in the Directive
Right of access
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.
GDPR, Article 15 · applies as in the Directive
Rectification, restriction and telling recipients
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.
GDPR, Articles 16, 18 and 19 · applies as in the Directive
Right to erasure
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.
GDPR, Article 17 · applies as in the Directive
Right to data portability
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.
GDPR, Article 20 · applies as in the Directive
Right to object
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.
GDPR, Article 21 · applies as in the Directive
Solely automated decisions
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.
GDPR, Article 22 · applies as in the Directive
Privacy by design and by default
Both cover it read the wording below
NIST Privacy Framework CT.DP-P
Privacy by design and by default
Technical and organisational measures built in from the start, with data-protection-friendly defaults.
Data protection by design
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.
GDPR, Article 25(1) · applies as in the Directive
Data protection by default
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.
GDPR, Article 25(2) · applies as in the Directive
Impact assessment
GDPR Estonia more detailed more requirements on this, not necessarily stricter
NIST Privacy Framework ID.RA-P
Impact assessments
A data protection impact assessmentAn assessment of the impact of planned processing on the protection of personal data, carried out before processing that is likely to result in a high risk to people's rights and freedoms. Article 35 of the GDPR makes it mandatory in those cases. for processing likely to lead to a high risk.
When an impact assessment is needed
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.
GDPR, Article 35(1) and (3) · applies as in the Directive
What the assessment contains
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.
GDPR, Article 35(2), (7), (9) and (11) · applies as in the Directive
Prior consultation
Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.
Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.
GDPR, Article 36(1) to (3) · applies as in the Directive
Records of processing
Both cover it read the wording below
NIST Privacy Framework ID.IM-P
Records of processing
A record of processing activities, with an exemption for smaller companies.
Controller's record of processing
Applies to: Controllers
Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.
GDPR, Article 30(1), (3), (4) and (5) · applies as in the Directive
Processor's record of processing
Applies to: Processors
Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.
GDPR, Article 30(2) to (5) · applies as in the Directive
International transfers
GDPR Estonia more detailed more requirements on this, not necessarily stricter
Transfers abroad
Transfers to countries on the Federal Council's list, under appropriate safeguards, or under exceptions.
Transfers need a Chapter V ground
Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.
GDPR, Articles 44 and 45 · applies as in the Directive
Appropriate safeguards
Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.
GDPR, Articles 46 and 47 · applies as in the Directive
Third-country orders
Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.
GDPR, Article 48 · applies as in the Directive
Derogations for specific situations
Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.
GDPR, Article 49 · applies as in the Directive
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 15 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.