Cookie policy

LockIn sets cookies for two purposes: keeping you signed in, and remembering which section’s timetable you asked to see. There are no analytics cookies, no advertising cookies and no third-party trackers, which is why you are not being asked to accept anything. The product carries no analytics service, no session recording and no error-reporting service, so there is nothing here for a consent banner to ask about.

• Authentication cookies issued by Supabase, which hold your session so the server can confirm on each request that it is really you.
• Two small preference cookies recording the programme, intake and section whose timetable you chose to view. They are set only when you make that choice, hold nothing but the labels shown in the picker, and are used only to draw the timetable screen.

The authentication cookies are strictly necessary. Blocking them does not degrade LockIn, it signs you out: there is no version of the product that works without knowing whose coursework to show.

The timetable cookies are not necessary in that sense. Blocking or clearing them costs you nothing except being asked which section you are in again. They do not affect which coursework LockIn treats as yours, and they are never used to identify you.

Two small values are kept in your browser’s local storage rather than in a cookie: your choice of light or dark theme, and the time of the last automatic refresh, which stops LockIn from starting a new sync every time you move between screens.

Neither is sent to the server and neither identifies you. Clearing site data removes both; the theme returns to following your system setting and the next screen you open may refresh once.

Your browser can block or clear cookies for this site at any time. Doing so signs you out. It does not delete your data, which is removed by deleting your account in Settings.

Questions go to contact@lockinapp.tech.