AML service providers, DPA, incidents and exit

Provider roles, processor contracts, personal-data breaches and taking over files at exit.

Processes and privacyUpdated Legal position as of Redakce eAML.cz

A provider may technically process an AML file, but the obliged entity’s responsibility remains. Before starting the service, determine roles, access and exit arrangements. A breach and file export need a concrete operational procedure, not merely a general contractual sentence.

Which roles and contract does the actual service require?

The obliged entity is generally controller of its AML data because it determines the statutory processing purpose. A provider acting only on its instructions is a processor for that activity. The provider’s own processing, such as billing or a separate purpose, needs separate assessment. The DPA label alone does not decide roles; actual powers over purpose and essential means matter under GDPR and EDPB guidance.

An Article 28 contract must define subject matter, duration, nature, purpose, data types, categories of individuals and controller rights. It covers documented instructions, confidentiality, security, other processors, assistance, audit information and handling data at exit. Establish actual storage locations, support access and other processors. Assess transfers outside the EEA under Chapter V; a European invoice does not itself ensure European processing.

    How do you ensure security and handle breaches?

    Article 32 requires measures appropriate to risk. For identity-document copies and AML evidence, establish customer separation, access control, authentication, encryption, backups, recovery and traceable administrative actions. Check how public links are prevented, former workers’ accounts removed and support access restricted. A contractual security promise does not replace a verifiable procedure and responsible contacts.

    A processor informs the controller of a personal-data breach without undue delay after becoming aware. Under Article 33, the controller notifies the supervisory authority without undue delay and, where feasible, within 72 hours of awareness, unless risk to individuals’ rights and freedoms is unlikely. High risk also requires consideration of communication to affected individuals under Article 34, subject to its exceptions. Every breach is documented; neither automatic reporting nor automatic concealment fits all cases.

      When must cyber-incident reporting be assessed alongside GDPR?

      An AML-file breach may affect both personal-data protection and a regulated service. Assess the duties separately: notifying the Czech data protection authority (ÚOOÚ) does not replace reporting under Act No. 264/2025 Coll., or vice versa. Supplying AML software or being an AML obliged entity does not itself bring a business within that Act. Check the actual regulated service, obligations regime, defined scope and commencement of the reporting duty.

      The Act took effect on 1 November 2025. Reporting for a newly regulated service begins no later than one year after delivery of its registration decision. Previously regulated entities have the special transition in Section 71 and use the NÚKIB Portal from registration. Under the general regime, reporting covers an incident within the defined scope, originating in cyberspace, where intentional causation cannot be excluded within the prescribed period; the lower regime additionally requires a significant effect on the service. The higher regime reports to NÚKIB and the lower regime to the National CERT, primarily through the same NÚKIB Portal.

      For selected digital services under Section 18, check the special rules, including the definition of significant incidents under Regulation (EU) 2024/2690. Also check any sector-specific rules under Section 70, for example for financial entities. GDPR controller and processor duties continue to apply.

      How do you manage one incident and two separate reporting decisions?

      Keep one timeline, but record separately for each organisation its awareness time, controller or processor role, affected data and service, responsible contact and decision on each notification. A supplier acting as processor informs the controller without undue delay; it does not wait 72 hours or for forensic investigation to finish. The controller assesses risk, notification to ÚOOÚ and, where risk is high, communication to affected individuals under Article 34, including its exceptions. Article 33(4) allows missing information to be supplied in phases without undue further delay.

      Where mandatory reporting under the new general cyber regime already applies, submit the initial report without undue delay and no later than 24 hours after awareness. A further notification is required for a significant effect on the service in the lower regime or on the state’s cyberspace in the higher regime, without undue delay and within 72 hours of awareness, or 24 hours for a trust service. The final report is due within 30 days of that notification; if the incident continues, an interim report is followed by a final report within 30 days of resolution. Do not automatically apply these deadlines to transitional or special regimes. Retain both decisions, submissions, receipt confirmations and the plan for supplying further information.

      How do you preserve the statutory file on exit?

      Before exit, test exporting documents, check results, sources, versions and timestamps. The file must remain readable and traceable throughout the applicable statutory period. An image of the final page does not replace complete evidence. Determine secure transfer, recipient, completeness checks and subsequent storage. Subscription expiry does not change the entity’s Section 16 retention period.

      Article 28(3)(g) provides for deletion or return at the controller’s choice after services end and deletion of copies, unless law requires storage. Specify backups, lawful exceptions and confirmation of completion. A technical application’s short pilot retention is not the statutory AML archive. A provider must not unilaterally change purpose and use client files for model training; any further purpose requires separate legal assessment.

        Practical steps

        1. Map roles, data and other processors.
        2. Conclude the appropriate contract and verify security.
        3. Arrange breach reporting and controller decisions.
        4. Verify export, subsequent archiving and provider deletion.

        Illustrative scenario

        When changing providers, a business receives a readable file including check history, verifies completeness and then documents contractual return or deletion.

        When the situation differs

        A business treats a DPA as proof of security and discovers at exit that it can download only a summary without original evidence.

        What to document

        • Roles, contract and other-processor inventory.
        • Breach timeline and risk assessment.
        • Verified export and exit evidence.

        Common pitfalls

        • Automatically assigning the 72-hour deadline to the processor.
        • Confusing temporary storage with a ten-year archive.

        Frequently asked questions

        Does the provider assume the client’s AML responsibility?

        Not automatically. Allocating technical services and data processing does not remove the obliged entity’s statutory duties.

        Must a supplier acting as processor wait to see whether the customer notifies ÚOOÚ?

        No. The processor informs the controller without undue delay after becoming aware of the breach. If the supplier also has a separate cyber-reporting duty for its own regulated service, it assesses and meets that duty independently. The controller’s GDPR decision does not suspend it.

        Put this guidance into practice

        Continue with related guidance or a template. Adapt the scope to your profession and actual case.

        Where to go next

        Article change history
        • — Added separate assessment of GDPR and cyber-incident reporting duties, scope, roles and deadlines.

        Sources and legal references

        1. Nařízení (EU) 2016/679 – GDPR
          čl. 5, 6, 28, 32–34, 44 a násl. · accessed 2026-10-15
        2. EDPB: Guidelines 07/2020 on controller and processor
          skutečné rozdělení rolí, pokyny a smlouva se zpracovatelem · accessed 2026-10-04
        3. Zákon č. 253/2008 Sb., znění od 11. 1. 2026
          § 16–17a, § 24, § 38–39 · accessed 2026-10-15
        4. Zákon č. 264/2025 Sb., o kybernetické bezpečnosti
          § 15–18, § 70–71 a § 73; rozsah, lhůty, zvláštní a přechodné režimy, účinnost · accessed 2026-10-15
        5. NÚKIB: Hlášení kybernetických bezpečnostních incidentů, verze 1.2 z 8. 6. 2026
          Kapitoly 3–6; povinné subjekty, Portál NÚKIB a postup hlášení · accessed 2026-10-15
        6. NÚKIB: Hlášení incidentů
          Portál, náhradní kanály a přechod původně regulovaných subjektů · accessed 2026-10-15
        7. ÚOOÚ: Porušení zabezpečení osobních údajů
          GDPR čl. 33–34; samostatnost oznámení ÚOOÚ a kybernetického hlášení · accessed 2026-10-15

        Redakce eAML.cz · Published · Text updated · Editorial check · Legal position as of

        Editorial work and source checks are not independent legal approval of your particular process. Compare the conditions and exceptions with your own circumstances.