Skip to content
CookieTosser

What does protectmyapp.com track?

Before any consent, protectmyapp.com loaded 2 tracking companies and set 0 advertising or analytics cookies.

That's fewer tracking companies than most sites we scanned: 56% of the 2,450 sites we checked loaded more.

Scanned October 2, 2026 from Germany, loading protectmyapp.com once and clicking nothing. How we scan

Tracking companies
2
Tracking cookies
0
Third-party hosts
6
Cookies in total
2

Consent banner

No known consent management platform was detected on the page.

Companies contacted before consent

2 of the 3 companies it contacted before consent were analytics companies.

  • Adobe

    use.typekit.net, p.typekit.net

    8 requestsAnalytics
  • HubSpot

    forms.hsforms.com, forms-na1.hsforms.com, js.hsforms.net

    8 requestsAnalytics

Other third parties (content delivery, consent, functional, unclassified)

  • Weglot

    cdn.weglot.com

    1 requestFunctional

Cookies set before consent

CookiePurposeSet byLasts
__cf_bmFunctionalhsforms.net (third party)Under a day
__cf_bmFunctionalhsforms.com (third party)Under a day

The page also wrote 1 key to local storage, which works like a cookie but isn't sent with requests.

Understanding this page

  • How to see which cookies and trackers a website loads

    A hands-on walkthrough for checking what a site sets before you've clicked anything, using Chrome and Firefox's built-in tools, plus how CookieTosser automates the same check every month.

  • What counts as valid cookie consent in the EU

    The rules that actually govern cookie banners — the ePrivacy Directive, the GDPR consent standard, the Planet49 ruling, the strictly-necessary exemption, and what "reject" has to offer compared with "accept.

  • Consent management platforms explained

    What a CMP banner is actually doing behind the scenes, how the IAB's TCF standard and Google's Consent Mode v2 fit in, and why a banner being present is no guarantee that nothing loads before you answer it.