AI register
Document the system, provider, role, first use, version, purpose, changes, evidence and owner.
AI compliance Munich
Cleero takes Munich businesses from initial AI Act orientation to a reliable AI register, clear ownership, practical actions and traceable evidence.
From general AI assistants to specialist systems
Teams often use AI before purpose, data, providers, versions, approvals and changes are documented. Cleero creates transparency first and derives practical guardrails rather than blanket bans.
Document the system, provider, role, first use, version, purpose, changes, evidence and owner.
Assess legal basis, processing terms, transfers, training data, confidentiality and DPIA needs.
Identify provider, deployer or other roles and the resulting duties.
Define approved tools, prohibited inputs, approvals, controls and training.
Turn official orientation into action
The Federal Network Agency’s free AI Compliance Compass provides an initial, non-binding orientation. Cleero does not duplicate it: we turn the outcome into an operating system of owners, actions, target dates and evidence.
Open the official compass ↗Narrow down the system, role and possible risk level.
Assign owners, concrete checks and a realistic timeline.
Bring versions, decisions, approvals and records together in the Evidence Pack.
Maintain a traceable history for existing AI
A timeline assessment needs findable facts. Cleero records the information required for review instead of presenting an automatic legal conclusion.
Provider, deployer or another role, plus placement on the market or putting into service.
Provider, product, current version and supporting version record.
Compare the original and current intended purpose.
Record the date and describe design, functional and purpose changes factually.
Link release notes, contracts, screenshots or change records.
Open, no indication or individual legal review required.
The local AI register is now included in the Cleero app. Entries remain on the device and can be exported with the working file.
Open the AI register in the app →Article 111(2) is a transition rule for certain high-risk AI systems placed on the market or put into service before 2 August 2026. It is not a general exemption for all existing AI. Article 5 and other applicable laws require separate assessment. Cleero does not automatically determine whether a change is significant.
Cleero 5
Map actual systems and informal use cases.
Determine roles, data flows, risks and transparency duties.
Set actions, approvals, ownership and required evidence.
Track versions, purpose and functional changes and train teams.
Local context
Cleero integrates AI governance with privacy processes instead of creating parallel lists and conflicting ownership. Individual legal questions are reviewed only under a separately agreed legal mandate.
A quick first assessmentArticle 50 quick check with full assessment ↗Frequently asked questions
Not as a blanket yes or no. Purpose, input data, provider terms, transfers and internal approval all matter.
At minimum: system, provider, role, date placed in service, version, original and current purpose, changes, owner, data, approval, evidence and next review.
No. Duties depend on role, system and use, including direct AI interaction, synthetic content, deepfakes and certain public-interest text.
Where you train or adapt your own model, collect publicly accessible web data yourself or through a third party, or obtain pre-assembled training datasets. It is not automatically needed for ordinary use of a ready-made AI tool.
No. It needs legal, privacy, IT, security, business owners and management decisions.
This content provides general guidance. Legal advice and binding individual legal assessments are not Cleero services.
Your next clear step
Tell us briefly where you stand. We will be open about what matters and which next step makes sense.