Cookie Policy

1. The short version

The public website sets no cookies. The dashboard sets two strictly necessary cookies so Sign in with Discord works. There are no analytics, advertising or tracking cookies anywhere, which is why you do not see a cookie banner: the law does not require consent for cookies a service cannot work without.

2. Cookies we set

• tl_session — keeps you signed in to the dashboard. Set when you sign in with Discord, on our domain only, HttpOnly and Secure. Expires after 15 days or when you sign out. Strictly necessary.
• tl_state — a one-time security token that protects the sign-in handshake against forgery. Lives about ten minutes, then is discarded. Strictly necessary.

3. Browser storage

The dashboard remembers one preference in your browser's local storage: whether you dismissed the Pro announcement (tl_ann_pro_v1). It identifies nothing about you and never leaves your browser. The docs remember nothing.

4. Third parties you may meet

• Discord — signing in happens on discord.com, under Discord's policies.
• Stripe — checkout and the billing portal run on Stripe's pages (checkout.stripe.com, billing.stripe.com). Stripe sets its own cookies there for payment security and fraud prevention, covered by Stripe's Cookie Policy. We do not load Stripe scripts on our pages.
• Cloudflare — our host may set strictly necessary bot-protection cookies to keep the site online, covered by Cloudflare's privacy policy.
• Links out — when you follow a link to another site, that site's cookie policy applies.

5. Managing cookies

Your browser lets you view and delete cookies at any time. Deleting tl_session signs you out of the dashboard; nothing else changes. Because we set no optional cookies, there is nothing to opt out of.

6. Changes

If Ticket Lab ever needs a cookie that is not strictly necessary, this page will say exactly what it is and why, and we will ask for your consent first.

7. Contact

dominic.s@buildablelabs.dev · Buildable Labs community on Discord · buildablelabs.dev.