Blog / · 5 min read
AI Act: on August 2, 2026, AI builders meet useful paperwork
The AI Act becomes fully applicable on August 2, 2026 for several obligations. What this changes for AI products, without legal panic.
August 2, 2026 is close. And as usual with regulation, many builders will pretend not to see the date until the week before.
Bad idea.
The AI Act is not only a lawyer-in-a-blazer topic. It is becoming a product constraint. Not necessarily a disaster. Not necessarily an innovation killer. But a constraint, yes.
And one that touches concrete things: documentation, transparency, labeling, model choices, internal policies, traceability.
The kind of thing you want to add early, while the product is still simple, not six months later when an enterprise customer asks for a compliance PDF by Friday.
The date that matters
The AI Act entered into force on August 1, 2024. Its application is phased. Full application is scheduled two years later, on August 2, 2026, with exceptions depending on the obligation.
For generative systems, one part becomes particularly visible: transparency obligations around AI-generated or manipulated content.
The European Commission has also published practical material to help actors comply, especially around general-purpose AI models and the marking of generated content.
In plain terms: Europe is no longer saying “one day you should pay attention”. It is starting to provide the manual.
What changes for a small AI product
Take a regular SaaS product in 2026. It generates sales replies, rewrites emails, produces social media images, summarizes customer calls, enriches a CRM record.
Not a frontier lab. Not OpenAI. Not Anthropic.
Just a product using models.
The questions come quickly:
- does the user know when content is AI-generated?
- should some outputs be marked?
- do we keep track of which model was used?
- can we explain to a customer where a response came from?
- do we have a clear policy on data sent to providers?
- do we distinguish assistance, automation, and decision-making?
These are not abstract questions. They change the interface.
A “generate” button is not always enough. Sometimes you need a state, a label, a history, a way to retrieve the source.
Compliance starts in product design
The classic reflex is to push this to legal. Wrong reflex.
A lot of AI compliance lives inside the product:
- action labels;
- logs;
- permissions;
- explanations shown to users;
- exports;
- human control;
- how a recommendation is presented.
If your interface says “validated answer” when the model only produced a plausible summary, you already have a product problem before a legal problem.
If your tool automatically sends a generated email without making that clear, same thing.
If your agent modifies CRM data with no usable journal, you are manufacturing regulatory debt.
The good news: the first layer is not that hard
For a product team, the first serious layer is simple.
Log generations. Who asked what, with which model, when, on which data, for what result. You do not need a ridiculous data warehouse. A clean journal already helps.
Separate draft from action. AI can propose. The user validates. If you automate without validation, make it explicit in the design and permissions.
Mark sensitive content. Generated images, published text, deepfakes, manipulated content: these cases need to be visible in the workflow.
Document providers. Models, regions, retention policies, enterprise options. When a customer asks, you do not start an archaeological dig.
Write one internal page. Not a thesis. A page saying what you use, why, where data goes, how to shut it off, and who owns it.
It sounds boring. It is a little boring. It is also what separates a prototype from a sellable product.
The wrapper trap
Many AI startups are wrappers with good UX. That is not an insult. A good wrapper can create a lot of value.
But a wrapper cannot delegate all responsibility to the underlying model.
“OpenAI / Anthropic / Google handles it” will not always be enough. The provider handles its model. You handle the usage context.
The same model can write a joke, prefill an HR diagnosis, generate a follow-up email, or assist a credit decision. The risk is not the same. The interface should not be either.
The product is responsible for the situation it creates.
What I would do now
If I were launching an AI product in Europe today, I would put these tasks in the backlog immediately:
- a registry of AI features;
- minimal logging for important generations;
- a clear distinction between suggestion and automatic action;
- AI-content labels where content leaves the product;
- a security / AI page for customers;
- a deletion or export procedure for traces;
- a switch to disable some AI features per workspace.
Nothing revolutionary. Just clean product work.
Most importantly: I would not leave it for “later”. Later is when the data model is already wrong, the UX lies by accident, and the enterprise customer asks for a formal answer.
My take
The AI Act will create useless paperwork. Of course. Every regulation does.
But it will also force a hygiene many AI products keep postponing: explain what the AI does, keep traces, do not dress up suggestions as truth, do not quietly automate sensitive decisions.
Honestly, that is not a bad thing.
The AI market has run on “trust me bro” for too long. Products that can clearly say what they do, what they do not do, and how they control their models will gain credibility.
Compliance will not make a bad product good.
But it can prevent a promising product from becoming unsellable at the first real customer conversation.
Sources
Keep reading