Does EU AI Act apply to you?
Your product calls a language model, generates or manipulates content, or makes an automated decision that affects someone. Calling an API rather than training a model does not take you out of scope — you are a deployer, and for most transparency duties that is the role that carries them.
- ✓Who it covers: anyone in the EU who uses, or is subject to, an AI system you provide.
- ✓In force since Phased from 2 February 2025; transparency and GPAI obligations from 2 August 2025 and 2 August 2026.
- ✓Exposure if you ignore it: Up to €35 million or 7% of worldwide annual turnover for prohibited practices; up to €15 million or 3% for transparency failures.
What EU AI Act asks a product to do
Four obligations carry most of the weight for a digital product. They are what the clause set below is written against, and what the scan is looking for evidence of.
- ✓Tell people when they are interacting with an AI system rather than a person, at the point the interaction starts, unless it is obvious to a reasonably well-informed user.
- ✓Say whether prompts and outputs are used to train or fine-tune a model, and how to opt out — for most products this is a sub-processor's retention term rather than your own.
- ✓Disclose automated decision-making and profiling, and offer human review where a decision has legal or similarly significant effects. GDPR Article 22 and the CPRA's ADMT rules both land here.
- ✓Keep the list of model providers and vector stores current, because each one is a sub-processor and a data transfer as well as a dependency.
What Poliogo puts in your documents
Poliogo carries a clause set written against EU AI Act specifically. Every heading in the list below is a section the generator really writes, drawn from a library built from published regulatory text. Your stack is identified by pattern matching, not by a model, and the EU AI Act sections are appended from the library whether or not any AI is reachable. An AI model is used for one thing: drafting extra clauses from operational notes you type yourself.
- ✓Transparency Of AI Features — appended automatically when your stack and jurisdiction call for it.
- ✓Automated Decisions And Profiling Opt-Out — appended automatically when your stack and jurisdiction call for it.
- ✓AI Input Training Rules — appended automatically when your stack and jurisdiction call for it.
- ✓Global Retention Baseline — appended automatically when your stack and jurisdiction call for it.
- ✓Security Safeguards And Breach Notification — appended automatically when your stack and jurisdiction call for it.
Why a generated EU AI Act policy beats a template
A template describes a product someone imagined. This one describes yours, and notices when yours changes.
Written from evidence, not recall
No SDKManifests first, then a vendor-endpoint sweep over the source. A raw fetch to a payment or model API with no SDK installed — the normal shape of AI-generated code — is still detected.
The statutory sections are fixed text
The EU AI Act sections come from a pre-drafted library and are appended from it, not written by a model. Your stack is identified by pattern matching, so a model outage cannot remove a mandatory section. An AI model drafts only the extra clauses you ask for from your own operational notes.
You can explain every paragraph
Beside each clause sits a plain-English note: what it means, and which detected service made it necessary. You will not publish a sentence you could not defend to a customer.
It stays true after launch
DriftEach scan is diffed against the snapshot your documents were generated from. Adding a tracker on a Tuesday produces a pull request, not a quiet inaccuracy discovered during an audit.
The law moves too
A curated bulletin written against the statutes, filtered to the changes your own stack makes relevant — not a news feed. Included from Starter.
One product, several regimes
Most products serve more than one jurisdiction. The regional clause sets stack rather than compete, so a policy can satisfy the GDPR, CCPA and Israeli law at once without three documents.
How it works
A Git repository, a hosting account, or the repository your no-code builder syncs to. Source is read in flight rather than stored, and nothing in it changes except through a pull request you approve.
Every service your code calls, in plain English, with the evidence for each. This is what decides which EU AI Act disclosures your documents need — a product with no advertising pixel should not carry an advertising disclosure.
Privacy policy, cookie policy and — from Starter — terms of service, with the EU AI Act sections appended from the clause library. Those sections are fixed text, not written by a model.
Re-scan whenever you like on any plan, or let a paid plan watch in the background. A stack change becomes a pull request with a plain-English diff, and merging it is the approval.
Questions people ask
Does EU AI Act apply to me?
Your product calls a language model, generates or manipulates content, or makes an automated decision that affects someone. Calling an API rather than training a model does not take you out of scope — you are a deployer, and for most transparency duties that is the role that carries them. If you are unsure, the honest answer is that most products serving anyone in the EU who uses, or is subject to, an AI system you provide are in scope, and the cost of assuming otherwise is up to €35 million or 7% of worldwide annual turnover for prohibited practices; up to €15 million or 3% for transparency failures.
What does Poliogo actually write for EU AI Act?
Poliogo carries a clause set written against EU AI Act specifically. Every heading in the list below is a section the generator really writes, drawn from a library built from published regulatory text. Your stack is identified by pattern matching, not by a model, and the EU AI Act sections are appended from the library whether or not any AI is reachable. An AI model is used for one thing: drafting extra clauses from operational notes you type yourself.
Is a generated policy good enough, or do I need a lawyer?
For routine day-to-day compliance — a privacy policy that matches your product, a working consent banner, and keeping both current as the product changes — this does the heavy lifting from clause logic built from published regulatory text. It does not replace counsel for a regulatory dispute, a corporate transaction or anything unusual about your situation. Poliogo is a compliance management technology platform, not a law firm, and this page is not legal advice.
How does it know what my product does with data?
It reads the project. Dependency manifests first, then a sweep of the source for known vendor endpoints — the URLs your fetch, axios and httpx calls address — so a raw HTTP call to a payment or model API is detected even with no SDK installed. Environment variable names are read as evidence; their values never are.
What happens when the law changes?
Regulation monitoring is a curated bulletin written against the statutes themselves, not a news crawler, and it is filtered to the changes your own stack makes relevant. It is included from Starter. When a change affects you, the update arrives with a plain-English explanation of what it asks for.
Can I see the EU AI Act sections before I commit to anything?
Yes. Connect a project on the Free plan, run the scan and generate the documents — the full text, with the plain-English explanation beside every clause saying what it means and which detected service made it necessary. Nothing is published until you approve it, and no card is asked for.
Generate your EU AI Act documents
Connect a project and see the detected stack in under 60 seconds. Free plan, no credit card, and nothing is published until you approve it. Poliogo is a compliance management technology platform, not a law firm, and this page is not legal advice.
Start free — no credit cardPoliogo is an automated code analysis and document display tool, not a law firm. Poliogo does not provide legal advice, representation, or guarantees of statutory compliance, ADA/WCAG certification, or legal immunity. Visual banners and generated documents are advisory tools and do not substitute for professional legal review.