01
Cookies are small values stored by a browser. Similar technologies, including local storage, can remember information on a device. This policy explains how JobClock uses both.
02
JobClock uses Supabase authentication cookies to maintain your signed-in session, refresh access securely, and protect account-only pages. Their names may vary by Supabase project and token format. These cookies are necessary for the account service you request and expire or rotate in line with the authentication session.
03
The job-assistant-theme preference is stored in a cookie and local storage so JobClock can remember light or dark appearance. The cookie lasts up to one year unless you remove it sooner.
JobClock may also use local storage for interface preferences such as sidebar state or analytics-view layout. These values stay on your device until the application or you remove them. They are not used for advertising or cross-site tracking.
04
JobClock uses Vercel Web Analytics to understand aggregate page usage. Vercel states that this service does not use cookies and identifies a visitor using a daily-changing hash rather than a persistent personal identifier. JobClock does not configure analytics events to include CV content, provider keys, extension tokens, or other workspace data.
05
JobClock currently does not set advertising cookies or non-essential analytics cookies, so it does not display a cookie-consent banner. If non-essential storage is introduced, JobClock will request consent before using it where required.
You can inspect or remove cookies and local storage through your browser settings. Blocking authentication cookies will prevent sign-in and account features, while removing preference storage will reset the related interface choices.
06
Questions can be sent to support@jobclock.michaelogunjimi.com. This policy will be updated if JobClock changes the browser storage or analytics technologies it uses.