| 开发者 |
legalithmteam
pedrammadani |
|---|---|
| 更新时间 | 2026年7月23日 19:53 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[legalithm_ai_act_disclosure].[legalithm_ai_act_literacy].legalithm_ai_act_settings), so it will not clash with other tools.legalithm-ai-act folder to /wp-content/plugins/.If your site shows an AI chatbot, AI-generated text or images, or an AI assistant to visitors in the EU, Article 50 of the EU AI Act requires you to disclose it. This plugin adds that disclosure.
No. Everything runs locally on your WordPress site. There is no account, no external API call, and no data leaves your server.
No. The AI-tool scan runs only when you trigger it (or on an optional schedule) and the result is cached. Nothing scans on every page load.
Yes. The Article 50 disclosure, the Article 4 literacy checklist, and AI detection are free and work on their own.
Open the Media Library in list view, find the image, and choose "Mark as AI-generated". The plugin watermarks the original and every generated size, so whichever one your theme serves carries the mark. The "AI marking" column shows which images are already done. There is no bulk "mark everything" option on purpose: only you know which images are AI-generated.
Barely. The watermark shifts each pixel by about 1.6% of the brightness range, which is imperceptible on photographs and AI artwork. On very large, smooth gradients you may be able to see faint blocking if you look for it. That small shift is what lets the mark survive compression.
Yes, that is the point of it. The mark lives in the pixels, not the metadata, so it survives lossy re-encoding, resizing, greyscale conversion and format changes, all of which strip normal metadata. Heavy cropping and rotation do defeat it, and it is not designed to withstand a deliberate attack.
You can run the action again safely; the plugin detects an existing mark and leaves the image alone rather than stacking a second watermark on top of it.
Edit the post and use the "AI Act transparency" panel in the sidebar. Choose "AI-generated", or "AI-drafted, reviewed by a human" and name the reviewer. The label then appears for visitors and a machine-readable declaration is added to the page. An "AI" column in the posts list shows which content is declared.
No. Article 50(4) is about AI-generated text on matters of public interest, which is narrower than everything a model helped write. A product description is unlikely to qualify; an article on health, money or politics probably does. The plugin leaves that judgement to you rather than guessing.
Then the disclosure duty generally falls away, provided the review was meaningful and someone holds editorial responsibility. Choose "AI-drafted, reviewed by a human" and the plugin records who reviewed it and when. That record is the point: months later you can show the review happened. By default the plugin still shows a label in this case, which is not required but reads as confident; you can turn that off in the settings.
No, deliberately. AI-text detectors are unreliable, and a false positive would make you declare something untrue. You declare it; the plugin renders and records it.
No. Detection only suggests settings. Enabling the Article 50 notice always requires an explicit admin action.
No plugin can do that. This helps you implement the transparency measures Article 50 asks for. It is not legal advice and does not guarantee compliance.