Cookie Policy

As of 30 September 2026, the Knowledge site's own front-end code does not intentionally set advertising, behavioural-profiling, analytics, shopping-cart, login or marketing cookies. We therefore do not use a Knowledge-specific consent banner for non-essential cookies that the current front end does not set.

This statement is limited to code controlled by the Knowledge site. A browser, network layer, GitHub or a destination reached through an external link may operate under its own technical and privacy practices.

A cookie is a small value usually stored by the browser and sent with qualifying HTTP requests. Modern browsers also provide other storage mechanisms that do not behave like cookies. Knowledge currently uses non-cookie browser storage for reading preferences and offline operation.

The absence of first-party analytics cookies does not mean that no technical data is ever processed during page delivery; ordinary hosting and network requests can still generate logs as described in the Privacy Policy.

Knowledge article pages use browser localStorage to remember a user's selected article text size. The current key is acx-reading-size, and the stored value is the chosen font size within the supported range.

This preference remains on the device until it is changed, removed by the site, cleared by the user or removed by the browser. It is not used by the Knowledge front end as an advertising identifier.

The progressive web app registers a service worker and uses browser Cache Storage to keep core site files and some visited pages available faster or offline. The service worker may replace older cached versions when the site is updated.

Cache Storage is local browser data rather than a cookie. A cached copy can be older than the online page, so reconnect and refresh before relying on time-sensitive legal, safety or product information.

The Knowledge search feature loads a static search index and ranks results in the browser. Search phrases are handled in the active page and are not intentionally saved by the search feature to a cookie, localStorage or a dedicated Alle's ClinX search profile.

The downloaded search index itself may be cached by the browser or service worker as a site asset.

Browsers may independently maintain HTTP cache, history, installed-PWA metadata, permissions and other local records. Those browser-managed functions are distinct from cookies set by website code.

Installing Knowledge as a web app does not create a Knowledge account. Removing the app may not remove every cached item in every browser, so use the browser's site-data controls when you want a complete local reset.

When you follow a link to GitHub, allesclinx.com, a standards body, government website, social-sharing service, email provider or another third party, that destination may use cookies or other storage under its own policy.

Knowledge does not control a third party's cookie choices simply because a link appears in an article. Review the destination's notice before entering personal information or changing its consent settings.

Most modern browsers let you inspect and clear cookies, local storage, cached files and service-worker data for a specific site. Clearing Knowledge site data can reset your reading-size preference and remove offline copies.

Browser settings differ, so consult the browser or device help documentation for exact steps. Blocking all storage may reduce offline or preference features but should not prevent ordinary reading of the static site.

If Knowledge later introduces analytics, authentication, advertising, personalisation or another technology that materially changes browser storage, we will update this notice and introduce consent controls where applicable law requires them.

The date below identifies the current version and should be checked if your browser shows storage behaviour that differs from this description.