EU AI Act tracker: what buyers should verify before August 2026

Readers should treat this as a sourcing-cautious tracker, not a definitive legal explainer. The verified source set available for this draft does not include the core primary materials needed to state, with publication-ready confidence, which specific EU AI Act obligations apply in August 2026, to which actors, or which vendors currently publish which compliance documents. Because of that gap, the safest useful version is a practical verification guide: what to look for, how to record it, and which claims still need primary-source confirmation.

Summary box

– Use this piece as a buyer-side verification checklist, not legal advice.

– Do not assume every vendor will publish the same AI disclosure page or use the same terminology.

– Missing public documentation should be recorded as “not found at time checked”, not treated as proof of non-compliance.

– Date-checked note: this draft is limited by the current verified source set and should be updated once official EU legal text, Commission or AI Office guidance, and vendor primary documents are attached.

What changed

The main change is editorial stance, not a newly verified legal development. With the current source set, it is not supportable to publish firm claims about the August 2026 applicability sequence, actor-specific obligations, enforcement details, or vendor-by-vendor disclosure status. The article therefore focuses on evidence standards and buyer checks that remain useful even when legal and vendor sourcing is incomplete.

What is confirmed in this draft

• This topic works best as a living tracker rather than a one-off summary.
• The current verified sources are not sufficient for a full legal timeline explainer.
• Public policy pages, trust centers, product docs, and contract terms should not be treated as interchangeable evidence.

What still needs verification

The article still needs primary legal and vendor documentation before it can responsibly answer three core questions: what the August 2026 milestone specifically covers, whether any given disclosure must be public, and which named vendors currently provide which relevant documents.

How to read vendor AI documentation

A practical review should prioritize durable, citable materials over broad marketing language. In most cases, a buyer will learn more from product-specific terms, privacy documents, technical documentation, or trust-center material than from a high-level AI principles page alone. General guidance on helpful, people-first content supports being explicit about what is verified and what is not.

A useful evidence hierarchy

When comparing vendors, this order is usually safer than relying on promotional pages first:

1. Product-specific terms, enterprise terms, or related contractual documents.
2. DPA, trust-center, or formal compliance documentation.
3. Product documentation explaining scope, controls, or responsibilities.
4. Privacy, transparency, or AI policy pages.
5. Blog posts, FAQs, or marketing copy only when backed by stronger documents.

What “not found at time checked” should mean

That wording should be narrow and factual. It means the relevant statement was not located in the public materials reviewed at that time. It does not mean the vendor lacks an internal process, has breached any law, or has failed a compliance requirement.

Buyer checks to verify now

Even without a complete legal source stack, buyers can improve their review process immediately. The aim is to capture what a vendor actually states, where it states it, and whether the statement appears in formal documentation rather than in loose promotional copy.

Practical checklist

• Confirm which product, feature, model access tier, or plan each document covers.
• Separate consumer-facing claims from business or enterprise commitments.
• Record the page title, URL, and the last updated or last checked date.
• Check whether claims about data use, transparency, or safeguards are repeated in formal terms or trust materials.
• Escalate gaps to procurement, security, privacy, or legal review instead of guessing what a missing page means.

Minimum documents worth collecting

For a basic buyer-side file, it is practical to collect more than a single policy page. A stronger review set usually includes:

• an AI policy or transparency page, if public
• privacy documentation
• product-specific or enterprise terms
• any DPA or trust-center material
• product documentation describing scope, controls, or data use

Tracker template for vendor review

Because the verified source set does not include current vendor primary pages, the table below is a template rather than a populated comparison. It is still useful as a capture format for teams building a repeatable review process.

Old article audit: what to remove or rewrite

If this piece replaces an older version, the main risk is overclaiming from thin evidence. Statements about one August 2026 date applying in the same way to every actor, or claims that vendors must all publish the same kind of public page, should be removed unless they are tied to primary legal text and current documentation.

Claims that are too broad

• Any wording that treats August 2026 as a single all-at-once start point for every obligation.
• Any wording that equates missing public pages with non-compliance.
• Any vendor comparison built only from blogs, FAQs, or marketing copy.

Safer rewrite approach

Use verbs that reflect evidence strength. Where documentation is incomplete, phrases like “states,” “does not appear to state,” and “not found at time checked” are safer than definitive compliance conclusions.

Sections to update before a full publish push

A stronger future version should be rebuilt around primary materials, not assumptions. The biggest improvements should happen in the legal timeline section, the vendor comparison section, and any passage that implies a public disclosure duty without direct support.

Priority updates

1. Replace broad deadline language with citations to official legal text and implementation guidance.
2. Add vendor-by-vendor findings only after checking current primary pages directly.
3. Separate legal requirements from buyer best practice and from unresolved questions.
4. Keep explicit date-checked notes wherever claims may change over time.

What readers should watch next

The most meaningful update trigger is better sourcing. Once official EU legal text, current implementation guidance, and directly checked vendor documents are added, this can become a more detailed tracker instead of a process guide. Until then, the most responsible use of this article is as a checklist for documenting what is actually public and what still needs confirmation.

Sources

• Google Search Central: helpful content — Google Search Central.
• Google Search Central: AI-generated content — Google Search Central.
• Publications Office of the European Union DOI metadata record cited in the current source set.
• Hart Publishing chapter on Article 86 cited in the current source set.