Guide

AI in Poland’s public sector and local government: uses, AI Act, GDPR and funding

This guide is for municipal secretaries and treasurers, heads of departments and managers of public bodies in Poland who are wondering whether and how to use AI in their office. We show the uses that make sense today and explain what the AI Act, GDPR and the Code of Administrative Procedure really say about them. Finally, we cover funding and a plan for the first year.

Author: Kacper Włodarczyk, CEO of ALGORCOMPPublished: May 30, 2026Reading time: 11 min readArtificial intelligenceFor: Universal
AI in Poland’s public sector and local government: uses, AI Act, GDPR and funding

Where AI can help a public office today

The best first uses have three features. They recur every day, they concern internal work and they do not decide on residents’ rights. That way, an official catches any AI error before anything leaves the office.

The table below lists typical uses, with the split of work between AI and the official. The last column shows how such a use usually looks from the AI Act’s point of view. However, the final assessment always has to be made for the specific system.

Typical uses of AI in a public office and how they are assessed
UseWhat AI doesWhat stays with the officialAssessment under the AI Act
Incoming correspondenceReads the letter, identifies the matter, suggests the unit and the person handling itApproving the assignment, unusual casesUsually not high-risk – a narrow supporting task
Searching council resolutions, orders and proceduresAnswers staff questions and points to the source documentChecking the answer against the sourceUsually not high-risk
Drafting letters and replies to freedom of information requestsPrepares a draft reply based on previous cases and regulationsContent, signature and responsibilityUsually not high-risk
Information chatbot on the websiteAnswers questions about opening hours, required documents and feesKeeping information up to date, individual casesObligation to disclose that it is AI (Article 50)
Assessing eligibility for public assistance benefits, e.g. allowances and supplementsAnalyses the application and suggests a decisionThe decisionHigh-risk (Annex III, point 5)
Pre-screening candidates for jobs in the officeAssesses and ranks candidatesThe hiring decisionHigh-risk (Annex III, point 4)

What the AI Act really says about public administration

The AI Act does not treat every system in a public office as high-risk. Annex III lists specific areas. For public administration, point 5 matters most: systems used by an authority to assess eligibility for essential public assistance benefits and services, and to grant, reduce or revoke those benefits.

High-risk systems also include, among others, those used in recruitment (point 4) and in migration and asylum matters (point 7). By contrast, a system that performs only a narrow supporting task, such as routing letters, is usually not high-risk (Article 6(3)). The condition is that it must not replace human assessment or materially influence it.

If an office uses a high-risk system, it has the deployer obligations under Article 26. It must use the system in line with its instructions, ensure human oversight and keep the system’s automatically generated logs. As a body governed by public law, it must also assess the impact on fundamental rights before putting the system into use (Article 27).

The deadlines are spread out over time. Some obligations already apply, while others will only apply from December 2027. The key dates are below.

  • From 2 February 2025: prohibited practices (Article 5) and the obligation to build staff knowledge of AI (Article 4).
  • From 2 August 2026: telling people that they are talking to AI, and labelling AI-generated content (Article 50).
  • From 28 October 2026: inspection powers of the Polish supervisory authority, the Commission for the Development and Safety of Artificial Intelligence.
  • From 2 December 2027: obligations for high-risk systems listed in Annex III, including the fundamental rights impact assessment.
AI in Poland’s public sector and local government: uses, AI Act, GDPR and funding

AI, administrative decisions and deadlines under the Code of Administrative Procedure

The Polish Code of Administrative Procedure (KPA) does not mention AI, but it sets clear deadlines. Under Article 35, a case is to be dealt with without undue delay. A case that requires investigation must be dealt with within one month at the latest, and a particularly complex one within two months.

AI can help meet these deadlines. It sends reminders when a deadline is approaching, compiles the case documents and prepares a draft decision. However, it should not issue decisions on its own.

GDPR also limits this. Article 22 gives everyone the right not to be subject to a decision based solely on automated processing if it produces legal effects. In public administration, an exception usually requires an explicit legal basis, and for typical local government decisions there is none. That is why the official must genuinely assess the case, not just approve the AI’s proposal.

GDPR and residents’ data: where to start

Today, the biggest risk does not lie in advanced systems but in everyday habits. An official who pastes the content of an application into a free chatbot on a private account is passing a resident’s data to a company the office has no contract with.

That is why the first step should be rules for using AI and a tool the office controls. Many offices already have Microsoft 365. In that case, it is worth checking which AI tools the current agreement covers and what data protection terms it includes.

For every new use, go through the points below with your data protection officer. Every public office is required to have one, so there is no need to look for an external adviser to get started.

  • Are we processing personal data, and if so, what data and on what legal basis?
  • Does the tool provider have a data processing agreement (DPA) with us (Article 28 of GDPR)?
  • Where is the data processed, and can the provider use it to train models?
  • Is a data protection impact assessment needed (Article 35 of GDPR)? For high-risk systems, it can be combined with the assessment under Article 27 of the AI Act.
  • Who in the office checks AI output before it reaches a resident?
An official reviews a letter with an AI-prepared summary in a document workflow system

In a public office, AI should prepare a case for decision, not make the decision for the official.

Invoices, KSeF and JPK in a public office and a municipal company

A municipality, together with its budgetary units, is a VAT taxpayer, so it is covered by KSeF, Poland’s National e-Invoicing System. Since 1 February 2026, all taxpayers have received invoices from businesses through KSeF. Taxpayers with sales above PLN 200 million in 2024 had to issue invoices in KSeF from that date, and everyone else from 1 April 2026.

Most invoices from domestic suppliers therefore arrive as structured data rather than PDFs. Here, AI is useful for writing the invoice’s substantive description, matching it to a contract and checking whether the amount agrees with the order.

JPK_CIT, the accounting books sent electronically to the tax office, usually does not apply to the municipality itself. The Corporate Income Tax Act exempts local government units from tax on income defined in the Act on Local Government Revenue, and budgetary units entirely. The JPK_CIT obligation may, however, apply to municipal companies, which are ordinary corporate income tax payers.

Translation and serving foreign nationals

AI tools translate simple texts well and can make it easier to talk to a foreign national at the counter. They also help to understand a letter in a foreign language before it goes to a translator.

There is a limit, however. The Polish Language Act (Article 5) requires bodies performing public tasks to carry out official acts in Polish, unless a specific provision states otherwise. AI translation can therefore help with communication, but it does not replace the Polish version of a letter or a sworn translation where one is required.

For information materials for residents, such as leaflets or websites, AI works well for a first draft. Before publication, however, the text should be reviewed by someone who knows the language.

Where to find money for AI in a public office

The National Recovery Plan (KPO) is in its final stage, and it is not worth planning a new project around it today. Calls for proposals for local governments in digitalisation are announced by, among others, the Ministry of Digital Affairs and the Digital Poland Projects Centre (CPPC), which runs the European Funds for Digital Development programme (FERC). One example is the Digital Development Clubs (Kluby Rozwoju Cyfrowego), funded from the European Funds for Social Development programme (FERS).

Some calls are also run by regional (voivodeship) authorities under regional programmes. The easiest way to check the current list is the grant search tool on funduszeeuropejskie.gov.pl, filtering by applicant type.

Also remember public procurement law. Buying implementation services and licences worth PLN 130,000 net or more (the threshold in Article 2 of the Public Procurement Law, Pzp) requires a procurement procedure. Below the threshold, the office’s internal rules apply.

A plan for the first year

The plan below assumes that the office is starting from scratch and wants to limit risk. Order matters more than pace: first rules and knowledge, then one pilot, and only then expansion.

Take a hypothetical municipality with 60 people working in its office. For the pilot, it chooses routing incoming correspondence, because this concerns every unit and decides nobody’s rights.

  • Months 1–2: rules for using AI, staff training (Article 4 of the AI Act), choosing a tool the office can use lawfully, and a conversation with the data protection officer.
  • Months 3–4: choosing one internal process and measuring the current state, e.g. how many letters arrive each day and how long it takes to route them.
  • Months 5–8: a pilot in one unit. AI proposes, the official approves every proposal, and the team records errors.
  • Months 9–12: assessing the results, deciding whether to extend to the whole office and choosing a second process. If a high-risk system is planned, this is a good moment to prepare the impact assessment before December 2027.

Typical risks and how to limit them

AI projects in public offices rarely fail for technical reasons. More often, the obstacles are people’s concerns and a lack of clear responsibility. The risks below can be reduced before you even start.

  • Officials’ fears about their jobs. Say plainly that the aim is less retyping and more time for residents’ matters. In public administration, cutting jobs is usually not the aim of such projects.
  • An AI error made in public. A mistake in a reply to a resident quickly reaches the local media. That is why, at the start, every piece of content leaving the office must go through a human.
  • Dependence on a single provider. State in the contract that the configuration, instructions and data belong to the office and can be transferred.
  • No project owner. Appoint a head of unit who is responsible for the pilot’s results, not just the IT person.

Related topics in the knowledge base

Read next

FAQ

AI in the public sector – frequently asked questions

Questions asked by municipal secretaries, treasurers and managers of public bodies.

Is it worth starting with AI in a small municipal office at all?
Yes, but modestly. In a small office, a tool available under existing licences, written rules and one use case, such as draft replies to typical letters, are usually enough. Building your own system rarely pays off there.
Can officials use the free version of ChatGPT?
Not with residents’ data. Free accounts give the office neither a data processing agreement nor control over the data. For work with the office’s documents, choose an organisational version of a tool, covered by a contract with the provider.
Is the office bound by its website chatbot’s answers?
The chatbot should provide only general information, such as which documents are required, and clearly refer individual cases to an official. It is worth stating this next to the chat window. The content it relies on must be updated together with the service information sheets.
Do we need an AI specialist in the office?
Not to begin with. You need a person who knows the process and can make decisions, an IT administrator or an IT services company, and a data protection officer. Specialist knowledge can be provided by a supplier selected in line with public procurement law.
Are municipal companies subject to the same rules?
As regards the AI Act and GDPR, broadly yes, and when providing public services they may also be required to carry out a fundamental rights impact assessment. They differ on tax: a company is a corporate income tax payer, so the JPK_CIT obligation may apply to it.

About this page

About the author

Kacper Włodarczyk — CEO of ALGORCOMP

Kacper Włodarczyk

CEO of ALGORCOMP

Kacper specializes in implementing Microsoft 365 Copilot, Copilot Studio, Power Platform (Power Automate, Power Apps, SharePoint) and AI agents for mid-sized B2B companies in Poland. He leads dozens of projects covering AI strategy, Power Platform governance, document workflow automation and sales processes. In his writing he focuses on the practical side of AI adoption in organizations — from the first proof of concept to company-wide rollout — with particular attention to data security, compliance (GDPR, NIS2, the AI Act) and return on investment.

Meet the team

Want to choose a safe first AI pilot for your office?

In a free consultation, we will help you identify a process with low legal risk and assess what it requires under the AI Act and GDPR.

Featured

Related articles