Privacy across search, accounts and plugin alerts.
Last updated: 4 September 2026. WP PlugIndex keeps public analytics deliberately small and processes additional account information only when you use account, membership or notification features.
1. Public product analytics
WP PlugIndex may record page and route activity, searches after automatic redaction, the number and order of returned results, result clicks, WordPress.org outbound clicks, missing plugin requests, broad traffic source, country code, device class, crawler family and sampled performance measurements. This is used to improve search, discover missing or weak results, understand demand and diagnose site performance.
2. Search terms
Search terms may be retained for a limited period. Before storage, obvious email addresses, web addresses and long phone or account-number-like sequences are automatically replaced with redaction markers. Do not enter personal or confidential information into the search box.
3. No advertising profile or persistent analytics identity
WP PlugIndex does not store a persistent visitor ID, cross-page analytics session ID, raw IP address, full browser user-agent, browser fingerprint or exact location in its product analytics database. It does not use third-party advertising analytics or sell personal information for advertising. Approximate daily visitor totals may be calculated with a one-way aggregate counting structure; the temporary input used for that count is not stored as an enumerable visitor record.
4. Account information
If you create an account, the account service processes the information needed for WordPress authentication and account administration, such as your user ID, login/account details and email address. WordPress remains the owner of the login session. The public pages stay shared and cacheable; after the page loads, the browser may make a separate private, no-store request to the account service to determine whether you are signed in and whether a plugin is currently watched.
5. Saved and Watched plugins
The account service stores the plugin slugs you save and watch, whether a watch is active or suspended, relevant timestamps and account dashboard state needed to show What changed information. Saved plugins are bookmarks. Watched plugins are actively monitored subject to your plan limit. Change history is based on detected public plugin-directory changes after the watch begins.
6. Membership and payments
Paid Memberships Pro manages the WP PlugIndex membership lifecycle and associated membership/order records. PayPal processes Alerts payments. WP PlugIndex may store or receive transaction identifiers, membership status, price/currency, renewal state and other billing metadata needed to administer the subscription, but WP PlugIndex does not receive or store your full PayPal credentials or full card/payment-account secrets.
7. Email, Telegram and Discord alerts
If you enable the Alerts features, the service stores the preferences and delivery state required for the channels you choose. Daily email uses your account email address and is delivered through Postmark, the current transactional email provider. Telegram pairing stores the Telegram identifiers needed to send your alerts. Discord stores the receiving Incoming Webhook connection you provide using the service's protected storage and uses it only to deliver or test your WP PlugIndex alerts. Delivery attempts and limited operational metadata may be retained for reliability, retries and troubleshooting.
8. Cookies and local storage
WP PlugIndex does not require an analytics cookie or analytics local-storage identifier. A light/dark theme preference may be stored locally and in a functional cookie shared across WP PlugIndex subdomains. The account subdomain uses WordPress authentication/session cookies when you sign in. If a signed-out visitor clicks Watch, a short-lived functional watch-intent cookie may temporarily store only the plugin slug and return path so the requested watch can continue after sign-in or registration.
9. Retention
Raw public page-view records are normally kept for about 72 hours; engagement and sampled performance records for about 7 days; crawler records for about 14 days; missing-plugin records for about 30 days; and sanitised search, search-click and WordPress.org outbound-click records for about 90 days. Compact aggregate statistics may be kept longer. Account, membership, Saved/Watched, notification and transaction records are retained for as long as reasonably needed to provide the service, maintain account history, meet legal/accounting obligations, resolve disputes or protect the service. Disconnected channel credentials are removed or made unusable according to the channel workflow, while limited operational records may remain where necessary.
10. Service providers and external services
WP PlugIndex uses hosting, CDN and security infrastructure to deliver the sites, Paid Memberships Pro for membership management, PayPal for payment processing, Postmark for transactional email delivery, and Telegram and Discord for the notification channels you choose to connect. Those providers process information under their own terms and privacy obligations where they act independently. Data may be processed in countries outside your own; where data-protection law requires safeguards for international transfers, appropriate safeguards are used.
11. Legal bases and choices
Where UK GDPR, EU GDPR or similar law applies, account and subscription processing is generally necessary to provide the service you request; payment and record keeping may also be necessary for legal obligations; security, service operation and privacy-minimised analytics may rely on legitimate interests where appropriate. Optional notification channels and settings are under your control, and consent or another appropriate legal basis is used where the law requires it.
12. Technical and security processing
Hosting, reverse-proxy and security infrastructure necessarily receives technical request information such as an IP address, browser information, requested path, timestamp and security signals while delivering and protecting the service. Product analytics minimises this information before persistence. Operational and security logs are separate from the public product analytics database and are kept only as needed for delivery, security and troubleshooting.
13. Plugin data and external links
Plugin information displayed by WP PlugIndex is sourced from the public WordPress.org plugin directory. When you follow an external link or connect an external notification provider, that destination's own privacy practices also apply.
14. Your rights
Depending on the law that applies to you, you may have rights to access, correct, delete or restrict personal information, object to certain processing, request portability, withdraw consent where processing is consent-based, and complain to an appropriate data-protection authority. Some records may need to be retained where there is a legal, security or accounting reason. Privacy and rights requests can be sent using the legal contact information loaded at the bottom of this page.