For businesses and teams
Rollout, data rules, the EU AI Act, and the questions a works council will ask.
This section is for people who have to defend a decision: rollout, data rules, regulation, employee participation. It leans deliberately towards Switzerland, Germany and Austria, because that is the part English-language guidance leaves out.
Orientation, not legal advice. These pages summarise publicly available legal sources and show a worked example of how to act on them. Law applies to specific facts, so the examples are there to be adapted rather than adopted. Each page says so on the page, not only here.
- An acceptable-use policy you can actually edit orientation
A short template to adapt, with notes on why each clause is there and which ones are usually wrong for a smaller organisation.
- Admin controls: what you can actually govern
The settings that exist, the defaults that differ between Team and Enterprise, and the gap where local sessions sit outside central control.
- The AI Act calendar, and which side of it you are on orientation
Transparency obligations under Article 50 came into force on 2 August 2026. Most organisations are deployers, and that changes which dates apply.
- The EU AI Act in fifteen minutes orientation
A risk-based law, not a technology law. Four tiers, and most people using these tools sit in the lowest one with two obligations that still apply.
- AI governance frameworks: which one, if you must pick
NIST AI RMF and ISO/IEC 42001 are not rivals. One is a free way to think, the other a paid way to prove — pick by whether you need a certificate.
- The EU AI Act's AI literacy obligation, practically orientation
In force since 2 February 2025. It covers your contractors too, no format is mandated, and the standard is proportionate rather than absolute.
- Disclosure: when to say a machine was involved orientation
Some contexts require it and have settled rules. Most do not. A workable test, and where the established norms already exist.
- Measure outcomes alongside AI adoption
Distinguish usage, reliance, and value, and compare complete developer tasks instead of treating message volume as productivity.
- Rolling out AI without a policy vacuum orientation
People are already using it. The question is whether they are doing so on accounts you chose, under terms you read.
- Seats, plans and quota planning for a team
Usage is uneven enough that averages mislead. Size from a pilot, and expect a handful of people to account for most of the consumption.
- Vendor questions: retention, processing and audit orientation
The questions worth asking any AI vendor, and what a good answer looks like. Written as questions because the answers change and yours may differ.
- What data may go into a model orientation
A classification scheme you can adopt, and the terms difference that most policies get wrong: consumer plans and commercial plans are not the same deal.