> GDPR Poland vs POPA side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# GDPR Poland vs POPA

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[GDPR Poland](https://grc.plus/regulation/general-data-protection-regulation-gdpr/poland/)Controllers and processors

[POPA](https://grc.plus/regulation/alberta-protection-of-privacy-act/)

## At a Glance

They differ on 4 of 5 topics. Each verdict names what it rests on; read the wording before relying on it.

- **GDPR Poland** Asks more on 0 topics Alone on 0 topics More detailed on 3 topics
- **POPA** Asks more on 0 topics Alone on 1 topic More detailed on 0 topics

| Topic | GDPR Poland | POPA | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | GDPR Poland: – | POPA: 1 | **Only POPA**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Data security | GDPR Poland: 2 | POPA: 1 | **Both cover it**read the wording below |
| Detection and response |  |  |  |
| Reporting to authorities | GDPR Poland: 3 | POPA: 1 | **GDPR Poland more detailed**more requirements on this, not necessarily stricter |
| Privacy and data protection |  |  |  |
| Lawful processing | GDPR Poland: 7 | POPA: 2 | **GDPR Poland more detailed**more requirements on this, not necessarily stricter |
| Impact assessment | GDPR Poland: 3 | POPA: 1 | **GDPR Poland more detailed**more 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

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

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.

Included

- [POPA](https://grc.plus/regulation/alberta-protection-of-privacy-act/) Protection of Privacy Act, SA 2024, c P-28.5 6 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

GDPR Poland: At the time the data are obtained (Controllers); 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 (Controllers); 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 (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); 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 (Controllers)

POPA: Not in the acts covered

### Threshold

GDPR Poland: 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)

POPA: Not in the acts covered

### Goes to

GDPR Poland: Controller (Processors); Data subjects (Controllers)

POPA: Not in the acts covered

### Evidence to keep

GDPR Poland: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

POPA: Not in the acts covered

### Incident reports go to

GDPR Poland: Competent supervisory authority (Controllers)

POPA: Not in the acts covered

### First notice of an incident

GDPR Poland: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

POPA: Not in the acts covered

### Intermediate report

GDPR Poland: In phases, without undue further delay (Controllers)

POPA: Not in the acts covered

### External assessment or certification

GDPR Poland: Approved code of conduct or certification may help show compliance (Controllers)

POPA: Not in the acts covered

### Review of the risk framework

GDPR Poland: Where necessary (Controllers)

POPA: Not in the acts covered

### Testing of critical systems

GDPR Poland: Regularly

POPA: Not in the acts covered

### Maximum fines

GDPR Poland: 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

POPA: Not in the acts covered

## Governance

### Management accountability

**Only POPA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

- Privacy management program
  Establish and implement a documented privacy management program proportional to the volume and sensitivity of the personal information held, meeting the Ministerial Regulation (section 6: a privacy officer, policies and procedures, a security classification system, mandatory training and periodic review); give anyone who asks a copy within 30 business days.
  [POPA, Section 25](https://grc.plus/regulation/alberta-protection-of-privacy-act/#requirements)

## 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

- Integrity and confidentiality
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Security arrangements
  Protect personal information with reasonable security arrangements against unauthorized access, collection, use, disclosure or destruction.
  [POPA, Section 10(1)](https://grc.plus/regulation/alberta-protection-of-privacy-act/#requirements)

## Detection and response

### Reporting to authorities

**GDPR Poland more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Notify a personal data breach
  Applies to: Controllers
  Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.
  [GDPR, Article 33(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Processor tells the controller
  Applies to: Processors
  Tell the controller of a personal data breach without undue delay after becoming aware of it.
  [GDPR, Article 33(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- What the breach notice contains
  Applies to: Controllers
  Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.
  [GDPR, Article 33(3) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Breach notification
  Notify the individual, the Commissioner and the Minister without unreasonable delay when an incident creates a real risk of significant harm; the notices are written and contain the information set by the Protection of Privacy (Ministerial) Regulation (section 4).
  [POPA, Section 10(2)](https://grc.plus/regulation/alberta-protection-of-privacy-act/#requirements)

## Privacy and data protection

### Lawful processing

**GDPR Poland more detailed** more requirements on this, not necessarily stricter

NIST Privacy Framework CT.PO-P

- 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Accountability
  Applies to: Controllers
  The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.
  [GDPR, Article 5(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Lawful basis
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Conditions for consent
  Applies to: Controllers
  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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · 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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Special category and criminal offence data
  Applies to: Controllers
  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](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Accuracy for decisions
  Make every reasonable effort to keep personal information used for decisions, including automated ones, accurate and complete, and keep it for at least one year after using it, or a shorter period agreed in writing by the individual, the public body and any body that approves its retention schedule.
  [POPA, Section 6](https://grc.plus/regulation/alberta-protection-of-privacy-act/#requirements)
- No sale of personal information
  Never sell personal information.
  [POPA, Section 11](https://grc.plus/regulation/alberta-protection-of-privacy-act/#requirements)

### Impact assessment

**GDPR Poland more detailed** more requirements on this, not necessarily stricter

NIST Privacy Framework ID.RA-P

- When an impact assessment is needed
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- What the assessment contains
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Prior consultation
  Applies to: Controllers
  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)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Privacy impact assessment
  Prepare a privacy impact assessment for a new or substantially changed practice, program, project or service involving personal information where a loss could cause significant harm or a submission factor applies, and submit it to the Commissioner where the information is highly sensitive, a significant share of the population is involved, data is matched between public bodies, the program is common or integrated, it uses innovative technology or the Commissioner asks (Ministerial Regulation, section 7).
  [POPA, Section 26](https://grc.plus/regulation/alberta-protection-of-privacy-act/#requirements)

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. 19 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare GDPR Poland](https://grc.plus/compare/gdpr-poland/)
- [Compare POPA](https://grc.plus/compare/popa/)

Source: https://grc.plus/compare/gdpr-poland-vs-popa/
