AI disclosure banner
A fully customizable notice — colour, message, position and display rules — that tells visitors AI is in use, like a cookie banner for AI.
Transparency
One plugin to tell visitors how you use AI, capture their consent, document your providers, and prove compliance — without touching a line of code.
Choose which AI-powered features may run for you. Every decision is recorded with a timestamp for your records.
From the front-end disclosure banner to board-ready PDF reports — every part of responsible AI use is covered out of the box.
A fully customizable notice — colour, message, position and display rules — that tells visitors AI is in use, like a cookie banner for AI.
Visitors control four AI categories independently. Every choice is stored with timestamp, user ID and a salted, one-way IP hash.
Document every AI vendor — purpose, data processed, retention, data location and DPA links — for OpenAI, Anthropic, Gemini, Bedrock and more.
Declare your model-training stance via robots meta, X-Robots-Tag, robots.txt crawler blocks and an auto-generated /llms.txt.
Record AI API requests, responses, token usage and consent verification in dedicated tables — one do_action('aicpm_log') call.
Generate audit-ready reports in CSV, JSON and PDF — with a dependency-free PDF engine — plus a live snapshot dashboard.
Publish an AI policy page instantly with a Gutenberg block and shortcodes like [aicpm_ai_policy] and [aicpm_consent_preferences].
Hooks into WordPress' native data export and erasure tools, and runs a daily retention cron to purge stale records automatically.
Three of the features site owners lean on most — shown as they actually appear.
Match it to your brand, set where and when it appears, and let visitors fine-tune each AI category. Consent is written to the REST API and remembered per policy version.
We personalise content and answer questions with AI assistants.
Publish your training stance in every format that matters — HTTP headers, robots directives and the emerging /llms.txt standard — generated and served automatically.
X-Robots-Tag: noai on every response/llms.txt at your domain root# llms.txt — AI usage & training policy Site: Your Company AI-training: disallowed Contact: privacy@yoursite.com # served automatically via robots.txt User-agent: GPTBot Disallow: / # and on every page response X-Robots-Tag: noai, noimageai
A live snapshot of consent, providers and training posture — exportable to CSV, JSON or a polished PDF generated without a single third-party library.
A modern, object-oriented codebase that passes WordPress Plugin Check with zero errors — built for developers who read the source before they buy.
aicpm/v1 namespace — consent read/write endpointsaicpm_log, aicpm_consent_types & more.pot · text domain aicpm · RTL-safeNo. When IP logging is enabled, only a salted, non-reversible HMAC-SHA-256 hash is stored — never the raw address. It's off by default and fully under your control.
Any. Presets are included for OpenAI, Anthropic, Google Gemini, Azure OpenAI and AWS Bedrock, and you can register any additional vendor with its own processing details.
No. Everything — banner, consent, providers, training controls and reports — is configured from the WordPress admin. Developers get hooks and a REST API when they want deeper integration.
Yes. Network-activate the plugin and every existing site is provisioned automatically; any site created later receives the schema on the fly.
/llms.txt?An emerging, machine-readable standard that publishes your AI usage and training policy at yoursite.com/llms.txt. The plugin generates and serves it for you.
Yes — a complete .pot template ships with the plugin under the aicpm text domain, so you can localise every string.
Give your visitors transparency, give regulators an audit trail, and give yourself one less thing to worry about.