ExactFlow p.s.a. Breach Notification Policy

Personal Data Breach Response, Notification, and Reporting Procedure

Effective Date: 1 April 2026  |  Version 1.0  |  Legal Basis: GDPR Articles 33–34; Polish PDPA; NIS2 Directive (EU) 2022/2555  (Last updated: 1 April 2026)

Document TypeBreach Notification Policy — Internal and Published
OwnerData Protection Officer (DPO)
Incident LeadChief Information Security Officer (CISO)
Contactprivacy@exactflow.com | security@exactflow.com
72-Hour ClockStarts from the moment ExactFlow becomes AWARE — not from when breach is confirmed
Supervisory AuthUODO — ul. Stawki 2, 00-193 Warsaw | www.uodo.gov.pl | +48 22 531 03 00
UODO Portalhttps://uodo.gov.pl/p/zgloszenie-naruszenia

THE 72-HOUR CLOCK IS ABSOLUTE. GDPR Article 33(1) requires notification to the UODO within 72 hours of BECOMING AWARE of a personal data breach posing risk to individuals — not from confirming it. Awareness is the trigger. All staff must report suspected breaches immediately — do not investigate before reporting internally.

1. What Is a Personal Data Breach

Under GDPR Article 4(12), a personal data breach is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. This includes three types:

Breach TypeExamples
Confidentiality breachUnauthorised external access; accidental email to wrong recipient containing personal data; insider access beyond role authorisation; data shared with wrong sub-processor; personal data visible in error on public-facing page
Integrity breachUnauthorised modification of personal data; ransomware altering records; data corrupted during migration; incorrect data merged with wrong customer record
Availability breachRansomware destroying or encrypting personal data without recovery; sustained DDoS causing unavailability of personal data individuals need access to; accidental database deletion without backup

2. Breach Severity Classification

LevelCriteriaUODO Notification?Individual Notification?Escalation
Level 1 — LowNo risk to individuals (e.g. data already public; single record; no sensitive data; immediately contained)No — document internallyNoLog in Breach Register; DPO review within 5 days
Level 2 — MediumRisk (not high risk) to individuals (e.g. limited personal data exposed; moderate sensitivity; contained)Yes — within 72 hoursNo — unless risk escalatesDPO leads; CISO supports; UODO notified; full documentation
Level 3 — HighHIGH risk to individuals — likely to result in discrimination, identity theft, financial loss, or significant harm (e.g. financial data; health data; large-scale; special category)Yes — within 72 hoursYes — without undue delayDPO + CISO + CEO; legal counsel; individuals notified; consider press statement
Level 4 — CriticalLarge-scale breach; vulnerable individuals or children; criminal activity; multiple organisations affected; regulatory investigation likelyYes — within 24 hours (best efforts)Yes — immediatelyBoard notification; legal counsel; UODO pre-notification call; law enforcement; crisis communications

3. Breach Response — Step-by-Step Procedure

Phase 1: Detection and Report (Hour 0)

Any person (staff, contractor, Client, sub-processor) aware of or suspecting a breach must immediately report to privacy@exactflow.com and security@exactflow.com. Include: what happened (as known); when discovered; what data may be involved; estimated number of individuals; systems affected. Preserve all evidence — do not delete logs or records.

Phase 2: Containment (Hours 0–4)

CISO leads containment — isolate affected systems from the network

  • Revoke compromised credentials and access tokens
  • Preserve forensic evidence — take system snapshots before remediation; do not wipe affected systems
  • Brief the DPO with initial assessment of data categories, record volumes, and individuals potentially affected

Phase 3: Assessment and Classification (Hours 0–24)

DPO leads risk assessment — determine data categories, sensitivity, volume, special category or children's data

  • Assess risk to individuals using four factors: type of breach; nature and sensitivity of data; ease of identification; consequences for individuals
  • Classify breach Level 1–4; determine whether UODO notification is required
  • Document all findings in the Breach Notification Record

Phase 4: UODO Notification (Within 72 Hours — where required)

Where breach poses risk to individuals (Level 2, 3, or 4), DPO submits notification to UODO via https://uodo.gov.pl/p/zgloszenie-naruszenia. GDPR Article 33(3) requires:

  • Nature of breach; categories and approximate number of data subjects and records concerned
  • Name and contact details of the DPO
  • Likely consequences of the breach
  • Measures taken or proposed, including mitigation of adverse effects

Where all information is unavailable within 72 hours, submit what is available with a clear note that it is a partial notification — supplement within 7 days.

Late UODO notification — or failure to notify — is a material GDPR violation exposable to administrative fines under GDPR Article 83(4) of up to €10,000,000 or 2% of total annual worldwide turnover, whichever is higher.

Phase 5: Individual Notification (where required)

Where breach is likely to result in HIGH risk (Level 3 or 4), ExactFlow notifies affected data subjects directly without undue delay under GDPR Article 34. Notification must be in plain language and include: nature of breach; DPO contact; likely consequences; measures taken; specific, practical advice for the individual (e.g. change passwords; monitor bank statements).

Phase 6: Remediation (Days 1–30)

Remediate root cause; strengthen failed controls; retrain staff; update processes

  • Post-incident review within 30 days — documented findings and action plan
  • High and critical priority remediation actions implemented within 30 days
  • Post-incident review findings reported to the Board

Phase 7: Documentation and Closure

All breaches — notifiable or not — documented in the Breach Register (GDPR Article 33(5)). Entry must include: discovery and containment timestamps; breach type and severity; data categories and estimated records/individuals affected; root cause; UODO notification details; individual notification details; remediation actions; DPO sign-off confirming closure.

4. Response Timeline Summary

TimelineActionOwner
Immediate (Hour 0)Report to privacy@exactflow.com and security@exactflow.comAll Staff / Sub-processors
Within 1 hourCISO and DPO notified; initial triage; evidence preservationCISO + DPO
Within 4 hoursContainment complete or underway; initial assessment to DPOCISO
Within 24 hoursRisk assessment and classification complete; CEO briefed for Level 3/4DPO
Within 48 hoursLegal counsel engaged for Level 3/4; UODO notification drafted and reviewedDPO + Legal
Within 72 hoursUODO notification submitted (where required); initial individual notifications for Level 3/4DPO
Within 7 daysUODO supplementary notification if initial was partial; all individuals notified; Board briefed for Level 3/4DPO + CEO
Within 30 daysRoot cause remediated; post-incident review completed; Board reportCISO + DPO

5. NIS2, Polish Cybersecurity Act, and PCI-DSS Obligations

NIS2 Directive (EU) 2022/2555: where ExactFlow qualifies as Essential or Important Entity, significant ICT incidents must be reported to CSIRT NASK within 24 hours (early warning) and 72 hours (full notification). Classification assessment underway — Policy to be updated on determination.

Polish Cybersecurity Act (Dz.U. 2018 poz. 1560): ICT incidents affecting critical services reported to relevant CSIRT (CSIRT GOV, CSIRT NASK, or CSIRT MON) per Act requirements.

PCI-DSS v4.0: card data breaches reported to Visa and Mastercard and the acquirer within 24 hours of confirming card data involvement per card scheme rules.

6. Sub-Processor and Client Obligations

6.1 ExactFlow as Data Processor

Where ExactFlow acts as Data Processor on behalf of a Platform Client and discovers a breach affecting the Client's personal data, ExactFlow will: notify the Client within 24 hours; provide all information needed for the Client's own GDPR notification assessment; cooperate fully with the Client's investigation; implement containment and remediation as directed where not in conflict with ExactFlow's own obligations.

6.2 Sub-Processors

All sub-processors are contractually required to notify ExactFlow at privacy@exactflow.com and security@exactflow.com within 24 hours of becoming aware of any breach affecting ExactFlow personal data.

7. Contact

DPOprivacy@exactflow.com
CISOsecurity@exactflow.com
UODOkancelaria@uodo.gov.pl | +48 22 531 03 00 | www.uodo.gov.pl
UODO Notification Portalhttps://uodo.gov.pl/p/zgloszenie-naruszenia
CSIRT NASK (NIS2)incydent@cert.pl | www.cert.pl
Registered AddressExactFlow p.s.a., Stanisława Bodycha 87, 05-816 Reguły, Poland

This Breach Notification Policy complies with: GDPR Articles 33–34; Polish Personal Data Protection Act (Dz.U. 2018 poz. 1000); NIS2 Directive (EU) 2022/2555; Polish Cybersecurity Act (Dz.U. 2018 poz. 1560); PCI-DSS v4.0; and ENISA Personal Data Breach Notification Guidelines. Annual tabletop exercises testing this procedure are strongly recommended.

— END OF BREACH NOTIFICATION POLICY — EXACTFLOW P.S.A. —

ExactFlow Breach Notification Policy