Effective: 25 September 2026

Cookie Policy

This policy explains how Binary Brain Technologies sp. z o.o. uses cookies and similar browser storage on www.worklog.click.

1.In short

WorkLog uses only what it needs to work: cookies that keep you signed in and remember your Workspace, and one local storage entry for your theme. There are no analytics, advertising, social-media or other third-party tracking cookies, on the website or in the app.

2.What cookies are

Cookies are small text files a website stores in your browser and receives back on later visits. Local storage is a similar browser feature that keeps data on your device without sending it to the server.

3.What WorkLog uses

Name	Type	Purpose	Lifetime
`__Secure-neon-auth.session_token`	Cookie, first party, HTTP-only, secure	Keeps you signed in. Set by Neon Auth, our sign-in provider.	Until you sign out or the session expires
`__Secure-neon-auth.local.session_data`	Cookie, first party, HTTP-only, secure	A signed, short-lived copy of your session so pages load without asking the sign-in service each time.	Minutes; renewed while you use WorkLog
`__Secure-neon-auth.session_challenge`	Cookie, first party, HTTP-only, secure	Protects a Google or GitHub sign-in in progress against forgery.	Only during that sign-in
`worklog_ws`	Cookie, first party, HTTP-only	Remembers which Workspace you had open.	1 year, or until you sign out
`worklog-theme`	Local storage, never sent to the server	Remembers a light or dark theme choice. Absent when the theme follows your system.	Until you choose “System” or clear site data

HTTP-only cookies cannot be read by scripts in the page; secure cookies are sent only over HTTPS. None of them is used to recognise you across other websites.

4.Why no consent banner

The law (Article 5(3) of the ePrivacy Directive, implemented in Poland by the Electronic Communications Law) requires consent for storing information on your device, except where it is strictly necessary to provide a service you asked for. Everything listed above falls within that exception: without it you could not sign in or keep your settings. If we ever want to use anything that is not strictly necessary, we will ask for your consent first and this policy will be updated.

The personal data involved (for example the session identifier) is processed as described in the Privacy Policy.

5.Third parties

Signing in with Google or GitHub takes you to that provider’s own pages, where their cookie policies apply. WorkLog does not embed third-party content, fonts or scripts that set cookies.

6.Controlling cookies

You can see and delete cookies and site data in your browser settings.
Blocking or deleting the sign-in cookies signs you out, and WorkLog cannot be used without them.
Signing out removes the sign-in cookies and the Workspace cookie.

7.Changes and contact

We update this policy when what we store changes; the date at the top shows the current version. Questions: support@worklog.click. Also available in Polish.