audit report
Postmark
Postmark loaded 4 third-party domain(s), of which 2 are privacy-sensitive. 1 warn finding(s): No privacy policy found. Privacy-sensitive vendors observed: Google Analytics, 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 3 time(s) on the page.
how we detected this →inline: window.dataLayer = window.dataLayer || []; function gtag() { dataLayer.push(arguments); } gtag('consent', 'default inline: window.dataLayer = window.dataLayer || []; function gtag() { dataLayer.push( inline: dataLayer = [{'siteType': 'landing', 'visitorIP': '34.105.113.14', 'doN - note
Google Analytics loaded (analytics)
Observed 2 time(s) on the page.
how we detected this →link dns-prefetch: https://ssl.google-analytics.com link dns-prefetch: https://www.google-analytics.com - note
No Content-Security-Policy header
A CSP header restricts what scripts the page can load. Its absence isn't a policy mismatch but is worth noting in a transparency report.
how we detected this →
third parties observed
| vendor | domain | category | hits | disclosure |
|---|---|---|---|---|
| Google Analytics | google-analytics.com | analytics | 2 | not named |
| Google Tag Manager | googletagmanager.com | tag_manager | 3 | not named |
| cookielaw.org | cookielaw.org | other | 1 | not named |
| svdcdn.com | svdcdn.com | other | 18 | not named |
policy claims
No privacy policy could be located on this site.
response headers
- hsts
- yes
- csp
- no
- server
- cloudflare
run this yourself
Every audit on this site is reproducible. Install stackpeek and run the same check against https://postmarkapp.com from your own machine — the tool is MIT-licensed and runs locally.
pip install stackpeek
stackpeek audit https://postmarkapp.com provenance
This audit was generated by running
stackpeek
against https://postmarkapp.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.