Cookies & Data Use
The short version of what we set, what we don't, and why you'll never see a consent banner here.
Why you don't see a cookie consent banner here
Cookie consent banners exist because most websites set cookies for advertising, analytics, retargeting, or third-party tracking — uses that the EU's ePrivacy Directive, the UK GDPR, and laws like California's CCPA say you have a right to decline.
Vinylaunch doesn't do any of that. The only cookies we set are the ones the platform literally cannot work without — the cookie that remembers you're signed in, the cookie that remembers which vendor account a multi-account user is currently acting as, and the security cookies set by Cloudflare and Stripe while you're actively using their parts of the checkout/signup flow.
Strictly-necessary cookies are exempt from consent requirements under every major privacy law. There's nothing to opt out of, because we've never opted you in to anything else.
When a company isn't moonlighting as a data broker, the toggles and banners aren't necessary. We'd rather lead with that fact than hide it behind dense legalese.
1. What we mean by “cookies”
A cookie is a small piece of text a website asks your browser to remember between page loads. Browsers also store similar small pieces of data via other mechanisms (local storage, session storage). Cookie law in most countries treats these interchangeably; this page does too.
Cookies come in two practical categories: strictly necessary(the site does not function without them — for example, the cookie that remembers you're signed in) and everything else (analytics, advertising, tracking, personalization, social-network embeds, retargeting pixels, and so on).
Vinylaunch uses only the first category. There is no second category to opt out of. That is why you will never see a consent banner on this site.
2. Every cookie we set, and why
The complete inventory. Add this up and you have the entire cookie footprint of using Vinylaunch.
- CookieSupabase auth sessionSet byVinylaunch (via Supabase)PurposeRemembers that you are signed in so you don’t have to re-enter your password on every page.LifetimeSession + refresh; cleared on sign-out.
- CookieVendor team operating contextSet byVinylaunchPurposeFor users invited to multiple vendor accounts, remembers which account you are currently acting as.Lifetime14 days, refreshes when you switch contexts.
- CookieCloudflare Turnstile challengeSet byCloudflare (during signup only)PurposeConfirms that the signup attempt is from a real person, not an automated script.LifetimeSet only during a signup attempt; cleared automatically.
- CookieStripe Checkout sessionSet byStripe (on stripe.com, during payment only)PurposeHolds your payment session while you complete a transaction on Stripe’s hosted checkout page.LifetimeSet only during checkout on stripe.com; never set on vinylaunch.com.
Two of those are set by services we partner with (Cloudflare and Stripe) and only while you are actively using the security challenge or payment flow they exist to protect. They are not set on every page; they are not set on the marketing pages you read before you sign up; and they are not used to track you across sessions or across other sites.
3. What we do not do
Because some absences matter as much as what is present, here is the explicit list of common practices Vinylaunch does not use:
- ✓No Google Analytics, no Facebook Pixel, no Microsoft Clarity, no Hotjar, no third-party analytics of any kind.
- ✓No advertising cookies. No remarketing or retargeting pixels.
- ✓No social-network share/like buttons that load tracker cookies.
- ✓No data brokers. No selling, renting, sharing, or licensing of your personal information for marketing purposes.
- ✓No behavioral profiling. We do not build advertising profiles of who you are or what you might buy.
- ✓No cross-site tracking. Once you close the tab, the platform forgets you in any context that is not strictly your authenticated session.
This is by design and by mission, not by oversight. The platform makes money from clear, declared things: subscriptions, a single-digit platform fee on transactions that move through it, and (eventually) advertising revenue that flows to the artists and creators whose content the ads appeared with. Data brokering is not on that list and never will be.
4. Data use — the short version
The same principle applies to the rest of your data, not just the cookie bits. We collect what we need to run your account — email, password (one-way hashed), display name, role, the content you upload, the campaigns and pledges and bids you participate in, and the financial identifiers Stripe issues so we can attribute payments correctly. We do not collect more than that, and we do not use what we do collect for purposes other than running the platform you signed up for.
The full inventory of what we collect, how we use it, who processes it on our behalf, how long we keep it, and your rights to access, correct, export, or delete it lives in our Privacy Policy. That is the legally operative document. This page is the plain-language summary of the cookies and data philosophy behind it.
5. Your rights — at a glance
You can edit your profile, delete content you've uploaded, and cancel your subscription at any time. For a full data export or account deletion, email info@vinylaunch.com and we will respond within 7 business days. California, EU, and UK residents have specific additional rights documented in Privacy Policy § 6, all of which we honor.
6. Why we made this a separate page
Most people have been trained by years of intrusive consent banners to associate the word cookies with something I'm supposed to be worried about. The honest answer in Vinylaunch's case is that you don't need to be worried — because we don't use the kind of cookies the banners were invented to disclose. But you shouldn't have to take that on faith. This page exists so you can verify it directly, in plain language, with the full inventory in front of you.
We'd rather over-explain the absence of something than have you assume it must be hiding somewhere.
Effective date: May 24, 2026