1. What are cookies
Cookies are small text files stored on your device when you visit a website or use an online service. Similar technologies include local storage, session storage, pixels, and security tokens. These technologies allow the website to remember your actions and preferences over a period of time.
2. Cookie categories
Kuluara uses cookies in the following categories. We describe each category, the specific cookies used, their purposes, and their durations below.
2.1 Strictly Necessary cookies
These cookies are essential for the operation of the Kuluara platform. They enable core functionality such as authentication, session management, and security. Without these cookies, the platform cannot function properly. These cookies cannot be disabled.
| Cookie name | Provider | Purpose | Duration |
|---|---|---|---|
| sb-*-auth-token | Supabase | Stores the authenticated user session token. Used to maintain login state and authorize API requests to the Supabase backend. | Session / 7 days (configurable) |
| sb-*-auth-token-code-verifier | Supabase | PKCE code verifier used during the OAuth authentication flow to prevent authorization code interception attacks. | Session |
| __next_hmr_refresh_hash__ | Next.js | Used in development environments only for hot module replacement. Not present in production builds. | Session (development only) |
| __Secure-next-auth.session-token | Next.js | Secure session token for authenticated sessions. Used when NextAuth.js session management is enabled. | Session / 30 days |
2.2 Functional cookies
Functional cookies enable enhanced functionality and personalization, such as remembering user interface preferences, language settings, or display configurations. They do not track browsing activity across other websites.
| Cookie name | Provider | Purpose | Duration |
|---|---|---|---|
| theme | Kuluara | Stores the user's preferred color theme (light/dark) for the platform interface. | 1 year |
| sidebar-collapsed | Kuluara | Remembers whether the navigation sidebar is in collapsed or expanded state. | 1 year |
2.3 Analytics cookies
As of the effective date of this policy, Kuluara does not use third-party analytics cookies or tracking pixels. We do not use Google Analytics, Facebook Pixel, or similar third-party tracking services.
If we introduce analytics cookies in the future, this Cookie Policy will be updated accordingly, and where required by law, we will obtain your consent before setting such cookies.
| Cookie name | Provider | Purpose | Duration |
|---|---|---|---|
| No analytics cookies are currently in use. | |||
3. Third-party technologies
When you use integrations or embedded services within Kuluara, third-party providers may set or process their own cookies or related identifiers. These are governed by the respective third party's cookie and privacy policies:
- Supabase — Authentication and session management cookies as listed above. See Supabase Privacy Policy.
- Vercel — May set cookies related to edge network routing and performance optimization. See Vercel Privacy Policy.
4. How to manage cookies
You can manage cookies through your browser settings. Most browsers allow you to:
- View which cookies are set and delete individual cookies.
- Block third-party cookies.
- Block cookies from specific sites.
- Block all cookies.
- Delete all cookies when you close the browser.
Please note that disabling Strictly Necessary cookies (particularly authentication cookies) will prevent you from logging in to and using the Kuluara platform.
Common browser cookie settings:
5. Relationship to Privacy Policy
This Cookie Policy is supplementary to our Privacy Policy, which provides comprehensive information about how we collect, use, store, and protect personal data. For information about your rights regarding personal data, data retention, and how to contact our Data Protection Officer, please refer to the Privacy Policy.
6. Updates
We may update this Cookie Policy from time to time to reflect changes in the cookies we use, technology, or legal requirements. Material changes will be posted on this page with an updated effective date.