| 开发者 | itsnothuman |
|---|---|
| 更新时间 | 2026年7月17日 21:18 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Digital Source Type (Iptc4xmpExt:DigitalSourceType) into the file's XMP, plus schema.org JSON-LD (ImageObject + IPTC:DigitalSourceType) on the page.[aicl_ai_notice] shortcode (and an optional floating notice) tells visitors when they are interacting with an AI, not a human, covering the EU AI Act Article 50(1) duty as well.http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMediahttp://cv.iptc.org/newscodes/digitalsourcetype/compositeWithTrainedAlgorithmicMediahttp://cv.iptc.org/newscodes/digitalsourcetype/algorithmicMediahttp://cv.iptc.org/newscodes/digitalsourcetype/digitalCapturehttp://cv.iptc.org/newscodes/digitalsourcetype/digitalCreationhttp://cv.iptc.org/newscodes/digitalsourcetype/compositeexiftool when present (JPEG/PNG/WebP/GIF/TIFF); otherwise a built-in pure-PHP writer handles JPEG and PNG.
Optional, off by default: an opt-in AI Transparency Directory lets you list your site publicly as one that discloses AI content. Nothing is shared without your explicit consent, and you can remove your listing anytime.
Disclaimer: this plugin is tooling to help meet Article 50 transparency obligations. It is not legal advice. Whether content is in scope (e.g. what counts as a "deepfake"), your deployer status, and the wording of your disclosure remain your responsibility.
/wp-content/plugins/, or install it from the Plugins screen in wp-admin.Yes — everything in this plugin is fully functional, nothing is locked. Flagging, the visible badge with all its styles and shapes (including the click-to-disclose modal and a custom logo), the in-dashboard media library, IPTC/XMP embedding for every supported format, JSON-LD, the AI-assistant notice, and the CSV compliance export are all free. A separate, optional AIM Transparency Pro add-on (sold on our site, not hosted here) adds its own features on top: automatic flagging on upload, a library scanner (strip-guard plus retroactive discovery of provenance your files already declare), additional report export formats (a print-ready report you can save as PDF, plus JSON, Markdown & TXT), and WooCommerce support.
The visible badge addresses the deployer's human-visible disclosure (Art. 50(4)); the embedded metadata addresses machine-readability. Both are on by default.
It hooks WordPress's own image and template filters — including render_block for block/FSE themes — so any theme using standard functions is covered. For themes that hardcode <img> tags, enable Universal badge coverage in Settings.
When file embedding is on, it writes XMP into flagged image files (and every generated size). It is idempotent. Turn it off to use the visible badge + JSON-LD only.
JPEG and PNG are still marked by the built-in PHP writer. WebP and other formats need exiftool; the Metadata screen shows your current capability.
digitalCapture), Human Created (digitalCreation, e.g. 3D renders or digital art made without generative AI) or Composite (composite, a non-AI mix such as photos + renders). Each embeds the current IPTC Digital Source Type into the file and the page JSON-LD, with no visible badge by default — honest provenance for human-made work, not just AI labels. (An optional visible badge for these types is available with the Custom badge style.)[aicl_ai_notice] shortcode into any page with a chat UI, or enable the optional floating notice that appears when a known chat widget is detected. Configurable disclosure text and position.