audit report
Zendesk
Zendesk loaded 16 third-party domain(s), of which 1 is privacy-sensitive. 1 warn finding(s): No privacy policy found. Privacy-sensitive vendors observed: Google Tag Manager.
findings
- warn
No privacy policy found
stackpeek could not discover a privacy policy for this page. This is unusual for anything serving real users.
how we detected this → - note
Google Tag Manager loaded (tag_manager)
Observed 2 time(s) on the page.
inline: window.dataLayer = window.dataLayer || []; window.dataLayer.push({ 'even <iframe> src: https://www.googletagmanager.com/ns.html?id=GTM-Z4DV
third parties observed
| vendor | domain | category | hits | disclosure |
|---|---|---|---|---|
| Google Tag Manager | googletagmanager.com | tag_manager | 2 | not named |
| AWS CloudFront | cloudfront.net | cdn | 4 | not named |
| Zendesk | zdassets.com | chat_support | 1 | not named |
| data:image | data:image | other | 38 | not named |
| gmpg.org | gmpg.org | other | 1 | not named |
| zendesk.co.jp | zendesk.co.jp | other | 1 | not named |
| zendesk.co.uk | zendesk.co.uk | other | 1 | not named |
| zendesk.com.br | zendesk.com.br | other | 1 | not named |
| zendesk.com.mx | zendesk.com.mx | other | 1 | not named |
| zendesk.de | zendesk.de | other | 1 | not named |
| zendesk.es | zendesk.es | other | 1 | not named |
| zendesk.fr | zendesk.fr | other | 1 | not named |
| zendesk.hk | zendesk.hk | other | 1 | not named |
| zendesk.kr | zendesk.kr | other | 1 | not named |
| zendesk.nl | zendesk.nl | other | 1 | not named |
| zendesk.tw | zendesk.tw | other | 1 | not named |
policy claims
No privacy policy could be located on this site.
response headers
- hsts
- yes
- csp
- yes
- server
- cloudflare
run this yourself
Every audit on this site is reproducible. Install stackpeek and run the same check against https://zendesk.com from your own machine — the tool is MIT-licensed and runs locally.
pip install stackpeek
stackpeek audit https://zendesk.comprovenance
This audit was generated by running
stackpeek
against https://zendesk.com
from a public IP, using only HTTP GET and standard browser headers. The
findings compare the observed HTML against the
policy discovery results (no policy document was located)
using the
public methodology.
Re-scans append new findings at new permalinks and never overwrite the
historical record.