English
English
Review of Corporate Data Protection Documentation

Ochrana osobních údajů

Data Protection Authority (ÚOOÚ) Inspection at Your Company: Key Actions for the First 72 Hours

Data Protection Authority (ÚOOÚ) Inspection at Your Company: Key Actions for the First 72 Hours

Data Protection Authority (ÚOOÚ) Inspection at Your Company: Key Actions for the First 72 Hours

Ochrana osobních údajů

Ochrana osobních údajů

Pavel Martiník

Managing Partner


If a company receives an inspection notice from the Office for Personal Data Protection (ÚOOÚ), it should first verify what exactly the Office has initiated, the scope of the inspection, and when the initial statutory deadline expires. Subsequently, it is advisable to designate a single point of contact, secure relevant documents and data against modification or deletion, and cross-check the written GDPR documentation against the actual operational practices of the company.

The greatest risk is often not merely a missing document. Frequently, it is a discrepancy between internal policies, technical configurations, and the statements the company provides to the ÚOOÚ during the initial days.

Brief answer: During the first 72 hours, verify the authorization credentials and the scope of the inspection, assemble a lean response team, preserve evidence, map the processing operations concerned, establish centralized communication with the ÚOOÚ, and prepare a response substantiated by concrete documentation. Do not backdate documentation and do not transmit uncontrolled data exports.

Is it already an inspection, or merely an inquiry from the ÚOOÚ?

Not every communication from the ÚOOÚ automatically signifies a formally initiated inspection. The Office may initially request an explanation, investigate a complaint, or notify the controller of a potential infringement. A formal inspection is governed primarily by Act No. 255/2012 Coll., on Inspection (the Inspection Code), Act No. 110/2019 Coll., on Personal Data Processing, the GDPR, and subsidiarily by the Code of Administrative Procedure.

According to information from the ÚOOÚ, inspections are conducted by authorized officers of the Office. The commencement must be notified to the inspected entity in writing, or orally during an on-site inspection, wherein the inspector presents their authorization credentials.

Upon receipt of the document, you should promptly address the following five questions:

  1. Is this a request for an explanation, a notice of commencement of an inspection, or another procedural action?

  2. Who precisely is the inspected entity — the controller, the processor, or another corporate group entity?

  3. What processing operations, period, and scope of personal data are being reviewed by the Office?

  4. What documentation does the Office request and in what format?

  5. When does the deadline for the response or the next procedural step expire?

In the event of an unexpected telephone call or email, verify its authenticity. The ÚOOÚ has previously issued warnings regarding phishing schemes where callers impersonated inspectors. A legitimate inspection is invariably accompanied by formal inspection authorization credentials.

The first 72 hours following notice of a ÚOOÚ inspection

0–4 hours: secure control over the situation

  • Preserve the notice, envelope, data box message, and proof of service.

  • Record all statutory deadlines and designate an individual responsible for monitoring them.

  • Verify the identity of the inspectors, their authorization credentials, and the precise scope of the inspection.

  • Notify executive management, legal counsel, and the Data Protection Officer (DPO), if designated.

  • Designate a single point of contact for all communication with the ÚOOÚ.

  • Suspend routine deletion of relevant records if such deletion could compromise evidence pertinent to the inspection.

At this stage, do not attempt to "amend history." A newly adopted corrective measure may be beneficial; however, it must bear its genuine date and must never be misrepresented as a document or process that existed prior to that date.

4–24 hours: assemble the response team and evidence map

The team should remain as lean as possible, yet capable of addressing both the legal and factual facets of the matter. Depending on the subject matter of the inspection, it typically comprises:

  • a member of executive management holding decision-making authority,

  • in-house or external legal counsel,

  • the DPO, where one has been appointed by the company,

  • the individual responsible for IT or cybersecurity,

  • the process owner concerned, such as HR, marketing, customer care, or operations,

  • a vendor representative, if the processing involves cloud, CRM, attendance management, or other third-party solutions.

For each ÚOOÚ requirement, establish a straightforward tracking matrix: requirement — responsible person — evidentiary source — legal assessment — deadline — status. This prevents contradictory responses, omissions, and interdepartmental discrepancies.

24–48 hours: compare documentation against operational reality

According to its annual report, during an inspection, the ÚOOÚ examines not only the substance of documents, but also how data processing is genuinely performed, how it is organizationally and technically implemented, and how personal data is secured.

Depending on the scope of the inspection, review in particular:

  • records of processing activities (ROPA),

  • legal bases and definitions of the processing purposes,

  • privacy notices pursuant to Articles 13 and 14 GDPR,

  • data processing agreements and the engagement of sub-processors,

  • records of consents and withdrawals of consent,

  • legitimate interest assessments (balancing tests),

  • data protection impact assessments (DPIAs), where required,

  • procedures for handling data subject rights and specific historical logs of requests handled,

  • retention and erasure policies, including their actual technical configuration,

  • access control management, audit logs, and security safeguards,

  • security incident logs and any personal data breach notifications,

  • cross-border data transfers outside the European Economic Area,

  • employee training programs and internal accountability allocation.

It is insufficient merely to establish that a document exists. It is necessary to verify that it pertains to the correct legal entity, corresponds to the audited period, and aligns with actual system configurations and employee statements.

48–72 hours: formulate the response strategy

The response to the ÚOOÚ should be substantive, complete, and readily verifiable. We recommend:

  1. structuring the response in strict correspondence with the questions posed by the Office;

  2. substantiating every assertion with a referenced exhibit or other supporting evidence;

  3. clarifying industry-specific or technical terminology that may carry a distinctive meaning within the organization;

  4. distinguishing between factual conditions that applied during the audited period and subsequent remedial measures;

  5. maintaining a complete index of all submitted documents and their respective version numbers;

  6. requesting timely clarification of ambiguous inquiries or a reasonable extension of the deadline where justified on legitimate grounds.

The statutory duty to provide cooperation does not imply that transmitting an indiscriminate server backup or a raw database export to the Office is advisable. The scope of documents provided must correspond to the subject matter of the inspection while safeguarding data unrelated to the inquiry. Any withholding, redaction, or selective production of materials must be supported by defensible legal grounds and must not obscure relevant facts.

What statutory powers does the ÚOOÚ hold during an inspection?

Article 58 of the GDPR vests the supervisory authority with powers, including but not limited to:

  • ordering the provision of any information required for the performance of its tasks,

  • conducting investigations in the form of data protection audits,

  • obtaining access to personal data and other necessary information,

  • obtaining access to any premises of the controller or processor, including any data processing equipment and means, subject to procedural law conditions.

Concurrently, the inspected entity is required to establish conditions necessary for the execution of the inspection and provide required cooperation. Refusal of cooperation is therefore generally not a sound legal strategy. However, it is appropriate to strictly monitor the scope of authorization, the subject matter of the inspection, the proportionality of requests, and maintain an accurate ledger of all materials disclosed to the Office.

Does an inspection report automatically result in a fine?

No. The ÚOOÚ distinguishes between the fact-finding and assessment stage—the inspection itself—and any subsequent remedial or sanctioning phase. The inspection report (protokol o kontrole) sets forth the established facts, deficiencies, violated statutory provisions, and the underlying evidence relied upon by the Office. The inspection report is not itself an administrative decision imposing a fine, nor can it impose corrective measures. Any such obligation or administrative sanction can only be imposed in subsequent administrative proceedings.

However, this does not mean that the report is a mere formality. Its factual and legal findings may fundamentally predetermine the subsequent course of action taken by the Office.

Objections to the inspection report: statutory deadline is typically 15 days

The inspected entity may submit written objections against the inspection findings set out in the report. Pursuant to Section 13 of the Inspection Code, the deadline is 15 days from the date of service of the report, unless the report stipulates a longer period.

Objections must identify the specific findings against which they are directed and must state the grounds for disagreement. A blanket assertion that the entity disagrees with the report does not satisfy statutory requirements.

Well-crafted objections typically address three levels of analysis:

  • whether the ÚOOÚ established the factual circumstances accurately,

  • whether specific evidence genuinely supports the conclusion set out in the report,

  • whether the Office correctly interpreted and applied the relevant legal provisions.

It is necessary to challenge precisely those findings that are erroneous or incomplete. Concurrently, it is advisable to distinguish the substantive legal defense from remedial steps that the company may adopt without acknowledging liability.

Seven errors that needlessly exacerbate an inspection

  1. Uncoordinated communication. Different departments communicate with the ÚOOÚ independently, producing conflicting accounts.

  2. Backdating documentation. Retroactively generated documentation is presented as historic records.

  3. Mistaking policies for reality. The company presents an impeccably drafted policy that is entirely disregarded in practice.

  4. Uncontrolled data export. Unrelated personal data, trade secrets, or differing versions of the same file are submitted to the Office without explanation.

  5. Disregarding vendors. Responses fail to consider that decisive audit logs or technical configurations reside with a cloud, payroll, or marketing vendor.

  6. Passive approach pending the report. The company fails to remediate an obvious deficiency, notwithstanding that it could be transparently corrected during the inspection.

  7. Belated preparation of objections. Legal and technical teams commence analysis of the report immediately prior to the expiration of the 15-day statutory deadline.

When to engage legal counsel for a ÚOOÚ inspection

Retaining legal representation should be considered immediately if the inspection arises from an individual complaint, a personal data breach, special categories of personal data, employee monitoring, CCTV or biometric systems, direct marketing, cross-border data transfers outside the EU, or large-scale processing of customer data.

Legal counsel can assist in particular by:

  • defining the procedural standing of the company and the lawful scope of the inspection,

  • coordinating communication among executive management, the DPO, IT, and external vendors,

  • drafting submissions and organizing supporting evidence,

  • participating in proceedings and on-site inspection visits,

  • assessing which information must be disclosed and safeguarding unrelated data,

  • drafting formal objections against inspection findings,

  • representing the company in subsequent administrative proceedings,

  • structuring remedial measures so that they are legally sound and technically viable.

Martiník advokátní kancelář provides counsel in GDPR and data protection compliance, drafts records of processing activities, data processing agreements, privacy notices, DPIAs, and incident response plans, and represents clients before the ÚOOÚ. In inspection matters, we align procedural defense with practical remediation of identified deficiencies.

If you have received an inquiry, a notice of commencement of an inspection, or an inspection report from the ÚOOÚ, send us the primary details regarding the scope of the inspection and the upcoming deadline. Schedule a non-binding consultation.

Frequently asked questions regarding ÚOOÚ inspections

What most commonly triggers an inspection by the ÚOOÚ?

The ÚOOÚ conducts both scheduled inspections and ad hoc inspections triggered primarily by complaints from data subjects or other formal submissions. Inquiries may also originate from another supervisory authority, courts, law enforcement agencies, or other public authorities. The 2025 Annual Report records 3,854 received complaints and submissions, representing a year-on-year increase exceeding 68%.

How long does a ÚOOÚ inspection take?

There is no uniform statutory duration for every inspection. The timeline depends on the scope, the complexity of the processing operations, the necessity of on-site inquiries, the volume of documentation requested, and any supplementary investigations. The Inspection Code nevertheless prescribes specific procedural deadlines, such as for the issuance of the inspection report following the final inspection action.

Can an inspection conclude without a fine?

Yes. The inspection is an investigative fact-finding phase. Subsequent remedial or sanction proceedings constitute a separate and, depending on the outcome of the inspection, merely potential stage. Timely and credible remediation can constitute a significant mitigating factor; however, it does not automatically expunge prior infringements.

Must the DPO be present during the inspection?

Statutory provisions do not mandate the physical presence of the DPO at every procedural step. However, if the organization has appointed a DPO and the inspection falls within their remit, they should be informed and engaged without delay. Concurrently, it is advisable to clearly delineate the roles of the DPO, executive management, and external legal counsel.

Can a company remediate an identified deficiency after notice of an inspection?

Yes, and as a rule, an evident deficiency should not be permitted to persist. However, remedial measures must be executed transparently, accurately dated, and substantiated with evidence documenting both the prior and updated state. Subsequent remediation must not be portrayed as evidence that no deficiency ever occurred.

What is the deadline for filing objections to an inspection report?

The standard statutory deadline is 15 days from service of the report, unless the ÚOOÚ specifies a longer period therein. Objections must be submitted in writing, identify the specific contested findings, and set forth substantiated grounds.

Does a GDPR infringement always carry a penalty of 20 million euros?

No. The GDPR establishes two tiers of statutory maximum administrative fines—depending on the nature of the infringement, up to 10 million euros or 2% of total global annual turnover, or up to 20 million euros or 4% of turnover, whichever is higher. These are statutory caps, not mandatory fixed rates. In determining the fine, the specific criteria set forth in Article 83 of the GDPR are evaluated.

Practical checklist for download or team dissemination

  • ☐ We have verified the procedural document type, authorization credentials, inspection scope, and inspected entity.

  • ☐ We log the date of service and monitor all procedural deadlines.

  • ☐ We have established a single point of contact for the ÚOOÚ.

  • ☐ We have engaged executive management, legal counsel, the DPO, and owners of affected processes.

  • ☐ We have preserved relevant documents, correspondence, system configurations, and logs.

  • ☐ We have suspended only such routine deletion schedules that could compromise relevant evidence.

  • ☐ We have audited GDPR documentation against actual operational practice and technical configurations.

  • ☐ We are capable of substantiating each assertion in our response with specific evidence.

  • ☐ We distinguish the state during the audited period from subsequent remedial measures.

  • ☐ We maintain an index of all documents and respective versions disclosed to the ÚOOÚ.

  • ☐ We are preparing for the inspection report and the potential 15-day objection period.

Legal framework and sources

This publication provides general information reflecting the legal status as of November 5, 2026, and does not constitute formal legal counsel for any specific case.

Would you like to receive more information regarding the field of modern law?

We regularly publish systematic analyses, insights, and market updates. Follow our content on social media.

©2026 All rights reserved.

Prague Branch


Martiník Law Firm, LLC
Uruguayská 380/17
120 00 Prague 2 - Vinohrady

Manage my cookie preferences

©2026 All rights reserved.

Prague Branch


Martiník Law Firm, LLC
Uruguayská 380/17
120 00 Prague 2 - Vinohrady

Manage my cookie preferences

Prague Branch


Martiník Law Firm, LLC
Uruguayská 380/17
120 00 Prague 2 - Vinohrady

Manage my cookie preferences

Privacy Policy

©2026 All rights reserved.

©2026 All rights reserved.

Prague Branch


Martiník Law Firm, LLC
Uruguayská 380/17
120 00 Prague 2 - Vinohrady

Manage my cookie preferences

Would you like to receive more information regarding the field of modern law?

We regularly publish systematic analyses, insights, and market updates. Follow our content on social media.

Would you like to receive more information regarding the field of modern law?

We regularly publish systematic analyses, insights, and market updates. Follow our content on social media.