Cookie Policy

Last Updated: 25 August 2026

1. What Are Cookies

Cookies are small text files stored on your device by your web browser when you visit a website. They help the website remember information about your visit, such as your preferences and login state. Carverse uses cookies and similar browser storage mechanisms (sessionStorage, localStorage) to provide and improve our services.

2. How We Use Cookies

We use cookies and browser storage for the following purposes:

  • Essential functionality: Keeping you logged in and maintaining your session state across page reloads.
  • Analytics: Understanding how users interact with our platform to improve features and user experience.
  • Error monitoring: Tracking JavaScript errors and performance issues to debug and stabilize the platform.
  • Preferences: Remembering your theme choice and role selection so you don't have to re-set them each visit.

3. Types of Cookies We Use

Cookie TypeProviderPurposeStorageDuration
Essential CookiesSupabaseAuthentication tokens (access token, refresh token) required for login and session managementsessionStorageSession (cleared on tab close)
Analytics CookiesPostHog, Google AnalyticsTracks page views, user events, feature usage, and custom events for product improvementCookies + localStorageUp to 13 months
Error MonitoringSentryCaptures JavaScript errors, stack traces, and browser metadata for debugging and platform stabilityCookiesSession
Preference CookiesCarverseStores theme preference (dark/light) and role selection (owner/provider)localStoragePersistent until cleared

4. Third-Party Cookies

Some cookies are set by third-party services integrated into our platform:

  • PostHog: Product analytics service that helps us understand user behavior. PostHog sets cookies to track sessions and user events. Data is processed in the European Union.
  • Google Analytics: Website traffic analysis service. It sets the _ga and _ga_* cookies to record page views and events, and only loads after you accept analytics cookies. Data is processed on Google servers globally.
  • Sentry: Error monitoring service that captures JavaScript errors and performance data. Sentry may set cookies for session tracking. Data is processed in EU/US.
  • Google Maps: When you use the nearby garage search feature, Google may set cookies to manage map interactions and place searches. Data is processed on Google servers globally.

We do not control the cookie practices of these third-party services. Please refer to their respective privacy policies for more information on how they use cookies.

5. How to Manage Cookies

You can control and manage cookies through the following methods:

  • Browser settings: Most browsers allow you to block or delete cookies. Check your browser's help section for instructions (Chrome, Firefox, Safari, Edge).
  • Clear sessionStorage: Open your browser's Developer Tools (F12) → Application tab → Session Storage → delete entries for carverse.in.
  • Clear localStorage: Open Developer Tools → Application tab → Local Storage → delete entries for carverse.in to remove preference and analytics data.
  • Incognito/Private mode: Browse in incognito or private mode to prevent cookies from being stored after you close the window.

6. Impact of Disabling Cookies

If you choose to block or disable cookies, some features may not function correctly:

  • Login will not work: Essential cookies in sessionStorage are required for Supabase authentication. Without them, you cannot log in or maintain a session.
  • Analytics will be disabled: PostHog and Google Analytics tracking will be blocked, and we will not collect usage data from your session.
  • Preferences will reset: Your theme and role selections will not persist across sessions.
  • Core features may still work: Browsing public pages and viewing content may still function, but authenticated features will be unavailable.

7. Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in our practices or applicable laws. We will notify you of material changes through:

  • In-app notification
  • Email to the address associated with your account

The "Last Updated" date at the top of this page indicates when this policy was last revised.

Version History:
Version 1.0 — 25 August 2026 — Initial release