Short version: this site sets no cookies of its own. My host, Cloudflare, may set one or two for bot protection, and the Discord widget on a couple of pages can set Discord's. No analytics, no ads, no tracking pixels.
__cf_bm: may be set by Cloudflare's bot protection to tell humans from automated traffic. Expires about 30 minutes after your last request. Not tied to any account or identity.cf_clearance: set only if Cloudflare makes you pass a human check (rare). Lasts up to 30 days. Also not tied to any account.
Neither is used for advertising, cross-site tracking, or analytics. They exist so bots can't hammer the site.
The homepage and the AudioScape page embed Discord's official server widget, which loads from discord.com. Discord can set its own cookies inside it (such as __dcfduid,__sdcfduid, and _cfuvid) for security and to run its service. Those are Discord's cookies underDiscord's privacy policy, and I can't read them. Blocking third-party cookies stops them and the rest of the site works the same.
No Google Analytics, no Meta Pixel, no ad-network cookies, no A/B testing tools, no session replay. If any of that ever changes, this page changes first.
Backline (jayslays.tech/backline) sets its own cookies for login sessions and Stripe checkout. Those are covered in Backline's cookie policy, not here. This page is only about the marketing site.
Every modern browser lets you block or clear cookies per site in its privacy settings. Blocking any of these is fine. The site still works, bots may just get through more often.
Questions:contact@jayslays.tech.