Cookies

SupplierSpy sets zero cookies by default.

No analytics cookies. No tracking cookies. No advertising cookies. No session cookies (there are no user accounts). Come to the site, read the benchmark, leave — your browser storage stays empty.

Last updated: 2026-04-17

What we don't set

  • No analytics cookies. No Google Analytics, Plausible, Fathom, Matomo, Segment, or anything equivalent.
  • No trackers. No Meta Pixel, no LinkedIn Insight Tag, no TikTok Pixel.
  • No ad-tech. No ad networks means no ad-network cookies.
  • No session cookies. There is no login on SupplierSpy, so there is nothing to remember about a session.
  • No first-party tracking. We do not set any identifier that would let us stitch two visits by the same browser into one profile.

The one optional cookie

Exactly one cookie may be set — only after you explicitly click the Lite / Pro view toggle in the header:

NamePurposePartyLifetimeSameSitePII
ssp_view Remembers your preferred reading density (lite or pro). First-party (supplierspy.com) 30 days Lax None

You can delete this cookie at any time from your browser settings. Removing it simply resets you to the default Lite view — nothing else changes.

GDPR & ePrivacy — why there's no consent banner

We do not display a cookie banner because no tracking cookies are set without your action. The only cookie that can be set — ssp_view — is set only after an explicit click on the Lite/Pro toggle. That click is itself the request for a preference to be remembered.

Under the ePrivacy Directive (2002/58/EC, amended by 2009/136/EC), cookies that are strictly necessary for a service explicitly requested by the user do not require prior consent. The ssp_view cookie meets this carve-out: it stores nothing more than the preference the user just expressed by clicking the toggle.

Under the GDPR, no lawful-basis analysis is required for tracking processing we do not perform. If that changes — for example if we ever introduce analytics — we will add a genuine consent mechanism and update this page.

Cloudflare's own cookies

Our hosting provider, Cloudflare, may set its own bot-defence cookie (__cf_bm) on some requests. This is controlled by Cloudflare, not by us. It is strictly a bot-challenge mechanism — not an advertising or analytics cookie. See Cloudflare's cookie policy for details.

See also

/privacy · /terms · /imprint · /trust · /contact.