| 开发者 | wpgeared |
|---|---|
| 更新时间 | 2026年9月15日 21:25 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. ClearStat Free collects, stores, aggregates, and reports analytics inside your WordPress installation. No ClearStat account is required.
Analytics is stored in dedicated tables in your WordPress database. Free sends no analytics, configuration, or product telemetry to ClearStat or WPGeared.
Strict mode uses no cookies or persistent visitor identifiers. Consent-aware continuity can issue a random 30-day first-party HttpOnly cookie only after an affirmative supported consent signal.
No raw IP address or full User-Agent is stored in analytics tables. ClearStat does not fingerprint visitors. A short-lived abuse-control key may be derived server-side without retaining the raw address.
Strict mode deliberately cannot link activity into visitor or visit estimates. ClearStat shows continuity-dependent metrics as unavailable rather than inventing numbers.
Free supports page views, outbound clicks, downloads, email and phone clicks, searches, 404 views, and supported basic form completions.
Yes. Report tables can be exported as bounded CSV files. Data Management provides retention controls, date-range purge, delete-all, and an explicit delete-on-uninstall choice.
The small dependency-free tracker is deferred and sends a first-party asynchronous request. Reporting and aggregation run separately from page rendering. Performance still depends on hosting, traffic, caching, and other plugins.
No. ClearStat is built to support responsible privacy work, but compliance depends on the site's jurisdiction, purposes, configuration, notices, consent tools, legal basis, and other software.
Geography is currently disabled. Search activity uses a separate internal marker path; other plain-permalink content URLs can still aggregate under / when WordPress cannot resolve them in strict query-free mode. Security or caching layers must allow anonymous POST requests to /metricpress/v1/collect. Strict Content Security Policy deployments may require a nonce or hash for the inline tracker configuration.
ClearStat requires WordPress 6.4+, PHP 7.4+, InnoDB, and utf8mb4 on MySQL 5.7+ or MariaDB 10.4+. A maintained database release is recommended for production.