al. Grunwaldzka 87/91 lok. 10, 80-244 Gdańsk +48 790 377 775 [email protected]
EN English

Personal data protection – GDPR, breaches, proceedings before UODO

We implement the GDPR in companies and institutions, prepare documentation and data processing agreements, assist with breaches and inspections, and represent clients before the President of UODO and in compensation disputes.

Since 25 May 2018, the GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council – has applied (Article 99(2) GDPR). It is supplemented by the Polish Personal Data Protection Act of 10 May 2018 (ustawa o ochronie danych osobowych, hereinafter u.o.d.o.). The supervisory authority is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, Prezes UODO) (Article 34 u.o.d.o.). The Inspector General for Personal Data Protection (Generalny Inspektor Ochrony Danych Osobowych, GIODO) operated under the previous Act of 1997 and no longer exists, although the name still appears in old clauses and contracts – a sign that the documentation needs updating.

We help companies, schools, housing communities, organisations and individuals: we implement the GDPR and put documentation in order, prepare data processing agreements, guide companies through personal data breaches and inspections, and represent clients before the President of UODO and the administrative courts and in compensation disputes. Below we describe how this works in practice.

Who the obligations apply to

The GDPR applies to anyone who processes personal data – information relating to an identified or identifiable natural person (Article 4(1) GDPR): name and surname, e-mail address, telephone number, PESEL number, CCTV footage, a vehicle registration number combined with other data. The rules distinguish between:

  • the controller – whoever determines the purposes and means of processing (e.g. an online shop in relation to its customers, an employer in relation to its employees),
  • the processor – whoever processes data on behalf of the controller (e.g. an accounting firm, a CRM system provider, a hosting company, a marketing agency).

Obligations and liability depend on this distinction, so we start by establishing the role the company plays in each relationship with a counterparty.

GDPR implementation step by step

The GDPR does not provide for a single "certificate of compliance". It is based on the principle of accountability – the controller must comply with the principles of processing and be able to demonstrate this (Article 5(2) GDPR). We usually carry out implementation as follows:

  1. Data inventory. We establish what data the company collects, from whom, for what purpose, where it is stored, to whom it is disclosed and how long it is kept. We talk to the people responsible for HR, sales, marketing and IT.
  2. Legal bases. Every processing operation must have a basis under Article 6(1) GDPR: consent, performance of a contract, a legal obligation, protection of vital interests, a task carried out in the public interest, or the controller's legitimate interest. A common mistake is to base everything on consent – including where the correct basis is a contract or a legal provision. Consent may be withdrawn at any time (Article 7(3) GDPR), and the controller must be able to demonstrate that it was given (Article 7(1) GDPR).
  3. Information obligation. We prepare privacy notices in accordance with Article 13 GDPR (data collected from the data subject) and Article 14 GDPR (data obtained from another source) – for customers, business partners, job applicants, employees, people recorded by CCTV and website users.
  4. Record of processing activities. The record is kept in writing, including in electronic form, and made available to the supervisory authority on request (Article 30(3) and (4) GDPR). Companies employing fewer than 250 people are exempt from this obligation only if the processing is occasional, does not pose a risk and does not include special categories of data or data relating to criminal convictions (Article 30(5) GDPR). In practice, most companies carrying on ongoing business – if only HR and payroll – should keep a record anyway.
  5. Data processing agreements. With every processor, the controller concludes a contract or other legal act setting out the subject matter, duration, nature and purpose of the processing, the type of data, the categories of data subjects and the obligations of the parties (Article 28(3) GDPR). We also review agreements proposed by suppliers – they often shift risks onto the customer and make no provision for a right of audit.
  6. Security. The controller and the processor implement technical and organisational measures appropriate to the risk – e.g. encryption, backups, access control, regular testing (Article 32(1) GDPR). We prepare the risk analysis in cooperation with the IT department or an external IT specialist.
  7. Data protection impact assessment (DPIA). Where processing – especially using new technologies – is likely to result in a high risk to the rights of individuals, a data protection impact assessment must be carried out before it begins (Article 35(1) GDPR). This applies, for example, to extensive CCTV monitoring, profiling or large-scale processing of health data.
  8. Data protection officer. Designating a DPO (inspektor ochrony danych, IOD) is mandatory, among others, for public bodies and where the core activities consist of regular and systematic monitoring of individuals on a large scale or large-scale processing of special categories of data (Article 37(1) GDPR). In other cases it is voluntary – we help assess whether the obligation applies.
  9. Procedures and training. Data protection policy, procedure for handling requests, breach response procedure, authorisations for employees, retention periods. We train employees using examples from their day-to-day work.
  10. Website and online shop. Privacy policy, a consent mechanism for cookies and marketing, contact forms, newsletter. For online sales, see also complaints and consumer disputes.

Data protection should be taken into account at the design stage of new processes and systems (Article 25 GDPR) – it is cheaper to do this before implementation than after an inspection.

Requests from data subjects

Data subjects have, among other things, the right of access to their data (Article 15 GDPR), the right to rectification, erasure (Article 17 GDPR), restriction of processing, data portability (Article 20 GDPR) and the right to object (Article 21 GDPR). An objection to direct marketing is effective without any further conditions (Article 21(2) and (3) GDPR).

The controller responds without undue delay and at the latest within one month of receiving the request. That period may be extended by two further months, taking into account the complexity or number of requests – but the data subject must be informed of the extension within the first month, together with the reasons (Article 12(3) GDPR). A refusal also requires a response within one month, with information about the right to lodge a complaint and to seek a judicial remedy (Article 12(4) GDPR).

We help respond to requests, especially those made in the context of a dispute – e.g. by a former employee or a customer demanding "all data" in order to prepare a lawsuit. In such cases, the obligation to provide information must be balanced against the protection of business secrets and the data of other people.

Personal data breach – the first 72 hours

A leak of a customer database, an e-mail sent with a list of addresses in the "To" field, a lost unencrypted laptop, a ransomware attack, documents thrown into an ordinary bin – these are personal data breaches. The procedure is as follows:

  1. Containing the situation – securing systems, cutting off access, attempting to recover the data (e.g. asking the recipient of a misdirected e-mail to delete the message).
  2. Risk assessment – what data, how many people, whether it could be misused (e.g. for identity theft), whether the data was encrypted.
  3. Notification to the President of UODO – without undue delay and, where feasible, not later than 72 hours after becoming aware of the breach, unless the breach is unlikely to result in a risk to the rights and freedoms of individuals. A late notification must be accompanied by reasons for the delay (Article 33(1) GDPR). The minimum content of the notification is set out in Article 33(3) GDPR.
  4. Communication to data subjects – if the breach is likely to result in a high risk, the controller communicates it to the data subjects without undue delay, in clear and plain language (Article 34(1) and (2) GDPR).
  5. Documentation – every breach, including those not notified, must be documented: the facts, its effects and the remedial action taken (Article 33(5) GDPR).

A processor that becomes aware of a breach notifies the controller without undue delay (Article 33(2) GDPR) – it is worth specifying this deadline in hours in the data processing agreement. Where the breach involves a criminal offence (e.g. hacking into a system, theft of data by an employee), we also help with reporting it to the law enforcement authorities – see criminal law.

The 72-hour period runs from becoming aware of the breach, including at weekends. That is why it is worth having the procedure and contact details of a decision-maker prepared in advance.

Inspection by the President of UODO

The President of UODO monitors compliance with the law in accordance with an inspection plan or on the basis of information received, e.g. a complaint (Article 78 u.o.d.o.). An inspector has the right to enter premises between 6:00 and 22:00, to inspect documents, examine systems, request explanations and question employees as witnesses (Article 84(1) and Article 86 u.o.d.o.). The inspected entity designates in writing a person authorised to represent it during the inspection (Article 83(2) u.o.d.o.). As a rule, an inspection lasts no longer than 30 days (Article 89(1) u.o.d.o.). Obstructing an inspection is a criminal offence (Article 108(1) u.o.d.o.).

We take part in the inspection, help prepare documents and file objections to the report. If the inspection reveals a possible infringement, the President of UODO opens administrative proceedings (Article 90 u.o.d.o.).

Proceedings before the President of UODO

Proceedings concerning infringements of the law are conducted by the President of UODO (Article 60 u.o.d.o.), applying the Code of Administrative Procedure (k.p.a.) in matters not regulated by the Act. The proceedings are single-instance (Article 7(1) and (2) u.o.d.o.) – there is no appeal to a second-instance authority. The decision is challenged by a complaint to the Voivodeship Administrative Court (wojewódzki sąd administracyjny) within 30 days of its service, lodged through the President of UODO (Article 53 § 1 and Article 54 § 1 of the Law on Proceedings before Administrative Courts (p.p.s.a.)). The competent court is determined by the seat of the authority (Article 13 § 2 p.p.s.a.). Lodging a complaint suspends enforcement of the decision as regards the administrative fine (Article 74 u.o.d.o.).

Important points we take care of in the proceedings:

  • reserving business secrets in the documents submitted – with the obligation to provide a public version, otherwise the reservation is ineffective (Article 65(1) and (2) u.o.d.o.),
  • demonstrating mitigating circumstances under Article 83(2) GDPR – the President of UODO must refer to them in the statement of reasons for a decision imposing a fine (Article 72 u.o.d.o.),
  • responding to a decision restricting processing, which may be issued in the course of the proceedings (Article 70 u.o.d.o.).

The President of UODO may publish information about a decision in the Public Information Bulletin (Biuletyn Informacji Publicznej) if the public interest so requires (Article 73(1) u.o.d.o.) – the reputational consequences can be as keenly felt by a company as the fine itself.

Administrative fines

Fines are imposed depending on the circumstances of the case, taking into account, among other things, the nature, gravity and duration of the infringement, whether it was intentional, the action taken to mitigate the damage, previous infringements and the degree of cooperation with the authority (Article 83(2) GDPR). Upper limits:

  • up to EUR 10,000,000 or, in the case of an undertaking, up to 2% of the total worldwide annual turnover of the preceding financial year, whichever is higher – among others, for infringements of the obligations under Articles 25–39 GDPR (security, record of processing, breach notification, data processing agreements, DPO) – Article 83(4) GDPR,
  • up to EUR 20,000,000 or up to 4% of turnover – among others, for infringements of the basic principles of processing and the conditions for consent (Articles 5, 6, 7 and 9 GDPR) and of data subjects' rights (Articles 12–22 GDPR) – Article 83(5) GDPR.

Amounts in euro are converted at the average exchange rate of the National Bank of Poland (NBP) of 28 January of the given year (Article 103 u.o.d.o.). Public finance sector entities are subject to fines of up to 100,000 zł, and some of them up to 10,000 zł (Article 102 u.o.d.o.).

Irrespective of administrative fines, processing data without authorisation, or where processing is not permitted, is a criminal offence punishable by a fine, restriction of liberty or imprisonment for up to two years (Article 107(1) u.o.d.o.).

Compensation for infringements of the GDPR

Any person who has suffered material or non-material damage as a result of an infringement of the GDPR has the right to receive compensation from the controller or processor (Article 82(1) GDPR). In matters not regulated by the GDPR, the Civil Code (k.c.) applies (Article 92 u.o.d.o.).

  • Competent court – at first instance, the Regional Court (sąd okręgowy), regardless of the value of the claim (Article 93 u.o.d.o. and Article 17 point 4⁵ of the Code of Civil Procedure (k.p.c.)).
  • Relationship with proceedings before UODO – the court stays the case if proceedings concerning the same infringement have been opened before the President of UODO (Article 95 u.o.d.o.), and a final decision finding an infringement is binding on the court as to the fact of the infringement (Article 97 u.o.d.o.).
  • What must be shown – an infringement of the law, damage (including non-material damage, e.g. distress or loss of control over one's data) and a causal link. An infringement of the law alone, without showing damage, is usually not enough.

We represent both individuals pursuing claims and companies being sued – see also litigation.

Help for individuals

If you believe that someone is processing your data unlawfully – e.g. a debt collection agency, an employer, a housing community or a shop sending unwanted marketing – you can:

  1. make a request to the controller (access, erasure, objection) – this is often the quickest route,
  2. lodge a complaint with the President of UODO (Article 77(1) GDPR); if the authority does not handle the complaint or inform you of its progress within three months, you have the right to an effective judicial remedy (Article 78(2) GDPR),
  3. go to court seeking cessation of the infringements and compensation (Articles 79 and 82 GDPR).

We help choose the right route and prepare the documents. Not every situation falls under the GDPR – for example, processing of data by a natural person in the course of a purely personal or household activity is excluded from it (Article 2(2)(c) GDPR); in that case, the protection of personal rights (dobra osobiste) under the Civil Code may come into play.

What to bring to the first meeting

  • your current GDPR documentation (policies, record of processing, notices, data processing agreements) – even if it is out of date,
  • a list of systems and suppliers (accounting, HR, CRM, hosting, e-mail, marketing),
  • in the case of a breach: a chronology of events with times, information on the type and amount of data, correspondence,
  • in the case of an inspection or proceedings: the inspection authorisation, the report, letters from UODO,
  • in the case of a dispute: the requests, the replies, evidence of damage.

Common mistakes

  • copying ready-made templates from the internet that do not reflect the company's actual processes,
  • references to GIODO and the repealed 1997 Act in clauses and contracts,
  • no data processing agreements with the accounting firm, software provider or IT company,
  • collecting consents where the basis is a contract or a legal provision, and then having a problem when the person withdraws consent,
  • "waiting out" a breach and hoping no one will find out – when setting the fine, the authority takes into account whether, and to what extent, the controller itself notified the breach (Article 83(2)(h) GDPR),
  • keeping data "forever", without retention periods.

How we work with you

  1. A conversation – we establish the objective: implementation, audit, an urgent breach, an inspection, a dispute.
  2. Analysis – a review of documents and interviews with the people responsible for the processes.
  3. Report – a list of risks and recommendations with priorities, without unnecessary documentation "for the shelf".
  4. Documents and implementation – we prepare the documents and train employees.
  5. Ongoing support – we answer day-to-day questions, update documents, and respond to breaches and requests.

In urgent matters – a breach, an announced inspection – we aim to respond the same day. We also help educational establishments as part of our education law practice.

Artificial intelligence in your business – GDPR and the AI Act

A company that merely uses a ready-made tool – a chatbot on its website, a customer service assistant, a text generator – is a deployer within the meaning of the AI Act (Regulation (EU) 2024/1689) and has obligations of its own. In July 2026 the AI Act was amended by Regulation (EU) 2026/1744 (the so-called Digital Omnibus). Article 4 on AI literacy has applied since 2 February 2025 – following the amendment, measures must be taken to support the development of staff competence, without an obligation to ensure a specific level. Since 2 August 2026 the transparency obligations under Article 50 have applied: the provider must ensure that users know they are interacting with AI and must mark generated content (paragraphs 1 and 2; for generative systems placed on the market earlier – by 2 December 2026), while the deployer discloses, among other things, deepfakes (paragraph 4). The obligations for high-risk systems have been postponed to 2 December 2027 (Annex III, e.g. recruitment) and 2 August 2028 (systems embedded in regulated products).

The Polish Act on Artificial Intelligence Systems (ustawa o systemach sztucznej inteligencji, Journal of Laws 2026, item 1003) has been in force since 11 August 2026, and its provisions on inspections, proceedings and penalties apply from 28 October 2026 (Article 127 point 2). The market surveillance authority is the Commission for the Development and Security of Artificial Intelligence (Komisja Rozwoju i Bezpieczeństwa Sztucznej Inteligencji, KRiBSI) (Article 5(1)). The Commission monitors compliance with the AI Act and the Act, issues decisions on infringements, establishes regulatory sandboxes and issues individual opinions (Article 6), and publishes in the Public Information Bulletin (Biuletyn Informacji Publicznej) a list of AI systems in respect of which a decision imposing a fine has been issued (Article 66(2)).

KRiBSI does not replace the President of UODO. If an AI tool processes personal data, the GDPR continues to apply. You need to establish the purpose and the legal basis (Article 6(1) GDPR), assess whether a data protection impact assessment is required (Article 35 GDPR), conclude a data processing agreement with the provider (Article 28 GDPR) – with an express clause on whether the data may be used to train the model – and check where the data is processed: a transfer outside the European Economic Area requires a basis under Chapter V GDPR. A typical problem: an employee pastes candidates' CVs into a public AI tool – with no agreement with the provider and no information for the candidates.

How we help:

  • agreements with AI providers – classification of the system, transparency, data processing agreement, confidentiality, rights to outputs, liability; see also contract law,
  • AI use policy – permitted tools, data that must not be entered, documented staff training (Article 4 AI Act),
  • impact assessment – DPIA for AI deployments and an analysis of whether the use may amount to a high-risk system,
  • transparency obligations – information for customers and candidates, disclosure of generated content (Article 50 AI Act),
  • inspections – preparing documentation, taking part in inspections by KRiBSI or the President of UODO, and representation in proceedings.

We start with an inventory – most companies do not know how many AI tools their employees actually use.

Where we operate

Our office is in Gdańsk at al. Grunwaldzka 87/91 lok. 10. We serve companies and institutions throughout the Tricity – Gdańsk, Gdynia and Sopot – and from Pruszcz Gdański, Rumia, Reda, Wejherowo, Kartuzy, Żukowo, Kościerzyna, Tczew, Starogard Gdański and Malbork. We also carry out implementations, audits and representation before the President of UODO remotely, for clients from all over Poland. Contact us.

Frequently asked questions

Does a small company have to keep a record of processing activities?

The exemption for companies employing fewer than 250 people does not apply if the processing is not occasional, is likely to result in a risk or includes special categories of data (Article 30(5) GDPR). Ongoing customer service or HR is regular processing, so in practice most companies should keep a record.

Does every breach have to be notified to UODO?

No. Notification is not required for a breach that is unlikely to result in a risk to the rights and freedoms of individuals (Article 33(1) GDPR). Every breach must, however, be documented internally (Article 33(5) GDPR), and it is worth recording the risk assessment in writing, because the authority may verify it.

Do I need a data protection officer?

Only in the cases set out in Article 37(1) GDPR – among others, in public bodies and where the core activities consist of monitoring individuals or processing special categories of data on a large scale. For other companies, designating a DPO is voluntary.

Is there an appeal against a decision of the President of UODO?

Not to a second-instance authority – the proceedings are single-instance (Article 7(2) u.o.d.o.). A complaint may be lodged with the Voivodeship Administrative Court within 30 days of service of the decision.

How long do I have to respond to a data access request?

One month from receiving the request, which may be extended by two months in complex cases or where there are many requests – the data subject must be informed of the extension before the first month expires (Article 12(3) GDPR).

Where can I sue a company for leaking my data?

In the Regional Court – it has jurisdiction over claims for infringement of personal data protection rules regardless of the value of the claim (Article 93 u.o.d.o.). You must show the infringement, the damage and a causal link.

Does GIODO still exist?

No. Since 25 May 2018, the supervisory authority has been the President of the Personal Data Protection Office. If your documents refer to GIODO, they most likely need updating.

Call: +48 790 377 775