| 开发者 | tuhaichelyk |
|---|---|
| 更新时间 | 2026年8月28日 19:59 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[aivow_disclosure id="123"].[aivow_interaction_gate id="123"], with optional per-use inner_text.[aivow_transparency_page].aivow-ai-disclosure-manager folder to /wp-content/plugins/.AIVOW > AIVOW Wizard to complete the readiness checklist.AIVOW > AIVOW Dashboard.AIVOW > AIVOW Settings.No. It is a technical documentation and transparency workflow tool. It does not provide legal advice, does not certify compliance, and does not guarantee compliance with the EU AI Act or any other law.
No. The plugin works locally inside WordPress and does not make plugin-initiated external API calls.
No. The plugin stores administrator-configured AI records, labels, readiness answers, Article 50 internal assessment fields, and transparency settings inside WordPress. It does not store IP addresses, full user agents, prompts, chat messages, AI responses, uploaded files, names, emails, or visitor identifiers. The global banner acknowledgement mode stores only a non-personal banner version fingerprint in a browser cookie. The interaction gate shortcode may store a non-personal acknowledgement value in the visitor's browser localStorage.
The generated page can contain site-specific transparency information, operational notes, and assessment details. It is created as a draft so an administrator can review the content before publishing it.
No. The interaction gate is a visitor acknowledgement and disclosure interface. It is not authentication, authorization, a paywall, a consent-management platform, or secure protection for sensitive content. Gated content is rendered in the page HTML and hidden until acknowledgement.
Yes. The plugin supports default colors and safe custom colors with opacity controls. Server-side validation accepts only six-character hex colors or normalized rgba(r,g,b,a) values.
Yes. Custom badge icons can be selected from the WordPress Media Library. The plugin does not enable SVG uploads and does not render administrator-provided inline SVG markup.
Yes, when explicitly enabled by the administrator. The plugin can output lightweight AI metadata meta tags on AI-labelled singular content. Separate opt-in settings can also include the WooCommerce Shop page and labelled taxonomy archives. Post type, date, author, and search archives remain excluded because they do not have a single editable disclosure source. The plugin does not output arbitrary custom schema, does not output Schema.org JSON-LD, and does not claim to provide watermarking or legal compliance certification.
Taxonomy archive badges can be configured for public taxonomy terms. Fixed-position badges are the most predictable option. Inline archive badge placement depends on theme hooks such as wp_body_open() and may appear near the top or bottom of the template depending on the active theme.
No. Version 1.0.0 does not collect disclosure event logs and does not generate downloadable report files. The Reports tab provides a read-only summary of the current configuration.
By default, plugin data is preserved on uninstall to prevent accidental loss of transparency records. You can enable data cleanup in the plugin settings before uninstalling if you want plugin tables, options, and AI content label metadata removed. Generated WordPress pages are normal site content and are not deleted by plugin cleanup; review, delete, or replace those pages manually if needed.
The plugin loads its CSS and JavaScript through the standard WordPress enqueue system. Basic cache plugins should generally work. Aggressive JavaScript optimization, delay, defer, or script-combination settings may break interactive features such as draggable fixed badges, acknowledgement banners, or interaction gates. If that happens, exclude aivow-ai-disclosure-manager/assets/js/frontend.js from JavaScript optimization.