No general free pass
TheSEO settles per deployment whether it is a provider, a deployer, a distributor or another actor. The customer can carry obligations too. This position is tested against the concrete functionality, the contracts and the model chain before go-live. One thing worth being plain about: TheSEO is established in the Netherlands, so the EU AI Act is the regulation we build to, and if you are in Ireland the same regulation reaches you directly.
If you are in the United Kingdom, we deliberately do not state here which rules apply to you. We have not looked them up with a source we can show you, and a page that guesses at a regulator is worse than a page that stays quiet. Ask your own adviser, and hold us to what this page does say about our own design.
Design rules
- AI output is recognisable as AI supported wherever transparency requires it;
- source provenance, version and human review are recorded;
- agents get a limited set of tools and actions;
- users receive instructions about limitations and appropriate oversight;
- incidents and material model changes get a review.
Not without a separate assessment
Jarvis is not deployed by default for prohibited practices or for high risk decisions about, among other things, employment, education, credit, essential services, biometrics or law enforcement. A customer may not quietly rebuild a general AI assistant into a regulated decision system.
Transparency and AI literacy
The organisation has to know when it is using AI, which sources and limitations apply and who carries final responsibility. Onboarding and documentation support that, but they do not replace training aimed at a role.
Changes
The EU AI Act, its guidance and its national implementation keep developing. A planned legal monitor may draft change proposals; publication and contract impact require human review.