Artificial Intelligence Policy Tracker
Search
Menu

AI compliance obligations

Practical requirements extracted from policy instruments, with the source article, the actors they bind, evidence examples and original framework mappings. Legal requirements are marked; everything else is voluntary guidance.

Results

5 of 117 obligations match · Download these as CSV

Legal requirement Governance and accountability European Union

Law-enforcement deployers must obtain authorisation for post-remote biometric identification and report annually

EU AI Act · Article 26(10)

A deployer using a high-risk post-remote biometric identification system in a criminal investigation must request authorisation from a judicial or independent administrative authority in advance or within 48 hours, unless the use is only the initial identification of a potential suspect on objective and verifiable facts. Use is limited to a targeted search; if authorisation is refused, use stops and the data is deleted. No adverse legal decision may rest solely on the output, each use is documented, and the deployer reports annually to the market surveillance and data protection authorities.

Verified (a factual check against the official source, not a legal review) Applies from 2 Dec 2027
Legal requirement Prohibited practices European Union

Do not deploy or provide AI for prohibited practices

EU AI Act · Article 5

Article 5 bans placing on the market, putting into service or using AI for listed practices, including subliminal or manipulative techniques that cause significant harm, exploitation of vulnerabilities, social scoring by public or private actors leading to detrimental treatment, untargeted scraping of facial images to build recognition databases, emotion recognition in workplaces and education institutions except for medical or safety reasons, biometric categorisation to infer protected characteristics, and real-time remote biometric identification in publicly accessible spaces for law enforcement outside narrow exceptions.

Pending review (a factual check against the official source, not a legal review) Applies from 2 Feb 2025
Legal requirement Prohibited practices Texas (United States)

Governmental entities must not use AI for biometric identification from public data without consent where it infringes rights

Texas Responsible AI Governance Act (TRAIGA) · Business and Commerce Code Section 551.054

A governmental entity may not develop or deploy an AI system for the purpose of uniquely identifying a specific individual using biometric data, or of gathering images or other media from the internet or another public source without the individual's consent, where doing so would infringe a right guaranteed under the United States or Texas constitutions or violate state or federal law. The Act preserves lawful uses that comply with existing biometric-privacy law.

Verified (a factual check against the official source, not a legal review) Applies from 1 Jan 2026
Legal requirement Prohibited practices Texas (United States)

Governmental entities must not use AI for social scoring

Texas Responsible AI Governance Act (TRAIGA) · Business and Commerce Code Section 551.053

A governmental entity may not develop or deploy an AI system that evaluates or classifies natural persons or groups on the basis of their social behaviour or personal characteristics, with the intent to calculate or assign a social score or similar valuation that leads to detrimental or unfavourable treatment unrelated to the context in which the data was collected, or that is unjustified or disproportionate to the behaviour.

Verified (a factual check against the official source, not a legal review) Applies from 1 Jan 2026
Legal requirement Public-sector use and procurement European Union

Public authorities must register their use of high-risk AI and must not use unregistered systems

EU AI Act · Article 26(8); Article 49(3) and 49(4)

Deployers that are public authorities or Union institutions, bodies, offices or agencies must register their use of an Annex III high-risk AI system in the EU database before putting it into service. If they find that the system they intend to use has not been registered in the database by its provider, they must not use it and must inform the provider or distributor.

Verified (a factual check against the official source, not a legal review) Applies from 2 Dec 2027

Frequently asked questions

What is an obligation on this site?

A single practical requirement pulled out of an instrument and stated on its own: keep a risk management system, log incidents, document training data, provide human oversight, and so on. Each one cites the article or section it comes from so you can check it against the source.

Does a voluntary obligation have legal force?

No, and every obligation is labelled either a legal requirement or voluntary guidance. Voluntary items still matter in practice, because procurement questionnaires and auditors ask about them, but only the binding ones carry legal consequence.

How do I find the obligations that apply to my organisation?

Filter by jurisdiction, category, actor, sector or use case. The applicability check asks a short set of questions and returns the duties that may reach you. It is an educational screen, not a legal determination, and it says so.

Why do some instruments have no obligations listed?

Because nobody has broken them out yet. Most instruments are recorded at summary level first; obligations are added jurisdiction by jurisdiction. The coverage and open-gaps pages publish exactly what is missing rather than hiding it.