Cookies are small text files placed on your device when you visit a website. They are widely used to make websites function, remember your preferences, or track your activity across sites. This policy explains exactly what YourLabel LLC (“we”, “us”) stores in your browser and why.
For how we handle your personal data more broadly, see our Privacy Policy.
YourLabel uses a minimal, fixed set of cookies and browser storage — all of them strictly necessary to run the site or remember a preference you set yourself.
| Name | Purpose | Duration | Type |
|---|---|---|---|
sb-* | Supabase authentication session — keeps you signed in | Session / 7 days | Strictly necessary |
YL_LOCALE | Remembers your chosen dashboard language | 1 year | Functionality |
NEXT_LOCALE | Remembers your chosen language on the public site | 1 year | Functionality |
yl_cookie_consent | Remembers whether you accepted or rejected the cookie banner, so it doesn’t reappear on every visit | 1 year | Functionality |
When you first visit YourLabel, a dialog shows two categories — Necessary (locked on) and Analytics & Marketing (an off-by-default toggle) — plus three equally-weighted buttons: Deny, Allow selected, and Allow all. Deny and Allow all carry the same visual weight, so rejecting is exactly as easy as accepting; nothing is pre-checked for you. Your choice is stored in the yl_cookie_consent cookie described above and applies until you change it.
Necessary cookies— the ones in the table above that keep you signed in, run security checks, and remember your language — are outside the scope of this choice; there’s no toggle for them because the site cannot function without them. Under GDPR (ePrivacy Directive Art. 5(3), Recital 30) and equivalent laws elsewhere, cookies that are strictly necessary to provide the service you asked for don’t require consent. Denying the Analytics & Marketing category never blocks you from signing in or using YourLabel.
Measurement without cookies. We count how the site is used — device category, operating system, browser family, a two-letter country code, and for public pages the website or campaign tag that sent you — by reading headers your browser and our network provider already send, plus the referrer the browser reports. Nothing is written to or read from your device for it: no cookie, no localStorage, no identifier of any kind. That is why it is not a cookie and is not covered by the choice above. The results are coarse daily totals, never a profile of you. See the Privacy Policy for the legal basis and how to object.
You can change your choice at any time — reopen the banner from the Cookie Settings link in the footer of any page, or clear cookies from your browser (see Section 5 below) to see the banner again on your next visit.
Our login and registration forms use Google reCAPTCHAto block automated abuse. reCAPTCHA may set its own cookies while verifying you’re not a bot. This is a strictly necessary security measure — we do not control what Google stores, and you can review its policy at policies.google.com/privacy. Google is also listed as a processor in Privacy Policy Section 5.
We do not embed any other third-party trackers, ad networks, or social media widgets on the public site.
The easiest way to change your choice is the Cookie Settingslink in the footer of any page — it reopens the dialog described in Section 3, pre-filled with your last choice, so you can toggle Analytics & Marketing and pick Deny, Allow selected, or Allow all again.
Strictly necessary cookies can’t be rejected through the banner, because blocking them breaks core functionality (you won’t be able to stay signed in, and your language choice won’t be remembered). If you still want to clear or block them, you can do so from your browser settings:
If we ever introduce a cookie that is not strictly necessary (e.g. analytics or advertising), we will update this page and — where required — ask for your consent through the banner described in Section 3 before setting it. Bumping the version of the consent banner also re-prompts everyone who already made a choice, so an old “reject” can never silently cover a new category of cookie it never described. The version in force is always the one published at this address; the date above indicates the edition then published rather than the date of each individual change.