stackpeek
← back to leaderboard

audit report

Pipedrive

https://pipedrive.com · crm

warn
scanned 2026-04-16 23:37:00 utc permalink · /audit/pipedrive

Pipedrive loaded 9 third-party domain(s), of which 2 are privacy-sensitive. 1 warn finding(s): No privacy policy found. Privacy-sensitive vendors observed: FullStory, Optimizely.

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

    Optimizely loaded (ab_testing)

    Observed 3 time(s) on the page.

    
                inline: sBW47Ie', { integrations: { // Performance 'Optimizely Web': groups.includes('C0002'), 'Google Tag Manager':
    link preconnect: https://cdn.optimizely.com
              
    how we detected this →
  3. note

    FullStory loaded (session_replay)

    Observed 1 time(s) on the page.

    
                CSP: https://rs.eu1.fullstory.com
              
    how we detected this →

third parties observed


vendor domain category hits disclosure
FullStory fullstory.com session_replay 1 not named
Optimizely optimizely.com ab_testing 3 not named
* * other 1 not named
browser-intake-datadoghq.com browser-intake-datadoghq.com other 1 not named
cookielaw.org cookielaw.org other 1 not named
pipedriveassets.com pipedriveassets.com other 134 not named
teads.tv teads.tv other 3 not named
xingcdn.com xingcdn.com other 1 not named
yimg.com yimg.com 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://pipedrive.com from your own machine — the tool is MIT-licensed and runs locally.

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

source on GitHub · methodology · cli docs

provenance


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