GDPR and AI: what a Belgian freelancer needs to know in 2026
Many freelancers assume the GDPR is a large-company topic. It is not, and Article 3 of the regulation says so in plain terms. Here is what actually applies to one person using an AI tool, with the official texts, without jargon.
I am not a lawyer. What I can do is read the texts and tell you what they say, with exact references so you can check every sentence. Every statement below is tied to a regulation article or an official source, listed at the bottom.
The GDPR applies to you, even if you work alone
The regulation applies to any undertaking established in the European Union that processes personal data, regardless of size, and even if the processing takes place outside the EU (Article 3(1)). There is no headcount threshold and no exemption for freelancers. If you process names, addresses, emails, photos or health data in your business, you are the controller of that processing.
The corollary is useful: obligations are proportionate to what you do. A freelancer sorting client emails does not need the register of a hospital. But they do have obligations.
The GDPR does not stop at the EU border
The regulation also applies to companies outside the EU that offer goods or services to people in the Union, or that monitor their behaviour (Article 3(2)). In practice: a US provider processing your clients' data on your behalf does not escape the framework, and you must be able to show the transfer is framed.
The geographic scope is wider than the EU-27: the GDPR is in force across the European Economic Area, meaning the Union plus Norway, Iceland and Liechtenstein, since 20 July 2018 (EEA Joint Committee Decision No 154/2018).
Two regulations, two authorities: do not confuse them
| GDPR | AI Act | |
|---|---|---|
| Text | Regulation (EU) 2016/679 | Regulation (EU) 2024/1689 |
| Subject | Personal data protection | Regulation of AI systems |
| Authority in Belgium | APD (Data Protection Authority) | BIPT (main market surveillance authority) |
| Penalties | Up to €20 million or 4 % of worldwide turnover | Up to €15 million or 3 % (€35 million or 7 % for prohibited practices) |
The timeline moved in 2026: the Digital Omnibus on AI (Regulation (EU) 2026/1744, published 24 July 2026, in force 27 July) postponed the high-risk obligations. Article 50 transparency obligations still apply since 2 August 2026: telling users they interact with AI, and marking generated content. Generative systems placed on the market before 2 August 2026 have until 2 December 2026 for the technical marking part. On the same 2 December 2026, a new prohibited practice applies (non-consensual sexual content and AI-generated child sexual abuse material). Annex III high-risk systems move to 2 December 2027, systems embedded in regulated products (Annex I) to 2 August 2028, and national regulatory sandboxes to 2 August 2027.
For a freelancer, Article 50 means one simple thing: if you use an agent to talk to your clients, those clients must know they are talking to an automated system. That is not a technical constraint, it is a sentence in your communication.
Your AI provider is a processor, and you need a contract
When a provider processes data on your behalf, it is a processor under Article 28, and it processes that data only on your documented instructions. A processing agreement, usually called a DPA, is mandatory. It is not a formality: it is what lets you answer a client who asks where their data goes.
Three questions for any provider, including me:
- Where are the data hosted, in which country, with which provider?
- Are the data used to train models?
- Is there a signed DPA, and what does it say about deletion?
Transfers outside the EEA require safeguards
A transfer to a country outside the European Economic Area requires appropriate safeguards: an adequacy decision by the Commission, or standard contractual clauses, under Chapter V of the regulation (Articles 44 to 49). In other words: "the server is in Europe" is not a sufficient answer if the AI model is called at a provider located elsewhere, or if technical support can access the data from a third country.
This is exactly where wording matters. A serious company does not say "100 % Europe": it says where the computation runs, where the data is stored, and which subcontractors are involved. That is what I call optimised sovereignty: data stays under the GDPR framework, hosting is European, and technical dependencies are named.
The right to erasure applies to your clients too
Everyone has the right to obtain erasure of their personal data, under conditions (Article 17). In practice, if a client asks you to delete their exchanges, you must be able to do it, which means knowing where those exchanges are stored. An agent keeping a history in a third-party tool with no purge option is a legal problem waiting.
What happens to companies outside the framework
Two levels, set by Article 83: up to €10 million or 2 % of worldwide annual turnover for security and record-keeping failures, and up to €20 million or 4 % of worldwide annual turnover for serious breaches, including principles, data subject rights and transfers outside the EU. The higher amount applies.
In practice, for a freelancer, the immediate risk is not the fine: it is the client who asks about data security and gets no clear answer.
What I actually do at TARSystems
- The agent runs on a secure VPS hosted in the European Union, with daily backups kept for 30 days.
- Exchanges go through Matrix, via the Element app, on a server self-hosted on your VPS and administered by TARSystems: conversations never pass through a third-party service.
- The model provider (Ollama Cloud) processes requests transiently: no storage, no training on your data. A nuance worth knowing: Ollama hosts its compute mainly in the United States and may route to Europe, so a request can be executed outside the EEA without being stored. That is an execution transfer, to be documented in the DPA and covered by contractual safeguards.
- Your professional mailbox stays on your usual infrastructure: I do not move it to my servers.
What that does not mean: that everything is magic. An agent reading your mail processes personal data, and that is why the framework exists. The right approach is not to avoid it, it is to know what happens and be able to document it.
The six-point checklist
- Identify what you process: names, emails, addresses, health data, financial data. A table is enough to start.
- Check your legal basis: contract, legal obligation, legitimate interest, consent when required.
- Require a DPA from every provider touching that data, including the AI tool.
- Know where the data is and which subcontractors are involved, with transfer safeguards if one is outside the EEA.
- Plan deletion: how you erase a client's data on request, and within what delay.
- Inform: an up-to-date privacy policy, and an explicit mention when a client talks to an agent rather than a human (Article 50 of the AI Act).
My privacy policy and terms of use are public and dated: they describe processing, subcontractors and retention periods. If something is missing, that is a defect, and I would rather be told.
Ask the uncomfortable question, before signing
"Where does my data go, and who can read it?" A 20-minute demonstration, with the answer to that question in writing, no commitment.
Request a demo Read the privacy policy Terms of useOfficial sources
- Regulation (EU) 2016/679 (GDPR), full text, Articles 3, 17, 28, 44 to 49 and 83: EUR-Lex, CELEX 32016R0679.
- Article 3 (territorial scope): gdpr-info.eu/art-3-gdpr. Article 17 (erasure): gdpr-info.eu/art-17-gdpr. Article 28 (processor): gdpr-info.eu/art-28-gdpr. Chapter V (transfers): gdpr-info.eu/chapter-5. Article 83 (fines): gdpr-info.eu/art-83-gdpr.
- EEA Joint Committee Decision No 154/2018 of 6 July 2018, GDPR entry into force in the EEA: EUR-Lex, EEA 154/2018. See also EFTA, "GDPR entered into force in the EEA": efta.int.
- Regulation (EU) 2024/1689 (AI Act), Article 50 and application timeline: EUR-Lex, CELEX 32024R1689. Official Belgian timeline: BIPT, application of the AI Act.
- Data Protection Authority (Belgium): APD.
- TARSystems privacy policy: tarsystems.be/politique-confidentialite.html. Terms of use: tarsystems.be/conditions-utilisation.html. Legal notice: tarsystems.be/mentions-legales.html.