Only what the product needs to operate.
Funl does not need an advertising-cookie layer for its current public website. Protected access and customer analytics use narrowly scoped mechanisms for their specific jobs.
Last updated 4 October 2026Public marketing pages
The current Funl marketing pages do not implement advertising or behavioural-targeting cookies. Standard hosting and network infrastructure may still process ordinary request metadata required to deliver the site.
Protected application sessions
When 1App integration is enabled, Funl uses short-lived authentication transaction state during sign-in and an opaque Funl application-session cookie after authorised access is established. Provider access and refresh tokens are designed to remain server-side rather than being written to browser storage.
Analytics on customer properties
The Funl tracker uses pseudonymous analytics identifiers and visit semantics to calculate journeys and conversion evidence. It is designed to respect Do Not Track. The exact storage behaviour on a customer property depends on the tracker version and the customer configuration deployed there.
Managing browser storage
You can control cookies and local browser storage through your browser settings. Blocking strictly necessary sign-in or session mechanisms may prevent protected Funl areas from working.