內容簡介
PMS Cookie Banner Lite 是一款幫助網站訪客選擇可選技術的外掛，提供清晰的 Cookie 橫幅和偏好中心，讓用戶能夠管理其同意的服務，確保網站遵循隱私法規。
【主要功能】
• 接受、拒絕、客製化及撤回可選同意
• 根據同意加載配置的腳本和嵌入內容
• 提供 Google Consent Mode v2 信號
• 全球隱私控制及獨立的銷售/分享隱私選擇
• Cookie 清單與 HTML 和瀏覽器運行時掃描
• 同意記錄、隱私請求及儀表板統計
外掛標籤
開發者團隊
原文外掛簡介
Help visitors choose which optional technologies your site may use. Set up a clear cookie banner and preference center, then configure the services you want to manage.
Features
Accept, reject, customize and withdraw optional consent.
Consent-based loading for configured scripts and supported embeds.
Google Consent Mode v2 signals.
Global Privacy Control and separate sale/sharing privacy choices.
Cookie inventory with HTML and browser runtime scanning.
Consent logs, privacy requests and dashboard statistics.
Configuration-specific text to copy into your privacy policy.
English, Polish, French, German, Spanish and Swedish interfaces.
Why PMS Cookie Banner Lite?
The included local features are free and do not expire. No PMS account or paid licence is required. Settings and visitor records remain under your control in WordPress.
Need more tools?
PMS Cookie Banner Pro adds banner layouts, custom colors and typography, a local Media Library logo and higher-capacity, path-aware classification.
The paid implementation is not included in Lite. Pro replaces Lite in the same plugin folder; do not install both together. See features and plans.
Privacy
This WordPress.org edition updates through WordPress.org and contains no external updater or licence manager. Public PMS branding is optional and off by default.
PMS classification is also off by default and requires a saved administrator opt-in. After opt-in, requests to https://pmscripts.com/licenses/v1/classification/register and /v1/classification/classify contain at most 50 cookie names and 50 resource origins or normalized resource paths, with an installation ID and pseudonymous credential. PMS receives the server IP and technical headers. Cookie values, page content, URL queries and visitor consent records are not intentionally sent; names and paths can still reveal website or personal information.
If the PMS operator enables AI assistance, unfamiliar names and resource origins may be sent to OpenAI. No OpenAI key is required in the plugin. Disabling classification stops new requests and retries while preserving the local inventory.
PMS privacy policy and service terms.
OpenAI privacy policy and service terms.
Before using it on a live site
This is a technical consent tool, not legal certification. Scanning and consent signals do not prove that every tracker is blocked. Verify your actual integrations, including third-party and server-side behavior, and adapt your privacy policy to the whole website. Visitor tags are supplied by the site administrator, not installed automatically by this plugin.
Technical Details
Managed scripts use WordPress’s native template enhancement lifecycle, without a separate response buffer.
A one-time WP-Cron HTML baseline runs in bounded batches. It covers the home page, regular pages, shop and supported landing pages, excluding individual posts/products, archives and technical templates.
The administrator’s runtime scan executes page JavaScript. Keep its tab open and finish the representative queue; closing or reloading it interrupts the run.
Accepted signed classifications are imported automatically after a completed scan, including AI-assisted results. Unresolved identities/categories remain private. Unknown retention periods or provider privacy URLs remain marked unknown. Importing a result does not create blanket domain-blocking rules.
Policy review metadata stays in WordPress. Relevant configuration, inventory and linked local policy changes require a new review; external policy changes need manual checking. Missing or unpublished local pages cannot be marked reviewed.
Decision logs are eligible for deletion after 180 days. Privacy requests use the saved 730–3650-day setting, with a minimum of 24 calendar months. Cleanup depends on WordPress scheduling. Consent expiry does not physically erase localStorage; separate privacy restrictions have no automatic browser expiry.
Scan and policy notices stay on Cookie Banner screens. Appearance fields and browser observations are validated before storage or extension callbacks.
