No third-party tracking before consent in Incident management
We load their front page and count third-party requests before anything is clicked.
3 of 32 companies we measured here publish it, that is 9%. Last checked 2026-10-17.
9% here against 6% across every category we measure. Incident management 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 Incident management.
- Found3
- Not found at checked addresses29
- Not measured2
34 companies in total. Unmeasured companies are excluded from the published share.
Published
No third-party requests before any interaction.
| Vendor | What we found |
|---|---|
| Causely | https://causely.ai/Checked |
| Kintaba | https://kintaba.com/Checked |
| Transposit | https://transposit.com/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 |
|---|---|
| AlertOps | 1 address checkedChecked |
| All Quiet | 1 address checkedChecked |
| BigPanda | 1 address checkedChecked |
| Cachet | 1 address checkedChecked |
| Everbridge | 1 address checkedChecked |
| FireHydrant | 1 address checkedChecked |
| Hyperping | 1 address checkedChecked |
| ilert | 1 address checkedChecked |
| incident.io | 1 address checkedChecked |
| Instatus | 1 address checkedChecked |
| Moogsoft | 1 address checkedChecked |
| OhDear | 1 address checkedChecked |
| OnPage | 1 address checkedChecked |
| PagerDuty | 1 address checkedChecked |
| Pagerly | 1 address checkedChecked |
| PagerTree | 1 address checkedChecked |
| Resolve | 1 address checkedChecked |
| Rootly | 1 address checkedChecked |
| SARStuff | 1 address checkedChecked |
| SIGNL4 | 1 address checkedChecked |
| Sorry | 1 address checkedChecked |
| Spike.sh | 1 address checkedChecked |
| Squadcast | 1 address checkedChecked |
| Status.io | 1 address checkedChecked |
| StatusHub | 1 address checkedChecked |
| Uptime.com | 1 address checkedChecked |
| Uptrends | 1 address checkedChecked |
| xMatters | 1 address checkedChecked |
| Zenduty | 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.
Other criteria in Incident management
- Data processing agreement
- Subprocessor list
- Data location stated
- Status page with history
- Public pricing
- Certifications named
- Uptime SLA with a figure
- 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.