CrackLab

Cookie Policy

We keep cookie usage minimal and purposeful. Here's exactly what we use and why.

Last updated: May 24, 2026v1.0Not legal advice — consult a qualified lawyer for your jurisdiction
1.

What Are Cookies?

Cookies are small text files that websites store on your device when you visit them. They are widely used to make websites work, to remember your preferences, and to give site owners information about how the site is being used.

Cookies are not programs — they cannot carry viruses or install malware. They are simply data stored in your browser.

2.

Summary: Cookies We Use

CrackLab uses a minimal number of cookies. We do not use advertising cookies, tracking pixels, or cross-site trackers. The majority of our cookies are set by Clerk (our authentication provider) and are essential for the platform to function.
  • Essential authentication cookies — set by Clerk (cannot be disabled).
  • Session state cookies — keep you logged in during your browser session.
  • UI preference cookies — remember dark mode or layout preferences.
  • Anonymized analytics — optional, no personal identifiers collected.
3.

Essential Cookies

These cookies are strictly necessary for the platform to function. Without them, you cannot log in, access your dashboard, or use any authenticated features. They cannot be disabled.

CookieProviderPurposeExpiry
__clerk_*ClerkAuthentication session managementSession
__sessionClerkMaintain logged-in stateSession
__client_uatClerkUser active timestamp for session validity30 days
4.

Functional Cookies

These cookies remember your preferences to improve your experience. They are not essential, but disabling them means the platform may not remember your settings between visits.

  • Theme preference (dark/light mode) — stored in localStorage, not a cookie.
  • Last-visited roadmap — helps the platform open where you left off.
  • UI collapse state — remembers which sidebar sections you have expanded.

Most of these preferences are stored in browser localStorage rather than cookies, which means they are local to your device and never transmitted to our servers.

5.

Analytics

We may use anonymized analytics to understand how features are being used, which pages are most visited, and where users encounter problems. Any analytics data collected:

  • Does not contain your name, email, or any personally identifiable information.
  • Is aggregated — we see trends, not individual user sessions.
  • Is used only to improve platform features and fix issues.
  • Is not sold or shared with advertisers.

If we add a third-party analytics tool in the future, we will update this policy and add it to our third-party services list.

6.

Third-Party Cookies

Third-party services we use may set their own cookies. We do not control these cookies and they are governed by each provider's privacy policy.

  • Clerk (auth.clerk.com) — authentication cookies. See Clerk's Privacy Policy.
  • Stripe — payment session cookies (only on checkout pages). See Stripe's Privacy Policy.
  • Sentry — error tracking may use session identifiers. See Sentry's Privacy Policy.

We do not use Google Analytics, Facebook Pixel, or any advertising or retargeting cookies.

7.

Managing Cookies

You can control and manage cookies in your browser settings. Most browsers allow you to refuse cookies, delete existing cookies, or be notified when cookies are set.

  • Chrome: Settings → Privacy and Security → Cookies
  • Firefox: Settings → Privacy & Security → Cookies and Site Data
  • Safari: Preferences → Privacy → Manage Website Data
  • Edge: Settings → Cookies and Site Permissions → Cookies
Disabling essential cookies (Clerk authentication cookies) will prevent you from logging in to CrackLab. The platform requires these cookies to function.
8.

Do Not Track

Some browsers offer a "Do Not Track" (DNT) signal. CrackLab currently does not respond to DNT signals because we do not engage in cross-site behavioral tracking regardless of whether a DNT signal is present.

9.

Changes to This Policy

We will update this Cookie Policy if we add new cookies or change our approach to tracking. Material changes will be communicated via the in-app notification system or email. The "Last updated" date at the top reflects the most recent revision.

10.

Contact

Cookie or tracking questions?

  • Email: privacy@cracklab.dev
  • Subject: Cookie Policy
  • Response time: 3 business days