Cookie Policy

Cookies are small values stored or sent by a browser. Web applications can also use local storage and related browser mechanisms. These technologies can maintain a session, remember a local preference, protect a flow, or measure product use.

Pakkawork uses Supabase-based authentication. The authentication libraries may set one or more session or flow values whose names and lifetimes are controlled by the configured authentication environment. These values are needed to sign in, maintain a session, complete OAuth handoffs, and protect account access.

Blocking essential authentication storage can prevent sign-in or cause a session to end between page loads.

When you dismiss the browser-storage notice, Pakkawork stores a local value named 'pw_cookie_notice_dismissed'. It records that the notice was dismissed in that browser; it is not an authentication credential and is not used to follow you across other websites.

If a Pakkawork deployment is configured with a PostHog key, the site initialises PostHog to capture page-view and page-leave events and to create profiles for identified users only. Depending on the configured PostHog host and library behaviour, analytics may use cookies or similar browser storage.

If no analytics key is configured, Pakkawork does not initialise that analytics client. Requirements for notice or consent depend on the deployment, location, and applicable law.

The Pakkawork source does not configure advertising cookies or cross-site marketing pixels. Links to connected providers or external websites are governed by those services' own storage and privacy policies.

Browser controls can display, clear, or block cookies and site storage. Clearing storage may sign you out, reset the notice preference, or interrupt an OAuth flow.

Pakkawork may update this policy when authentication, analytics, or browser-storage behaviour changes. Questions can be sent to admin@pakkawork.com.