Push plugin subscriber stores
Where WordPress push plugins store subscriber tokens
Push plugins let visitors subscribe to notifications. Some store subscription details with an outside provider; others store them on your WordPress server. This table compares the documented setups below. Your settings can change how they work.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group push plugins
We compare the push-notification setups named below. A plugin that stores subscription details on your WordPress server is different from a plugin that stores them with an outside provider. We have not tested consent timing or how long push-service logs are kept.
Push-notification plugins
No paid placement. Tokens stored on your site first, then outside push services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Documented script hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Perfecty Push (self-hosted) In its default self-hosted setup, Perfecty stores subscription details on your WordPress server. This does not mean notifications stay entirely on your server: browser push delivery services are outside this comparison. Consent timing has not been tested. | Tokens stored on your site | No outside plugin script host documented for this setup. Browser push delivery services and other page requests are not covered. | Not assessed | Not tested |
| |
| OneSignal This row covers OneSignal when an App ID is saved. The plugin loads scripts from an outside OneSignal host on the visitor page. The listing says visitors opt in to receive push notifications and names a dashboard of subscribed users. Consent timing is not tested here. | Outside push service | cdn.onesignal.com | Not assessed | Not tested |
| |
| PushEngage This row covers PushEngage when a site key is saved. The plugin loads scripts from an outside PushEngage host on the visitor page. The listing says subscribers receive browser notifications after they leave the site. WhatsApp, chat widget, and WooCommerce cart recovery are other PushEngage products and are not this row. Consent timing is not tested here. | Outside push service | clientcdn.pushengage.com | Not assessed | Not tested |
| |
| Webpushr This row covers Webpushr when public and private keys are saved. The plugin loads scripts from an outside Webpushr host on the visitor page. The listing says visitors see an opt-in message and names subscriber logs in the Webpushr console. Consent timing is not tested here. | Outside push service | cdn.webpushr.com | Not assessed | Not tested |
| |
| WonderPush This row covers WonderPush when an access token is saved. The plugin loads scripts from an outside WonderPush host on the visitor page. AMP web-push is a different setup and is not this row. Consent timing is not tested here. | Outside push service | cdn.by.wonderpush.com | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named push-notification setups. It does not show what loads on your site. Where no outside plugin script host is documented, that applies only to the setup described. Browser push delivery services and other page requests are not covered. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long push-service logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.
Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-push-notification-privacy