security privacy
AI Act and your blog
Provider and deployer roles under Art. 50, what Quibo does, and a checklist for publishers.
This page is not legal advice. It summarizes the parts of EU Regulation 2024/1689 (the AI Act) that touch AI-generated blog content and explains what Quibo does about them, as of September 2026. Check with a lawyer for your own situation, especially if you publish on health, finance, law or news.
Two roles, two sets of duties
The AI Act separates the provider of an AI system from the deployer who uses it.
- Quibo is the provider. We operate a system that generates text and images. Art. 50(2) requires us to mark that output so it is machine-readable and detectable as artificially generated, within the limits of what is technically feasible.
- You are the deployer. Art. 50(4) applies to the act of publishing. It asks deployers to disclose that text was artificially generated when it is published to inform the public on matters of public interest.
Human review does not change our duty under 50(2): a pipeline that turns a keyword into a full article is not "assistive editing", so we mark everything we produce. Human review does change your position under 50(4).
When Art. 50(4) applies to you
The disclosure duty on deployers has a narrow scope and an important exemption:
- It applies to AI-generated text published to inform the public on matters of public interest. Typical examples: health, personal finance, legal topics, news, civic and political subjects.
- It does not apply when the content went through human review or editorial control and a natural or legal person holds editorial responsibility for its publication.
Most product, e-commerce and B2B marketing content is not "information on matters of public interest". If you do publish informational content in a sensitive vertical, the exemption is available to you, but only if the review is real. An authority looks at practice, not at the existence of an editor: approving thirty articles in four seconds is not editorial control.
Also relevant: Art. 4 asks providers and deployers to make sure the people who operate AI systems on their behalf have a sufficient level of AI literacy. It has applied since February 2025.
What Quibo does
| What | Where | Duty it supports |
|---|---|---|
contentRating: "AI-generated, human-reviewed" and an additionalProperty marking in the Article JSON-LD | Every article. Injected into the page on WordPress, Shopify, Ghost, HubSpot and Wix; on Webflow and Sanity only when a matching field exists; exposed as a feed field on Framer | Art. 50(2), on Quibo |
| Provenance record: provider, model ids, pipeline version, keyword, language, timestamp | Article page | Documentation and audit |
| XMP / IPTC "trained algorithmic media" metadata in cover images | WordPress, Sanity, Ghost and HubSpot uploads | Art. 50(2), on Quibo |
| Reader-facing disclosure line, on by default, translated, editable | Site settings | Art. 50(4), on you |
| Per-article review: edits, "Mark as reviewed", schedule and publish are logged with who and when | Article page, exportable | Evidence for the 50(4) exemption |
| Batch approval as a plan feature, per-article review as the default | Calendar | Keeps review substantive |
Details of each marking are on AI transparency.
Deployer checklist
- Review each article before it goes out. Open it, read it, fix what is wrong, then publish or schedule. Publishing and scheduling record your approval; "Mark as reviewed" records it without publishing.
- Keep the approval log. Owners and admins can export it as CSV or JSON at any time. It is the record that shows review happened, by whom and when. The trail is kept for as long as your account exists, with a snapshot of each article (title, URL, provenance) taken at log time, so it survives the removal of the article body 30 days after publishing and the deletion of the article or the site. Export the log on a schedule anyway and file it with your own records. See Approval log.
- Keep the disclosure line on for informational sites. If you publish on health, finance, law, news or civic matters, the reader-facing line is the simplest way to meet 50(4) even where you would qualify for the exemption. Turn it off only after you have decided, with advice, that your review process covers you.
- Do not remove the markup. Leave the JSON-LD and the image metadata in place. Check that a theme, SEO plugin or image optimizer on your CMS does not strip them. On Webflow and Sanity, make sure your collection or schema has a field for the JSON-LD, or it is not published at all.
- Train the people who use Quibo (Art. 4). Everyone who approves articles should know what the pipeline does and does not do: it drafts from search results and your brand profile, it can be wrong, and the person who approves is the one taking editorial responsibility.
- Use batch approval with care. It is meant for teams that already reviewed the drafts in the editor and want to schedule them in one go. It records your approval for every article in the batch.
Deadlines
- Art. 50 (transparency duties for providers and deployers) has applied since 2 August 2026. Penalties for breaching the transparency duties are in force from the same date.
- Art. 50(2) marking for systems that were already on the market before 2 August 2026 applies from 2 December 2026. Quibo ships the marking now.
- The European Commission's code of practice on AI content transparency, which will become the practical reference for how to mark text, was still in draft as of September 2026 (second draft March 2026). We will align the marking with the final version when it is published.
- The Digital Omnibus on AI (in force since 27 July 2026) postponed the high-risk regime; it did not touch Art. 50. Content marketing is not a high-risk use case under Annex III.
Territorial scope
The regulation applies to providers placing systems on the EU market and to deployers established in the EU. Quibo is established in the EU, so the provider duties apply to everything we generate, for every customer. Whether the deployer duties apply to you depends on where you are established and who your content targets.