No third-party tracking before consent in Push and realtime messaging
We load their front page and count third-party requests before anything is clicked.
1 of 10 companies we measured here publish it, that is 10%. Last checked 2026-10-20.
10% here against 6% across every category we measure. Push and realtime messaging sits above the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to No third-party tracking before consent across all categories, or to Push and realtime messaging.
- Found1
- Not found at checked addresses9
- Not measured0
10 companies in total. Unmeasured companies are excluded from the published share.
Published
No third-party requests before any interaction.
| Vendor | What we found |
|---|---|
| Pushover | https://pushover.net/Checked |
Third-party requests seen on the first load, before any interaction.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Catapush | 1 address checkedChecked |
| ntfy | 1 address checkedChecked |
| PushAlert | 1 address checkedChecked |
| PushEngage | 1 address checkedChecked |
| Pusher | 1 address checkedChecked |
| Pushsafer | 1 address checkedChecked |
| TrueDialog | 1 address checkedChecked |
| Webpushr | 1 address checkedChecked |
| WonderPush | 1 address checkedChecked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
None. Every vendor here was measured for this criterion.
Other criteria in Push and realtime messaging
- Data processing agreement
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- HTTPS enforced with HSTS
- security.txt (RFC 9116)
- Notice before subprocessors change
- Named privacy contact
No third-party tracking before consent in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.