Clerk Cookies
Cookies play a vital role in authentication, state management, and browser-server communication. By understanding their attributes, developers can ensure secure and efficient use in their applications. Clerk leverages cookies in a secure, privacy-compliant manner to facilitate seamless user authentication across domains and subdomains. To learn more about cookies, like what they are and how they work, see the resource guide on cookies.
Strictly necessary application cookies
Clerk sets cookies when your users interact with your application in ways that trigger requests for services, such as signing in or signing up. This cannot be disabled.
These cookies:
- Are required for Clerk to function, and should not be blocked by you or your users.
- Do not store any personally identifiable information by default.
- Can be configured by modifying the session token in the Clerk Dashboard.
Cookie Subgroup | Cookies | More Information |
---|---|---|
.clerk.com | __session , __client_uat | First party |
.clerk.com, .dashboard.clerk.com (cloudflare) | _cfuvid | Third party Cloudflare Cookies |
Feedback
Last updated on