stackpeek
← back to leaderboard

audit report

Twilio

https://twilio.com · communication

warn
scanned 2026-04-16 23:37:03 utc permalink · /audit/twilio

Twilio loaded 5 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


  1. 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 →
  2. note

    Google Tag Manager loaded (tag_manager)

    Observed 3 time(s) on the page.

    
                inline: window.dataLayer = window.dataLayer || [];
    inline: ontext5.a(2, new Promise(function (resolve) { gtag("get", CONTAINER_ID, property, resolve); }));
    <iframe> src: https://www.googletagmanager.com/ns.html?id=GTM-5JLZ694
              
    how we detected this →
  3. 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 Tag Manager googletagmanager.com tag_manager 3 not named
adobedtm.com adobedtm.com other 1 not named
hlx.page hlx.page other 1 not named
trustarc.com trustarc.com other 2 not named
visualwebsiteoptimizer.com visualwebsiteoptimizer.com other 1 not named

policy claims


No privacy policy could be located on this site.

response headers


hsts
yes
csp
no
server

run this yourself


Every audit on this site is reproducible. Install stackpeek and run the same check against https://twilio.com from your own machine — the tool is MIT-licensed and runs locally.

pip install stackpeek
stackpeek audit https://twilio.com

source on GitHub · methodology · cli docs

provenance


This audit was generated by running stackpeek against https://twilio.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.