AI transparency

Every article Quibo produces is drafted by a language model and reviewed by a person before it publishes. We say so in the places machines read and in the place readers read. This page lists exactly what is marked where. It describes what the product does; it is not a statement that your site or ours meets any particular law. For the legal background, see AI Act and your blog.

Structured data (JSON-LD)

Every article ships with a JSON-LD graph (Article, FAQPage, BreadcrumbList). The Article node carries two markings:

• contentRating: "AI-generated, human-reviewed". The older value "AI-assisted" under-described the process: the model writes the whole draft and a person reviews it, so that is what we say.
• additionalProperty: a list of PropertyValue entries, aiGenerated: true, humanReviewed: true, generator: "Quibo", so audit tools can detect the marking without parsing free text.

The node also names Quibo as creator (a SoftwareApplication). Editing the FAQ in the editor keeps these values; only the FAQPage node is rebuilt.

Where the graph ends up depends on the CMS:

• WordPress, Shopify, Ghost, HubSpot and Wix: written into the published page as a <script type="application/ld+json"> block.
• Webflow: written only when your collection has a matching Plain Text field: one named after custom code, head code, embed or script gets the complete <script type="application/ld+json"> tag, one named after JSON-LD, schema or structured data gets the bare JSON; otherwise it is not published.
• Sanity: written only when your post schema has a string field for it (schemaJsonLd, jsonLd or structuredData).
• Framer: exposed as the jsonLd field of the feed, for you to map in the sync plugin.

Provenance record

Each article stores a generation record next to its body: the LLM provider, the model id behind each tier the pipeline used, the pipeline version, the cover image model, the keyword, the language and the generation timestamp. It is written once when the article is assembled and never edited. You can read it in the Provenance block on the article page. It is not published to your CMS.

Cover images

Cover images are generated by a model, so they are synthetic media too. When a cover passes through Quibo on its way to your CMS, we embed an XMP packet in the file with:

• xmp:CreatorTool = "Quibo"
• Iptc4xmpExt:DigitalSourceType = trainedAlgorithmicMedia (the IPTC code for AI-generated media)
• dc:description set to the alt text

JPEG covers get an APP1 segment; PNG covers get an iTXt chunk. Pixels are never touched. This applies to WordPress (media library upload), Sanity (asset upload), Ghost (image upload) and HubSpot (file upload). Shopify, Webflow, Wix and Framer fetch the image themselves from its URL, so we cannot mark those files; the JSON-LD marking still applies to the article. Some CMS image pipelines strip metadata when they resize; check one published cover with a metadata inspector if this matters to you.

Reader-facing disclosure

By default, every published article ends with one italic line telling readers it was produced with AI assistance and reviewed before publication. The sentence is localized to the site language (English, Italian, Spanish, French, German, Portuguese, Dutch, Polish, Japanese) and you can replace it with your own wording, up to 500 characters.

Open a site under Sites and use the AI disclosure card to turn the line off or change the text (owners and admins only). The change applies to articles published from then on; the stored draft is never modified. The line is appended to every publish (WordPress, Shopify, Webflow, Wix, Ghost, HubSpot and Sanity) and to the Framer feed (html, plus a separate aiDisclosure field you can map on its own). The paragraph carries a data-ai-disclosure="true" attribute so it can be styled or detected.

Turning it off does not remove the JSON-LD marking. Whether you should keep it on depends on what you publish; see the deployer checklist in AI Act and your blog.

Human review trail

Every edit, "Mark as reviewed", schedule, unschedule, publish, content refresh and regeneration on an article is logged with who did it and when. The trail is visible on the article page and exportable as CSV or JSON by owners and admins. The trail is kept for as long as your account exists and carries a snapshot of the article (title, URL, provenance), so it survives the removal of the article body 30 days after publishing and the deletion of the article. Export the log regularly if you need it in your own records.

Article body

We do not claim personal experience the brand does not have. If your brand profile carries earned anecdotes, they stay in. We do not invent them.

Why we do not hide it

Detection scores are a moving target and pretending content is fully human when it is not:

• risks a spam classification under Google's policies on scaled content abuse;
• misleads readers;
• is the opposite of what the EU AI Act asks of providers of generative systems.

Disclosing while shipping well-sourced, on-brand, reviewed content is the position we are comfortable defending. Google's guidance evaluates whether content is helpful, not how it was produced; nobody can promise a ranking either way.