Article 50 of Regulation (EU) 2024\/1689 \u2014 the AI Act \u2014 says a person must be told when they are\ninteracting with an AI system, and when what they are looking at was generated or manipulated by\none. This plugin renders those notices.<\/p>\n\n
It renders one disclosure per piece of content<\/strong>, chosen on the page that carries it, because a\ndisclosure is a statement about that content and not about the site. There is no site-wide default:\nwhich duty a page owes is a judgement about your own system, and this plugin does not make it for\nyou.<\/p>\n\n What it does not do.<\/strong> It does not tell you, or a reader, that your site meets article 50. Whether\nit does is for a qualified professional to say. This plugin gives you information and structure; it\ngives you no verdict, and it is not legal advice.<\/p>\n\n Both read the wording from the plugin on every visit<\/strong>. Nothing is copied into your post, so a\ncorrected wording reaches pages that are already published \u2014 which is the whole reason the block\nstores your two choices and none of the words.<\/p>\n\n One per duty the article names: an AI system a visitor is interacting with (art. 50(1)), generated\nor edited image, audio or video (50(2)), a deep fake (50(4)), AI-generated text published as news\n(50(4)), an emotion-recognition system (50(3)) and biometric categorisation (50(3)). Each ships in\nEnglish and Dutch.<\/p>\n\n The plugin stores nothing about a visitor, sets no cookie and makes no network call. A disclosure is\nread from a file inside the plugin and rendered on your server.<\/p>\n\n Kaderlab is a trade name of AVS Digital, a one-person Dutch business (KvK 67123783). The software is\nwritten by one person working with AI automation. The disclosure wording is not written here at all:\nit is the text of Article 50 itself \u2014 see the FAQ.<\/p>\n\n This plugin ships one compiled JavaScript file, The build is plain The disclosure wording is not compiled from anything: it is GPLv2 or later. The canonical text is at https:\/\/www.gnu.org\/licenses\/gpl-2.0.html, and no copy of\nit ships inside this plugin: a licence transcribed rather than fetched is a licence that might not\nbe the one it names.<\/p>\n\n\n There is nothing to configure site-wide, and the settings screen deliberately has no settings: it\nreports the state of the disclosure wording and nothing else.<\/p>\n\n\n From the Regulation. Each disclosure is the operative wording of the paragraph of Article 50 that it\nserves, taken from the official language version for its own locale \u2014 the English text from the\nEnglish version, the Dutch from the Dutch \u2014 with the form of address and the sentence structure\nadjusted so that it reads as a statement to your visitor rather than as a duty on you. Every one of\nthose adjustments is recorded next to the text in the plugin's own catalogue file as an edit, and the\nplugin's own test suite re-applies every one of them to the official quote and fails unless the\nresult is the shipped wording exactly. At run time the rule works the other way round: a disclosure\nwhose wording is not adopted from the Regulation renders nothing at all.<\/p><\/dd>\n Either the block is not configured, or its wording is not adopted from the Regulation. Neither the\nblock nor the shortcode has a default disclosure or a default language, so an unconfigured one renders\nnothing and says so in the editor. Separately, the plugin renders nothing<\/strong> for any wording that is\nnot the Regulation's own until a qualified professional has reviewed it: an unreviewed legal sentence\non your site in your name is worse than no sentence. The settings screen lists every disclosure and\nsays which languages it is shown in, so you can see the answer without a reader telling you.<\/p><\/dd>\n That is a question about your own system and your own use of it, and this plugin will not answer it.\nNeither the block nor the shortcode has a default disclosure: an unconfigured block renders nothing\nand says so in the editor.<\/p><\/dd>\n No. It renders a notice; it does not inspect your site and it reaches no conclusion about it. Ask a\nqualified professional.<\/p><\/dd>\n Not from the plugin, and that is the point of it. Both halves of this product read one catalogue file,\nso the words on your page are the Regulation's own and not a paraphrase \u2014 two transcriptions of one\nlegal text become two different claims, and only one of them can be the right one. If your notice\nneeds different words, that is a conversation to have with a qualified professional.<\/p><\/dd>\n No. No cookie, no request to any server, nothing stored.<\/p><\/dd>\n\n<\/dl>\n\n\nHow you place a disclosure<\/h4>\n\n
\n
[kaderlab_ai_disclosure kind=\"ai-interaction\" locale=\"en\"]<\/code>, anywhere a shortcode\nruns.<\/li>\n<\/ul>\n\nThe disclosures<\/h4>\n\n
Privacy<\/h4>\n\n
Who makes it<\/h4>\n\n
Source code<\/h3>\n\n
blocks\/ai-disclosure\/editor.js<\/code>, which registers\nthe block in the editor. Its human-readable TypeScript source ships inside this plugin too:<\/p>\n\n\n
blocks\/ai-disclosure\/editor.js<\/code>: src\/block\/editor.ts<\/code><\/li>\ntsc --target ES2020 --lib ES2020,DOM --module none --strict --removeComments --newLine lf --outDir blocks\/ai-disclosure src\/block\/editor.ts<\/code><\/li>\n<\/ul>\n\ntsc<\/code> with module: \"none\"<\/code> \u2014 no bundler and no minifier \u2014 and the plugin's\ntest suite runs exactly that command on the shipped source and compares the result byte for byte\nwith the file shipped here.<\/p>\n\ncopy\/disclosures.json<\/code>, read as it is.<\/p>\n\nLicence<\/h3>\n\n
\n
\n
Where does the wording come from?<\/h3><\/dt>\n
I placed a disclosure and nothing appears. Why?<\/h3><\/dt>\n
Which disclosure does my page need?<\/h3><\/dt>\n
Does it check whether my site meets the AI Act?<\/h3><\/dt>\n
Can I change the wording?<\/h3><\/dt>\n
Is my visitors' data collected?<\/h3><\/dt>\n
0.2.2<\/h4>\n\n
\n
0.2.1<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n